1BKR-SYSTEM-CREATE(1)                Beaker                BKR-SYSTEM-CREATE(1)
2
3
4

NAME

6       bkr-system-create - Create a system
7

SYNOPSIS

9       bkr system-create [options] <fqdn> ..
10

DESCRIPTION

12       Creates a Beaker system. By default the new system is owned by the user
13       who created it.
14

OPTIONS

16       --lab-controller <fqdn>
17              Attaches the lab controller specified by <fqdn> to the system.
18
19       --arch <arch>
20              Architecture supported by the system. This option can be  speci‐
21              fied  multiple times to add more than one architecture supported
22              by the system.
23
24       --location <location>
25              Physical location of the system.
26
27       --power-type <power-type>
28              Remote power control type. This value must be a valid power type
29              configured by the Beaker administrator (or one of the Beaker de‐
30              faults).
31
32       --power-address <power-address>
33              Address passed to the power control script.
34
35       --power-user <power-user>
36              Username passed to the power control script.
37
38       --power-password <power-password>
39              Password passed to the power control script.
40
41       --power-id <power-id>
42              Unique identifier passed to the power control script. The  mean‐
43              ing  of  the  power  ID depends on which power type is selected.
44              Typically this field identifies a particular plug, socket, port,
45              or virtual guest name.
46
47       --power-quiescent-period <seconds>
48              Quiescent  period  for power control. Beaker will delay at least
49              this long between consecutive power commands.
50
51       --release-action <release-action>
52              Action to take whenever a reservation for  this  system  is  re‐
53              turned: PowerOff, LeaveOn, ReProvision.
54
55       --reprovision-distro-tree <id>
56              Distro  tree to be installed when the release action is ReProvi‐
57              sion.
58
59       --condition <condition>
60              Ccondition of the system. Valid values  are  Automated,  Manual,
61              Broken, and Removed.
62
63       --host-hypervisor <type>
64              Type of hypervisor which this system is hosted on.
65
66              For  systems  which  are virtualized, this field indicates which
67              virtualization technology is used by the host.  An  empty  value
68              indicates that the system is bare metal (not a virtual guest).
69
70       Common bkr options are described in the Options section of bkr(1).
71

EXIT STATUS

73       Non-zero on error, otherwise zero.
74

EXAMPLES

76       Create a system called "beakertestsystem":
77
78          bkr system-create beakertestsystem
79

SEE ALSO

81       bkr(1)
82

AUTHOR

84       The Beaker team <beaker-devel@lists.fedorahosted.org>
85

87       2013-2022 Red Hat, Inc.
88
89
90
91
9228.3                             May 21, 2022             BKR-SYSTEM-CREATE(1)
Impressum