Mapping of Areas of Mutual Interest between ETSI
and the OpenStack Foundation

 

 

1 Overview

 

 

 

 

ETSI Technical Activities

 

 

ISG ENI

ISG MEC

ISG NFV

ISG ZSM

OSG OSM

OpenStack Foundation Projects

Airship

 

 

Kata Containers

 

 

 

 

OpenStack

StarlingX

 

 

Note: The above table may from time to time be amended by the duly authorized representatives of the parties upon consultation. The latest and current version of this table is available at the following link:

https://portal.etsi.org/webapp/AgreementView/Mapping_tables/Mapping_OpenStackFoundation.htm

 

 

 

 

next page: detailed description

↓↓↓

 

 


 

2 Detailed description

 

 

 

ETSI Technical Activities

 

 

ISG ENI*

ISG MEC*

ISG NFV*

ISG ZSM*

OSG OSM*

OpenStack Foundation Projects

Airship

TO BE UPDATED

 

 

 

 

 

Kata Containers

 

 

 

 

 

OpenStack

 

 

 

 

 

StarlingX

 

 

 

 

 

*Including, in each area, cooperation to help identify relevant SEP declarations made pursuant to ETSI processes.

 

 

 

Note: The above table may from time to time be amended by the duly authorized representatives of the parties upon consultation. The latest and current version of this table is available at the following link:

https://portal.etsi.org/webapp/AgreementView/Mapping_tables/Mapping_OpenStackFoundation.htm

 

ISG ENI (Experiential Networked Intelligence)

 

                  Relevance to OpenStack: OpenStack covers the NFVi and VIM components in the ETSI NFV Architectural Framework. While this is not in the direct scope of ISG ENI it is relevant to the work to ensure all the required interfaces are available for data collection and action through the AI engine. As the scope of the work recognizes SDN controllers as well it is crucial that the integration of these tools with OpenStack provides all the support for the AI-based actions that are required.

 

                  Relevance to StarlingX: StarlingX is a fully integrated platform for edge and IoT use cases that integrates OpenStack and Kubernetes. Edge Computing through 5G is in focus for operators along with containers as technology choice for next generation network functions. In this sense StarlingX and the ISG ENI group can benefit from collaborating to advance platforms to meet the requirements of IoT, self-driving vehicles, and so forth.

 

                  Relevance to Airship: As Airship is an OSF project that is focusing on deployment and lifecycle management it is beneficial to connect this project and ISG ENI to see how Airship could be further leveraged in the process of optimizing the network based on the inputs of an AI framework and make sure the interfaces and configuration of the network is per standard.

 

Beyond the above all the above three projects can benefit from use cases and best practices that are to be delivered by ISG ENI.

 

 

ISG MEC (Multi-access Edge Computing)

 

                  Relevance to OpenStack: OpenStack covers the NFVi and VIM components in the ETSI NFV Architectural Framework and with that provides services and interfaces utilized for MEC use cases. The collaboration between OpenStack and ETSI MEC can ensure the compatibility between the infrastructure and application layers. As the edge computing area is still relatively new sharing information about relevant use cases and requirements can help to evolve the infrastructure services in line with the standardization activities.

 

                  Relevance to StarlingX: StarlingX is a fully integrated platform for edge and IoT use cases that integrates OpenStack and Kubernetes on the infrastructure layer. It has the same collaboration points as OpenStack extended with the work around containerized workloads and container orchestration technologies as further building blocks towards open infrastructure that are highly relevant for MEC use cases as well.

 

                  Relevance to Airship: Airship is an OSF project that is focusing on deployment and lifecycle management of containerized services. As the focus of the Airship project is highly relevant for edge computing use cases it is important to have alignment between the project and related standardization activities. The initial focus of Airship is deploying and managing OpenStack and Kubernetes components. This scope can expand to further components from the MANO layer. Both for the initial and extended scope the collaboration between the groups can ensure alignment with standardization activities to ensure the deployed platform provides compatible interfaces and configuration.

 

                  Relevance to Kata Containers: Kata Containers is a container runtime that combines containers and virtual machines to provide security through isolation while being lightweight and highly performant. As a packaging option for edge computing applications it is important to make sure it supports any relevant guidelines given by the ISG MEC group.

 

ISG NFV (Network Function Virtualization)

 

                  Relevance to OpenStack: OpenStack covers the NFVi and VIM components in the ETSI NFV Architectural Framework which are two main building blocks on the diagram. The two communities have been collaborating to synchronize the work around interface definitions between these components and other connecting items in the framework. With new and emerging use cases the requirements towards a telecom infrastructure demand enhancements in the NFVi and VIM components. In this sense it is crucial to keep up the collaborative activities to make sure the alignment is maintained.

 

                  Relevance to StarlingX: StarlingX is a fully integrated platform for edge and IoT use cases that integrates OpenStack and Kubernetes on the infrastructure layer. As with 5G edge computing is relevant for NFV as well and in this sense StarlingX can benefit from the above described collaboration as well as look into interface definitions and directions for containerized workloads in addition.

 

                  Relevance to Airship: Airship is an OSF project that is focusing on deployment and lifecycle management of containerized services such as OpenStack components in containers. Collaboration between Airship and the ISG NFV group would be beneficial to ensure the deployment options support the standard interfaces and configurations for the NFVi and VIM.

 

ISG ZSM (Zero touch network and Service Management)

 

                  Relevance to OpenStack: OpenStack covers the NFVi and VIM components in the ETSI NFV Architectural Framework which are two main building blocks on the diagram. Use cases such as network slicing have already been demonstrated using OpenStack services. By the collaboration between OpenStack and ISG ZSM we can ensure that the platform services can support the management and automation functions defined by the standards group and can provide opportunities for testing and demonstration activities.

 

                  Relevance to StarlingX: StarlingX is a fully integrated platform for edge and IoT use cases that integrates OpenStack and Kubernetes on the infrastructure layer. As StarlingX is incorporating OpenStack and Kubernetes services to utilize them for the edge automation is crucial for this project especially from the perspective of the management-type services the community is working on in addition to the open source components they integrate. The collaboration between StarlingX and ISG ZSM can further ensure the alignment between the design, development and standardization activities in this area.

 

OSG OSM (Open Source MANO)

 

                  Relevance to OpenStack: OpenStack covers the NFVi and VIM components in the ETSI NFV Architectural Framework which are two main building blocks on the diagram and are connected to the MANO components as well. OpenStack has a few services in the area of orchestration. With having OpenStack collaborating with OSG OSM we can ensure that the integration points work as well as share knowledge and experience between the groups.

 

                  Relevance to StarlingX: StarlingX is a fully integrated platform for edge and IoT use cases that integrates OpenStack and Kubernetes on the infrastructure layer. As StarlingX is integrating OpenStack and adding management services for further automation on the IaaS layer the above described collaboration option is relevant for this project as well.