OPEN-O Modelling Project Proposal Version 1.2 Draft – For Review Chengli

Overview Project Name: Modelling Repository Name: TBA[modelling?] Project Description: –OPEN-O modelling project coordinates all the metadata modelling from both design time and run time of OPEN-O orchestration. It’s a document requirement project, intended to ensure cross-project alignment in metadata model design and implementation for each OPEN-O release, with no code output, and may share tools in other projects. Participants: –CMCC, Gigaspaces, Huawei, Intel, ZTE, Raisecom, others? Targeted Release: Release 2 –To be held as an incubation project for Release 1 –For Release 1, Create a project wiki page to host and maintain all metadata modelling documentation and related follow-up discussion 2

Project Scope From current OPEN-O Architecture, The metadata modelling includes –Several model types, each may be consumed in different project in different time, e.g. resource modelling, network service modelling, end2end service modelling and may introduce new model type in the future (like product, offer etc.) All these models can be classified in different views: –For different format: Package(CSAR)/Template(Blueprint) –For different domain: E2E/SDN/NFV –For different users: CFS/RFS Participating projects need to be aligned with consistent data modelling – 3

Alignment with TSC and Architecture Committee modelling project should instruct the models design and coordination between projects in the view of implementation, maintain the documents of models. All of these practical works should keep in alignment with Architecture Committee's long- term architecture and models approaches. 4

Problems to be solved Problem: Without a common coordination platform, the interaction between different implementation and tooling projects has to go through an ad hoc manner, which is not efficient and trackable. Goals: To ensure for each OPEN-O release, a centralized and therefore consistent metadata modelling for the whole E2E assets management procedure, where all related participating projects can collaborate in reaching a common understanding for data modelling to address the targeted usecase for a given OPEN-O release in the planning phase, before ad-hoc design and coding in parallel in implementation phase. 5

How to solve the problems For each release, the OPEN-O TSC is committed to address a group of usecases from the BoD, which need to be broken down into a common metadata model as well as functional features of each participating projects. For the model part, as shown in this diagram, which borrows the TMF’s model for service modelling, there is a layering of different models, to be supported by various participating projects, with support from common tooling projects. 6 Usecase model feature CFS RFS NF GSO SDNO/NFVO VNF SDK Product Offer Common Tosca Common Services NS

Action in planning stage 7 In planning stage, modelling project is responsible for the organization and coordination of works between projects. Identify the gaps. Combined with Top-down and Bottom-up manners OPEN-O X- release Planning Coding Archiving modelling Impl. Projects Planning Impl. models Impl. models Impl. models

OPEN-O X-release Planning Coding Archiving modelling Impl. Projects Impact assessment Coding Update req Coding Action in design and implementing stage In implementing stage, If issues are discovered during the implementation phase, projects are empowered to make any updates that are required and update the Modeling project accordingly. In cases where there are modeling dependencies between projects, participating projects should coordinate the changes within the Modeling project. –If the influence is within the scope of a single project, the implementation of the relevant project will be updated by itself –If the modification impact multiple projects, modelling need organize the coordination cross-projects 8

Action in achiving stage After code freeze, modelling project need to organize an assessment about the consistence between design and implementation. Modify or update documents if needed. 9 OPEN-O X-release Planning Coding Archiving modelling Impl. Projects Archiving

Cooperation with Projects 10 PlanDesignImplementationArchive Gaps New requirements IM/DM/Specs of Templates SDOs Domain Project Review & reach a consensus Modelling Project Assets Modelling Project Assets Templat es GS-OSDN-ONFV-OOthers… GS-O NFV- O SDN- O VNF SDK Modelling Project Assets Modelling Project Assets Coordinate/ reach a consensus Other s…

Lifecycle of Models 11 M0 M2 Plan 1.1 Collect Requirements 1.1 Collect Requirements 1.2 Identify gaps 1.2 Identify gaps 1.3 Review 1.3 Review Design 3.1 Propose Modification 3.1 Propose Modification 3.2 Update 3.2 Update 3.3 Review 3.3 Review 3.1 Domain projects: Propose modification for resolving the issues coming from the practical implementation. 3.2 Domain projects update itself if the influence within specific project, otherwise Modelling project organize the coordination cross-projects. 3.3 Modelling project ： Review the modification, reach a consensus if needed. M1 Implementation 2.1 Template Define 2.1 Template Define 2.3 Review 2.3 Review 2.4 Approve 2.4 Approve 1.1 Domain projects: Collect suggestion and requirement from projects specific domain. 1.2 Domain projects: Identify the gaps individually by domain specific project. 1.3 Modelling Project ： Review and reach a consensus(if it’s within one specific project bypass to M4) 2.1 Domain projects: define template based on planed user case independently 2.2 Modelling project ： Organize and coordinate in intersection part together with related projects. 2.3 Modelling project ： Review the draft. reach a consensus with projects. 2.4 Modelling project ： Approving the detailed Models/Templates, freeze. M3 M4 Archive/Release 4.1 Assessment 4.1 Assessment 4.2 Archive 4.2 Archive 4.1 Modelling project ： Assess the consistence between design and implementation 4.2 Modelling project ： Archive all the output for the release. 2.2 Cooperation 2.2 Cooperation

Seed for modelling Release 1 modelling Documentation Modelling Project wiki page: For Release 1: –Specifications –Templates 12

Resources Contact Person: Chengli Wang 13 Initial Committers: Lingli Deng - Yuan Liu – Zongbiao Li - Jianguo Zeng – Zhaoxing Meng – Huabing Zhao – Maopeng Zhang - Manjie Fan – Yongming Peng - Alex Vul - Olga Havel - Arthur - Hui Deng – Contributors: Casem Majd Youcai Pan

s Thank you For more information about Modelling: 谢谢