Skip to content

Commit 67a7b26

Browse files
committed
adding a procedure detailing removing node from provisioning
1 parent 91f420b commit 67a7b26

File tree

2 files changed

+46
-0
lines changed

2 files changed

+46
-0
lines changed
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
// Module included in the following assemblies:
2+
//
3+
// scalability_and_performance/managing-bare-metal-hosts.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="removing-bare-metal-hosts-from-provisioner_{context}"]
7+
= Removing bare metal hosts from the provisioner node
8+
9+
In certain circumstances, you might want to temporarily remove bare metal hosts from the provisioner node.
10+
For example, during provisioning when a bare metal host reboot is triggered by using the {product-title} administration console or as a result of a Machine Config Pool update, {product-title} logs into the integrated Dell Remote Access Controller (iDrac) and issues a delete of the job queue.
11+
12+
To prevent the management of the number of `Machine` objects that matches the number of available `BareMetalHost` objects, add a `baremetalhost.metal3.io/detached` annotation to the `MachineSet` object.
13+
[NOTE]
14+
====
15+
This annotation has an effect for only `BareMetalHost` objects that are in either `Provisioned`, `ExternallyProvisioned` or `Ready/Available` state.
16+
====
17+
18+
.Prerequisites
19+
20+
* Install {op-system} bare metal compute machines for use in the cluster and create corresponding `BareMetalHost` objects.
21+
* Install the {product-title} CLI (`oc`).
22+
* Log in as a user with `cluster-admin` privileges.
23+
24+
.Procedure
25+
26+
. Annotate the compute machine set that you want to remove from the provisioner node by adding the `baremetalhost.metal3.io/detached` annotation.
27+
+
28+
[source,terminal]
29+
----
30+
$ oc annotate machineset <machineset> -n openshift-machine-api 'baremetalhost.metal3.io/detached'
31+
----
32+
+
33+
Wait for the new machines to start.
34+
+
35+
[NOTE]
36+
====
37+
When you use a `BareMetalHost` object to create a machine in the cluster and labels or selectors are subsequently changed on the `BareMetalHost`, the `BareMetalHost` object continues be counted against the `MachineSet` that the `Machine` object was created from.
38+
====
39+
40+
. In the provisioning use case, remove the annotation after the reboot is complete by using the following command:
41+
+
42+
[source,terminal]
43+
----
44+
$ oc annotate machineset <machineset> -n openshift-machine-api 'baremetalhost.metal3.io/detached-'
45+
----

scalability_and_performance/managing-bare-metal-hosts.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ include::modules/maintaining-bare-metal-hosts.adoc[leveloffset=+1]
1919
include::modules/adding-bare-metal-host-to-cluster-using-web-console.adoc[leveloffset=+2]
2020
include::modules/adding-bare-metal-host-to-cluster-using-yaml.adoc[leveloffset=+2]
2121
include::modules/automatically-scaling-machines-to-available-bare-metal-hosts.adoc[leveloffset=+2]
22+
include::modules/removing-bare-metal-hosts-from-provisioner.adoc[leveloffset=+2]
2223

2324
[role="_additional-resources"]
2425
.Additional resources

0 commit comments

Comments
 (0)