Please add support for network bindings
Bug #1893180 reported by
Xav Paice
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Prometheus libvirt exporter charm |
New
|
High
|
Unassigned |
Bug Description
In a situation where a compute host has multiple addresses, e.g. a management network and an openstack overlay network, we need to be able to control which network is used for the binding for the prometheus relation. In one particular case, the compute hosts supplied the address from the overlay network to Prometheus for the target address, which is unreachable from the prometheus host.
Changed in charm-prometheus-libvirt-exporter: | |
importance: | Undecided → High |
Changed in charm-prometheus-libvirt-exporter: | |
assignee: | nobody → Joe Guo (guoqiao) |
status: | Confirmed → In Progress |
milestone: | none → 21.04 |
Changed in charm-prometheus-libvirt-exporter: | |
assignee: | Joe Guo (guoqiao) → nobody |
status: | In Progress → New |
milestone: | 21.04 → none |
To post a comment you must log in.
The http interface type used on the scrape interface takes an optional "hostname=" argument to scrape_ service. configure.
If unspecified, this runs: hookenv. unit_get( 'private_ address' )
This should be run in the reactive module to set hostname of the interface to the scrape binding in "configure_ scrape_ relation" :
scrape_ service. configure(
PORT_NUMBER, hostname= hookenv. network_ get_primary_ address( 'scrape' )
)