This repository has been archived by the owner on Oct 24, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Use a task to create the influxdb/grafana per-run info #54
Comments
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 18, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
bbangert
added a commit
that referenced
this issue
Apr 19, 2017
Locks down the metrics node to the load-test nodes for metrics and restricts outside grafana access to the Grafana SG. Closes #54
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The only remaining thing to lock-down in the security-group is the metrics instance. To fully lock it down, ardere won't be able to directly communicate with it. To create the influxdb database and grafana dashboard/datasource, we'll need to run a few commands on the metrics host directly via a task definition we run per-run instead.
The text was updated successfully, but these errors were encountered: