Uploaded image for project: 'Service Design and Creation'
  1. Service Design and Creation
  2. SDC-3819

Solution for identifying SOL004 packages

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • Jakarta Release
    • None
    • None
    • None

      Currently SDC depends on the presence of 2.6.1 metadata in a package to identify the package as an ETSI SOL004 package (as opposed to an ONAP package). This causes a problem for 2.5.1 SOL004 packages as the required metadata is not present.

      The consequence of this is any package onboared will be considered an ETSI package unless it contains the new metadata entry. This is divergent from ONAP behaviour but it is not anticipated the operators will be using ONAP packages. If an operator wants to onboard an ONAP package they can still do so, but will need to manually update it to contain the "onap_csar" metadata entry

            aribeiro aribeiro
            aribeiro aribeiro
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: