2 # Drydock BaremetalNode resources for a specific rack are stored in this file.
4 # NOTE: For new sites, you should complete the networks/physical/networks.yaml
5 # file before working on this file.
7 # In this file, you should make the number of `drydock/BaremetalNode/v1`
8 # resources equal the number of bare metal nodes you have, either by deleting
9 # excess BaremetalNode definitions (if there are too many), or by copying and
10 # pasting the last BaremetalNode in the file until you have the correct number
11 # of baremetal nodes (if there are too few).
13 # Then in each file, address all additional NEWSITE-CHANGEME markers to update
14 # the data in these files with the right values for your new site.
16 # *NOTE: The Genesis node is counted as one of the control plane nodes. Note
17 # that the Genesis node does not appear on this bare metal list, because the
18 # procedure to reprovision the Genesis host with MaaS has not yet been
19 # implemented. Therefore there will be only three bare metal nodes in this file
20 # with the 'masters' tag, as the genesis roles are assigned in a difference
21 # place (profiles/genesis.yaml).
22 # NOTE: The host profiles for the control plane are further divided into two
23 # variants: primary and secondary. The only significance this has is that the
24 # "primary" nodes are active Ceph nodes, whereas the "secondary" nodes are Ceph
25 # standby nodes. For Ceph quorum, this means that the control plane split will
26 # be 3 primary + 1 standby host profile, and the Genesis node counts toward one
27 # of the 3 primary profiles. Other control plane services are not affected by
28 # primary vs secondary designation.
30 # TODO: Include the hostname naming convention
32 schema: 'drydock/BaremetalNode/v1'
34 schema: 'metadata/Document/v1'
35 # NEWSITE-CHANGEME: Replace with the hostname of the first node in the rack,
36 # after (excluding) genesis.
41 storagePolicy: cleartext
43 # NEWSITE-CHANGEME: The IPv4 address assigned to each logical network on this
44 # node. In the reference Airship deployment, this is all logical Networks defined
45 # in networks/physical/networks.yaml. IP addresses are manually assigned, by-hand.
46 # (what could possibly go wrong!) The instructions differ for each logical
47 # network, which are laid out below.
49 # The iDrac/iLo IP of the node. It's important that this match up with the
50 # node's hostname above, so that the rack number and node position encoded
51 # in the hostname are accurate and matching the node that IPMI operations
52 # will be performed against (for poweron, poweroff, PXE boot to wipe disk or
53 # reconfigure identity, etc - very important to get right for these reasons).
54 # These addresses should already be assigned to nodes racked and stacked in
55 # the environment; these are not addresses which MaaS assigns.
58 # The IP of the node on the PXE network. Refer to the static IP range
59 # defined for the PXE network in networks/physical/networks.yaml. Begin allocating
60 # IPs from this network, starting with the second IP (inclusive) from the
61 # allocation range of this subnet (Genesis node will have the first IP).
62 # Ex: If the start IP for the PXE "static" network is 10.23.20.11, then
63 # genesis will have 10.23.20.11, this node will have 10.23.20.12, and
64 # so on with incrementing IP addresses with each additional node.
67 # Genesis node gets first IP, all other nodes increment IPs from there
68 # within the allocation range defined for the network in
69 # networks/physical/networks.yaml
72 # Genesis node gets first IP, all other nodes increment IPs from there
73 # within the allocation range defined for the network in
74 # networks/physical/networks.yaml
77 # Genesis node gets first IP, all other nodes increment IPs from there
78 # within the allocation range defined for the network in
79 # networks/physical/networks.yaml
82 # Genesis node gets first IP, all other nodes increment IPs from there
83 # within the allocation range defined for the network in
84 # networks/physical/networks.yaml
87 # NEWSITE-CHANGEME: Set the host profile for the node.
88 # Note that there are different host profiles depending if this is a control
89 # plane vs data plane node, and different profiles that map to different types
90 # hardware. Control plane host profiles are further broken down into "primary"
91 # and "secondary" profiles (refer to the Notes section at the top of this doc).
92 # Select the host profile that matches up to your type of
93 # hardware and function. E.g., the r720 here refers to Dell R720 hardware, the
94 # 'cp' refers to a control plane profile, and the "primary" means it will be
95 # an active member in the ceph quorum. Refer to profiles/host/ for the list
96 # of available host profiles specific to this site (otherwise, you may find
97 # a general set of host profiles at the "type" or "global" layers/folders.
98 # If you have hardware that is not on this list of profiles, you may need to
99 # create a new host profile for that hardware.
100 # Regarding control plane vs other data plane profiles, refer to the notes at
101 # the beginning of this file. There should be one control plane node per rack,
102 # including Genesis. Note Genesis won't actually be listed in this file as a
103 # BaremetalNode, but the rest are.
104 # This is the second "primary" control plane node after Genesis.
105 host_profile: cp_r720-primary
108 # NEWSITE-CHANGEME: See previous comment. Apply 'masters' tag for control
109 # plane node, and 'workers' tag for data plane hosts.
111 # NEWSITE-CHANGEME: Refer to site engineering package or other supporting
112 # documentation for the specific rack name. This should be a rack name that
113 # is meaningful to data center personnel (i.e. a rack they could locate if
114 # you gave them this rack designation).
118 schema: 'drydock/BaremetalNode/v1'
120 schema: 'metadata/Document/v1'
121 # NEWSITE-CHANGEME: The next node's hostname
126 storagePolicy: cleartext
128 # NEWSITE-CHANGEME: The next node's IPv4 addressing
131 address: 10.23.104.13
142 # NEWSITE-CHANGEME: The next node's host profile
143 host_profile: cp_r720-primary
145 # NEWSITE-CHANGEME: The next node's rack designation
147 # NEWSITE-CHANGEME: The next node's role desigatnion
152 schema: 'drydock/BaremetalNode/v1'
154 schema: 'metadata/Document/v1'
155 # NEWSITE-CHANGEME: The next node's hostname
160 storagePolicy: cleartext
162 # NEWSITE-CHANGEME: The next node's IPv4 addressing
165 address: 10.23.104.14
176 # NEWSITE-CHANGEME: The next node's host profile
177 # This is the third "primary" control plane profile after genesis
178 host_profile: cp_r740-secondary
180 # NEWSITE-CHANGEME: The next node's rack designation
182 # NEWSITE-CHANGEME: The next node's role desigatnion
187 schema: 'drydock/BaremetalNode/v1'
189 schema: 'metadata/Document/v1'
190 # NEWSITE-CHANGEME: The next node's hostname
195 storagePolicy: cleartext
197 # NEWSITE-CHANGEME: The next node's IPv4 addressing
200 address: 10.23.104.17
211 # NEWSITE-CHANGEME: The next node's host profile
212 # This is the one and only appearance of the "secondary" control plane profile
213 host_profile: dp_r720
215 # NEWSITE-CHANGEME: The next node's rack designation
217 # NEWSITE-CHANGEME: The next node's role desigatnion
222 schema: 'drydock/BaremetalNode/v1'
224 schema: 'metadata/Document/v1'
225 # NEWSITE-CHANGEME: The next node's hostname
230 storagePolicy: cleartext
232 # NEWSITE-CHANGEME: The next node's IPv4 addressing
235 address: 10.23.104.19
246 # NEWSITE-CHANGEME: The next node's host profile
247 host_profile: dp_r720
249 # NEWSITE-CHANGEME: The next node's rack designation
251 # NEWSITE-CHANGEME: The next node's role desigatnion