Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Issue #DeliverableComments
2794Hybrid Multi-Cloud

Updates to:

  • multi-cloud summary table and examples (PR#2676) wiki  , PR#2824
  • storage for multi-cloud (Issue#2578) - contents both in Storage and Multi Cloud sections, will be cross-referenced
  • hybrid / multi-cloud security and regulatory (Issue #2804), address the gaps in Sec 8.2.8 (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
  • single pane requirements (a minimum set) (Issue #2797), Chapter 8 in the new Requirements section 
2793Security 

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
  • 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
2795Storage

Updates to storage:  

  • Storage principles (Issue#2666) - propose placement of contents wStorage for multi-cloud (Issue#2578) - contents in Multicloud section
  •  Storage for multi-cloud (Issue#2578) - contents both in Storage and Multi Cloud sections, will be cross-referenced
  • Storage scenarios (Issue#2747) - propose placement of contents, currently focused
2087Infrastructure LCM Automation (revised title)
  • Infrastructure LCM Automation Introduction (Issue#2816) - PR#2851
  • 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
2785General PaaS ServicesSection 5.1.5 lists a set of General PaaS Services. We need to will specify requirements for each of these services -- an issue will be opened for each service.










































...