diff options
Diffstat (limited to 'doc/plugins/generators')
| -rw-r--r-- | doc/plugins/generators/account.txt | 2 | ||||
| -rw-r--r-- | doc/plugins/generators/cfg.txt | 2 | ||||
| -rw-r--r-- | doc/plugins/generators/decisions.txt | 6 | ||||
| -rw-r--r-- | doc/plugins/generators/hostbase.txt | 6 | ||||
| -rw-r--r-- | doc/plugins/generators/nagiosgen.txt | 4 | ||||
| -rw-r--r-- | doc/plugins/generators/packages.txt | 2 | ||||
| -rw-r--r-- | doc/plugins/generators/pkgmgr.txt | 2 | ||||
| -rw-r--r-- | doc/plugins/generators/sshbase.txt | 6 |
8 files changed, 15 insertions, 15 deletions
diff --git a/doc/plugins/generators/account.txt b/doc/plugins/generators/account.txt index e07cef8b6..9a2718ce5 100644 --- a/doc/plugins/generators/account.txt +++ b/doc/plugins/generators/account.txt @@ -18,7 +18,7 @@ User access data is stored in three files in the Account directory: * rootlist (a list of user:host pairs for scoped root privs) * useraccess (a list of user:host pairs for login access) -SSH keys are stored in files named $username.key; these are installed into root's authorized keys for users in the superusers list as well as for the pertitent users in the rootlike file (for the current system). +SSH keys are stored in files named $username.key; these are installed into root's authorized keys for users in the superusers list as well as for the pertitent users in the rootlike file (for the current system). Authentication data is read in from (static|dyn).(passwd|group) The static ones are for system local ones, while the dyn. versions are for external synchronization (from ldap/nis/etc) There is also a static.limits.conf that provides the limits.conf header and any static entries. diff --git a/doc/plugins/generators/cfg.txt b/doc/plugins/generators/cfg.txt index 8ef9b17dc..e4e342842 100644 --- a/doc/plugins/generators/cfg.txt +++ b/doc/plugins/generators/cfg.txt @@ -89,7 +89,7 @@ info.xml files This feature is included in version 0.9.5pre3 and newer of the bcfg2 server. -info.xml files add the ability to specify different sets of file metadata on a group by group basis. These files are XML, and work similarly to those used by [wiki:Plugins/Rules Rules] or [wiki:Plugins/Pkgmgr Pkgmgr]. +info.xml files add the ability to specify different sets of file metadata on a group by group basis. These files are XML, and work similarly to those used by [wiki:Plugins/Rules Rules] or [wiki:Plugins/Pkgmgr Pkgmgr]. The following specifies a different global set of permissions (root/sys/0651) than on clients in group webserver (root/root/0652) diff --git a/doc/plugins/generators/decisions.txt b/doc/plugins/generators/decisions.txt index 17bc5c66c..079e748f9 100644 --- a/doc/plugins/generators/decisions.txt +++ b/doc/plugins/generators/decisions.txt @@ -4,9 +4,9 @@ Decisions ========= -This page describes the Decisions plugin. The client has support for a centralized set of per-entry installation decisions. This approach is needed when particular changes are deemed "high risk"; this gives the ability to centrally specify these changes, but only install them on clients when administrator supervision is available. Because collaborative configuration is one of the remaining hard issues in configuration management, these issues typically crop up in environments with several administrators and much configuration variety. +This page describes the Decisions plugin. The client has support for a centralized set of per-entry installation decisions. This approach is needed when particular changes are deemed "high risk"; this gives the ability to centrally specify these changes, but only install them on clients when administrator supervision is available. Because collaborative configuration is one of the remaining hard issues in configuration management, these issues typically crop up in environments with several administrators and much configuration variety. -In these cases, the client can be configured to run in either a whitelist or blacklist mode, wherein a list of entries is downloaded from the server. The client uses this list to determine which incorrect entries should be corrected during the current run of the installation tool. The Decision plugin is the only stock plugin that generates entries for client's whitelists or blacklists. +In these cases, the client can be configured to run in either a whitelist or blacklist mode, wherein a list of entries is downloaded from the server. The client uses this list to determine which incorrect entries should be corrected during the current run of the installation tool. The Decision plugin is the only stock plugin that generates entries for client's whitelists or blacklists. The Decision plugin uses a directory in the bcfg2 repository called Decisions. Files in the Decisions subdirectory are named similarly to files managed by Cfg, probes, TCheetah, and TGenshi. File basenames are either whitelist or blacklist. These files have a simple format; the following is an example. @@ -24,6 +24,6 @@ The Decision plugin uses a directory in the bcfg2 repository called Decisions. F vim: ft=xml --> -This example, included as a whitelist due to its name, enables all services, and the path entry named /etc/apt/apt.conf to be installed on systems running in whitelist mode; all other entry installation will be surpressed. +This example, included as a whitelist due to its name, enables all services, and the path entry named /etc/apt/apt.conf to be installed on systems running in whitelist mode; all other entry installation will be surpressed. When a client askes for its whitelist or blacklist, all of the files pertaining to that client of the correct type are aggregated into a single list. This list is sent to the client. Note that this list is only generated when a client is run with the appropriate option (-l (whitelist|blacklist)); client behavior is not controlled unless this option is used. diff --git a/doc/plugins/generators/hostbase.txt b/doc/plugins/generators/hostbase.txt index 4b85fecd0..a03dd2f82 100644 --- a/doc/plugins/generators/hostbase.txt +++ b/doc/plugins/generators/hostbase.txt @@ -34,9 +34,9 @@ Create the hostbase database and a user. For MySQL users:: mysql> CREATE DATABASE hostbase mysql> quit - + systemprompt#: mysql -u root hostbase - mysql> GRANT ALL PRIVILEGES ON *.* TO hostbaseuser@mycomputer.private.net IDENTIFIED + mysql> GRANT ALL PRIVILEGES ON *.* TO hostbaseuser@mycomputer.private.net IDENTIFIED BY 'password' WITH GRANT OPTION; mysql> quit @@ -164,7 +164,7 @@ Authentication Edit Django settings -------------------- -Django allows for custom authentication backends to its login procedure. Hostbase has an NIS authentication backend that verifies a user to be in the unix group allowed to modify Hostbase. +Django allows for custom authentication backends to its login procedure. Hostbase has an NIS authentication backend that verifies a user to be in the unix group allowed to modify Hostbase. To enable this feature: * first edit your {{{Hostbase/settings.py}}} file and uncomment the line {{{'Hostbase.backends.NISBackend',}}} in the list of {{{AUTHENTICATION_BACKENDS}}} diff --git a/doc/plugins/generators/nagiosgen.txt b/doc/plugins/generators/nagiosgen.txt index 55b6063a5..fd33fe374 100644 --- a/doc/plugins/generators/nagiosgen.txt +++ b/doc/plugins/generators/nagiosgen.txt @@ -4,7 +4,7 @@ NagiosGen ========= -This page describes the installation and use of the [http://trac.mcs.anl.gov/projects/bcfg2/browser/trunk/bcfg2/src/lib/Server/Plugins/NagiosGen.py NagiosGen] plugin. +This page describes the installation and use of the [http://trac.mcs.anl.gov/projects/bcfg2/browser/trunk/bcfg2/src/lib/Server/Plugins/NagiosGen.py NagiosGen] plugin. Update /etc/bcfg2.conf, adding NagiosGen to plugins:: @@ -55,7 +55,7 @@ Create default host, and group specs in: retain_status_information 1 retain_nonstatus_information 1 is_volatile 0 - + check_period 24x7 max_check_attempts 4 check_interval 5 diff --git a/doc/plugins/generators/packages.txt b/doc/plugins/generators/packages.txt index 837a6b14a..c7ac2deea 100644 --- a/doc/plugins/generators/packages.txt +++ b/doc/plugins/generators/packages.txt @@ -1,4 +1,4 @@ -.. -*- mode: rst -*- +.. _plugins-generators-packages: ======== Packages diff --git a/doc/plugins/generators/pkgmgr.txt b/doc/plugins/generators/pkgmgr.txt index b6940f9b1..fc15fad79 100644 --- a/doc/plugins/generators/pkgmgr.txt +++ b/doc/plugins/generators/pkgmgr.txt @@ -1,4 +1,4 @@ -.. -*- mode: rst -*- +.. _plugins-generators-pkgmgr: ====== Pkgmgr diff --git a/doc/plugins/generators/sshbase.txt b/doc/plugins/generators/sshbase.txt index 65fe1cca7..4741fc8eb 100644 --- a/doc/plugins/generators/sshbase.txt +++ b/doc/plugins/generators/sshbase.txt @@ -21,13 +21,13 @@ Interacting with SSHbase Aliases ======= -As of 1.0pre4, SSHbase has support for Aliases listed in clients.xml. The address for the entries are specified either through DNS (e.g. a CNAME), or via the address attribute to the Alias. +SSHbase has support for Aliases listed in clients.xml. The address for the entries are specified either through DNS (e.g. a CNAME), or via the address attribute to the Alias. Getting started =============== #. Add SSHbase to the generators line (plugins line in 1.0 or greater) in /etc/bcfg2.conf and restart the server -- This enables the SSHbase plugin in the bcfg2 server. -#. Add ConfigFile entries for /etc/ssh/ssh_known_hosts, and /etc/ssh/ssh_host_dsa_key, etc to a bundle or base. +#. Add Path entries for /etc/ssh/ssh_known_hosts, and /etc/ssh/ssh_host_dsa_key, etc to a bundle or base. #. Enjoy. At this point, SSHbase will generate new keys for any client without a recorded key in the repository, and will generate an ssh_known_hosts file appropriately. @@ -35,4 +35,4 @@ At this point, SSHbase will generate new keys for any client without a recorded Blog post ========= -[http://www.ducea.com/2008/08/24/using-the-bcfg2-sshbase-plugin/] +http://www.ducea.com/2008/08/24/using-the-bcfg2-sshbase-plugin/ |