1. VDU proposal comparison

2. VDU proposals
Option 1:Mapping between NFV model and TOSCA-v3.ppt (Huawei,IBM, Brocade)
Option 2:Issue_TOSCA310_VDU change proposal v2.zip (NOKIA)
Option 1
Option 2

3. Main different VDU topology Descriptor sharing SwImageDesc
virtualStorageDesc
virtualComputeDesc
Option 1
TOSCA composition mechainism
TOSCA DSL_definition mechanism
TOSCA artifact mechainism
Derived from TOSCA storage node,
different types of virtual storage shall have different node types.
New tosca.capabilities.nfv.Compute.Container Derived from tosca.capabilities.compute
Align with IFA UML definition
Align with TOSCA
Align with IFA requirements
Not align with IFA model, but fulfill their requirement
May need to change IFA model, but fulfill their requirements
Align with TOSCA mechanism.
Option 2
Relationship link based
Requirement link
New node type, New relationship type needed
New node type
Existing TOSCA relationship type can not be used to describe the connection in IFA UML model
Not align with TOSCA
Not align with IFA model (One of the side effect is that it indicates not only descriptor sharing but also instance sharing)
Align with IFA model
Draft (way to go)
Two implementation options will be accepted(Composition based and abstract based)
YAML profile V1.0 ~V1.2 only use artifact
Try this method first
IFA to decide

4. conclusion
Option 1
Option 2