summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorAlexander Sulfrian <alexander@sulfrian.net>2014-11-25 00:51:23 +0100
committerAlexander Sulfrian <alexander@sulfrian.net>2014-11-25 16:00:48 +0100
commitbe564316c7c4deaad090bfc0bc79c460965cb1d6 (patch)
tree38c7ab16fc403d8d067cdae1f91fcc3d9af07317 /doc
parentc544b18a985edd7444593e75ad52483f4842c119 (diff)
downloadbcfg2-be564316c7c4deaad090bfc0bc79c460965cb1d6.tar.gz
bcfg2-be564316c7c4deaad090bfc0bc79c460965cb1d6.tar.bz2
bcfg2-be564316c7c4deaad090bfc0bc79c460965cb1d6.zip
Bundler: add modification support to Bundle dependencies
Bundle dependencies are now realized with RequiredBundle and support inheritance of the modification flag. This requires new client support and will only work with clients >= 1.4.0pre2.
Diffstat (limited to 'doc')
-rw-r--r--doc/server/plugins/structures/bundler/bcfg2.txt2
-rw-r--r--doc/server/plugins/structures/bundler/index.txt24
2 files changed, 15 insertions, 11 deletions
diff --git a/doc/server/plugins/structures/bundler/bcfg2.txt b/doc/server/plugins/structures/bundler/bcfg2.txt
index 0fd0a3fdf..6d1159ae0 100644
--- a/doc/server/plugins/structures/bundler/bcfg2.txt
+++ b/doc/server/plugins/structures/bundler/bcfg2.txt
@@ -16,7 +16,7 @@ entries between Bundler and Rules.
.. code-block:: xml
<Bundle>
- <Bundle name="bcfg2-server-base.xml"/>
+ <RequiredBundle name="bcfg2-server-base.xml"/>
<Path name="/etc/pki/tls/private/bcfg2.key"/>
<Path name="/etc/sysconfig/bcfg2-server"/>
diff --git a/doc/server/plugins/structures/bundler/index.txt b/doc/server/plugins/structures/bundler/index.txt
index 31faeaf17..e6a9cf345 100644
--- a/doc/server/plugins/structures/bundler/index.txt
+++ b/doc/server/plugins/structures/bundler/index.txt
@@ -151,20 +151,20 @@ See :ref:`bcfg2-info <server-bcfg2-info>` for more details.
Dependencies
============
-Dependencies on other bundles can be specified by adding an empty
-bundle tag that adds another bundle by name, e.g.:
+Dependencies on other bundles can be specified by adding an
+RequiredBundle tag that adds another bundle by name, e.g.:
.. code-block:: xml
<Bundle>
- <Bundle name="nfs-client"/>
+ <RequiredBundle name="nfs-client"/>
...
</Bundle>
The dependent bundle is added to the list of bundles sent to the
-client, *not* to the parent bundle itself. In other words, if an
-entry in the dependent bundle changes, Services are restarted and
-Actions are run in the dependent bundle *only*. An example:
+client, *not* to the parent bundle itself. If you want to propagate
+the modification flag from the required bundle, you can add
+``modification="inherit"`` to the RequiredBundle tag. An example:
``nfs-client.xml``:
@@ -182,7 +182,7 @@ Actions are run in the dependent bundle *only*. An example:
.. code-block:: xml
<Bundle>
- <Bundle name="nfs-client"/>
+ <RequiredBundle name="nfs-client"/>
<Path name="/mnt/home"/>
<Path name="/etc/auto.master"/>
@@ -193,9 +193,13 @@ Actions are run in the dependent bundle *only*. An example:
If a new ``nfs-utils`` package was installed, the ``nfslock``,
``rpcbind``, and ``nfs`` services would be restarted, but *not* the
-``autofs`` service. Similarly, if a new ``/etc/auto.misc`` file was
-sent out, the ``autofs`` service would be restarted, but the
-``nfslock``, ``rpcbind``, and ``nfs`` services would not be restarted.
+``autofs`` service. If you would add ``modification="inherit`` to
+the RequiredBundle tag, you would ensure the propagation of the
+modification flag and the ``autofs`` service would be restarted,
+too. But if a new ``/etc/auto.misc`` file was sent out, *only* the
+``autofs`` service would be restarted, but the ``nfslock``,
+``rpcbind``, and ``nfs`` services would not be restarted
+(independent of the ``modification`` flag).
Altsrc
======