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 TOSCA as the "normative", supplier/operator neutral way to package and describe (model) network service and functions in ONAP.
- Enable 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 | ||||||
|---|---|---|---|---|---|---|
|
To Do's
- Initial list of gaps - Fred (Verizon)
- Initial persona definitions - Michela (Ericsson)
- Stage definitions - Alex
- Gaps with respect to VNF requirements - Thinh (Nokia)
Contributions...
| Attachments |
|---|