Cloud RAN commercial instructions v2.pptx

Cloud RAN commercial instructions v2.pptx

1. Cloud RAN Commercial Readiness: Teams and Confluence usage information Kirsi Ellilä 23.2.2024 v1.0 Terhi Kiskonen 3.4.2024 v.2.0

2. Introduction This documents contain information about Teams and Confluence usage in testing camps. Purpose of these tools is to ease up the camp control and follow up in daily work. These tools should be used commonly in all streams to get the best results for overall success. Teams usage and Issue handling, l ink: Cloud RAN Commercial readiness Teams In General folder all needed common information like documents, links etc can be shared. Also Notes links, powerpoints , excels and such can be shared in Teams. Main task for this Teams is the Issue handling. Issues will be created as own channels under this Teams. Channel should be the only place to discuss and investigate this particular issue and only one issue per channel. Pre-screening channel established (limited # of members) if need to ask e.g. how something is working? is this known issue? who should investigate?  Confluence for camps and test lines: https://confluence.ext.net.nokia.com/display/CloudInfra/Cloud+RAN+commercial+readiness Every Stream should create own “Camp” page using template. All testlines need to be added to confluence under Test Line folder : Link

3. Teams channels Pre-screening channel to ask questions from R&D General Bootcamp materials and instructions Issue handling & discussion in channels

4. Teams usage

5. Teams usage and Issue handling Common Teams for Cloud RAN Commercial readiness has been created. Link: Cloud RAN Commercial readiness Teams Anyone in Nokia can join the Teams via this link. Also Owners can add any member who is needed into this Teams. In General folder all needed common information like documents, links etc can be shared. Also Notes links, powerpoints , excels and such can be shared in Teams. Main task for this Teams is the Issue handling. Issues will be created as own channels under this Teams. Channel should be the only place to discuss and investigate this particular issue and only one issue per channel. For Clarity the Issue creation need to be agreed from the naming pov . To separate Issues made from different streams the used prefixes will be: NETWM – Network Management AUTOM - Automation (CNF Automation, Cloud Infra Automation) SEOPR - Serviceability & Operability TRBLS - Troubleshooting CAPER - Capacity & Performance SECVL - Security & Vulnerability AVLRB - High Availability & robustness INUPG - Installation & Upgrade

6. Teams usage and Issue handling Common Teams for Cloud RAN Commercial readiness now contains example Issues for each streams: These examples needs to be replaced by real items by each stream when starting. Channels are created from 3 dots seen above picture by “Add Channel”. Template is recommended to be used when creating new channel: Link to template First Automation channel has template include d: Link to channel All Preinvestigation will be done under the channel and if Pronto will be created about the issue the Channel name will be updated to correspond the Pronto number. When agreed to close the issue channel can be closed by adding agreed closed tag e.g. [CL] in the beginning .

7. Teams usage and Issue handling As Team is common for all streams it is easy to check what kind of issue are found already in different streams. And if needed also contribution can be given from other streams to all issue when suitable. Issues will be followed up daily. It is camp leads responsibility to make sure that discussion and investigation is ongoing and relevant people are aware about ongoing activities.

8. Confluence for camps and test lines

9. Confluence for Camp/Stream information Confluence page has been created: https://confluence.ext.net.nokia.com/display/CloudInfra/Cloud+RAN+commercial+readiness Every Stream should create own “Camp” page using template. You can check examples from e.g. ASOG L3 camp

10. Confluence for Testline usage All testlines need to be added to confluence under Test Line folder : Link Test Line template to be used for creation. Daily status need to be fulfilled by tester on daily basis.

11. Other information Bootcamp introduction Pronto tagging instructions

12. Bootcamp Setup Confidential Network Management & Management System with Automation Sponsor: Merja Hemmi, Responsible: Markku Lukkarinen, Architect: Damian Nowak, PDM: Eric Desorbay (Automation), Sami Jalonen (NM) Full testing of the Management System (NEAT, NADCM, MantaRay ) Empty room deployments with full automation like customer would do including HW, eSW , OCP, vCU and vDU installations. Operability, UUF, HA+Robustness & Logging-Troubleshooting Sponsor: Bindhya Tiwari, Responsible: Atul Pala, Architect: Tuomas Niemelä , Visagan Soundaram, PDM: Marcin Lipa RAN-NIC + h/w + eSW + BIOS + Drivers & linked areas (like RN-NIC s/w controller, sync-operator) Operability + UUF (Deployment + Upgrade + Rollback + Back-up-Restore + Scaling + FCAPS) + Operational KPIs High Availability & robustness (redundancy & failure recovery mechanisms) Monitoring Overall logging & troubleshooting. Specific focus to lower levels (RAN-NIC, NADCM & etc.) Capacity & Performance Sponsor: Hannu Tammi, Lead: Timo Komulainen, Architect: Tuomas Niemelä , Mikko Ollanketo, PDM: Marko M. Virtanen Benchmarking of Application & Cloud Infra with LOAD Security Sponsor: Soma Sarkar, Responsible: Enping Wu, Architect: Thierry Pernot, PDM: Risto Harju Application Infra Solution (i.e., h/w, CaaS & Management System) Owner: Soma Sarkar Camp Leader: Suvi Pukkila , Technical Leader: Tuomas Niemela Mentor: Juha Pekka Karjalainen PDM: Jaska Sainio, NPI: Wolfgang Ulrich, Program: Veerendra Gangwar