1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
.. -*- mode: rst -*-
.. _server-plugins-generators-decisions:
=========
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.
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
Decisions plugin is the only stock plugin that generates entries for
client's whitelists or blacklists.
The Decisions 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 (so you can use host-
and group-specific files and the like after their basename). File basenames
are either ``whitelist`` or ``blacklist``. These files have a simple format;
the following is an example.
.. code-block:: xml
$ cat Decisions/whitelist
<Decisions>
<Decision type='Service' name='*'/>
<Decision type='Path' name='/etc/apt/apt.conf'/>
</Decisions>
.. note:: To add syntax highlighting in vim, you can add a modeline such as this:
<!--
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``. All these entries must
already be present in your repository, the Decisions plugin just references
them. In whitelist mode, only the given items are applied to the client; all
other entry installation will be surpressed.
In blacklist mode, every entry that is not blacklisted will be installed.
When a client asks 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:: This list is only generated when a client is explicitly run with
the appropriate option (``-l (whitelist|blacklist)``); client
behavior is not controlled unless this option is used. If you do
not use Decisions, all your entries will be installed normally.
.. note:: Also, using this plugin does not present additional prompts or
safety nets to the administrator running the client, you have to
control these via their respective options (``-I`` or ``-n``, for
example).
|
