Here is a series of example configurations for Bcfg2, each introducing another layer of functionality.
Our example starts with the bare minimum configuration setup. We have a client, a profile group, a list of packages, and an NTP bundle.
<Clients> <Client profile='server' name='foo.bar.com'/> </Clients>
<Groups> <Group profile='true' name='server'> <Bundle name="ntp"/> </Group> </Groups>
<Bundle name="ntp"> <Package name='ntp'/> </Bundle>
<PackageList type='rpm' priority='0'> <Package name='ntp' version='4.2.0.a.20050816-11.FC5'/> </PackageList>
(This can also be performed more elegantly with the Packages plugin.)
Configure the service, and add it to Rules.
<Services priority='0'> <Service name='ntpd' status='on'/> </Services>
<Bundle name="ntp"> <Package name='ntp'/> <Service name='ntpd'/> </Bundle>
Setup an etc/ directory structure, and add it to the base:
# cat Cfg/etc/ntp.conf/ntp.conf server ntp1.utexas.edu
<Bundle name="ntp"> <Package name='ntp'/> <Service name='ntpd'/> <Path name='/etc/ntp.conf'/> </Bundle>
Bundles allow the grouping of related configuration entries that are used to provide a single service. This is done for several reasons:
The config file, package, and service are really all related components describing the idea of an ntp client, so they should be logically grouped together. We use a bundle to accomplish this.
<Bundle name='ntp'> <Package name='ntp'/> <Service name='ntpd'/> <Path name='/etc/ntp.conf'/> </Bundle>
After this bundle is created, it must be associated with a group (or groups). Add a bundle child element to the group(s) which should install this bundle.
<Groups> ... <Group profile='true' name='server'> <Bundle name="ntp"/> </Group> ... </Groups>
Once this bundle is created, a client reconfigure will install these entries. If any are modified, then the ntpd service will be restarted. If you only want ntp configurations to be updated (and nothing else), the bcfg2 client can be run with a -b <bundle name> option that will only update entries in the specified bundle.