Beaker Provider

The following tables and example YAML configuration file snippets contain details needed to provision resources via the Contra HDSL.

Additional reference can be made to the Linchpin Beaker provider documentation as well as the bkr_server.py module and the bkr_info.py module on which the Linchpin Beaker provider is based.

Linchpin supports the Kerberos and OAuth2 authentication methods see the documentation at for more details.

Beaker configuration keys

distro

Type Required Purpose
String true A user defined name to refer to this resource.

arch

Type Required Purpose
String true Processor architecture for the requested system.

variant

Type Required Purpose
String true The operating system for the requested system.

job_group

Type Required Purpose
String false The job group that a given machine belongs to.

bkr_data

Type Required Purpose
String false Arbitrary data passed to beaker.

count

Type Required Purpose
Integer false
The quantity desired fo the requested resource.
If the count is greater than one, resources will be named name_1, etc.

Defaults to 1

whiteboard

Type Required Purpose
String false A message to be displayed on beaker.

hostrequires

Type Required Sub-field Layout Options
param required type
List False tag true String
op false String
value false String
type false String
Dict False force false String
Dict False rawxml false String

keyvalue

Type Required Purpose
List false