...
• Initial focus on a Unified IM and TOSCA construct representation
[Thinh Nguyenphu] what is Unified IM? currently, my understanding from there are many projects using different part of one ore models. Or, are we trying to bring Service CSAR, NS CSAR, VNF CSAR, WAN API, Cont/WAN into a Unified IM?
Thinh Nguyenphu] Also, this bullet point should be separate into two bullets for additional clarifications. for example, SO and SDN-C: WAN API is using TOSCA Rel1 and 2? Or we should clearly states: VNF descriptor, NS descriptor, and CSAR package (VNF package and NS/service Package) as initial focus.
...
Identify GAPs and prioritize per release
- Thinh Nguyenphu] beside gaps and priority, the guideline should identify supporting features. For example, scaling feature can a simple scaling to a more complex scale such as aspect scaling to scaling to a specific level, etc. A similar different to deployment flavour too. Describing use case is important.
-Initial round should be based on SDC DM and OpenECOMP (Not relevant in the guidelines section. Consider moving to Principles) Thinh Nguyenphu: agreed with the comment
...
-Propose new constructs to TOSCA NFV profile when desired types are not defined (It would be good to define extensions to SOL001. VNF vendors will provide TOSCA VNFD compliant to SOL001. The new constructs in ONAP can be proposed in ETSI SOL001). Thinh Nguyenphu: agreed with the comment
•Try to maintain backward compatibility
...
•Properties
-Best effort to put properties on capabilities (Not clear. Consider rephrase to clarify)
•Namespace
-TBD
- Thinh Nguyenphu] In order to avoid namespaces and types name types definitions collision, it is recommended that ONAP uses the rule and guidelines as described in the OASIS TOSCA Simple YAML Profile v1.2. At minimum, ONAP describes:
- Namespace Alias: TBD
- Namespace Prefix: TBD
- tosca_definitions_version:TBD
- ONAP's types: naming convention and format
...