diff options
Diffstat (limited to 'doc/unsorted/annotated_examples.txt')
| -rw-r--r-- | doc/unsorted/annotated_examples.txt | 39 |
1 files changed, 22 insertions, 17 deletions
diff --git a/doc/unsorted/annotated_examples.txt b/doc/unsorted/annotated_examples.txt index 99c6f774c..b5b7e6b4e 100644 --- a/doc/unsorted/annotated_examples.txt +++ b/doc/unsorted/annotated_examples.txt @@ -11,7 +11,8 @@ ntp example Author: Jason Pepas -Here is a series of example configurations for bcfg2, each introducing another layer of functionality. +Here is a series of example configurations for bcfg2, each introducing +another layer of functionality. * After each change, run 'bcfg-repo-validate -v'. * Run the server with 'bcfg2-server -v'. @@ -20,7 +21,8 @@ Here is a series of example configurations for bcfg2, each introducing another l package only ------------ -Our example starts with the bare minimum configuration setup. We have a client, a profile group, a list of packages, and a base configuration. +Our example starts with the bare minimum configuration setup. We have +a client, a profile group, a list of packages, and a base configuration. :: @@ -77,7 +79,7 @@ Setup an etc directory structure, and add it to the base.:: <Group name='fedora'> <Package name='ntp'/> <Service name='ntpd'/> - <ConfigFile name='/etc/ntp.conf'/> + <Path name='/etc/ntp.conf'/> </Group> </Base> @@ -86,10 +88,10 @@ create a bundle The above configuration layout works fine for a single service, but that method of organization would quickly become a nightmare as you -approach the number of packages, services, and config files required -to represent a fully configured host. Bundles allow the grouping of -related configuration entries that are used to provide a single -service. This is done for several reasons: +approach the number of packages, services, and config files required to +represent a fully configured host. Bundles allow the grouping of related +configuration entries that are used to provide a single service. This +is done for several reasons: * Grouping related things in one place makes it easier to add those entries for a multiple groups of clients @@ -102,20 +104,20 @@ service. This is done for several reasons: entity in that bundle is modified. This ensures that new configuration files and software are used after installation. -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.:: +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.:: # cat Bundler/ntp.xml <Bundle name='ntp' version='2.0'> <Package name='ntp'/> <Service name='ntpd'/> - <ConfigFile name='/etc/ntp.conf'/> + <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). Add a bundle child element to the group(s) which should install +this bundle.:: # cat Metadata/groups.xml @@ -146,8 +148,8 @@ I added a new bundle: .. code-block: xml <Bundle name="mysql-server" version="3.0"> - <ConfigFile name="/root/bcfg2-install/mysql/users.sh"/> - <ConfigFile name="/root/bcfg2-install/mysql/users.sql"/> + <Path name="/root/bcfg2-install/mysql/users.sh"/> + <Path name="/root/bcfg2-install/mysql/users.sql"/> <PostInstall name="/root/bcfg2-install/mysql/users.sh"/> <Package name="mysql-server-4.1"/> <Service name="mysql"/> @@ -162,14 +164,17 @@ The `users.sh` script looks like this: mysql --defaults-extra-file=/etc/mysql/debian.cnf mysql \ < /root/bcfg2-install/mysql/users.sql -On debian there is a user account in `/etc/mysql/debian.cnf` automatically created, but you could also (manually) create a user in the database that has enough permissions and add the login information in a file yourself. This file looks like this:: +On debian there is a user account in ``/etc/mysql/debian.cnf`` +automatically created, but you could also (manually) create a user in +the database that has enough permissions and add the login information +in a file yourself. This file looks like this:: [client] host = localhost user = debian-sys-maint password = XXXXXXXXXX -The `users.sql` looks like this:: +The ``users.sql`` looks like this:: DELETE FROM db; INSERT INTO db VALUES ('localhost', 'phpmyadmin', 'pma', 'Y', 'Y', |