distro_mgr - Distribution Object Manager, used to manipulate sofware configuration attributes in the database




distro_mgr [--help] [--man] [--db connectstring] [--new <dist_name>... [--type <class>] [--collection <name>]] [--copy <from> <to> [--type <class>] [--collection <name>]] [--destroy <dist_name>... [--cleanup]] [[--get] <dist_name>... [--<attribute>] | [(--image|--overlay <name>) [--<directive> (ALL|<target>)]]] [--set <dist_name>... [--<attribute> <value>] | [(--image|--overlay <name>) --<directive> (ALL|<target>) <value>]] [--remove <dist_name>... [--<attribute>] | [(--image|--overlay <name>) --<directive> (ALL|<target>)]] [--types [<class>]] [--find [<class>]] [--methods [<class>] [--diff <dist_name1> <dist_name2>]


This tool is used to manage Distro objects in the CIToolkit configuration database. It can be used to create new Distros, remove existing ones, as well as duplicate an existing Distro object with a new name.

distro_mgr can also be used to modify attributes of existing Distro objects. By specifying either --image or --overlay <name>, the SoftConf sub-objects can be manipulated. See the SoftConf documentation for a list of available directives.

If neither --image or --overlay are specified, distro_mgr will act on simple attributes of the Distro object itself.

distro_mgr must be passed the name of an existing Distro object, or the name of a collection which contains Distro objects, or the name of a new Distro to create.


-new <dist_name>... Create a new Distro object and add it to the database. May be used with --type and --collection.

--copy <from> <to> Create a new Distro object with the same attributes as an existing one. May be used with --type and --collection.

--type <class> When creating a Distro object with either --new or --copy, change the object type (class) of the new object. Any attributes in the old object not supported by the new type will be dropped.

--collection <name> When createing a new Distro with either --new or --copy, also add the new object to the specified existing collection.

--find [<class>] List all Distro objects in the database, or all objects of the given subclass (eg. Distro::RPM::SuSE) Might be slow for very large databases as every object must be fetched and checked to see if it is an alias. (may not be combined with other options)

--types [<class>], --classes [<class>] List the types of objects that are supported by this tool, as well as shortcut names may be used with the --type option. You may optionally specify a class to display the subclasses of.

--methods [<class>] Display the methods implemented by the Distro class, or specify a particular class of which to view method information, including parent classes.

--get <dist_name>... Display information about existing Distro objects. This is the default action. When specified with the --image or --overlay <name> options, operate on the given SoftConf sub-object. The output can be further restrictd by specifying the SoftConf directive name followed by either the target name or keyword ``ALL''. For example, ``--overlay common'' will display the configuration directives for the overlay named ``common''. The options ``--image --link ALL'' will display all symlinks that will be created in the image. If neither --image nor --overlay <name> are specified, then distro_mgr will act on simple attributes of the Distro object itself. For example, use ``--get --source_dir'' to display the directory path from which the base image will be created. If one or more SoftConf directives are specified without --image or --overlay <name>, then those directives will be shown for the image and all overlays.

--set <dist_name>... Change attributes for existing Distro objects. Usage is similar to --get, but an additional argument must follow the target name, to specify the value to use. For example, ``--set --overlay compute --service syslog-ng 1'' will enable the startup of the syslog-ng client on compute nodes. The options ``--set --image --delete ALL 0'' will dissable the removal of all files and directories already configured for deletion from the image. Note that it is not possible to set an entire image or overlay. --<directive <target>> must be specified

--remove <dist_name>... Remove attributes from existing Distro objects. Usage is the same as for --get. Note that it is not possible to remove an entire image or overlay. --<directive <target>> must be specified

--destroy <dist_name>... Remove the existing Distro object or objects from the database. If it was part of any collections, or referenced by any Aliases, then a warning of dangling references will be reported.

--cleanup Used with --destroy, remove all references (Aliases or Collection membership) to the removed Distro, instead of warning about dangling references.

--diff <dist_name1> <dist_name2> Display the differences between two Distro objects. (may not be combined with other options)

--db <connectstring> Database type and connection information. For GDBM, "GDBM:" followed by the filename of the cluster database to use. For LDAP, the syntax is "LDAP:host:port:dbname"

--help Print extended usage information

--man Print this manpage.



The default paths for location of the cluster configuration database, cloned directories, supporting libraries, and other settings are recorded in the config file. Set the environment variable CLUSTER_CONFIG to the location of, or use the default of /cluster/config


device_mgr, alias_mgr, collection_mgr, db_mgr, lookup