Updates to:

• multi-cloud summary table and examples (PR#2676) wiki  , PR#2824
• storage for multi-cloud (Issue#2578), storage sections are under review by John Hartley

• 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).  Plan proposed:

  • Create general section in Chapter 7 (Security) on overall regulatory high level directions (Issue#2839)
  • In Sec 8.2.8 (Aspects of Multi-Cloud Security) refer to relevant portions of this general section on regulatory matters (plus any needed extensions)
  • Update Requirements in Sec 7 appropriately (Issue#2841)
• 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 
• multi cloud use cases (as examples to drive requirements), needs a discussion at RM meeting
  • specialised clouds (e.g. game clouds)

Developments on:

• SBOM, alignment with LFN security forum (Issue#2810) 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#2839)
• Security for hybrid and multi-cloud, Issue #2804 (to be removed?), Issue#2840
• Both "Monitoring for security" and "Security of monitoring" aspects are included in Table 7-7 which needs review by the team, and updates 

Updates to storage:  storage sections are under review by John Hartley

• Storage principles (Issue#2666) - propose placement of contents
• Storage for multi-cloud (Issue#2578) - propose placement of contents
• Storage scenarios (Issue#2747) - propose placement of contents, currently focused

Walter Kozlowskito start PRs for the Issues:

• Infrastructure LCM Automation Introduction (Issue#2816) - state goal/ambition of Anuket work, 

• 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

• PR#2826: Remove
Issue#TBD)
• Principles (Issue#TBD)
• Best Practice Issue#TBD)
• Previous comment on contents
  
  • Design and build consideration (with Automation) - collaboration with RAs and RIs. Principles, guidelines (to be shared between RM and RAs). Declarative approach to automation. 
• Proposal to remove the following sections (blank) :- under review - to be covered in Framework section, Walter Kozlowskiraise a PR to remove these subsections (PR#2826): 
  • 9.5.1.1. Hardware Configuration CI/CD
  • 9.5.1.2. Networking Automation
  • 9.5.1.3. Software Development CI/CD1.

Section 5.1.5 lists a set of General PaaS Services. We need to specify requirements for each of these services -- an issue will be opened for each service. - Pankaj Goyalto start work on contents in wiki page (RM Work Spaces) and PRs (collaborate with Per Andersson)