...
Each project within ONAP has its own configuration data generally consisting of: environment variables, configuration files, and database initial values. Many technologies are used across the projects resulting in in significant operational complexity and an inability to apply global parameters across the entire ONAP installationdeployment. OOM solves this problem by introducing a common configuration technology, Helm charts, that provide a hierarchical configuration configuration with the ability to override values with higher level charts or command line options. For example, if one wishes to change the debug level of one of the projects this appropriate OpenStack instance oam_network_cidr and ensure that all ONAP components reflect this change, one could change the vnfDeployment/openstack/oam_network_cidr value in the global configuration file as shown below:
| Code Block |
|---|
| theme | Midnight |
|---|
| title | global configuration exampleexcerpt |
|---|
| collapse | true |
|---|
|
nsPrefix: onap
nodePortPrefix: 302
apps: consul msb mso message-router sdnc vid robot portal policy appc aai sdc dcaegen2 log cli multicloud clamp vnfsdk aaf kube2msb
dataRootDir: /dockerdata-nfs
# docker repositories
repository:
onap: nexus3.onap.org:10001
oom: oomk8s
aai: aaionap
filebeat: docker.elastic.co
image:
pullPolicy: Never
# vnf deployment environment
vnfDeployment:
openstack:
ubuntu_14_image: "Ubuntu_14.04.5_LTS"
public_net_id: "e8f51956-00dd-4425-af36-045716781ffc"
oam_network_id: "d4769dfb-c9e4-4f72-b3d6-1d18f4ac4ee6"
oam_subnet_id: "191f7580-acf6-4c2b-8ec0-ba7d99b3bc4e"
oam_network_cidr: "192.168.30.0/24"
username: "vnf_user"
api_key: "vnf_password"
tenant_name: "vnfs"
tenant_id: "47899782ed714295b1151681fdfd51f5"
region: "RegionOne"
keystone_url: "http://1.2.3.4:5000"
flavour_medium: "m1.medium"
service_tenant_name: "services"
dmaap_topic: "AUTO"
demo_artifacts_version: "1.1.0-SNAPSHOT" |
The migration from the disparate configuration methodologies to Helm charts is tracked under the
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | OOM-460 |
|---|
|
JIRA story. Within each of the projects a new configuration repository contains all of the project specific configuration artifacts. As changes are made within the project, it's the responsibility of the project team to make appropriate changes to the configuration data.Monitoring
