juju controller #1

  • By xavpaice
  • Latest version (#1)
  • xenial, bionic
  • Stable

Description

In order to add subordinate charms such as nrpe, we need to have a primary
unit to relate them to. This charm provides that primary.


Overview

This charm provides a principal Juju unit so that we relate things like nrpe,
landscape-client, etc., to service the Juju controllers in a controller model.
Typically we want to do this when we have Nagios in a separate model and wish
to use cross model relations to allow monitoring and updates of the controller
machines.

Usage

In order to monitor a controller on machine 0 in a model named 'controller':

juju switch controller
juju deploy cs:~xavpaice/juju-controller --to 0 juju-controller
juju deploy cs:nrpe nrpe-controller
juju add-relation nrpe-controller juju-controller
juju config nrpe-controller nagios_host_context=mysitename
juju offer nrpe-controller:monitors
  Application "nrpe" endpoints [monitors] available at "admin/controller.nrpe-controller"

juju switch $nagiosmodel
juju add-relation nagios admin/controller.nrpe-controller

Bugs

TODO

Configuration

nagios_servicegroups
(string) A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup
nagios_context
(string) Used by the nrpe subordinate charms. A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-myservice-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.
juju