Bcfg2 schema for declaring groups and associating groups with bundles. Declaration of a bundle as a member of a group. The bundle name The Group tag serves two purposes: * If it is at the top level of ``groups.xml`` (i.e., its direct parent is :xml:element:`Groups`), or if it has no children, then it is considered to declare a new group, and :xml:attribute:`MetadataGroupType:profile`, :xml:attribute:`MetadataGroupType:public`, :xml:attribute:`MetadataGroupType:category`, and :xml:attribute:`MetadataGroupType:default` are parsed. * If it is not at the top level of ``groups.xml`` *and* it has children, then it is considered to be a conditional; its children only apply to clients that are already members in the group. The attributes listed above are not parsed. Name of the group Mark the group as a profile, which allows a client to be directly associated with this group in :ref:`server-plugins-grouping-metadata-clients-xml`. Mark the group as public, which allows any client to assert membership in the group with ``bcfg2 -p``. Set as the profile to use for clients that are not associated with any profile explicitly in :ref:`server-plugins-grouping-metadata-clients-xml`. Setting ``default`` to ``true`` requires setting :xml:attribute:`MetadataGroupType:profile` to ``true`` as well. Assign the group to the given category. A client can only be a member of one group in a given category. When the Group tag is used as a conditional, only apply the child elements if the named group does not match. When the Group tag is used as a declaration, do not apply the named group to matching clients. Client tags are conditionals, and can be used to set per-client groups and bundles. The name of the client. Only apply the child tags if the named client does not match. Metadata group list top-level tag Nested ``Groups`` tags allowed to support XInclude Group schema version URI of master version (for common repository) Master version control revision