Age | Commit message (Collapse) | Author | Files | Lines |
|
* changes:
Add a playbook that tests collectd 6 vs collectd5
[docker][ansible] Add a playbook for building the containers
Create a flask app to show metrics from collectd
|
|
|
|
After the introduction of the collectd_config roles, for generating
configs, some of the configs changed, as they were no longer relying on
collectd's defaults.
One of these was the cpu plugin, which configured ``ReportPercentage True``
by the config role. The effected the grafana dashboards, because the CPU
usage dashboard explicitly selected ``type=cpu``. With the values being
reported as percentage, collectd sets the ``type=percent`` for the metrics
stored in influx (which grafana retrieves), so the dashboards dodn't
have any data to display. By removing the ``type=cpu`` filter, the CPU
metrics are once again showing in grafana, and will be shown whether the
CPU usage is reported in percentage or the default jiffies.
Signed-off-by: "Emma Foley <efoley@redhat.com>"
Change-Id: I03a6f01677514d888e7805358855947791ab173c
|
|
The playbook will:
* build collectd-6, collectd-latest and flask app
containers
* generate a set of collectd configs
* launch the collectd-6, collectd-latest with the generated configs
* run the flask app which has a http_server that receives metrics from
collectd v5 and collectd v6
* display the received metrics from both versions of collectd
Collectd v5 shows PUTVAL
Collectd v6 shows PUTMETRIC
The playbook takes the following parameters:
* PR (optional)
The PRID for an upstream collectd pull request that will be
passed to the collectd 6 container build
* plugin (optional)
The name of the plugin that is bneing ported
This will filter the received metrics to show the value passed.
Additional updates to existing roles include:
* run_collectd
parameterises the collectd container name so that the role can be reused for
launching multiple collectd containers by passing distinct names.
Change-Id: Ia62196c347387d380aae69e14ed0dd8e2c76d9c9
Signed-off-by: Emma Foley <efoley@redhat.com>
|
|
To run the playbook and build the containers, run::
sudo ansible-playbook docker/ansible/collectd_build.yml
Change-Id: I60e044f09c8da53f6d5a56d2aaa7b837b19a0b0b
Signed-off-by: Emma Foley <efoley@redhat.com>
|
|
Change-Id: Ief2e99d551809705c0b246a7cae5bd5804f97137
Signed-off-by: Emma Foley <efoley@redhat.com>
|
|
Update collectd_apply_pull_request.sh to check out PR when only one PR is given.
A comma-separated list of PR_IDs will still result in rebasing on top of the checked-out branch.
Signed-off-by: Emma Foley <efoley@redhat.com>
Change-Id: I22012c950be80dce26a51fcf02b13469f27e1ca8
|
|
|
|
|
|
Added a tox target for reno, so new notes can be creted using::
tox -e docs-create-note -- slug-goes-here
Signed-off-by: Emma Foley <efoley@redhat.com>
Change-Id: Ie3b7a3326e80c4d1d49fed42900ce4d31fa3a2ba
|
|
The note for the updated contaienr namespace was omitted
Signed-off-by: Emma Foley <efoley@redhat.com>
Change-Id: Ice710a7008fb7c713fbd56d55219a3823a46f5ab
|
|
Signed-off-by: "Emma Foley <efoley@redhat.com>"
Change-Id: I6dd8e166433feab16dd06c9767e58d6d96ca948d
|
|
Remove old dpdk plugins, since they are superceeded by dpdk_telemetry
plugin.
JIRA: https://jira.anuket.io/browse/BAROMETER-183
Change-Id: Ie4abf2b1fe37a2197d9d5dd01820ac8b0d01df6d
Signed-off-by: Emma Foley <efoley@redhat.com>
|
|
The unixsock plugin is useful for debugging issues in collectd, and can
be used to verify that metrics are being collected without having to
create CSV files or log into the container.
Typically, the unixsock plugin can be queried using the following
syntax::
$ docker exec bar-collectd /opt/collectd/bin/collectdctl -s /var/run/collectd-socket listval
Signed-off-by: Emma Foley <efoley@redhat.com>
Change-Id: Id342fe7659c809f4eec71085ae6572f9d855684c
|
|
The template for release notes wasn't conforming to the expected
headings. A template was added to the config.
To generate a new note (from the base directory in the repo), use::
reno --rel-notes-dir docs/release/release-notes/ new slug-goes-here
The release notes are also included as part of the docs build, and the
existing releases notes have been renamed accordingly.
Signed-off-by: Emma Foley <efoley@redhat.com>
Change-Id: I05d1950b37f266bb6eb3515b3660665cfd5c1d8b
|
|
Reno[1] is used to create release notes. It can be used in conjunction
with sphinx to automatically create and publish release notes. In this
case it is being added to help with release notes collation at the end of
the release cycle.
There is a possibility that it can be more fully integrated later, if
there is need for it.
For the moment, release notes can be outputted using tox::
tox -e docs-releasenotes
Release notes can be added to features using::
reno new slug-goes-here
where slug-goes-here is combined with a random suffic to create a unique
name for the release note.
[1] https://docs.openstack.org/reno/latest/
Change-Id: Id7f113fa4817585bb429503ff3491c633a4ce8e2
Signed-off-by: Emma Foley <efoley@redhat.com>
|