@@ -13,7 +13,7 @@ how to do this.
1313Enable CloudKitty and disable InfluxDB, as we are using OpenSearch as the
1414storage backend. Set the following in ``kolla.yml ``:
1515
16- .. code-block :: console
16+ .. code-block :: yaml
1717
1818 kolla_enable_cloudkitty : true
1919 # Explicitly disable influxdb as we are using OpenSearch as the CloudKitty backend
@@ -26,7 +26,7 @@ work with OpenSearch. Proper support is still pending in Kolla-Ansible `here
2626TLS enabled, you will also need to allow insecure connections for Prometheus
2727and Elasticsearch. Set the following in ``kolla/globals.yml ``:
2828
29- .. code-block :: console
29+ .. code-block :: yaml
3030
3131 cloudkitty_collector_backend : prometheus
3232 cloudkitty_fetcher_backend : prometheus
@@ -40,7 +40,7 @@ within this timeframe. This means that even just one minute will be counted as
4040an hour's usage. It is recommended to change this to a lower number, such as
4141ten minutes. When using Prometheus as the collector, you need to change the
4242scope_key to match the metrics provided by the Prometheus OpenStack Exporter.
43- Set the following in ``cloudkitty.conf ``:
43+ Set the following in ``kolla/config/ cloudkitty.conf ``:
4444
4545.. code-block :: console
4646
@@ -52,7 +52,7 @@ You will need to configure which metrics CloudKitty should track. This example
5252will track for flavors and volumes, set in
5353``kolla/config/cloudkitty/metrics.yml ``:
5454
55- .. code-block :: console
55+ .. code-block :: yaml
5656
5757 metrics :
5858 openstack_nova_server_status :
@@ -85,7 +85,7 @@ Post-configuration with openstack-config
8585
8686This is an example `openstack-config
8787<https://github.com/stackhpc/openstack-config> `__ setup to create mappings for
88- the metrics configured above. Note that the costs are scaled for the ten- minute
88+ the metrics configured above. Note that the costs are scaled for the ten minute
8989collection period, e.g. a flavor with 1 VCPU will cost 1 unit per hour.
9090
9191.. code-block :: yaml
0 commit comments