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