Skip to content

Commit cec5661

Browse files
authored
Merge pull request #81714 from maxwelldb/shiftstack-etcd-volumes-osdocs9716
[OSDOCS#9716] GA OpenStack with rootVolume and etcd on local disk
2 parents 7e4093c + dc98ab7 commit cec5661

File tree

2 files changed

+8
-12
lines changed

2 files changed

+8
-12
lines changed

installing/installing_openstack/deploying-openstack-with-rootVolume-etcd-on-local-disk.adoc

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,6 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9-
:FeatureName: Deploying on {rh-openstack-first} with rootVolume and etcd on local disk
10-
include::snippets/technology-preview.adoc[]
11-
129
As a day 2 operation, you can resolve and prevent performance issues of your {rh-openstack-first} installation by moving etcd from a root volume (provided by OpenStack Cinder) to a dedicated ephemeral local disk.
1310

1411
include::modules/installation-osp-local-disk-deployment.adoc[leveloffset=+1]

modules/installation-osp-local-disk-deployment.adoc

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,6 @@
88

99
If you have an existing {rh-openstack} cloud, you can move etcd from that cloud to a dedicated ephemeral local disk.
1010

11-
[WARNING]
12-
====
13-
This procedure is for testing etcd on a local disk only and should not be used on production clusters. In certain cases, complete loss of the control plane can occur. For more information, see "Overview of backup and restore operation" under "Backup and restore".
14-
====
1511

1612
.Prerequisites
1713

@@ -71,11 +67,6 @@ $ oc wait clusteroperators --all --for=condition=Progressing=false <1>
7167

7268
. Create a file named `98-var-lib-etcd.yaml` by using the following YAML file:
7369
+
74-
[WARNING]
75-
====
76-
This procedure is for testing etcd on a local disk and should not be used on a production cluster. In certain cases, complete loss of the control plane can occur. For more information, see "Overview of backup and restore operation" under "Backup and restore".
77-
====
78-
+
7970
[%collapsible]
8071
====
8172
[source,yaml]
@@ -152,6 +143,7 @@ spec:
152143
153144
After=migrate-to-local-etcd.service
154145
Before=crio.service
146+
Requisite=var-lib-etcd.mount
155147
156148
[Service]
157149
Type=oneshot
@@ -175,6 +167,13 @@ spec:
175167
<7> Copies and moves in separate steps to ensure atomic creation of a complete member directory.
176168
<8> Performs a quick check of the mount point directory before performing a full recursive relabel. If restorecon in the file path `/var/lib/etcd` cannot rename the directory, the recursive rename is not performed.
177169
====
170+
+
171+
[WARNING]
172+
====
173+
After you apply the `98-var-lib-etcd.yaml` file to the system, do not remove it. Removing this file will break etcd members and lead to system instability.
174+
175+
If a rollback is necessary, modify the `ControlPlaneMachineSet` object to use a flavor that does not include ephemeral disks. This change regenerates the control plane nodes without using ephemeral disks for the etcd partition, which avoids issues related to the `98-var-lib-etcd.yaml` file. It is safe to remove the `98-var-lib-etcd.yaml` file only after the update to the `ControlPlaneMachineSet` object is complete and no control plane nodes are using ephemeral disks.
176+
====
178177

179178
. Create the new `MachineConfig` object by running the following command:
180179
+

0 commit comments

Comments
 (0)