12:39 p.m.
On Fri, Jan 5, 2018 at 12:36 PM, David Moreau Simard <dms(a)redhat.com> wrote:
There are already plans [1] to add the software factory
implementation of
Grafana on review.rdoproject.org, you can see what it looks like on
softwarefactory-project.io [2].
The backend to this grafana implementation is currently influxdb, not
graphite.
However, there are ongoing discussions to either both graphite and
influxdb simultaneously or optionally either.
We're interested in leveraging this influxdb (or graphite) and grafana
implementation for monitoring data in general (uptime, resources, disk
space, load, etc.) so our goals align here.
We both agree that using graphite would be a plus in order to re-use the
same queries in the grafana dashboard but at the same time, influxdb is
more "modern" and easier to work with -- this is why we might end up
deploying both, we'll see.
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1514086
[2]: https://softwarefactory-project.io/grafana/
This is great news David, thank you for sharing.
Given that this is already in plan software factory and we have an
immediate need I'm wondering how to proceed.
Does the RDO Infra team have an estimate when graphite/influxdb/grafana
will be moved to production?
Some possibilities come to mind, depending on when it moves to prod
1. The TripleO-CI team waits for prod
2. TripleO CI would stand up a test instance of graphite/influxdb and
grapha and start to work out what we need to send and how to send data
3. Is it possible to use the stage instance RDO SF as a testbed for
TripleO-CI's work? Meaning we send metrics and use the stage instance with
a backing up the data in mind?
What do you think?
Thanks
David Moreau Simard
Senior Software Engineer | OpenStack RDO
dmsimard = [irc, github, twitter]
On Fri, Jan 5, 2018 at 12:13 PM, Wesley Hayutin <whayutin(a)redhat.com>
wrote:
> Greetings,
>
> At the end of 2017, a number of the upstream multinode scenario jobs
> started to run over our required deployment times [1]. In an effort to
> better understand the performance of the deployment and CI the tripleo
> cores requested that a Graphite and Grafana server be stood up such that we
> can analyze the core issues more effectively.
>
> There is a certain amount of urgency with the issue as our upstream
> coverage is impacted. The TripleO-CI team is working on the deployment of
> both tools in a dev-ops style in RDO-Cloud this sprint. Nothing yet has
> been deployed.
>
> The TripleO CI team is also working with upstream infra to send metric
> and data to the upstream Graphite and Grafana servers. It is not clear yet
> if we have permission or access to the upstream tools.
>
> I wanted to publically announce this work to the RDO infra community to
> inform and to gather any feedback anyone may have. There are two scopes of
> work here, the initial tooling to stand up the infra and the longer term
> maintenance of the tools. Perhaps there are plans to build these into RDO
> SF already.. etc.
>
> Please reply with your comments and concerns.
> Thank you!
>
>
> [1] https://github.com/openstack-infra/tripleo-ci/commit/7a2
> edf70eccfc7002d26fd1ce1eef803ce8d0ba8
>
>
>
> _______________________________________________
> dev mailing list
> dev(a)lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/dev
>
> To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
>
>