Extra XML provided by the user. Must have a namespace. Beaker will preserve the XML when cloning the job. Specifies the user who will be the owner of this job. This requires that the submitting user is a valid delegate of the user. Specifies the group this job was submitted on behalf of. This will allow other group members to view and modify this job. Specifies the data retention policy for the job. See http://your-beaker-server/retentiontag/ for the possible values. Some of these tags may require a product to be specified (see below). Specifies the product with which this job is associated. The product names are customized to suit a beaker deployment and hence there there are no standard or default product names shipped with Beaker. Note that this specification is meaningful only for retention tagging purposes (see above). A textual description of this job, for human consumption only. A recipeset defines one or more recipes which are to be run in parallel. Define multiple recipes within a recipeset for multihost testing. Otherwise, define only one recipe within the recipeset. Sets the scheduling priority of this job. Possible values are low, medium, normal, high and urgent. Low Medium Normal High Urgent This element is a container for configuring notifications that this job has finished running. An e-mail address which will be cc'ed on the job completion e-mail. A recipe is a sequence of tasks which are run on a single system, in parallel with any other recipes in the same recipeset. The system is always provisioned with an operating system at the start of each recipe. Options for provisioning are contained within this element. Additional kernel options to be passed to Anaconda during installation. Additional kernel options to be passed to Anaconda after installation. Additional kickstart metadata variables. If a role is specified, an environment variable of the same name will be created on each of the hosts the test runs. The value of the environment variable will be set to a space-separated list of all the host names in that role. If there are multiple roles, there will an environment variable for each of them present on all the hosts the test runs. Useful for multihost tests (see the role attribute for the task element). A textual description of this recipe, for human consumption only. You can specify a custom kickstart template here. This template should be a valid Jinja2 template. Review the existing kickstart templates to get an idea of what you can specify here. Beaker will add extra "defaults" based on the system options specified in the recipe such as the architecture and distro. This element is a container for expressing constraints on the operating system distribution which will be selected and provisioned at the start of this recipe. This element is a container for specifying the operating system distribution which will be provisioned at the start of this recipe. This element is a container for expressing constraints on the system which will be selected to run this recipe. Select a specific system by FQDN. This bypasses the normal filtering mechanisms for selecting a system, and always uses the named system regardless of its current condition. No other filter criteria can be specified when this attribute is used. If this element is specified, the system will be reserved at the end of the recipe when all tasks have completed execution. Reserve for the specified duration in seconds. If not specified, this defaults to 86400 seconds or 24 hours. Reserve the system only under certain conditions. The default value "always" will reserve the system unconditionally. The value "onwarn" will reserve the system if any task reported a Warn or Fail result, or if the recipe aborted. The value "onfail" will reserve the system if any task reported a Fail result, or if the recipe aborted. The value "onabort" will reserve the system if the recipe aborted. always onwarn onfail onabort Settings that influence the selection of the system used to run this recipe without imposing strict constraints as 'hostRequires' does. When set to "true", randomizes the choice of system across all eligible systems. This can help avoid a recipe being repeatedly scheduled on the same system. When omitted or set to "false", the system selection is done according to a default ordering that favours the user's systems, then systems associated with the user's groups and finally systems generally available to all users of the Beaker instance. TRUE FALSE If the value is set to 'ignore', jobs which output panics to the console are not aborted. If absent, such jobs will be aborted by the watchdog. The default value is None. ignore None You can specify additional kickstart commands to add to the base kickstart file. This element is a container for specifying additional packages to be installed for this recipe. These packages are appended to the existing default set of packages. This element is a container for defining additional repositories. These are also available during installation. Type of filesystem to be created on this partition. Defaults to 'ext3' if not specified. Mount point without the initial slash. Eg: 'mnt/test'. part = Partition, lvm = LVM volume Partition size in GB. Name of the task. When no fetch element is specified, the named task must exist in Beaker's task library. URL from which the harness should fetch the task. Refer to the harness documentation for supported URL schemes and task formats. If the fetch URL points at an archive or repository containing multiple tasks, this attribute identifies which subtree the harness should use to find the task. The default value is the empty string ("") which means that the task is at the root of the archive. Name of the task. When the fetch element is specified, the task name is only used to report results (the task need not exist in Beaker's task library). If the task name is not given, it defaults to the fetch URL combined with the subdirectory (if any). The task name can also be updated by the harness when the recipe executes. If the task is standalone, specify STANDALONE. If this is a multihost task, then either specify CLIENTS or SERVERS. If it is not relevant, simply omit. This sets up an environment variable of the same name as specified in the role (Also, see the role attribute in the recipe element). You can specify additional parameters in name=value formats for the task. These parameters are set in the environment when the task is executed. Deprecated. Use <family> instead. Deprecated. Use <name> instead. Deprecated. Use <tag> instead. Deprecated. Use <variant> instead. Deprecated. Use <arch> instead. Deprecated. Deprecated. Use <method> instead. Deprecated. Use <labcontroller> instead. The URL where the installation tree is located. Location of the installer kernel image. May be specified as an absolute URL or as a path relative to the installation tree URL. Location of the installer initramfs image. May be specified as an absolute URL or as a path relative to the installation tree URL. Location of the installer netboot image. May be specified as an absolute URL or as a path relative to the installation tree URL. CPU architecture that the distro is built for. OS version expressed as the major and minor versions of this distro. For example, <osversion major="RedHatEnterpriseLinux7" minor="4"/>. The (optional) distro name, used for display purposes. The (optional) distro variant, used for display purposes. Deprecated. Use <system><name> instead. Deprecated. Use <labcontroller> instead. Deprecated. Use <system><type> instead. Deprecated. Use <system><memory> instead. Deprecated. Use <cpu><processors> instead. Deprecated. Use <system><numanodes> instead. Deprecated. Use <system><name> instead. Deprecated. Use <system><arch> instead. Deprecated. Use <system><hypervisor> instead. Selects systems by device. If operator is ==, selects systems which have at least one matching device. If operator is !=, selects systems which have no matching devices. Selects systems by disk. A system will match this filter if any of its disks matches the criteria in this element. Selects systems by total disk space. Selects systems by total number of disks. Deprecated. Use <pool> instead. Select system from a specific pool. If operator is = or ==, select a system which belongs to the specified pool. If the operator is, !=, select a system which does not belong to the pool, != "" will select a system which belongs to any pool. Specify the type of CPU required for this job. Specify the system required for this task. If you have any specific requirements for the system, you must specify it here. Size of the disk in bytes. Logical sector size of the disk in bytes. Modern hard disks with large sector sizes may emulate a 512-byte sector size in firmware for compatibility reasons. Physical sector size of the disk in bytes. Date on which the system was last inventoried. The date should be specified as "YYYY-MM-DD". It can be specified as "" to be used in conjunction with the '=' or '!=' operators - the former matching only uninventoried machines and the latter only inventoried machines. Selects systems which are compatible with a particular distro. For example, you can use this element to select systems which are compatible with Red Hat Enterprise Linux 7.4 x86_64. CPU architecture that the system must be compatible with. This attribute is mandatory because system exclusions are specified in Beaker on a per-architecture basis. The OS major version, for example "RedHatEnterpriseLinux7". The OS minor version, for example "4" for RHEL7.4. If this attribute is ommitted, the filter selects only systems which are compatible with *all* minor versions of the OS. != like == = <= < >= > != like == = TRUE FALSE bytes B kB KB KiB MB MiB GB GiB TB TiB