Update the docs to reflect not having grafyaml in the container.
Also move the import into a separate helper script, which can be
manually run on the host if the container needs to be restarted
out-of-band for some reason.
Change-Id: Ib1f6aea7e16180d9b122552a2aa30ce223426941
It seems the images have split into enterprise and oss releases. The
OSS release is the one we want.
Since If0d584f848f213aeea385885e3decfaee6303de5 we don't run anything
in the container. So we can switch to the upstream default of the
Alpine-based container, which is their reccommendation.
Just use the :latest tag. Generally the API seems pretty stable. If
we do break, it's better to figure it out quickly rather than pin to
an old version and then have to make huge jumps.
Depends-On: https://review.opendev.org/c/opendev/grafyaml/+/825990
Change-Id: I312a141baf73d750591957197cb5ba829f503fcb
Instead of building a local grafana image with grafyaml installed,
use the plain upstream grafana image along with the newly created
separate opendev grafyaml image to run the dashboards.
Depends-On: https://review.opendev.org/780119
Change-Id: If0d584f848f213aeea385885e3decfaee6303de5
This includes a fix for I216528a76307189d8d87bd2fcfeff95c6ceb53cc.
Now it's released we can be a bit more explicit about why we added the
workaround.
Change-Id: Ibaf1850549b5e7ec3622418b650bc5e59a289ab6
Currently the http site redirects to https://grafana01.opendev.org
which is a bit confusing. Change this to redirect to the CNAME
grafana.opendev.org.
Change-Id: I174ce06af036a8f74ace6b4d95edaaf85f63fa27
This uses the Grafana container created with
Iddfafe852166fe95b3e433420e2e2a4a6380fc64 to run the
grafana.opendev.org service.
We retain the old model of an Apache reverse-proxy; it's well tested
and understood, it's much easier than trying to map all the SSL
termination/renewal/etc. into the Grafana container and we don't have
to convince ourselves the container is safe to be directly web-facing.
Otherwise this is a fairly straight forward deployment of the
container. As before, it uses the graph configuration kept in
project-config which is loaded in with grafyaml, which is included in
the container.
Once nice advantage is that it makes it quite easy to develop graphs
locally, using the container which can talk to the public graphite
instance. The documentation has been updated with a reference on how
to do this.
Change-Id: I0cc76d29b6911aecfebc71e5fdfe7cf4fcd071a4
