Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-1456

SDNC is not installing when installing a subset of ONAP in Rancher/Kubernetes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Medium Medium
    • None
    • Casablanca Release
    • None

      I'm following the instructions at https://wiki.onap.org/display/DW/OOM+Helm+%28un%29Deploy+plugins to install a subset of the ONAP components in a Rancher/Kubernetes environment.  To install only a subset, I copied oom/kubernetes/onap/values.yaml to an "override.yaml" file and set "enabled: true" to "enabled: false" for those components I do not want to install. I then executed:
      helm deploy demo local/onap --namespace onap -f ~/override.yaml
      All the selected components were installed except for SDNC even though the parameters for SDNC in the yaml file were not touched.

      Comments from others:

      Andrew Fenner:

      I was running into something similar and I think it is a little more complex (still investigating but think I’m close to the root of the problem)./ 

      I think the parsing in the deploy.sh is a tiny bit off and it is been confused by the sniro-emulator as the “–“ isn’t in the word definition.

      Later: That fix didn't work because we can't have a - in an environment variable.  I'll keep looking to see if I can workaround it.

            melliott melliott
            georgeclapp georgeclapp
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: