Versions Compared

Version Old Version 1 New Version Current
Changes made by

David McBride

Karine Sevilla

Saved on

Key

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

Table of Contents

Reference Model

Issue #DeliverableComments
27943088Hybrid 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 / multiCloud Infrastructure Lifecycle automation; chapter restructure    		PRs: #3210, #3220 - restructured the flow of LF  chapter; Automation consolidated at the end
    2804 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 will specify requirements for each of these services -- an issue will be opened for each service.aspects in Chapter 8PR#3246 - contents added based on white paper on 5G pn responsibility vs accountability Evolving-5G-Security-for-the-Cloud-2022-InDesign.pdf. 
    3247Security references updatePR#3249 - references updated
    3080Hybrid Multi-Cloud Catalog ManagementPR#3261 - contents reg catalog mgmt added
    3136Alignment of Hybrid Multi-Cloud interaction model with LCM AutomationPRs: #3239, 3240, 3241, 3234, 3235 - multiple updates
    3120Hardware Acceleration updatesPRs: #3242, #3243 - references to current O-RAN specifications updated
    3223Energy consumption metricsPRs: #3262, 3258 - definitions of energy efficiency and corresponding metrics added


    Reference Architecture 1

    Issue #DeliverableComments
    2776Automation 
    • Lifecycle Automation: align with RM development on automation (issue #2238)
    • Deployment automation: give more guidance (issue #2776)
    2784Hybrid and multi cloud
    • Hybrid multi-cloud orchestration (#2784)
    • Evaluate other communities: ONAP, GSMA OPG, ...  (#2784)
    2786Acceleration
    • 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)
    2787Storage
    • 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.

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

    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
    2732Specification references updates 
  • 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 

    3015

    3068

    		Restructuration of the document for GSMA

    Chapter 1 restructured: PRs 3144, 3158, 3163

    New bibliography : PRs 3073, 3097, 3127, 3154, 3143

    Addition of an abbreviations table: PRs 3132, 3142  

    References into text for all chapters: PRs 3134, 3141, 3165, 3173, 3186


    		Tables formatting

    To ease future updates and to ease conversion towards GSMA word document

    PRs 3133, 3138, 3202, 3204


    		Automation of the production of the GSMA Document

    Tox.ini and conf.py evolutions

    PRs 3138, 3161, 3164, 3174, 3185, 3203

    3128Merging of RC1 into RA1


    New chapter Conformance

    PRs: 3121, 3139, 3150, 3153, 3156, 3162 

    3178Update of OpenStack release

    Yoga release, new features for SmartNIC, provisioning, monitoring

    Postponed for O release (TBC)

    3179Use cases: 5G deployments with OpenStack

    OpenStack needs to change to be efficient for 5G, especially for deployments. No content could be added.

    Issue closed

    3180Acceleration: support of FPGA and GPU and their use cases

    Update on Cyborg and acceleration

    PRs: 3238, 3263

    3181Edge: hyperconverged solution, EMCO

    OpenStack limitations for use at edge, no content could be added.

    Issue closed

    3182Security : addition of solutions to cover RM security requirementsPostponed for O release 
    3183Support of containerized applications on OpenStack

    Reference to the RA2 chap4

    PR 3260

    3184Develop on infrastructure management

    ODIM

    It will follow RM content, postponed for O release


    		Bugs corrections

    Titles, typos, spelling, grammar...

    PRs 3111, 3113, 3124, 3140, 3157, 3170, 3171, 3188, 3205, 3207, 3211

    Reference Architecture 2

    #DeliverableComments
    2511Application Packaging specs
    • Add HELM or other CNF packaging specs
    • Clarify relationship with TOSCA and ONAP packaging
    2788Monitoring & telemetry
    • Input from Barometer re: metrics and architecture
    • add requirements for monitoring
    • add specs on caas cluster monitoring & telemetry
    2790Service Mesh
    • clarify l2/3 vs l7 service mesh
    • add service mesh requirements in ch2
    • add service mesh specs in ch4
    2792CaaS Manager interface
    • 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

    Updates & fixes
  • 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
    3085Update to K8s 1.25

    1.25 out on 23rd August 22

    1.26 should be out end of December 22 (after Nile)

    2788

    2789

    		Monitoring & Telemetry
    2259security requirements
    2975Finalise CNF workload requirements

    2790

    2791

    		Service Mesh
    2822Specifications for orphaned ch2 requirements (Storage)
    2823PaaS requirements alignment to RM
    2792Infrastructure management

    3057

    2551

    		Updates & Fixes
    3099API specs for CNI multiplexer