Members
NOTE - In order to make fast progress, we are looking to keep the group size to a minimum and consisting as much as possible of TOSCA SME's.
Objectives
- Establish
Desired Outcome
- Enable use of TOSCA as the "normative", supplier and /operator neutral way to package and describe (model/describe ) network service and functions in ONAP.
- Enable specification of deployment targets, other then virtual machines (e.g. K8S, Azure, etc.).
- Do not preclude use of alternative packaging and modeling approaches.
Lifecycle Stages
- template reuse and orchestration outcome consistency across ONAP related on-boarding, design, instantiation and operation activities.
- Identify TOSCA adoption barriers/gaps and recommend closure actions.
Tasks
- Template use...
- Define when and how TOSCA templates are used across on-boarding, design, instantiation and operation time
- Define template versioning and SDO compatibility strategy.
- Identify template gaps and recommend closure actions.
- Network service and function lifecycle orchestration...
- Define end-to-end component interactions and dependencies required for TOSCA based orchestration activities across on-boarding, design, instantiation and operation time.
- Identify interaction gaps and recommend closure actions.
- Define how TOSCA templates are used in conjunction with emerging encoding and packaging alternatives.
- Recommendations...
- Architecture Subcommittee
- Modeling Subcommittee
- Projects
Personas & NS/NF Template Lifecycle (Draft)
| Gliffy Diagram | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Contributions...
| Attachments |
|---|