Skip to end of banner
Go to start of banner

Baraque Release Highlights

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

  1. General
    1. Security
      1. RM Ch 07:  Defined composite set of security requirements (link)
      2. RA-1 Ch 02/06 (link) and RA-2 Ch 02/05 (link):  Defined how to meet these security requirements in RM Ch 07
  2. RM
    1. Scope.  Clear definition of CNTT scope
      1. Functional capabilities of the cloud infrastructure and the infrastructure management
      2. Functional interfaces between infrastructure and infrastructure management
      3. Functional interfaces between workloads and workload management
      4. Link:  https://github.com/cntt-n/CNTT/blob/master/doc/common/chapter00.md#functional-scope
    2. Modeling.   Completely revamped content to abstract infrastructure support for virtual and containerized workloads.
      1. New section on sample model realization:  https://github.com/cntt-n/CNTT/blob/master/doc/ref_model/chapters/chapter03.md#37-sample-reference-model-realization
      2. Section Link:  https://github.com/cntt-n/CNTT/blob/master/doc/ref_model/chapters/chapter03.md
    3. Misc (to be categorized)
      1. Technology agnostic to cover both VM-based virtualization as well as containerization of network functions.
      2. Enable co-existence of different Cloud Infrastructure deployments in line with the evolving technology.
      3. To enable the co-existence, a new important element was added to RM: Hardware Infrastructure Manager (HIM) which can allow different virtual infrastructure implementations simultaneously using the same share hardware infrastructure. 
      4. CNTT started a collaboration with ODIM on the definition of HIM (possibly using RedFish)
      5. Expanded network and storage discussion, clarifying distinction between the virtual and hardware layers within networking and storage.
      6. RM (Baraque version) will be handed over to GSMA Networking Group (NG), where it is planned to be published as a GSMA NG PRD (Permanent Reference Document).
      7. The on-going maintenance of this PRD and hence the collaboration with the CNTT RM will be a responsibility of a newly formed subgroup under GSMA NG called OITF (Open Infrastructure Task Force). In the course of this collaboration, several CNTT RM contributors registered as the members of OITF.
  3. Edge Computing and Networking
    1. Define some expectation capabilities that fit Edge use cases like FPGA for OpenRAN "https://github.com/cntt-n/CNTT/blob/master/doc/ref_model/chapters/chapter04.md#425-cloud-infrastructure-profile-capabilities-mapping"
    2. Edge workstream defined the multiple edge architecture based on Openstack, start to reflect it on RA01
  4. RA-1
    1. Upgrade documentation in support of OpenStack Train release
      1. See chapters 3, 4 and 5
    2. Align Networking sections with RM Network modeling changes
  5. RI-1
    1. TBD + Link
  6. RC-1
    1. TBD + Link
  7. RA-2
    1. RA2 Requirements are relatively stable
    2. RA2 Specification is now in a state where it can be used by RI/RC/VI
  8. RI-2
    1. Initial release of RI2 launched with introduction, lab requirements and operational runbook
      1. See chapters 1, 3 and 4 
    2. Kuberef project has launched within OPNFV to manage integrations into OPNFV labs
  9. RC-2
    1. TBD + Link


  • No labels