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

Top level helm chart for ONAP

XMLWordPrintable

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

      As a ONAP devops engineer, I want to use a global helm chart and values to deploy all of the components so that I don't need to deploy each component separately or define platform wide configuration values individually

      Helm allows for the definition of a top level chart/values, under which we can nest each of the ONAP components. This will allow for fewer commands to deploy a system and pull up any important deployment specific variables into a single top level values file.

      See https://wiki.onap.org/display/DW/OOM+Configuration+Management#OOMConfigurationManagement-ONAPInfrastructureConfiguration for additional info.

      Acceptance Criteria

      • An ONAP engineer can specify at least the following deployment specific parameters in a single file/command line that will override component default values:
        • namespace prefix
        • pull policy
        • storage location (i.e. dockerdata-nfs)
        • node port prefixes
        • Should we allow image versions here as well
      • An ONAP engineer can issue a single command to deploy all of the components in kubernetes utilizing the global parameter values.
      • OOM code base is restructured to accommodate the new hierarchy, i.e.:
        • Kubernetes
          • oneclick
          • onap
            • Chart.yaml
            • values.yaml (new top level file)
            • mso
              • Chart.yaml
              • values.yaml
              • templates
            • <repeated for each component>

            melliott melliott
            cfridgen cfridgen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: