...
The full list of containers includes:
- Collectd container image: barometer-collectd (https://hub.docker.com/r/opnfv/barometer-collectd/)
- SNMPD container image - (WIP)
- Kafka container image: barometer-kafka (https://hub.docker.com/r/opnfv/barometer-collectd/)
- InfluxDB container image: barometer-influxdb (https://hub.docker.com/r/opnfv/barometer-influxdb/)
- Grafana container image: barometer-grafana (https://hub.docker.com/r/opnfv/barometer-grafana/)
- Collectd VES application container: barometer-ves (https://hub.docker.com/r/opnfv/barometer-ves/)
NOTE 1: The containers can run on the same host or on multiple hosts. Default configuration assumes everything is running on a single host, but this is easily overriden
NOTE 2: The Zookeeper container used is the official zookeeper container from docker hub and not a custom built container.
Userguide: http://docs.opnfv.org/en/latest/submodules/barometer/docs/release/userguide/docker.userguide.html
The following sections will describe each of the containers in more detail.
| Table of Contents |
|---|
...
barometer-collectd container
The collectd container should include the following barometer plugins (above and beyond what is included in collectd by default):
...
- The container will run as a privileged container.
- The collectd container should work standalone - Ansible will be used to disable plugins that aren't supported on the platform - but essentially if someone pulls the container image it should have everything built in and configured. It is still advised that the end user overrides the default configuration with appropriate configurations for each of the plugins.
- The container will use a CentOS 7 image.
- Ansible scripts will also be provided so that it can be configured and deployed at scale in any environment.
- NOTE DPDK plugins can be left out until the DPDK community pushes their new stats model and plugin to collectd.
...
barometer-snmpd container
AgentX is a protocol defined in RFC 2741 allowing a master agent to be extended by independent sub-agents. The architecture was designed to be simple in respect of authorisation, privacy and encoding. It offers full support for data retrieval (Get, GetNext and GetBulk), data modifications (Set) and notifications (Trap). AgentX transport mappings are specified for UNIX domain sockets and TCP. Every connection is spit up into several sessions, which in turn can convey several transactions.
...
The SNMP Master agent in our case is SNMPD - so we need a container running SNMPD in order to be able to send SNMP Replies to a SNMP collector. For more information on the implementation details of the collectd SNMP plugin please see: SNMP Agent HLD
...
barometer-influxdb Container
This container simply runs an Influxdb instance we can send the collectd metrics to
...
barometer-grafana Container
This container runs the grafana front end with the barometer dashboards being fed metrics from the influxdb container.
...
barometer-kafka Container
Collectd can send telemetry to a VES application that will normalize metrics it receives into a VES format. The messaging bus being used between collectd and the VES application is Kafka. A container running Kafka is needed to bridge the gap between collectd and the VES application. For more information on Kafka and the VES application please see: VES plugin updates
...
barometer-ves Container
Collectd can send telemetry to a VES application that will normalize metrics it receives into a VES format. The messaging bus being used between collectd and the VES application is Kafka. A container running the VES application is required to normalize the data and send it to a VES collector. For more information on the VES application please see: VES plugin updates