<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 5, 2018 at 12:36 PM, David Moreau Simard <span dir="ltr"><<a href="mailto:dms@redhat.com" target="_blank">dms@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:arial,helvetica,sans-serif">There are already plans [1] to add the software factory implementation of Grafana on <a href="http://review.rdoproject.org" target="_blank">review.rdoproject.org</a>, you can see what it looks like on <a href="http://softwarefactory-project.io" target="_blank">softwarefactory-project.io</a> [2].</div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">The backend to this grafana implementation is currently influxdb, not graphite.</div><div style="font-family:arial,helvetica,sans-serif">However, there are ongoing discussions to either both graphite and influxdb simultaneously or optionally either.</div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">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.</div><div style="font-family:arial,helvetica,sans-serif">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.</div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">[1]: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1514086" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=1514086</a><br></div><div style="font-family:arial,helvetica,sans-serif">[2]: <a href="https://softwarefactory-project.io/grafana/" target="_blank">https://softwarefactory-<wbr>project.io/grafana/</a></div><div style="font-family:arial,helvetica,sans-serif"><br></div></div></blockquote><div><br></div><div>This is great news David, thank you for sharing.</div><div>Given that this is already in plan software factory and we have an immediate need I'm wondering how to proceed.</div><div>Does the RDO Infra team have an estimate when graphite/influxdb/grafana will be moved to production?</div><div>Some possibilities come to mind, depending on when it moves to prod</div><div><br></div><div>1. The TripleO-CI team waits for prod</div><div>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</div><div>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?</div><div><br></div><div>What do you think?</div><div>Thanks</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:arial,helvetica,sans-serif"></div></div><div class="gmail_extra"><br clear="all"><div><div class="m_-402693832577081064gmail_signature" data-smartmail="gmail_signature"><br>David Moreau Simard<br>Senior Software Engineer | OpenStack RDO<br><br>dmsimard = [irc, github, twitter]</div></div>
<br><div class="gmail_quote"><div><div class="h5">On Fri, Jan 5, 2018 at 12:13 PM, Wesley Hayutin <span dir="ltr"><<a href="mailto:whayutin@redhat.com" target="_blank">whayutin@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Greetings,<div><br></div><div>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.</div><div><br></div><div>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. </div><div><br></div><div>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. </div><div><br></div><div>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.</div><div><br></div><div>Please reply with your comments and concerns.</div><div>Thank you!</div><div><br></div><div><br></div><div>[1] <a href="https://github.com/openstack-infra/tripleo-ci/commit/7a2edf70eccfc7002d26fd1ce1eef803ce8d0ba8" target="_blank">https://github.com/opensta<wbr>ck-infra/tripleo-ci/commit/7a2<wbr>edf70eccfc7002d26fd1ce1eef803c<wbr>e8d0ba8</a><br><div><br></div><div><br></div></div></div>
<br></div></div>______________________________<wbr>_________________<br>
dev mailing list<br>
<a href="mailto:dev@lists.rdoproject.org" target="_blank">dev@lists.rdoproject.org</a><br>
<a href="http://lists.rdoproject.org/mailman/listinfo/dev" rel="noreferrer" target="_blank">http://lists.rdoproject.org/ma<wbr>ilman/listinfo/dev</a><br>
<br>
To unsubscribe: <a href="mailto:dev-unsubscribe@lists.rdoproject.org" target="_blank">dev-unsubscribe@lists.rdoproje<wbr>ct.org</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div></div>