Details

    • Epic Name:
      Platform configuration management
    • Epic Status:
      Done

      Description

      As an ONAP operator, I want to centrally manage ONAP platform and components configurations so that I can enable multi-instance, scalable/resilient container platform deployment.

      New requirement 20180315 - verify that healthcheck is working for each retrofitted component

      Acceptance Criteria

      • All ONAPĀ componentsĀ are parameterized and fully configurable
      • Ability for operators to manage independent platform environments without any hardcoded parameters
      • Configurability includes at least, but not limited to:
        • Credentials, Secrets
        • Environment parameters: host names, node ports, IP addresses, URLs/Paths
        • Environment variables
        • Versions, Image names
        • Logging levels
        • Runtime parameters, e.g. JVM size
        • High-availability, resiliency, clustering parameters
        • Auto-Scaling, auto-healing policies

        Attachments

          Issue Links

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

            Activity

              People

              • Assignee:
                rogerm Roger Maitland
                Reporter:
                david.sauvageau David Sauvageau
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: