• Type: Story
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Beijing Release
    • Labels:


      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 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>


          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.



              • Assignee:
                melliott Mike Elliott
                cfridgen Chris Fridgen
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created: