bundle schema for bcfg2 Narayan Desai, Argonne National Laboratory Abstract implementation of a Package entry. The full specification will be included in Rules. Abstract implementation of a Path entry. The entry will either be handled by Cfg, TGenshi, or another DirectoryBacked plugin; or handled by Rules, in which case the full specification of this entry will be included in Rules. Abstract implementation of a Service entry. The full specification will be included in Rules. Abstract implementation of an Action entry. The full specification will be included in Rules. Fully bound description of a software package to be managed. Fully bound description of a filesystem path to be handled by the POSIX driver. Fully bound description of a system service to be managed. Fully bound description of a command to be run. Elements within Group tags only apply to clients that are members of that group (or vice-versa; see #element_negate below) The group name Negate the sense of this group; i.e., entries within this tag are only used on clients that are not members of the group A bundle describes a group of inter-dependent configuration entries, such as the combination of packages, configuration files, and service activations that comprise typical Unix daemons. Bundles are used to add groups of configuration entries to the inventory of client configurations, as opposed to describing particular versions of those entries. For example, a bundle could say that the configuration file ``/etc/passwd`` should be included in a configuration, but will not describe the particular version of ``/etc/passwd`` that a given client will receive. Abstract implementation of a Package entry. The full specification will be included in Rules. Abstract implementation of a Path entry. The entry will either be handled by Cfg, TGenshi, or another DirectoryBacked plugin; or handled by Rules, in which case the full specification of this entry will be included in Rules. Abstract implementation of a Service entry. The full specification will be included in Rules. Abstract implementation of an Action entry. The full specification will be included in Rules. Fully bound description of a software package to be managed. Fully bound description of a filesystem path to be handled by the POSIX driver. Fully bound description of a system service to be managed. Fully bound description of a command to be run. Elements within Group tags only apply to clients that are members of that group