[wishlist] apps where we have different deployments on container and metal need splitting out

[Xav Paice]

In the example of nrpe subordinates, we have a version for use with containers, where we disable monitors such as disk space and load. It would be good to report on subordinates named, e.g., nrpe-container or nrpe-lxd, that are located on a non-container machine (and the opposite too).

[James Hebden (ec0)]

The current code simply checks for presence of a unit with a given source charm name. So, a check for nrpe will pick up nrpe-container and nrpe-physical.
I think with this in mind, a neater way to handle this would be able to check charm configuration, regardless of how the charm was placed on a machine (via an nrpe-physical or nrpe-container charm), conditional to whether or not the machine being checked is a container or physical host.

That way you could do something like -

openstack physical charms:
  nrpe:
    load:
      eq: "-w 10,10,10 -c 25,25,25"
openstack container charms:
  nrpe:
    load:
      eq: ""

And any of the NRPEs deployed to physical machines would have their config checked against the first value, and any NRPEs deployed to containers, the second.

In your view, would this address the use case you are describing?