You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* xref:../../edge_computing/image_based_upgrade/preparing_for_image_based_upgrade/ztp-image-based-upgrade-prep-resources.adoc#ztp-image-based-upgrade-creating-backup-resources-with-ztp_ztp-gitops[Creating ConfigMap objects for the image-based upgrade with GitOps ZTP]
= Configuring a shared container directory between ostree stateroots
7
+
8
+
Apply a `MachineConfig` to both the seed and the target clusters during installation time to create a separate partition and share the `/var/lib/containers` directory between the two `ostree` stateroots that will be used during the upgrade process.
9
+
10
+
[IMPORTANT]
11
+
====
12
+
You must complete this procedure at installation time.
13
+
====
14
+
15
+
.Procedure
16
+
17
+
* Apply a `MachineConfig` to create a separate partition:
<2> Specify the start of the partition in MiB. If the value is too small, the installation will fail.
68
+
<3> Specify a minimum size for the partition of 500 GB to ensure adequate disk space for precached images. If the value is too small, the deployments after installation will fail.
= Sharing the container directory between `ostree` stateroots
6
+
= Configuring a shared container directory between ostree stateroots when using {ztp}
7
7
8
-
You must apply a `MachineConfig` to both the seed and the target clusters during installation time to create a separate partition and share the `/var/lib/containers` directory between the two `ostree` stateroots that will be used during the upgrade process.
== Sharing the container directory between `ostree` stateroots when using GitOps ZTP
81
-
82
-
When you are using the GitOps ZTP workflow, you can do the following procedure to create a separate disk partition on both the seed and target cluster and to share the `/var/lib/containers` directory.
8
+
When you are using the {ztp-first} workflow, you do the following procedure to create a separate disk partition on both the seed and target cluster and to share the `/var/lib/containers` directory.
83
9
84
10
[IMPORTANT]
85
11
====
@@ -88,12 +14,11 @@ You must complete this procedure at installation time.
88
14
89
15
.Prerequisites
90
16
91
-
* Log in as a user with `cluster-admin` privileges.
92
17
* Install Butane.
93
18
94
19
.Procedure
95
20
96
-
. Create the `storage.bu` file.
21
+
. Create the `storage.bu` file:
97
22
+
98
23
[source,yaml]
99
24
----
@@ -105,8 +30,8 @@ storage:
105
30
wipe_table: false
106
31
partitions:
107
32
- label: var-lib-containers
108
-
start_mib: <start_of_parition> <2>
109
-
size_mib: <parition_size> <3>
33
+
start_mib: <start_of_partition> <2>
34
+
size_mib: <partition_size> <3>
110
35
filesystems:
111
36
- path: /var/lib/containers
112
37
device: /dev/disk/by-partlabel/var-lib-containers
@@ -119,9 +44,9 @@ storage:
119
44
----
120
45
<1> Specify the root disk.
121
46
<2> Specify the start of the partition in MiB. If the value is too small, the installation will fail.
122
-
<3> Specify the size of the partition. If the value is too small, the deployments after installation will fail.
47
+
<3> Specify a minimum size for the partition of 500 GB to ensure adequate disk space for precached images. If the value is too small, the deployments after installation will fail.
123
48
124
-
. Convert the `storage.bu` to an Ignition file.
49
+
. Convert the `storage.bu` to an Ignition file:
125
50
+
126
51
--
127
52
[source,terminal]
@@ -136,7 +61,7 @@ $ butane storage.bu
136
61
----
137
62
--
138
63
139
-
. Copy the output into the `.spec.clusters.nodes.ignitionConfigOverride` field in the `SiteConfig` CR.
64
+
. Copy the output into the `.spec.clusters.nodes.ignitionConfigOverride` field in the `SiteConfig` CR:
140
65
+
141
66
[source,yaml]
142
67
----
@@ -150,7 +75,7 @@ spec:
150
75
151
76
.Verification
152
77
153
-
. During or after installation, verify on the hub cluster that the `BareMetalHost` object shows the annotation.
78
+
. During or after installation, verify on the hub cluster that the `BareMetalHost` object shows the annotation:
0 commit comments