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
Copy file name to clipboardExpand all lines: deploy/README.md
+54Lines changed: 54 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,6 +106,60 @@ $ make force-stop
106
106
$ make destroy
107
107
```
108
108
109
+
### Managing Multiple AWS Metal Machines
110
+
111
+
The tooling supports deploying and managing multiple AWS metal machines simultaneously. This is useful for testing different configurations or running multiple clusters in parallel.
112
+
113
+
#### How It Works
114
+
115
+
Two key variables in `aws-hypervisor/instance.env` control which machine you're working with:
116
+
-**`SHARED_DIR`**: The directory where instance data is stored (e.g., `instance-data-machine1`)
117
+
-**`STACK_NAME`**: The CloudFormation stack name (e.g., `machine1`)
118
+
119
+
Each unique combination of these variables represents a separate AWS metal machine deployment.
120
+
121
+
#### Workflow for Multiple Machines
122
+
123
+
**Initial deployment of a machine:**
124
+
```bash
125
+
# Edit instance.env to set your first deployment
126
+
export SHARED_DIR=instance-data-machine1
127
+
export STACK_NAME=machine1
128
+
129
+
# Deploy the machine
130
+
$ make deploy
131
+
```
132
+
133
+
**Deploy a second machine:**
134
+
```bash
135
+
# Edit instance.env with new values
136
+
export SHARED_DIR=instance-data-machine2
137
+
export STACK_NAME=machine2
138
+
139
+
# Deploy the second machine
140
+
$ make deploy
141
+
```
142
+
143
+
**Switch between machines:**
144
+
145
+
To switch which machine you're working with, simply update the two variables in `instance.env` and update the inventory:
146
+
147
+
```bash
148
+
# Edit instance.env to point to the machine you want
149
+
export SHARED_DIR=instance-data-machine1
150
+
export STACK_NAME=machine1
151
+
152
+
# Update SSH configuration to point to this machine
153
+
$ make inventory
154
+
155
+
# Now use any command normally (it will operate on machine1)
156
+
$ make fencing-ipi
157
+
$ make ssh
158
+
$ make stop
159
+
```
160
+
161
+
This allows you to seamlessly switch between different AWS metal machines without any additional configuration changes.
162
+
109
163
### OpenShift Cluster Management
110
164
111
165
When running OpenShift clusters on the instance (using dev-scripts), you have several options for managing cluster lifecycle:
0 commit comments