Elasticsearch moved to fuel-ccp-elasticsearch repo, due
to collisions between similar docker image names, remove
elasticsearch code from here.
Change-Id: Ia8c74a335ffe9355e4c033d0998080ce56fb1d8f
Depends-On: Ic39eb474f42b25e55772cb95edd362e4be5623c3
9.0-2016-09-02-140322 is already gone, so let's use 9.0-latest instead.
It should always point to latest in foreseeable future.
Change-Id: I3c20c935b15904bdde8caeadd14532477a9420c1
We want to alling with k8s definitions and it would be more convenient
to have one param instead of several flags.
Change-Id: I378f7fd3e89ac12e9f6d16fca3591d09ff33d4f9
Now we have "node_name" variable to render config files
Change-Id: I6ff108cf769da846fd878a3f0fb221df2854917f
Depends-On: I8ebbbd94803ccb9a8d13eede2db7db8b13673937
This commit fixes the network-related graphs in Grafana. The
network statistics provided by Snap are cumulative values.
For example, bytes_recv is the number of bytes received
since the machine boot. For that reason, we need to
configure the Grafana network graphs to use the derivative()
function in SELECT queries.
Change-Id: Icbf5a60c7bc3a34972a4045d454e8ab40917e391
In I7b2b98f379c49bdbf23177a038bdca9433d1c6e5 reviews
suggested to use "base" rather than "base-tools" as the base
image. This commit reverts that. Using "base" forces to add
dependencies such as "dumb-init", which should really not be
the responsibility of authors of non-base images.
This commit also changes the way we specify versions of
Python dependencies in requirements.txt. Fixing versions
using `==` allows for more repeatable builds, but it also
means that we will quickly rely on old versions and will not
be able to guarantee that our code works with the latest
versions of our dependencies. Using `>=` is also consistent
with what we currently use in base-tools/requirements.txt.
requirements.txt was updated using openstack_requirement's
update-requirements tool.
Change-Id: I60d0d8e761da717e2f73485bae53f1e11e3aebba
alarm-manager is responsible for watching a configurable
location within the filesystem where the user can put
a YAML file which defines alarms. When change/creation is
detected, the YAML file is checked for proper contents
and if verification is successfull, LUA code is generated
as well as LUA configuration files. Hindsight will pick
up those changes after a certain period of time and
provides proper alarming to the platform.
Change-Id: I7b2b98f379c49bdbf23177a038bdca9433d1c6e5
Due to the fact that yamllint utity is now run
on each YAML file, this change fix the current
error for line being too long
Change-Id: If35a7fc823c5d13a0dbdade6900be6ee51b1a28f
This change does two things:
* rename variables in Lua code
* add a "cluster" dimension to afd annotations. This is required
to display specific annotations in Grafana dashboards
Change-Id: Iebafb5a63034bec937afedd2697b4a4cce964321
This commit adds alarm annotations to the Grafana System
dashboard. Annotations are displayed when the node status
changes (e.g. OKAY -> WARN).
Change-Id: I1eca90eb574ba3e985566709cc8cc353209da7d2
This commits adds Lua code for generating AFD (Anomaly and
Fault Detection) metrics based on the evaluation of alarms.
The Lua code was copied from the lma_collector Fuel plugin
[*], with changes to accomodate Hindsight and the versions
of lua_sandbox and lua_sandbox_extensions we rely on.
In the future we plan to move this Lua code in its own Git
repository. And the Hindsight Dockerfile will install the
Lua code in the image using Debian packages.
The afd_node_default_cpu_alarms.lua and
hindsight_afd_node_default_cpu_alarms.cfg.j2 files will be
removed. Instead the operator will configure alarms through
a YAML file, and we will use a sidecar container for
generating Lua tables including alarm definitions and
corresponding plugin configuration files.
[*] https://github.com/openstack/fuel-plugin-lma-collector/
Change-Id: If182c3a6453f7bf8b72f03af56a14ace109eaa68
This commit adds support for metrics with multiple values.
Multi-value metrics will for example be needed for alarming.
Change-Id: I496fa1925c389f2638cf9b99243fbf45d7d2dad7
Removed decimals part for number of hours in power on state
Ran format-dashboards.py script on updated JSON file
Change-Id: Ib2b8bcde7c3d01908d39b5bdb55b6a6062005f1a
Note that we can not gather SMART infos from the host within
VMs
See https://www.smartmontools.org/wiki/FAQ
and more particularly the
DosmartctlandsmartdrunonavirtualmachineguestOS
sub-entry
Change-Id: Idee7d48e45a5a388061d196d1e07c55404780085
Andreas Jaeger