This is typically used to mount Docker containers but it generates too
many volatile metrics which aren't useful.
Change-Id: I00117895570515b2c8f9690542e83061309464c3
Since metrics on dropped packets are counters, the alerts should use
the rate() function. This change also fixes some inconsistencies in the
alert descriptions.
Change-Id: I9abbc0a49f45ba760836c436a3e7e65aa62f652e
- Add posibility do delete user password
- Delete any password, if no other option has been passed
- Allow to pass hash\plain password
- Allow to unchange password
Change-Id: Id2b7234ca5d4417475b2114e74840292fc57d0de
Interface name was hardcoded when checking if peer is set for
ovs interface.
This patch unhardcode interface name.
Change-Id: Id465d5f84751b5516aebc9d80716d21d14e56abc
This patch adds dependency for ovs_port_up_{{ interface_name }} on
linux_interfaces_final_include. This is needed to avoid errors like
"Unknown interface XXX"
Change-Id: I763ff8ae32a170df3802a65a547c6e76959a0137
This change adds the Telegraf configuration to collect swap metrics, the
associated Prometheus alarms and graphs to the Grafana dashboard.
Change-Id: I3595fd0b8cab06215c620642da69dd29c398396a
The `linux_netlink.ls` function used a regex to choose which interfaces
to collect metric for.
`_alphanum_re = re.compile(r'^[a-z0-9]+$')`
Unfortunately, by default this excludes vlan and tap interfaces, which
are kind of important. ie `bond0.120` or `tap2a3dab86-fb`.
We also have a problem where even if we update the regex to include
these interfaces... if someone deletes and spawns a new instance then
the tap device name changes on the compute host, which will not be
monitored unless someone re-runs the `collectd` on the compute again.
Less than ideal.
This commit lets us choose `VerboseInterface "all"` using Pillar data
to avoid this problem.
Change of mtu is not handled by reclass. Example interface:
```
br_ctl:
enabled: true
type: bridge
proto: static
mtu: 1450
address: ${_param:single_address}
gateway: ${_param:ctl_gateway}
netmask: ${_param:control_network_netmask}
use_interfaces:
- ${_param:primary_first_nic}
```
Currently when Salt starts setup-loopback-device service
systemd executes losetup command and even if it worked
successfully, systemd marks service as inactive(dead).
And Salt considers service as dead. In order to fix
this behavior, we need to add RemainAfterExit=true to
loopback systemd unit template.
Other changes:
.gitreview added
Related Prod: https://mirantis.jira.com/browse/PROD-11760
Change-Id: I6d0c3baf1c22d0a626ff1fd6aaab802c08fb029e
This enables a more fine tuned dpdk for better performance.
More details on pmd-rxq-affinity config:
http://docs.openvswitch.org/en/latest/howto/dpdk/
Change-Id: I630c6af94ff733619fb175f522fc515984862ff6
* RIL-267 Adding cpu governor and kernel module opts
* RIL-267 Adding cpu governor and kernel module opts
* RIL-267 Adding cpu governor and kernel module opts
Filip Pytloun
Jakub Pavlik
Petr Michalec
car-da
Simon Pasquier
Bartosz Kupidura
Olivier Bourdon
Jaymes Mosher
Petr Jediný
Jiri Broulik
Yuriy Taraday
azvyagintsev
Vasyl Saienko
Dmitry Kalashnik
Kalynovskyi
mceloud
Ramon Melero
Oleg Bondarev
Mykyta Karpin
Ales Komarek
tomas kamm
Dmitry Tyzhnenko
Andrey Shestakov
teoyaomiqui