opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
20.5.4 opsi hostgroup: opsihostgroups.cfg
164 / 193
The nest step is to define the hostgroups. This helps to structure the display of the results as well as the service
definitions.
So create a file named opsihostgroups.cfg wit the following content:
define hostgroup {
hostgroup_name opsi-clients
alias OPSI-Clients
}
define hostgroup {
hostgroup_name opsi-server
alias OPSI-Server
members configserver.domain.local, depotserver.domain.local
}
Do not forget to edit the member line.
20.5.5 opsi server: .cfg
The next step is to create for every opsi server you are running an own configuration file. This file should be named
based on the pattern .cfg. For example configserver.domain.local.cfg.
(You may also create one file (e.g. opsihost.cfg with all server definitions).
The content should look like this:
define host{
use opsi-server-tmpl
host_name configserver.domain.local
hostgroups opsi-server
alias opsi Configserver
address configserver.domain.local
}
define host{
use opsi-server-tmpl
host_name depotserver.domain.local
hostgroups opsi-server
alias opsi Depotserver
address depotserver.domain.local
}
Explanation of the entries: * use references to the used template. * hostgroups tells us to which hostgroup this server
belongs.
20.5.6 opsi Clients: clients/.cfg
The opsi client configurations should be placed in an own sub directory. They should be defined like this:
define host{
use opsi-client-tmpl
host_name client.domain.local
hostgroups opsi-clients
alias opsi client
address client.domain.local
_depotid depotserver.domain.local
}
This client configuration uses again a custom variable: _depotid. This custom variable may be referenced by the
macro $_HOSTDEPOTID$.