forked from cloudfoundry/docs-bosh
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathinit-openstack.html.md.erb
196 lines (131 loc) · 7.49 KB
/
init-openstack.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
---
title: Creating environment on OpenStack
---
This document shows how to initialize new [environment](terminology.html#environment) on OpenStack.
## <a id="prepare-openstack"></a>Step 1: Prepare an OpenStack environment
### <a id="prerequisites"></a> Prerequisites
1. An OpenStack environment running one of the following supported releases:
* [Liberty](http://www.openstack.org/software/liberty) (actively tested)
* [Mitaka](http://www.openstack.org/software/mitaka) (actively tested)
* [Newton](http://www.openstack.org/software/newton) (actively tested)
<p class="note">Note: Juno has a <a href="https://bugs.launchpad.net/nova/+bug/1396854">bug</a> that prevents BOSH to assign specific IPs to VMs. You have to apply a Nova patch to avoid this problem.</p>
1. The following OpenStack services:
* [Identity](https://www.openstack.org/software/releases/ocata/components/keystone):
BOSH authenticates credentials and retrieves the endpoint URLs for other OpenStack services.
* [Compute](https://www.openstack.org/software/releases/ocata/components/nova):
BOSH boots new VMs, assigns floating IPs to VMs, and creates and attaches volumes to VMs.
* [Image](https://www.openstack.org/software/releases/ocata/components/glance):
BOSH stores stemcells using the Image service.
* **(Optional)** [OpenStack Networking](https://www.openstack.org/software/releases/ocata/components/neutron):
Provides network scaling and automated management functions that are useful when deploying complex distributed systems. **Note:** OpenStack networking is used as default as of v28 of the OpenStack CPI. To disable the use of the OpenStack Networking project, see [using nova-networking](openstack-nova-networking.html).
1. The following OpenStack networks:
* An external network with a subnet.
* An private network with a subnet. The subnet must have an IP address allocation pool.
1. Configuration of a new OpenStack Project
1. Automated configuration
You can use a [Terraform enviroment template](https://github.com/cloudfoundry-incubator/bosh-openstack-environment-templates/tree/master/bosh-init-tf) to configure your OpenStack project.
1. Manual configuration
<p class="note"><strong>Note</strong>: See the <a href="http://docs.openstack.org/">OpenStack documentation</a> for help finding more information.</p>
Alternatively, you can do the following things manually as described below:
* Create a [Keypair](#keypair).
* Create and configure [Security Groups](#security-groups).
* Allocate a [floating IP address](#floating-ip).
---
### <a id="keypair"></a>Create a Keypair
1. Select **Access & Security** from the left navigation panel.
1. Select the **Keypairs** tab.
<%= image_tag("images/micro-openstack/keypair.png") %>
1. Click **Create Keypair**.
1. Name the Keypair "bosh" and click **Create Keypair**.
<%= image_tag("images/micro-openstack/create-keypair.png") %>
1. Save the `bosh.pem` file to `~/Downloads/bosh.pem`.
<%= image_tag("images/micro-openstack/save-keypair.png") %>
---
### <a id="security-groups"></a>Create and Configure Security Groups
You must create and configure two Security Groups to restrict incoming network traffic to the BOSH VMs.
#### BOSH Security Group
1. Select **Access & Security** from the left navigation panel.
1. Select the **Security Groups** tab.
<%= image_tag("images/micro-openstack/security-groups.png") %>
1. Click **Create Security Group**.
1. Name the security group "bosh" and add the description "BOSH Security Group"
<%= image_tag("images/micro-openstack/create-bosh-sg.png") %>
1. Click **Create Security Group**.
1. Select the BOSH Security Group and click **Edit Rules**.
1. Click **Add Rule**.
<%= image_tag("images/micro-openstack/edit-bosh-sg.png") %>
1. Add the following rules to the BOSH Security Group:
<p class="note"><strong>Note</strong>: It highly discouraged to run any production environment with <code>0.0.0.0/0</code> source or to make any BOSH management ports publicly accessible.</p>
<table border="1" class="nice" >
<tr>
<th>Direction</th>
<th>Ether Type</th>
<th>IP Protocol</th>
<th>Port Range</th>
<th>Remote</th>
<th>Purpose</th>
</tr>
<tr><td>Ingress</td><td>IPv4</td><td>TCP</td><td>22</td><td>0.0.0.0/0 (CIDR)</td><td>SSH access from CLI</td></tr>
<tr><td>Ingress</td><td>IPv4</td><td>TCP</td><td>6868</td><td>0.0.0.0/0 (CIDR)</td><td>BOSH Agent access from CLI</td></tr>
<tr><td>Ingress</td><td>IPv4</td><td>TCP</td><td>25555</td><td>0.0.0.0/0 (CIDR)</td><td>BOSH Director access from CLI</td></tr>
<tr><td>Egress</td><td>IPv4</td><td>Any</td><td>-</td><td>0.0.0.0/0 (CIDR)</td></tr>
<tr><td>Egress</td><td>IPv6</td><td>Any</td><td>-</td><td>::/0 (CIDR)</td></tr>
<tr><td>Ingress</td><td>IPv4</td><td>TCP</td><td>1-65535</td><td>bosh</td><td>Management and data access</td></tr>
</table>
---
### <a id="floating-ip"></a>Allocate a floating IP address
1. Select **Access & Security** from the left navigation panel.
1. Select the **Floating IPs** tab.
<%= image_tag("images/micro-openstack/create-floating-ip.png") %>
1. Click **Allocate IP to Project**.
1. Select **External** from the **Pool** dropdown menu.
1. Click **Allocate IP**.
<%= image_tag("images/micro-openstack/allocate-ip.png") %>
1. Replace `FLOATING-IP` in your deployment manifest with the allocated Floating IP Address.
<%= image_tag("images/micro-openstack/floating-ip.png") %>
---
## <a id="deploy"></a> Step 2: Deploy
1. Install [CLI v2](./cli-v2.html).
1. Use `bosh create-env` command to deploy the Director.
<pre class='terminal'>
# Create directory to keep state
$ mkdir bosh-1 && cd bosh-1
# Clone Director templates
$ git clone https://github.com/cloudfoundry/bosh-deployment
# Fill below variables (replace example values) and deploy the Director
$ bosh create-env bosh-deployment/bosh.yml \
--state=state.json \
--vars-store=creds.yml \
-o bosh-deployment/openstack/cpi.yml \
-v director_name=bosh-1 \
-v internal_cidr=10.0.0.0/24 \
-v internal_gw=10.0.0.1 \
-v internal_ip=10.0.0.6 \
-v auth_url=test \
-v az=test \
-v default_key_name=test \
-v default_security_groups=[test] \
-v net_id=test \
-v openstack_password=test \
-v openstack_username=test \
-v openstack_domain=test \
-v openstack_project=test \
-v private_key=test \
-v region=test
</pre>
If running above commands outside of an OpenStack network, refer to [Exposing environment on a public IP](init-external-ip.html) for additional CLI flags.
See [OpenStack CPI errors](openstack-cpi.html#errors) for list of common errors and resolutions.
1. Connect to the Director.
<pre class="terminal">
# Configure local alias
$ bosh alias-env bosh-1 -e 10.0.0.6 --ca-cert <(bosh int ./creds.yml --path /director_ssl/ca)
# Log in to the Director
$ export BOSH_CLIENT=admin
$ export BOSH_CLIENT_SECRET=`bosh int ./creds.yml --path /admin_password`
# Query the Director for more info
$ bosh -e bosh-1 env
</pre>
1. Save the deployment state files left in your deployment directory `bosh-1` so you can later update/delete your Director. See [Deployment state](cli-envs.html#deployment-state) for details.
---
[Back to Table of Contents](index.html#install)
Previous: [Create an environment](init.html)