Page Comparison

...

3: Now you will need to add the Network Service CSAR package to this service. You can do this by clicking in the blank whitespace of the composition, then on the right hand side of the page select the 2nd tab in order to add a deployment artifact. Click "ADD ARTIFACT" here, give an "Artifact Label" of "ns", any description value and ensure you choose a "Type" of "OTHER". Then click "DONE".

Please note, in the Honolulu release of ONAP, the "OTHER" type has been removed. However it is simple to add the type back through the SDC-backend Pod, you can edit this at runtime for the "SDC-BE" pod.

Simply exec into the "sdc-be" pod on your ONAP deployment, then you will need to edit the following file: /var/lib/jetty/config/catalog-be/configuration.yaml

Find the following section in the configuration.yaml:

- type: OTHER
  categories:
    - DEPLOYMENT
    - INFORMATIONAL
  componentTypes:
    - RESOURCE
  resourceTypes:
    - VFC
    - CVFC
    - CP
    - VL
    - VF
    - VFCMT
    - Abstract
    - PNF

You will then need to add "- SERVICE" under the "componentTypes:" heading above. This will immediately add the OTHER type into your SDC deployment. Your file should look as follows:

- type: OTHER
  categories:
    - DEPLOYMENT
    - INFORMATIONAL
  componentTypes:
    - RESOURCE
    - SERVICE
  resourceTypes:
    - VFC
    - CVFC
    - CP
    - VL
    - VF
    - VFCMT
    - Abstract
    - PNF

Please note, you will need to complete this workaround again if the SDC-BE pod is restarted for any reason.

Alternatively, you can edit the configuration file before deployment by editting this file in the Helm Charts: 

sdc/src/main/docker/backend/chef-repo/cookbooks/sdc-catalog-be/templates/default/BE-configuration.yaml

4: Finally you can click "Certify" in the top right hand corner, followed by "Distribute". Your Service will now distributed across ONAP.

...