VDU Mapping:

• Make the org.openecomp.resource.abstract.nodes.ETSI.VFC a superset of both tosca.nodes.nfv.Vdu and org.openecomp.resource.abstract.nodes.VFC
• Note: the org.openecomp.resource.abstract.nodes.VFC represents design-time VFC, not VFC instances
• During VNF onboarding, SDC copies SOL001 VDU attribute contents to the corresponding attributes in the org.openecomp.resource.abstract.nodes.ETSI.VFC
  • In Guilin, SO NFVO, VFC and SVNFM get those SOL001 VDU attributes from the descriptor, not from AAI. So, AAI schema changes are not expected in Guilin.
• SOL001 VDU attributes in SDC AID DM VNF will be visible to SDC UI, so SDC UI can change the attributes.
  • But the onboarded vendor ETSI package will note be changed by the SDC UI users in Guilin.
  • Since SO NFVO, VFC and SVNFM use only the original ETSI package, those changes will not be used in Guilin;
  • For the Honolulu release, it is under consideration
    • to sync up between those modified SOL001 VDU attributes and the vendor ETSI Package attributes 
    • to reflect those modified SOL001 VDU / VFC attributes in the orchestration