Cobbler-Register

cobbler-register - create a Cobbler system record

Synopsis

cobbler-register [--server=<cobbler.example.org>] --profile=<cobbler-profile-name> [--fqdn=<hostname>]

Description

Running cobbler-register on a system will create a Cobbler system record for that system on a remote Cobbler server. No changes will be made on the system itself.

Details

When installing new machines into a Cobbler managed datacenter/lab, it helps to not have to manually enter in the network information for those systems. Using cobbler-register either from a kickstart or a live environment (or even SSH) can help seed the Cobbler database.

Network information is discovered automatically for all physical interfaces. cobbler-register will attempt to discover the hostname, though if localhost.localdomain is found, it will have to use some other data for the Cobbler system record. This is probably not what you want, so specify --fqdn in this instance to override that registration value.

For this to work, the register_new_installs setting must be enabled on the remote Cobbler server.

When the remote system record is created, for safety reasons, it will be set in Cobbler to be “netboot disabled”. Use cobbler system edit --name=foo --netboot-enabled=1 to set the machine to reinstall, where “foo” is the name of the new system record.

Environment variables

cobbler-register respects the COBBLER_SERVER variable to specify the Cobbler server to use. This is a convenient way to avoid using the --server option. This variable is set automatically on systems installed via Cobbler, assuming standard kickstart templates are used. If you need to change this on an installed system, edit /etc/profile.d/cobbler.{csh,sh}.

Additional

Reading the Koan manpage, www.cobbler.github.io or this Readthedocs-Project is highly recommended.

Author

Michael DeHaan <michael.dehaan AT gmail>

Revised by: Enno Gotthold <matrixfueller@gmail.com>