Changes between Version 2 and Version 3 of Web/QuattorClientUsage

Timestamp:

Mar 21, 2010, 10:23:09 AM (14 years ago)

Author:

loomis

Comment:

--

Web/QuattorClientUsage

@@ -5 +5 @@
 = Fetching profiles =
 Quattor configuration information is stored in configuration profiles, which are XML files retrieved from a server (normally over HTTP/S). Profiles are usually fetched at regular intervals from the server. If you want to manually pull down a profile on a node, use the following command:
+{{{
+ [root@client-node root]# ccm-fetch
+}}}
 
- [root@client-node root]# ccm-fetch
-
-
-If this command returns almost immediately, then the profile is up to date. If it takes a little longer, then a new profile is being fetched. To force the profile to be retrieved from the server, use the -f flag to ccm-fetch.
+If this command returns almost immediately, then the profile is up to date. If it takes a little longer, then a new profile is being fetched. To force the profile to be retrieved from the server, use the -f flag to '''ccm-fetch'''.
 
 = Configuring a node =
 Quattor configuration is performed by '''components''' which are named ncm-<component-name>. Examples are ncm-accounts which configures the user accounts on the system. Components are configured like this:
-
+{{{
  ncm-ncd --co accounts
-
+}}}
 This will also configure any components defined as pre- or post-dependencies. For example, the package manager spma is normally defined as a pre-dependency.
 
 == Configuring all components ==
 To configure all components defined in the profile, use the <tt>-all</tt> flag to ncm-ncd:
-
+{{{
  ncm-ncd --co -all
+}}}
 
 == Configuring a single component ==
 To prevent pre- and post-dependencies from being configured:
-
+{{{
   ncm-ncd --co accounts --nodeps --autodeps no
+}}}
 
 = Query configuration =
 To find out what the currently-active profile contains, use the ncm-query command. You can either query by component name, or by path in the tree. Here's an example of querying the configuration of a component:
-
+{{{
  [root@client-node root]# ncm-query --co ccm
  
@@ -52 +54 @@
    $ retrieve_wait : (long) '30'
    $ world_readable : (long) '1'
-
+}}}
 And here's an example of querying a specific path:
-
+{{{
  [root@client-node root]# ncm-query --dump /hardware/harddisks/hda
  
@@ -63 +65 @@
    $ interface : (string) 'ide'
    $ model : (string) 'Generic IDE disk'
+}}}
 
 = Package management =
@@ -72 +75 @@
 
 spma is normally invoked via its controlling component:
-
+{{{
  [root@client-node root]# ncm-ncd --co spma
  
@@ -82 +85 @@
  [OK] /usr/bin/spma --quiet finished succesfully (please check spma.log)
  [INFO] configure on component spma executed, 0 errors, 0 warnings
-
-This will (re)generate the package list (/var/lib/spma-target.cf) from
+}}}
+This will (re)generate the package list (`/var/lib/spma-target.cf`) from
 the profile and run spma. If this procedure fails, you can see why by
-inspecting spma's log file at /var/log/spma.log. SPMA runs may fail
+inspecting spma's log file at `/var/log/spma.log`. SPMA runs may fail
 due to dependency problems as it is very difficult to check
 dependencies at the time the node templates are compiled. (You may