71a0d5dd26
This is useful in dashboards where we display libvirt and ovs metrics for a physical host, it will elimnate the step of translating vm and tenant ids if needing to investigate project usage. The libvirt plugin metadata config array will now support 'vm_name' and 'tenant_name', and the ovs plugin will now support the metadata config value for 'tenant_name'. Change-Id: If76418b83119a12b8534fb7f7cb224339f357be8
47 lines
2.2 KiB
Plaintext
47 lines
2.2 KiB
Plaintext
# (C) Copyright 2016 Hewlett Packard Enterprise Development LP
|
|
init_config:
|
|
# These are Neutron credentials, [keystone_authtoken] in /etc/neutron/neutron.conf
|
|
admin_password: password
|
|
admin_tenant_name: services
|
|
admin_user: neutron
|
|
identity_uri: 'http://192.168.10.5:35357/v2.0'
|
|
# Number of seconds to wait before updating the neutron router cache file.
|
|
neutron_refresh: 14400
|
|
# The region name in /etc/neutron/neutron.conf
|
|
region_name: 'region1'
|
|
# Location of temporary files maintained by the plugin. Ramdisk preferred.
|
|
cache_dir: /dev/shm
|
|
# Specfies network metrics in bitslog.
|
|
network_use_bits: false
|
|
# If set, will submit raw counters from ovs-vsctl command output for the given
|
|
# network interface
|
|
use_absolute_metrics: true
|
|
# List of router metadata keys to be sent as dimensions when cross posting
|
|
# metrics to the infrastruture project.
|
|
metadata:
|
|
- tenant_name
|
|
# Installations that don't allow usage of sudo should copy the `ovs-vsctl`
|
|
# command to another location and use the `setcap` command to allow the
|
|
# monasca-agent to run that command. The new location of the `ovs-vsctl`
|
|
# command should be what is set in the config file for `ovs_cmd`.
|
|
ovs_cmd: 'sudo /usr/bin/ovs-vsctl'
|
|
# Regular expression for the interfaces type
|
|
included_interface_re: qg.*|vhu.*|sg.*
|
|
# If set, will submit the rate metrics derived from ovs-vsctl command
|
|
# output for the given network interface.
|
|
use_rate_metrics = true
|
|
# If set, will submit the health related metrics from ovs-vsctl command
|
|
# output for the given network interface.
|
|
use_health_metrics = true
|
|
# If specified, the collector will skip calling the plugin until the specified
|
|
# number of seconds has passed.
|
|
# NOTE: Collection is dictated by the default collection frequency therefor
|
|
# collect_period should be evenly divisible by the default collection frequency
|
|
# otherwise the plugin will be called on the collection run after the specified time
|
|
collect_period = 300
|
|
|
|
instances:
|
|
# Instances are not used and should be empty in `ovs.yaml` because like the
|
|
# ovs plugin it runs against all routers hosted on the node at once.
|
|
- {}
|