Nile Specification Planning Dashboard

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 

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

• 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

• Lifecycle Automation: align with RM development on automation (issue #2238)
• Deployment automation: give more guidance (issue #2776)

• Hybrid multi-cloud orchestration (#2784)
• Evaluate other communities: ONAP, GSMA OPG, ...  (#2784)

• Development on acceleration focusing on use cases. Identify the acceleration needs and technologies for workloads hosted in Data Centre and for workloads deployed at the edge (#2786)

• Chapter 3 (issue #2860)

 Expand the section "Virtual storage" highlighting the storage requirements for workloads and for the infrastructure components. Refer to RM chapter 3.

On the "Cloud Topology" section, describe the differences per hosting environments: large DC to edge infrastructures, in conjunction with RM Chapter 3, 3.6.4. Storage scenarios and architecture fit.

• Chapter 4 (issue #2861)

Develop on interactions between OpenStack Cinder/Swift and storage backends.

Add examples of backend solutions.

• Chapter 4 (issue #2874)

In "Edge cloud topology", add a sub section addressing hyperconverged SDS for edge cloud.

• Collect requirements and characteristics from existing production deployments ( Chapters 2 & 4) (issue #2500)

Content improvement (issue #2775):

• Chapter 03: Topology overview, make clearer the redundancy models, eventually with high level diagrams
• Chapter 04: Cloud Topology and Control plane scenarios, in table 4-5,  "*" and "**" need to be defined

• Chapter 2 (issue #2877) - Review all the requirements' tables of chapter 2 and add, when it is missing, a specification reference pointing where the requirement is addressed.
• Other chapters: add requirements matching content 

• Add HELM or other CNF packaging specs
• Clarify relationship with TOSCA and ONAP packaging

• Input from Barometer re: metrics and architecture
• add requirements for monitoring
• add specs on caas cluster monitoring & telemetry

• clarify l2/3 vs l7 service mesh
• add service mesh requirements in ch2
• add service mesh specs in ch4

• define API for CaaS manager interface
• define required CaaS LCM operation through API
• API to allow flavours and profiles of clusters

2807

2259

2798

2509

• Align with RM
• Host OS
  • restore host OS requirements
  • refresh host OS and kernel specs for CNF support
• align ch4 specs and ch2 requirement references
• K8s 1.23
  • update references to k8s 1.23
  • remove deprecated features and APIs
  • add relevant new features and APIs
  • align conformance testing ref ch6