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
|
==================
JOID Configuration
==================
Bare Metal Installations:
=========================
Requirements as per Pharos:
===========================
Networking:
===========
**Minimum 2 networks**
| ``1. First for Admin/Management network with gateway to access external network``
| ``2. Second for floating ip network to consume by tenants for floating ips``
**NOTE: JOID support multiple isolated networks for API, data as well as storage.
Based on your network options for Openstack.**
**Minimum 6 physical servers**
1. Jump host server:
| `` Minimum H/W Spec needed``
| `` CPU cores: 16``
| `` Memory: 32 GB``
| `` Hard Disk: 1(250 GB)``
| `` NIC: if0(Admin, Management), if1 (external network)``
2. Node servers (minimum 5):
| `` Minimum H/W Spec``
| `` CPU cores: 16``
| `` Memory: 32 GB``
| `` Hard Disk: 2(1 TB preferred SSD) this includes the space for ceph as well``
| `` NIC: if0 (Admin, Management), if1 (external network)``
**NOTE: Above configuration is minimum and for better performance and usage of
the Openstack please consider higher spec for each nodes.**
Make sure all servers are connected to top of rack switch and configured accordingly. No DHCP server should be up and configured. Only gateway at eth0 and eth1 network should be configure to access the network outside your lab.
------------------------
Jump node configuration:
------------------------
1. Install Ubuntu 16.04.1 LTS server version of OS on the first server.
2. Install the git and bridge-utils packages on the server and configure minimum two bridges on jump host:
brAdm and brExt cat /etc/network/interfaces
| `` # The loopback network interface``
| `` auto lo``
| `` iface lo inet loopback``
| `` iface if0 inet manual``
| `` auto brAdm ``
| `` iface brAdm inet static``
| `` address 10.5.1.1``
| `` netmask 255.255.255.0``
| `` bridge_ports if0``
| `` iface if1 inet manual``
| `` auto brExt``
| `` iface brExt inet static``
| `` address 10.5.15.1``
| `` netmask 255.255.255.0``
| `` bridge_ports if1``
**NOTE: If you choose to use the separate network for management, pulic , data and
storage then you need to create bridge for each interface. In case of VLAN tags
use the appropriate network on jump-host depend upon VLAN ID on the interface.**
Configure JOID for your lab
===========================
**Get the joid code from gerritt**
*git clone https://gerrit.opnfv.org/gerrit/joid.git*
**Enable MAAS (labconfig.yaml is must and base for MAAS installation and scenario deployment)**
If you have already enabled maas for your environment and installed it then there is no need to enabled it again or install it. If you have patches from previous MAAS enablement then you can apply it here.
NOTE: If MAAS is pre installed without 03-maasdeploy.sh not supported. We strongly suggest to use 03-maaseploy.sh to deploy the MAAS and JuJu environment.
If enabling first time then follow it further.
- Create a directory in joid/labconfig/<company name>/<pod number>/ for example
*mkdir joid/labconfig/intel/pod7/*
- copy labconfig.yaml from pod6 to pod7
*cp joid/labconfig/intel/pod5/\* joid/labconfig/intel/pod7/*
labconfig.yaml file
===================
-------------
Prerequisite:
-------------
1. Make sure Jump host node has been configured with bridges on each interface,
so that appropriate MAAS and JUJU bootstrap VM can be created. For example if
you have three network admin, data and floating ip then I would suggest to give names
like brAdm, brData and brExt etc.
2. You have information about the node MAC address and power management details (IPMI IP, username, password) of the nodes used for deployment.
---------------------
modify labconfig.yaml
---------------------
This file has been used to configure your maas and bootstrap node in a
VM. Comments in the file are self explanatory and we expect fill up the
information according to match lab infrastructure information. Sample
labconfig.yaml can be found at
https://gerrit.opnfv.org/gerrit/gitweb?p=joid.git;a=blob;f=labconfig/intel/pod6/labconfig.yaml
*lab:
location: intel
racks:
- rack: pod6
nodes:
- name: rack-6-m1
architecture: x86_64
roles: [network,control]
nics:
- ifname: eth1
spaces: [public]
mac: ["xx:xx:xx:xx:xx:xx"]
power:
type: ipmi
address: xx.xx.xx.xx
user: xxxx
pass: xxxx
- name: rack-6-m1
architecture: x86_64
roles: [network,control]
nics:
- ifname: eth1
spaces: [public]
mac: ["xx:xx:xx:xx:xx:xx"]
power:
type: ipmi
address: xx.xx.xx.xx
user: xxxx
pass: xxxx
- name: rack-6-m1
architecture: x86_64
roles: [network,control]
nics:
- ifname: eth1
spaces: [public]
mac: ["xx:xx:xx:xx:xx:xx"]
power:
type: ipmi
address: xx.xx.xx.xx
user: xxxx
pass: xxxx
- name: rack-6-m1
architecture: x86_64
roles: [network,control]
nics:
- ifname: eth1
spaces: [public]
mac: ["xx:xx:xx:xx:xx:xx"]
power:
type: ipmi
address: xx.xx.xx.xx
user: xxxx
pass: xxxx
- name: rack-6-m1
architecture: x86_64
roles: [network,control]
nics:
- ifname: eth1
spaces: [public]
mac: ["xx:xx:xx:xx:xx:xx"]
power:
type: ipmi
address: xx.xx.xx.xx
user: xxxx
pass: xxxx
floating-ip-range: 10.5.15.6,10.5.15.250,10.5.15.254,10.5.15.0/24
ext-port: "eth1"
dns: 8.8.8.8
opnfv:
release: d
distro: xenial
type: noha
openstack: newton
sdncontroller:
- type: nosdn
storage:
- type: ceph
disk: /dev/sdb
feature: odl_l2
spaces:
- type: floating
bridge: brEx
cidr: 10.5.15.0/24
gateway: 10.5.15.254
vlan:
- type: admin
bridge: brAdm
cidr: 10.5.1.0/24
gateway:
vlan:*
Deployment of OPNFV using JOID:
===============================
Once you have done the change in above section then run the following commands to do the automatic deployments.
------------
MAAS Install
------------
After integrating the changes as mentioned above run the MAAS install.
then run the below commands to start the MAAS deployment.
`` ./03-maasdeploy.sh custom <absolute path of config>/labconfig.yaml ``
or
`` ./03-maasdeploy.sh custom http://<web site location>/labconfig.yaml ``
For deployment of Danbue release on KVM please use the following command.
`` ./03-maasdeploy.sh default ``
This will take approximately 20 minutes to couple hours depending on your
environment. This script will do the following:
1. Create 1 VMs (KVM) for Juju bootstrap.
2. Install MAAS on the jumphost.
3. Configure the MAAS to enlist and commission a VM for Juju bootstrap node.
4. Configure the MAAS to enlist and commission bare metal servers.
5. In case of virtual server deployments MAAS will create three more KVM servers and add those servers in MAAS fir deployment.
When it's done, you should be able to view MAAS webpage (http://<MAAS IP>/MAAS) and see 1 bootstrap node and bare metal servers in the 'Ready' state on the nodes page.
-------------
OPNFV Install
-------------
| `` ./deploy.sh -o newton -s nosdn -t noha -l custom -f none -d xenial -m openstack``
| `` ``
./deploy.sh -o newton -s nosdn -t noha -l custom -f none -d xenial -m openstack
NOTE: Possible options are as follows:
choose which sdn controller to use.
[-s|--sdn <nosdn|odl|opencontrail>]
nosdn: openvswitch only and no other SDN.
odl: OpenDayLight Boron version.
opencontrail: OpenContrail SDN.
Mode of Openstack deployed.
[-t|--type <noha|ha|tip>]
noha: NO HA mode of Openstack
ha: HA mode of openstack.
Wihch version of Openstack deployed.
[-o|--openstack <ocata|newton>]
Ocata: Ocata version of openstack.
Newton: Newton version of openstack.
Where to deploy
[-l|--lab <custom | default>] etc...
custom: For bare metal deployment where labconfig.yaml provided externally and not part of JOID.
default: For virtual deployment where installation will be done on KVM created using 03-maasdeploy.sh
what feature to deploy. Comma seperated list
[-f|--feature <lxd|dvr|sfc|dpdk|ipv6|none>]
none: no special feature will be enabled.
ipv6: ipv6 will be enabled for tenant in openstack.
lxd: With this feature hypervisor will be LXD rather than KVM.
dvr: Will enable distributed virtual routing.
dpdk: Will enable DPDK feature.
sfc: Will enable sfc feature only supported with onos deployment.
which Ubuntu distro to use.
[ -d|--distro <xenial> ]
Which model to deploy
JOID introduces the various model to deploy apart from openstack for docker based container workloads.
[-m|--model <openstack|kubernetes>]
openstack: Openstack which will be used for KVM/LXD container based workloads.
kubernetes: Kubernes model will be used for docker based workloads.
Deploy MAAS or not?
[--maasinstall <0|1>]
0: Do not deploy MAAS
1: Deploy MAAS first.
Lab Config file location
[--labfile <labconfig.yaml file>]
location of the file labconfig.yaml if no valid location then virtual MAAS would be deployed.
OPNFV Scenarios in JOID
Following OPNFV scenarios can be deployed using JOID. Seperate yaml bundle will be created to deploy the individual scenario.
Scenario Owner Known Issues
os-nosdn-nofeature-ha Joid
os-nosdn-nofeature-noha Joid
os-odl_l2-nofeature-ha Joid Floating ips are not working on this deployment.
os-nosdn-lxd-ha Joid Yardstick team is working to support.
os-nosdn-lxd-noha Joid Yardstick team is working to support.
os-ocl-nofeature-ha OCL Keystone V2 has been used.
os-ocl-nofeature-noha OCL Keystone V2 has been used.
k8-nosdn-nofeature-noha Joid No support from Functest.
k8-nosdn-lb-noha Joid No support from Functest.
k8-ovn-lb-noha OVN No support from Functest.
Is the deployment done successfully?
------------------------------------
Once deploy.sh is complete, use juju status to verify that all deployed unit are in the ready state.
| `` juju status ``
Find the Openstack-dashboard IP address from the *juju status* output, and see if you can log in via browser. The username and password is admin/openstack.
Optionally, see if you can log in Juju GUI. Juju GUI is on the Juju bootstrap node which is the VM define using 03-maasdeploy.sh. The username and password deplayed at the end of deployment along with url.
If you deploy ODL, OpenContrail or ONOS, find the IP address of the web UI and login. Please refer to each SDN guides for username/password.
------------
Troubleshoot
------------
By default debug is enabled in script and error messages will be printed on ssh terminal where you are running the scripts.
To Access of any control or compute nodes.
juju ssh <service name>/<instance id>
for example to login into openstack-dashboard container.
juju ssh openstack-dashboard/0
juju ssh nova-compute/0
juju ssh neutron-gateway/0
All charm jog files are availble under /var/log/juju
By default juju will add the current user keys for authentication into the deployed server and only ssh access will be available.
|
