forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathstart-stop-vms.html.md.erb
361 lines (321 loc) · 14 KB
/
start-stop-vms.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
---
title: Starting and Stopping Pivotal Cloud Foundry® Virtual Machines
owner: Ops Manager
---
<strong><%= modified_date %></strong>
This topic describes starting and stopping the component virtual machines (VMs) that make
up a [Pivotal Cloud Foundry®](https://network.pivotal.io/products/pivotal-cf) (PCF)
deployment. This procedure uses the BOSH Command Line Interface (CLI). See [Prepare to Use the BOSH CLI](./trouble-advanced.html#prepare) for help setting up this tool.
Dependencies between the components in your PCF deployment require that you
start and stop the VMs for those components in a specific order.
These orders are specified below in the [start order](#start) and [stop order](#stop) tables.
<p class="note"><strong>Note</strong>: When you deploy Elastic Runtime, the process automatically starts VMs. These steps are not required to install any part of your deployment.</p>
## <a id='get-names'></a>Finding the Names for Your PCF Virtual Machines ##
You need the full names for the VMs to [start](#start) or [stop](#stop) them using the BOSH CLI. To find full names for the VMs running each component, run `bosh vms`:
<pre id='term-bosh-vms' class='terminal'>
○ → bosh vms
Acting as user 'director' on 'p-bosh-399383d4525762cdc35c'
Deployment `cf-1ef2da789c0ed8f3567f'
Director task 26
Task 26 done
+-------------------------------------------------------------------------------------------------------+---------+-----+--------------------------------------------------------------+--------------+
| VM | State | AZ | VM Type | IPs |
+-------------------------------------------------------------------------------------------------------+---------+-----+--------------------------------------------------------------+--------------+
| clock_global-partition-bb35e96d6d3184a2d672/0 (92174545-ea16-448c-bea8-5a3d27ef2078) | running | n/a | clock_global-partition-bb35e96d6d3184a2d672 | 192.0.2.101 |
| cloud_controller-partition-bb35e96d6d3184a2d672/0 (a315eb23-04bf-4228-a346-0ff8cc936a86) | running | n/a | cloud_controller-partition-bb35e96d6d3184a2d672 | 192.0.2.100 |
| cloud_controller_worker-partition-bb35e96d6d3184a2d672/0 (62ccf688-29dc-42f4-9191-78cf6c363afd) | running | n/a | cloud_controller_worker-partition-bb35e96d6d3184a2d672 | 192.0.2.102 |
| consul_server-partition-bb35e96d6d3184a2d672/0 (5eb05f9b-90d3-437f-aeeb-4a1b30320c77) | running | n/a | consul_server-partition-bb35e96d6d3184a2d672 | 192.0.2.92 |
| diego_brain-partition-bb35e96d6d3184a2d672/0 (2abe95cd-5094-4f87-bcb9-c9fec68c6033) | running | n/a | diego_brain-partition-bb35e96d6d3184a2d672 | 192.0.2.104 |
| diego_cell-partition-bb35e96d6d3184a2d672/0 (23d12fad-ca7a-4efa-9cd7-dc7d242c89ae) | running | n/a | diego_cell-partition-bb35e96d6d3184a2d672 | 192.0.2.105 |
| diego_cell-partition-bb35e96d6d3184a2d672/1 (9f94e756-f648-4c4b-a7e7-08099bd75263) | running | n/a | diego_cell-partition-bb35e96d6d3184a2d672 | 192.0.2.106 |
| diego_database-partition-bb35e96d6d3184a2d672/0 (0cca205b-bc68-42d5-95f0-47fc0c072bb6) | running | n/a | diego_database-partition-bb35e96d6d3184a2d672 | 192.0.2.95 |
| doppler-partition-bb35e96d6d3184a2d672/0 (a5bcd2ed-7b3c-4ebb-901c-614e2064d10c) | running | n/a | doppler-partition-bb35e96d6d3184a2d672 | 192.0.2.108 |
| etcd_server-partition-bb35e96d6d3184a2d672/0 (3e3b53cd-0b68-4f94-81cf-61da48dd20ab) | running | n/a | etcd_server-partition-bb35e96d6d3184a2d672 | 192.0.2.94 |
| ha_proxy-partition-bb35e96d6d3184a2d672/0 (bc7dada2-8e31-4d70-b314-f85ebb51a503) | running | n/a | ha_proxy-partition-bb35e96d6d3184a2d672 | 192.0.2.254 |
| loggregator_trafficcontroller-partition-bb35e96d6d3184a2d672/0 (57157a16-6309-494f-8133-b831b52bb363) | running | n/a | loggregator_trafficcontroller-partition-bb35e96d6d3184a2d672 | 192.0.2.109 |
| mysql-partition-bb35e96d6d3184a2d672/0 (ff18bb42-3df8-44b3-ba69-0b7e1f2dfc30) | running | n/a | mysql-partition-bb35e96d6d3184a2d672 | 192.0.2.99 |
| mysql_proxy-partition-bb35e96d6d3184a2d672/0 (e4f72312-336d-465d-a8d0-57dc6b7abd66) | running | n/a | mysql_proxy-partition-bb35e96d6d3184a2d672 | 192.0.2.98 |
| nats-partition-bb35e96d6d3184a2d672/0 (654b2470-c6fb-40d1-a7d2-c7839a7c6403) | running | n/a | nats-partition-bb35e96d6d3184a2d672 | 192.0.2.93 |
| nfs_server-partition-bb35e96d6d3184a2d672/0 (df18f438-a0f1-46b2-b3ea-31bf96d47a18) | running | n/a | nfs_server-partition-bb35e96d6d3184a2d672 | 192.0.2.96 |
| router-partition-bb35e96d6d3184a2d672/0 (4fbc6b8c-8bc6-425c-a4fc-04b7127b1f4a) | running | n/a | router-partition-bb35e96d6d3184a2d672 | 192.0.2.97 |
| uaa-partition-bb35e96d6d3184a2d672/0 (82c39142-da6e-42ec-af1c-b0247f74e8bd) | running | n/a | uaa-partition-bb35e96d6d3184a2d672 | 192.0.2.103 |
+-------------------------------------------------------------------------------------------------------+---------+-----+--------------------------------------------------------------+--------------+
VMs total: 17
</pre>
You can see the full name of each VM in the `VM` column of the terminal output. Each full name includes:
* A prefix indicating the component function of the VM. The [table](#start-order) below associates each component VM function with a prefix.
* The word `partition`
* An identifier string specific to your deployment
* An `INDEX` suffix. For component processes that run on a single VM instance, INDEX is always 0. For processes running on multiple VMs, INDEX is a sequentially numbered value that uniquely identifies each VM.
* An `ID` in parentheses that is the UUID (Universally Unique Identifier) for that instance and can generally be used interchangeably with the index value from the CLI.
For any component, you can look for its prefix in the `bosh vms` output to find the full name of the VM or VMs that run it. In the example shown here, the full name of one of the two Diego Cell VMs is `diego_cell-partition-bb35e96d6d3184a2d672/1`.
## <a id='start'></a>Starting PCF Virtual Machines ##
In the order specified in the [Start Order table](#start-order) below, run `bosh start VM-NAME` for each component in your PCF deployment. Use the full name of the component VM as listed in your `bosh vms` [terminal output](#term-bosh-vms) with the `INDEX` at the end. In the example here, the first component you would start is the NATS VM, by running `bosh start nats-partition-458f9d7042365ff810e9 0`:
<pre class='terminal'>
Processing deployment manifest
------------------------------
You are about to start nats-partition-458f9d7042365ff810e9/0
Detecting deployment changes
----------------------------
Start nats-partition-458f9d7042365ff810e9/0? (type 'yes' to continue): yes
Performing `start nats-partition-458f9d7042365ff810e9/0'...
...
Started updating job nats-partition-458f9d7042365ff810e9 > nats-partition-458f9d7042365ff810e9/0 (canary). Done (00:00:43)
Task 42 done
nats-partition-458f9d7042365ff810e9/0 has been started
</pre>
<p class='note'><strong>Note</strong>:
To start a specific instance of a VM, include the <code>INDEX</code>, space delimited, at the end of its full name. In the example here, you could start only the first Diego Cell instance by running: <code>$ bosh start diego_cell-partition-458f9d7042365ff810e9 0 </code>
</p>
<table id='start-order' border="1" class="nice">
<tr>
<th>Start Order</th>
<th>Component</th>
<th><code>Job/index</code> name prefix <br>(in <code>bosh vms</code> output)</th>
</tr>
<tr>
<td>1</td>
<td>NATS</td>
<td><code>nats-</code></td>
</tr>
<tr>
<td>2</td>
<td>consul</td>
<td><code>consul_server-</code></td>
</tr>
<tr>
<td>3</td>
<td>etcd</td>
<td><code>etcd_server-</code></td>
</tr>
<tr>
<td>4</td>
<td>Diego Database</td>
<td><code>diego_database-</code></td>
</tr>
<tr>
<td>5</td>
<td>NFS Server</td>
<td><code>nfs_server-</code></td>
</tr>
<tr>
<td>6</td>
<td>Router</td>
<td><code>router-</code></td>
</tr>
<tr>
<td>7</td>
<td>MySQL Proxy</td>
<td><code>mysql_proxy-</code></td>
</tr>
<tr>
<td>8</td>
<td>MySQL Server</td>
<td><code>mysql-</code></td>
</tr>
<tr>
<td>9</td>
<td>Cloud Controller Database</td>
<td><code>ccdb-</code></td>
</tr>
<tr>
<td>10</td>
<td>UAA Database</td>
<td><code>uaadb-</code></td>
</tr>
<tr>
<td>11</td>
<td>Apps Manager Database</td>
<td><code>consoledb-</code></td>
</tr>
<tr>
<td>12</td>
<td>Cloud Controller</td>
<td><code>cloud_controller-</code></td>
</tr>
<tr>
<td>13</td>
<td>HAProxy</td>
<td><code>ha_proxy-</code></td>
</tr>
<tr>
<td>14</td>
<td>Health Manager</td>
<td><code>health_manager-</code></td>
</tr>
<tr>
<td>15</td>
<td>Clock Global</td>
<td><code>clock_global-</code></td>
</tr>
<tr>
<td>16</td>
<td>Cloud Controller Worker</td>
<td><code>cloud_controller_worker-</code></td>
</tr>
<tr>
<td>17</td>
<td>Collector</td>
<td><code>collector-</code></td>
</tr>
<tr>
<td>18</td>
<td>UAA</td>
<td><code>uaa-</code></td>
</tr>
<tr>
<td>19</td>
<td>Diego Brain</td>
<td><code>diego_brain-</code></td>
</tr>
<tr>
<td>20</td>
<td>Diego Cell</td>
<td><code>diego_cell-</code></td>
</tr>
<tr>
<td>22</td>
<td>Doppler Server</td>
<td><code>doppler-</code></td>
</tr>
<tr>
<td>23</td>
<td>Loggregator Traffic Controller</td>
<td><code>loggregator_trafficcontroller-</code></td>
</tr>
</table>
## <a id='stop'></a>Stopping PCF Virtual Machines ##
In the order specified in the [Stop Order table](#stop-order) below, run `bosh stop VM-NAME INDEX-OR-ID --hard` for each component in your PCF deployment. Use the full name of the component VM as listed in your `bosh vms` [terminal output](#term-bosh-vms), with the `INDEX`, space delimited, at the end. In the example here, the first component you would stop is the Loggregator Traffic Controller VM, by running `bosh stop loggregator_trafficcontroller-partition-458f9d7042365ff810e9 0 --hard`:
<pre class='terminal'>
$ bosh stop loggregator_trafficcontroller-partition-458f9d7042365ff810e9 0 --hard
Processing deployment manifest
------------------------------
You are about to stop loggregator_trafficcontroller-partition-458f9d7042365ff810e9/0
Detecting deployment changes
----------------------------
Stop loggregator_trafficcontroller-partition-458f9d7042365ff810e9/0? (type 'yes' to continue): yes
Performing `stop loggregator_trafficcontroller-partition-458f9d7042365ff810e9/0'...
...
Started updating job loggregator_trafficcontroller-partition-458f9d7042365ff810e9 > loggregator_trafficcontroller-partition-458f9d7042365ff810e9/0 (canary). Done (00:00:37)
loggregator_trafficcontroller-partition-458f9d7042365ff810e9/0 has been stopped
</pre>
<p class='note'><strong>Note</strong>:
To stop a specific instance of a VM, include the <code>INDEX</code>, space delimited, at the end of its full name. In the example here, you could stop only the second Diego Cell instance by running: <code>$ bosh stop diego_cell-partition-bb35e96d6d3184a2d672 1 --hard</code>
</p>
<table id='stop-order' border="1" class="nice">
<tr>
<th>Stop Order</th>
<th>Component</th>
<th><code>Job/index</code> name prefix <br>(in <code>bosh vms</code> output)</th>
</tr>
<tr>
<td>1</td>
<td>Loggregator Traffic Controller</td>
<td><code>loggregator_trafficcontroller-</code></td>
</tr>
<tr>
<td>2</td>
<td>Doppler Server</td>
<td><code>doppler-</code></td>
</tr>
<tr>
<td>4</td>
<td>Diego Cell</td>
<td><code>diego_cell-</code></td>
</tr>
<tr>
<td>5</td>
<td>Diego Brain</td>
<td><code>diego_brain-</code></td>
</tr>
<tr>
<td>6</td>
<td>UAA</td>
<td><code>uaa-</code></td>
</tr>
<tr>
<td>7</td>
<td>Collector</td>
<td><code>collector-</code></td>
</tr>
<tr>
<td>8</td>
<td>Cloud Controller Worker</td>
<td><code>cloud_controller_worker-</code></td>
</tr>
<tr>
<td>9</td>
<td>Clock Global</td>
<td><code>clock_global-</code></td>
</tr>
<tr>
<td>10</td>
<td>Health Manager</td>
<td><code>health_manager-</code></td>
</tr>
<tr>
<td>11</td>
<td>HAProxy</td>
<td><code>ha_proxy-</code></td>
</tr>
<tr>
<td>12</td>
<td>Cloud Controller</td>
<td><code>cloud_controller-</code></td>
</tr>
<tr>
<td>13</td>
<td>Apps Manager Database</td>
<td><code>consoledb-</code></td>
</tr>
<tr>
<td>14</td>
<td>UAA Database</td>
<td><code>uaadb-</code></td>
</tr>
<tr>
<td>15</td>
<td>Cloud Controller Database</td>
<td><code>ccdb-</code></td>
</tr>
<tr>
<td>16</td>
<td>MySQL Server</td>
<td><code>mysql-</code></td>
</tr>
<tr>
<td>17</td>
<td>MySQL Proxy</td>
<td><code>mysql_proxy-</code></td>
</tr>
<tr>
<td>18</td>
<td>Router</td>
<td><code>router-</code></td>
</tr>
<tr>
<td>19</td>
<td>NFS Server</td>
<td><code>nfs_server-</code></td>
</tr>
<tr>
<td>20</td>
<td>Diego Database</td>
<td><code>diego_database-</code></td>
</tr>
<tr>
<td>21</td>
<td>etcd</td>
<td><code>etcd_server-</code></td>
</tr>
<tr>
<td>22</td>
<td>consul</td>
<td><code>consul_server-</code></td>
</tr>
<tr>
<td>23</td>
<td>NATS</td>
<td><code>nats-</code></td>
</tr>
</table>