Versions Compared

Old Version 53

changes.mady.by.user Byung-Woo Jun

Saved on

compared with

New Version Current

changes.mady.by.user Byung-Woo Jun

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Gliffy
macroIdfbc6e2f8-a0f2-4c65-9293-6931f8e8b2e9
nameETSI SDC Onboarding - Honolulu
pagePin1416



  1. SOL004 VNF/PNF and SOL007 NS Packages are onboarded to SDC.
  2. SDC creates its Resource CSAR by adding ONAP-specific files and metadata according to SDC procedure.
    1. For VNF onboarding, SOL001 VNFD is mapped to SDC Data Model.
    2. For NS onboarding, SOL001 NSD is mapped to SDC Data Model. Note: the SDC NS Data Model would be SOL001 NSD-based.
    3. For PNF onboarding, SOL001 PNFD is mapped to SDC Data Model.
    4. The original SOL004 VNF/PNF and SOL007 NS packages will be stored in the ETSI_PACKAGE directory.
    5. SDC shall have a capability to design SOL007 NSDs and generates SOL007 NS packages
      1. Since SDC does not have a proper NS Model, it will follow SOL001 NSD.
    6. SDC embeds the Resource CSAR into its Service CSAR for distribution.
      1. After SDC validates the onboarded packages, the Service CSAR is distributed.
      2. SDC sends the package notification to DMaaP for its package notification subscribers.
  3. ETSI Catalog Manager receives the package notification from SDC.
    1. ETSI Catalog Manager queries SDC for the SDC CSAR.
      1. ETSI Catalog Managers examines the SDC CSAR. If the SDC CSAR contains the ETSI_PACKAGE directory, it extracts the SOL004/SOL007 packages from the directory.
      2. ETSI Catalog Manager stores the SOL004/SOL007 packages to its Catalog Database.
    2. ETSI Catalog Manager provides APIs for the SOL003/SOL005 Adapters to distribute the packages to SVNFM/NFVO.

...

Gliffy
macroIdd34e147d-5457-466e-a4b2-206abd612a83
nameSOL004 VNF-CNF structure onboarding - Honolulu
pagePin119


Design NS


NSD Structure


SDC supports NSD design that meets the following requirements.

...

NSD Mapping to SDC AID DM

Initial Input

NSD Mapping to SDC AID DM

...

Gliffy
macroIdfbc6e2f8-a0f2-4c65-9293-6931f8e8b2e9
nameETSI SDC Onboarding - Honolulu
pagePin1416



  1. SOL004 VNF/PNF and SOL007 NS Packages are onboarded to SDC.
  2. SDC creates its Resource CSAR by adding ONAP-specific files and metadata according to SDC procedure.
    1. For VNF onboarding, SOL001 VNFD is mapped to SDC Data Model.
    2. For NS onboarding, SOL001 NSD is mapped to SDC Data Model. Note: the SDC NS Data Model would be SOL001 NSD-based.
    3. For PNF onboarding, SOL001 PNFD is mapped to SDC Data Model.
    4. The original SOL004 VNF/PNF and SOL007 NS packages will be stored in the ETSI_PACKAGE directory.
    5. SDC shall have a capability to design SOL007 NSDs and generates SOL007 NS packages
      1. Since SDC does not have a proper NS Model, it will follow SOL001 NSD.
    6. SDC embeds the Resource CSAR into its Service CSAR for distribution.
      1. After SDC validates the onboarded packages, the Service CSAR is distributed.
      2. SDC sends the package notification to DMaaP for its package notification subscribers.
  3. ETSI Catalog Manager receives the package notification from SDC.
    1. ETSI Catalog Manager queries SDC for the SDC CSAR.
      1. ETSI Catalog Managers examines the SDC CSAR. If the SDC CSAR contains the ETSI_PACKAGE directory, it extracts the SOL004/SOL007 packages from the directory.
      2. ETSI Catalog Manager stores the SOL004/SOL007 packages to its Catalog Database.
    2. ETSI Catalog Manager provides APIs for the SOL003/SOL005 Adapters to distribute the packages to SVNFM/NFVO.

...

NSD Mapping to SDC AID DM

Initial Input

NSD Mapping to SDC AID DM

...