1
edit
Changes
no edit summary
The profile determines the primary group that this client is associated with and ultimately defines how it will be configured. The '''name''' indicates the fully qualified domain name. The '''FQDN''' must resolve to the IP address of the host and the IP must resolve to the FQDN. If the resolving is done through a hosts file, the name given to a client must match the first entry in the host file for that IP address. The '''pingable''' and '''pingtime''' entries should be left as default and are not covered in this documentation.
==Client Side==
To ensure that a client is up to date, or to test a configuration without changing anything on the client use the command:
<pre>bcfg2 -vqn </pre>
=The BCFG2 Configuration Management System=
===Bundles===
Bundles are a means of defining configuration elements to be pushed out to clients. Bundles are defined in /var/lib/bcfg2/Bundler as XML files, the contents of which are the name of the file and where it located on the server. Bundle declarations for files must also contain a declaration of the file path. For example: if there is a bundle used named "hosts" which contains the file "/etc/hosts", there would need to be a file present in /var/lib/bcfg2/Bundler called "hosts.xml". The contents of such a file are as follows:
<pre>
<Bundle name='BUNDLE NAME' version='2.0'>
<Path name='/PATH/TO/FILE' />
</Bundle>
</pre>
Bundles can also be used to define packages that must be installed. The use of this feature will be discussed later in this documentation.
Bundles are assigned in groups.xml file using the following entry placed within the group tags:
<pre>
<bundle name="BUNDLE NAME" />
</pre>
=Sources=
