Merge ~rharding/charm-telegraf:update-2.3 into ~telegraf-charmers/charm-telegraf:master
Status: | Merged |
---|---|
Approved by: | Haw Loeung |
Approved revision: | b621eee2d4324a82ab6b2958278acfb7040dfdaf |
Merged at revision: | 9512ea7934dba8adff992b6b74228420e3d9fce0 |
Proposed branch: | ~rharding/charm-telegraf:update-2.3 |
Merge into: | ~telegraf-charmers/charm-telegraf:master |
Diff against target: |
86 lines (+40/-33) 1 file modified
reactive/telegraf.py (+40/-33) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Haw Loeung | Approve | ||
Review via email: mp+332427@code.launchpad.net |
Description of the change
Add support for using network-get in updated charm-helpers to fetch the correct IP address to send across the relation.
Per the new upcoming documentation here:
https:/
This allows for using cross model relations from telegraf to a centralized prometheus instance and is meant to provide an example of charms to leverage network-get to help determine if a public or private address should be sent to a related application.
QA instructions:
CMR QA - Juju 2.3beta
You need two controllers
juju bootstrap google bigbrother
juju bootstrap aws monitorme
juju switch bigbrother
juju deploy cs:~rharding/
juju expose prometheus
juju offer prometheus:target offerprom
juju switch monitorme
juju deploy ubuntu
juju deploy cs:~rharding/
juju relate ubuntu:juju-info telegraf
juju consume bigbrother:
juju relate telegraf:
juju switch bigbrother
juju show-machine 0
<get the public IP of prometheus and load it in the browser <ip>:9090
<open the status->targets list and make sure you see the CMR with the public IP address of the telegraf unit in AWS>
LGTM, +1