Page Comparison

Updates to:

• multiMulti-cloud interaction summary table and examples examples  (PR#2676Issue#2806 CLOSED)  wiki-  , PR#2824
• storage for multi-cloud (Issue#2578) - contents both in Storage and Multi Cloud sections, will be cross-referenced
• hybrid - approved and merged, closing umbrella  Issue#2794. Chapter 8, Section 8.5.3 "Requirements, Reference Architecture & Industry Standards Intersect"
• single

  Hybrid / multi-cloud security and regulatory (Issue #2804 BACKLOG), address the gaps in  reviewed  Sec 8.25.8 (5 "Aspects of Multi-Cloud Security), and update Requirements in Sec 7, (references in RAs are from Chapter 7). 

• APIs (Issue#2812), to be done in Chapter 6 - alignment will be necessary, reference in RAs are from Chapter 6

• ", and Requirements in Sec 7, no gaps found, review to be continued post Moselle

• Single pane requirements (a minimum set) (Issue #2797 CLOSED), Chapter 8 in the new Requirements section section 8.5.4 - PR#2902; approved and merged

Developments on:

• SBOM, alignment with LFN security forum in Chapter 7; will need to be understood in the context of overall Software Supply Chain and considered from both open source and vendor software (Issue#2838)
• Security for hybrid and multi-cloud,) Issue#2840
• Regulatory directives for cybersecurity, issue#2839

  Software supply chain security (Issue#2838 CLOSED) - PR#2913 approved and merged into a new section 7.7 'Software Supply Chain Security"

• Regulatory directives for cybersecurity (Issue#2839 CLOSED) - PR#2981 approved and merged into a new section 7.9 "Cloud Regulatory Compliance"

• SBOM content added  - PR#2978 approved and merged into section 7.7.3 "Software Bill of Material (SBOM) Security"

• Add reference to FS.40 v2 which is now a non binding PRD and must be added, issue#2828

• Restructure and update section about common security standards, issue #2841

• Both "Monitoring for security" and "Security of monitoring" aspects are included in Table 7-7 for further review

• Issue #2828 (CLOSED); PR#2982 approved and merged

• Infrastructure LCM Automation Introduction (Issue#2816 CLOSED) - PR#2851 merged into Section 9.5.2 "Infrastructure LCM Automation Framework (Issue#2848) - Create a high level framework identifying different layers and different actors in the Infrastructure LCM Automation"
• Infrastructure LCM Automation Principles (Issue#2849) - Create principles for Infrastructure LCM Automation to govern best practices. Need to be on high level because of different specificity of operations in different telecoms.
• Infrastructure LCM Automation Best Practice (Issue#2850) - Develop high level best practice guidance for Infrastructure LCM Automation

•  final update includes Introduction, Framework, Best Practice, Principles  (Issues#2816,2848, 2849, 2850 - CLOSED) - PR#2929 merged  into Section 9.5.2 "Infrastructure LCM Automation"

• Load Balancer Requirements, (Issue 2906 CLOSED), PR#2907 approved and merged into Section 5.1.5.1 "Platform Services - Load Balancer Requirements"
• Logging, (Issue #2960 CLOSED), PR#2961 -  approved and merged into Section 5.1.5.2 "Platform Services - Log Management Services (LMS)"
• Monitoring (Issue #2957 CLOSED), PR#2958  approved and merged into Section 5.1.5.3 "Platform Services - Monitoring Service Requirement"

• Should we flesh out the specs for infrastructure monitoring from ETSI GS NFV-TST 008 V3.5.1  (question form RA-2); PR#2983 Internal Performance Metrics approved and merged into Section 4.1.3.3 "Internal Performance Measurement Capabilities"