cclone - utility to clone/install diskfull nodes in a CIT cluster




cclone (also known as 'cyclone') is a front end utility used for cloning/ installing diskfull nodes in a CIT cluster. The utility will use different methods for installing a diskfull node depending on default values in, attributes for nodes in the CIT database, and command line options.


cclone [OPTION]


--kickstart --ks -ks Use a kickstart cloning process

--kstarget Specify the kickstart target to use in the PXE config file. Otherwise, cclone will figure it out based on and node attributes.

--rsync Use the rsync cloning process (CIT default) which is bootstrapped by a diskless boot. Thus, this cloning method requires a working diskless configuration.

--wait Specify the number of seconds that cclone will wait before starting to check for completion of the cclone process. Default is 600 seconds.

--dry[run] Do everything but that cloning would do without actually doing any cloning or power cycling.

--delay Specify the number of seconds that cclone will delay between starting up parallel executing commands. Default is 2 seconds.

--update Just do an update of a cloned node as opposed to a full clone. Depending on how a node was cloned and where updated files are located (base image versus overlays), files will be updated differently. The best strategy for centrally managing files and propagating them to nodes regardless of whether they are diskless or diskfull cloned via rsync or diskfull cloned via kickstart is to put them in the overlays structure. Then build_diskfull --update and build_diskless --update will pick up changes to nodes without having to do a full reclone (which of course doesn't apply to diskless!).

--man Print this manpage.

--help --usage Print command-line usage information

--debug n Where n is a numeric level of debug information required, prints extra output for debugging purposes from the utility itself.

--libdebug class Enable debug output from the comma separated list of libraries. Where class is the class from the base libs that you wish to output debug information from. Ex. cclone n0 --libdebug MkConf::pxelinux


If neither --kickstart or --rsync parameters are given on the command- line, cclone attempts to figure out the proper cloning method (as configured that is) for each node individually (i.e. each node can potentially be using a different method or configuration within a method) using the following steps in order: 1) checking for the existence of a clone_method attribute for the node and a valid method 2) checking for a default clone_method attribute for the cluster 3) giving up!

Supported values for clone_method are 'rsync' and 'kickstart'.

If a kickstart cloning method is specified, then cclone also needs to decide on a 'kickstart target' to boot the node into. A kickstart target is a short way of saying that the node is configured to boot using the proper kernel image, possible initrd image, and kernel bootline options specifying the kickstart config file so that the kickstart process can be started. Usually this means generating an appropriate PXE config file for a node and setting the DEFAULT line accordingly. When a cluster is being integrated and kickstart cloning of nodes is desired, appropriate kickstart config files and PXE targets need to be setup. PXE targets for kickstarting are configured by editing the CIT_pxe_include file (or the file specified by the CConf::{pxe_include_file} attribute). See the Perldoc documentation on mk_conf (perldoc /path/mk_conf) for more information on the PXE include file. If a cluster is configured using a CIT system architecture (sysarch) that has support for kickstarting nodes, Kickstart config file samples/templates are installed in /cluster/clone/kickstart. If not, look through the CIT distribution source tree in the 'config' tree for sysarches that have kickstart support (i.e. they have a clone subdir).







Questions, comments, bugs should be sent to