From a6b6871ecbc700229969f350b869bd19e785129d Mon Sep 17 00:00:00 2001 From: "Chris St. Pierre" Date: Wed, 15 Aug 2012 14:53:18 -0400 Subject: Removed deprecated plugins BB, Svcmgr, SGenshi --- doc/appendix/files/ntp.txt | 93 ++++++++++++++++++++++------------------------ 1 file changed, 45 insertions(+), 48 deletions(-) (limited to 'doc/appendix') diff --git a/doc/appendix/files/ntp.txt b/doc/appendix/files/ntp.txt index 53b3347c8..38d5e2208 100644 --- a/doc/appendix/files/ntp.txt +++ b/doc/appendix/files/ntp.txt @@ -19,95 +19,92 @@ 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. +a client, a profile group, a list of packages, and an NTP bundle. ``Metadata/clients.xml``: .. code-block:: xml - - + + ``Metadata/groups.xml``: .. code-block:: xml - - + + + + -``Base/base.xml``: +``Bundler/ntp.xml``: .. code-block:: xml - - - - - + + + ``Pkgmgr/packages.xml``: .. code-block:: xml - + +(This can also be performed more elegantly with the +:ref:`server-plugins-generators-pacakges` plugin.) + Add service ----------- -Configure the service, and add it to the base. +Configure the service, and add it to Rules. -``Svcmgr/services.xml``: +``Rules/services.xml``: .. code-block:: xml - + -``Base/base.xml``: +``Bundler/ntp.xml``: .. code-block:: xml - - - - - - + + + + Add config file --------------- -Setup an ``etc/`` directory structure, and add it to the base.:: +Setup an ``etc/`` directory structure, and add it to the base:: # cat Cfg/etc/ntp.conf/ntp.conf server ntp1.utexas.edu ``Base/base.xml``: +``Bundler/ntp.xml``: + .. code-block:: xml - - - - - - - + + + + + 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: +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 multiple groups of clients @@ -128,10 +125,10 @@ logically grouped together. We use a bundle to accomplish this. .. code-block:: xml - - - - + + + + After this bundle is created, it must be associated with a group @@ -143,15 +140,15 @@ install this bundle. .. code-block:: xml - ... - - - - ... + ... + + + + ... -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 +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 `` option that will only update entries in the specified bundle. -- cgit v1.2.3-1-g7c22