Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Style and definition

...

We will use a generic term for this site management, Realms.

Realms in few words 

A realm is a pool of resources (scheduler, poller, reactionner, receiver and broker) that hosts or hostgroups that can be attached to. A host or hostgroup can be attached to only one realm. All "dependancies" or parents of this hosts must be in the same realm. A realm can be tagged "default"' and realm untagged hosts will be put into it. In a realm, pollers, reactionners and brokers will only get jobs from schedulers of the same realm.

Realms are different than the poller_tags

Make sure to undestand when to use realms and when to use poller_tags.

...

  • If you just need a poller in a DMZ network: use poller_tag
  • If you need a scheduler/poller in a customer LAN: use realms

Sub realms 

A realm can contain another realm. It does not change anything for schedulers: they are only responsible for hosts of their realm not the ones of the sub realms. The realm tree is useful for satellites like reactionners or brokers: they can get jobs from the schedulers of their realm, but also from schedulers of sub realms. Pollers can also get jobs from sub realms, but it's less useful so it's disabled by default. Warning: having more than one broker in a scheduler is not a good idea. The jobs for brokers can be taken by only one broker. For the Arbiter it does not change a thing: there is still only one Arbiter and one configuration whatever realms you have.

 

Example of realm usage 

Let's take a look at two distributed environnements. In the first case the administrator wants totally distinct daemons. In the second one he just wants the schedulers/pollers to be distincts, but still have one place to send notifications (reactionners) and one place for database export (broker).

...


Satellites can be used for their realm or sub realms too. It's just a parameter in the configuration of the element.

 

Variable Descriptions

 

PropertyDefaultDescription
realm_nameN/AThis variable is used to identify the *short name* of the realm.
realm_membersN/AThis directive is used to list realm sub-realms.
default0This directive is used to define if the realm is the default one or not. Only one default realm is allowed.

Example Definition

 

Code Block
  define realm{
      realm_name     World
      realm_members  Europe,America,Asia
      default        0
  }