You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Note: work in progress

SDC Package Onboarding Process

SDC User Story

PriorityUser StoryDescriptionJIRA Ticket
1US 1

Actor:

Create an SDC VSP package thru onboarding of an Application Service CSAR based on ASD

  • create metadata to distinguish the model type (e.g., ETSI, ASD, HOT, others)
  • create metadata to distinguish the artifact type (e.g., HELM)

1US 2

Actor:

Create AS internal CSAR (VF resource) by importing VSP CSAR to add CNF/Application based on ASD


1US 3

Actor:

Create an Service CSAR consists of one or more CNF/Application based on ASD


1US 4

Actor:

Distribute Service CSAR to ONAP runtime components thru DMaaP


1US 5

Actor:

Distribute associated Helm Charts to the target Helm Artifact Repository


1US 6

Actor:

Distribute associated Image files to the target Image Repository 






Sequence


SDC App Package Onboarding

Vendor App Package

Application Service Package conforms to ETSI SOL004.

SOL004 Package CSAR Structure

ONAP supports SOL004-conformed CSAR with the TOSCA-Metadata directory, which includes the TOSCA.meta metadata file providing and entry information for processing a CSAR file.

e.g., 

!------TOSCA-Metadata

!------TOSCA.meta

!------TOSCA.meta.sig.cms

!------Definitions

!----- MRF.yaml

!----- MRF.yaml.sig.cms (signature)

!----- OtherTemplates (e.g. type definitions)

|----- OtherTemplates signatures

!------Files

!----- ChangeLog.txt

!----- ChangeLog.txt.sig.cms

!----- global.cert (global certificate for the package)

!----- image(s)

!----- image(s) signature(s)

!----- other artifacts

!----- other artifacts signatures

!------Tests

!----- file(s)

!----- signature(s)

!------Licenses

!----- file(s)

!----- signature(s)

!------Scripts

!----- install.sh

!----- install.sh.sig.cms

!----- MRF.mf 

Note: SOL001 VNFD requirement in the current SOL004 needs to be changed; i.e., make SOL001 VNFD in SOL004 optional. 

Root directory

  • MRF.mf

e.g., f5_FW_cnf.mf

  • TOSCA-Metadata directory
    • TOSCA.meta

e.g.,

TOSCA-Meta-File-Version: 1.0
CSAR-Version: 1.1
Created-By: <vendor>
Entry-Definitions: Definitions/f5_FW_cnf.yaml
ETSI-Entry-Manifest: f5_FW_cnf.mf
ETSI-Entry-Licenses: Licenses
ETSI-Entry-Change-Log: ChangeLog.txt


<keynames extension>


  • Definitions
    • asd_types.yaml
    • f5_FW_cnf.yaml
  • Files
    • Images
      • <image>
      • <image>
    • Licenses
      • LICENSE.txt
    •  Artifacts
      • Deployment
        • AS_PACKAGE
        • ETSI_PACKAGE
    • Scripts

Create VSP CSAR file

  • TOSCA-Metadata
    • TOSCA.meta

e.g., 

TOSCA-Meta-File-Version: 1.0
CSAR-Version: 1.1
Created-By: ASDC Onboarding portal
Entry-Definitions: Definitions/f5_FW_cnf.yaml

  • Definitions
    • f5_FW_cnf.yaml
    • GlobalSubstitutionTypesServiceTemplate.yaml.            //TBD
    •  onap (TBD)
      • _index.yml
      • artifacts.yml
      • capabilities.yml
      • data.yml
      • interfaces.yml
      • nodes.yml
      • relationships.yml
    • onapecomp                                // TBD
      • _index.yml
      • artifacts.yml
      • capabilities.yml
      • data.yml
      • interfaces.yml
      • nodes.yml
      • relationships.yml
    • openecomp-heat                       // TBD
      • _index.yml
      • data.yml
      • groups.yml
      • nodes.yml
    •  tosca
      • _index.yml
      • artifacts.yml
      • capabilities.yml
      • data.yml
      • groups.yml
      • interfaces.yml
      • nodes.yml
      • policies.yml
      • relationships.yml
      • asd_types.yaml
  • Artifacts
    • F5_FW_cnf.mf
    • Definitions
      • f5_FW_cnf.yaml
    •  Deployment
      • AS_PACKAGE.              // copy of the original AS package
    • Images
      • <image>
      • <image>
    • Informational
      • <Guide>
        • VSP_f5_Information.txt
    • LcmScripts
      • <scripts>
    • Licenses
      • LICENSE.txt
    • TOSCA-Metadata
      • TOSCA.meta.original
    • ChangeLog.txt
    • vendor-license-model.xml
    • vf-license-model.xml


Create VF CSAR file - an OLD way; not used for the ASD

  • TOSCA-Metadata
    • TOSCA.meta
  • Definitions
    • artifacts.yml
    • capabilities.yml
    • data.yml
    • groups.yml
    • interfaces.yml
    • nodes.yml
    • policies.yml
    • relationships.yml
    • resource-<...>-template.yml
    • resource-<...>-template-interface.yml
  • Artifacts
    • Deployment
      • AS_PACKAGE
      • VENDOR_LICENSE
      • VF_LICENSE
    • Informational
      • OTHER
        • VSP_f5_Information.txt
  • csar.meta

Create VF CSAR file thru the SDC Multi Model Way.       // Propose to use for the AS Package Onboarding

  • TOSCA-Metadata
    • TOSCA.meta
  • Definitions
    • artifacts.yml
    • capabilities.yml
    • data.yml
    • groups.yml
    • interfaces.yml
    • nodes.yml
    • policies.yml
    • relationships.yml
    • asd_types.yaml.                            // instead of using ONAP type definitions, support the ASD model specific definitions are included
    • resource-<...>-template.yml
    • resource-<...>-template-interface.yml
  • Artifacts
    • Deployment
      • AS_PACKAGE
        • AS_<...>DataTypes.csar
      • VENDOR_LICENSE
        • vendor-license-model.xml

e.g.,

<vendor-license-model xmlns="http://xmlns.openecomp.org/asdc/license-model/1.0">

<vendor-name>VendorA</vendor-name>

<entitlement-pool-list/>

<license-key-group-list/>

</vendor-license-model>

      • VF_LICENSE
        • vf-license-model.xml

e.g., 

<vf-license-model xmlns="http://xmlns.openecomp.org/asdc/license-model/1.0">

<vendor-name>VendorA</vendor-name>

<vf-id>367db414413b4f3e96fcb92df023df27</vf-id>

<feature-group-list/>

</vf-license-model> 

    • Informational
      • OTHER
        • VSP_f5_Information.txt
  • csar.meta


Create Service CSAR file

  • TOSCA-Metadata
    • TOSCA.meta
  • Definitions
    • annotations.yml
    • artifacts.yml
    • capabilities.yml
    • data.yml
    • groups.yml
    • interfaces.yml
    • nodes.yml
    • policies.yml
    • relationships.yml
    • asd_types.yaml.                            // instead of using ONAP type definitions, support the ASD model specific definitions are included
    • resource-<...>-template-inteface.yml
    • resource-<...>-template.yml
    • service-<...>-template-interface.yml
    • service-<...>-template.yml
  • Artifacts
    • Resources
      • <VF-name>
        • Deployment
          • HELM
            • <helm files>
  • csar.meta
  • NS.mf
  • No labels