forked from cloudfoundry/docs-bosh
-
Notifications
You must be signed in to change notification settings - Fork 0
/
deploying.html.md.erb
46 lines (31 loc) · 1.61 KB
/
deploying.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
---
title: Deploying
---
Once referenced stemcells and releases are uploaded to the Director and the deployment manifest is complete, a deployment can be formed on the Director. The CLI provides a single command to create and update deployments: `bosh deploy`. From the perspective of the Director, creation and update of the deployment happens through the same steps.
To let the CLI know that you are planning to operate on a specific deployment you must set the deployment:
<pre class="terminal">
$ bosh deployment ~/workspace/my-deployment/manifest.yml
Deployment set to `/Users/pivotal/workspace/my-deployment/manifest.yml'
</pre>
From then on most commands the CLI provides act on the set deployment. To form a deployment on the Director represented by the `manifest.yml`, run the deploy command:
<pre class="terminal">
$ bosh deploy
</pre>
After the deploy command completes with either success or failure you can run a command to list VMs created for this deployment:
<pre class="terminal">
$ bosh instances
Deployment `my-deployment'
Director task 10326
Task 10326 done
+----------------+---------+---------------+-------------+
| Instance | State | Resource Pool | IPs |
+----------------+---------+---------------+-------------+
| redis-master/0 | running | redis-servers | 10.10.30.71 |
| redis-slave/0 | running | redis-servers | 10.10.30.72 |
| redis-slave/1 | running | redis-servers | 10.10.30.73 |
+----------------+---------+---------------+-------------+
Instances total: 3
</pre>
---
[Back to Table of Contents](index.html#basic-deploy)
Previous: [Uploading Releases](uploading-releases.html)