At the moment the following actions have to be carried out when changes are done, or default doesn't match:
AP:
1. Audit the clouds for the 3x values form
$ juju config nova-cloud-controller cpu-allocation-ratio
$ juju config nova-cloud-controller ram-allocation-ratio
$ juju config nova-cloud-controller disk-allocation-ratio
2: Use the information obtained from the commands above to replace the defaults from prometheus-openstack-exporter with the correct values:
$ juju config prometheus-openstack-exporter cpu-allocation-ratio
$ juju config prometheus-openstack-exporter ram-allocation-ratio
$ juju config prometheus-openstack-exporter disk-allocation-ratio
For customer using Grafana as reference, the defaults can be misleading.
Grafana does not correctly display `ram-allocation -ratio` on the dashboard because it uses values from prometheus- openstack- export which are set statically /git.launchpad. net/~prometheus -charmers/ prometheus- openstack- exporter- charm/+ git/charm- prometheus- openstack- exporter/ tree/config. yaml
https:/
At the moment the following actions have to be carried out when changes are done, or default doesn't match: controller cpu-allocation- ratio controller ram-allocation- ratio controller disk-allocation -ratio
AP:
1. Audit the clouds for the 3x values form
$ juju config nova-cloud-
$ juju config nova-cloud-
$ juju config nova-cloud-
2: Use the information obtained from the commands above to replace the defaults from prometheus- openstack- exporter with the correct values: openstack- exporter cpu-allocation- ratio openstack- exporter ram-allocation- ratio openstack- exporter disk-allocation -ratio
$ juju config prometheus-
$ juju config prometheus-
$ juju config prometheus-
For customer using Grafana as reference, the defaults can be misleading.