1 Bare Metal Installations:
2 =========================
4 Requirements as per Pharos:
5 ===========================
10 **Minimum 2 networks**
12 | ``1. First for Admin/Management network with gateway to access external network``
13 | ``2. Second for floating ip network to consume by tenants for floating ips``
15 **NOTE: JOID support multiple isolated networks for API, data as well as storage.
16 Based on your network options for Openstack.**
18 **Minimum 6 physical servers**
22 | `` Minimum H/W Spec needed``
25 | `` Hard Disk: 1(250 GB)``
26 | `` NIC: if0(Admin, Management), if1 (external network)``
28 2. Node servers (minimum 5):
30 | `` Minimum H/W Spec``
33 | `` Hard Disk: 2(1 TB preferred SSD) this includes the space for ceph as well``
34 | `` NIC: if0 (Admin, Management), if1 (external network)``
37 **NOTE: Above configuration is minimum and for better performance and usage of
38 the Openstack please consider higher spec for each nodes.**
40 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.
42 ------------------------
43 Jump node configuration:
44 ------------------------
46 1. Install Ubuntu 16.04.1 LTS server version of OS on the nodes.
47 2. Install the git and bridge-utils packages on the server and configure minimum two bridges on jump host:
49 brAdm and brPublic cat /etc/network/interfaces
51 | `` # The loopback network interface``
53 | `` iface lo inet loopback``
54 | `` iface eth0 inet manual``
56 | `` iface brAdm inet static``
57 | `` address 10.5.1.1``
58 | `` netmask 255.255.255.0``
59 | `` bridge_ports if0``
61 | `` iface brPublic inet static``
62 | `` address 10.5.15.1``
63 | `` netmask 255.255.255.0``
64 | `` bridge_ports if1``
66 **NOTE: If you choose to use the separate network for management, pulic , data and
67 storage then you need to create bridge for each interface. In case of VLAN tags
68 use the appropriate network on jump-host depend upon VLAN ID on the interface.**
71 Configure JOID for your lab
72 ===========================
74 **Get the joid code from gerritt**
76 *git clone https://gerrit.opnfv.org/gerrit/joid.git*
78 **Enable MAAS (labconfig.yaml is must and base for MAAS installation and scenario deployment)**
80 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.
82 NOTE: If MAAS is pre installed without 00-maasdeploy.sh then please do the following and skip rest of the step to enable MAAS.
84 1. Copy MAAS API key and paste in ~/.juju/environments.yaml at appropriate place.
85 2. Run command cp ~/.juju/environments.yaml ./joid/ci/
86 3. Generate labconfig.yaml for your lab and copy it to joid.
87 a. cp joid/labconfig/<company name>/<pod number>/labconfig.yaml joid/ci/ or
88 b. cp <newly generated labconfig.yaml> joid/ci
90 5. python genMAASConfig.py -l labconfig.yaml > deployment.yaml
91 6. python genDeploymentConfig.py -l labconfig.yaml > deployconfig.yaml
92 7. cp ./environments.yaml ~/.juju/
93 8. cp ./deployment.yaml ~/.juju/
94 9. cp ./labconfig.yaml ~/.juju/
95 10. cp ./deployconfig.yaml ~/.juju/
97 If enabling first time then follow it further.
98 - Create a directory in joid/labconfig/<company name>/<pod number>/ for example
100 *mkdir joid/labconfig/intel/pod7/*
102 - copy labconfig.yaml from pod6 to pod7
103 *cp joid/labconfig/intel/pod5/\* joid/labconfig/intel/pod7/*
112 1. Make sure Jump host node has been configured with bridges on each interface,
113 so that appropriate MAAS and JUJU bootstrap VM can be created. For example if
114 you have three network admin, data and public then I would suggest to give names
115 like brAdm, brData and brPublic.
116 2. You have information about the node MAC address and power management details (IPMI IP, username, password) of the nodes used for control and compute node.
118 ---------------------
119 modify labconfig.yaml
120 ---------------------
122 This file has been used to configure your maas and bootstrap node in a
123 VM. Comments in the file are self explanatory and we expect fill up the
124 information according to match lab infrastructure information. Sample
125 labconfig.yaml can be found at
126 https://gerrit.opnfv.org/gerrit/gitweb?p=joid.git;a=blob;f=labconfig/intel/pod6/labconfig.yaml
135 roles: [network,control]
139 mac: ["xx:xx:xx:xx:xx:xx"]
147 roles: [network,control]
151 mac: ["xx:xx:xx:xx:xx:xx"]
159 roles: [network,control]
163 mac: ["xx:xx:xx:xx:xx:xx"]
171 roles: [network,control]
175 mac: ["xx:xx:xx:xx:xx:xx"]
183 roles: [network,control]
187 mac: ["xx:xx:xx:xx:xx:xx"]
193 floating-ip-range: 10.5.15.6,10.5.15.250,10.5.15.254,10.5.15.0/24
217 ipaddress: 10.2.117.92
220 NOTE: If you are using VLAN tagged network then make sure you modify the case $1 section under Enable vlan interface with maas appropriately.
224 enableautomodebyname eth2 AUTO "10.4.9.0/24" compute || true
225 enableautomodebyname eth2 AUTO "10.4.9.0/24" control || true
228 Deployment of OPNFV using JOID:
229 ===============================
231 Once you have done the change in above section then run the following commands to do the automatic deployments.
237 After integrating the changes as mentioned above run the MAAS install.
238 then run the below commands to start the MAAS deployment.
240 `` ./00-maasdeploy.sh custom <absolute path of config>/labconfig.yaml ``
242 `` ./00-maasdeploy.sh custom http://<web site location>/labconfig.yaml ``
248 | `` ./deploy.sh -o mitaka -s odl -t ha -l custom -f none -d xenial``
251 ./deploy.sh -o mitaka -s odl -t ha -l custom -f none -d xenial
253 NOTE: Possible options are as follows:
255 choose which sdn controller to use.
256 [-s <nosdn|odl|opencontrail|onos>]
257 nosdn: openvswitch only and no other SDN.
258 odl: OpenDayLight Lithium version.
259 opencontrail: OpenContrail SDN can be installed with Juno Openstack today.
260 onos: ONOS framework as SDN.
262 Mode of Openstack deployed.
264 nonha: NO HA mode of Openstack
265 ha: HA mode of openstack.
267 Wihch version of Openstack deployed.
268 [-o <liberty|Mitaka>]
269 liberty: Liberty version of openstack.
270 Mitaka: Mitaka version of openstack.
273 [-l <custom | default | intelpod5 >] etc...
274 custom: For bare metal deployment where labconfig.yaml provided externally and not part of JOID.
275 default: For virtual deployment where installation will be done on KVM created using ./00-maasdeploy.sh
276 intelpod5: Install on bare metal OPNFV pod5 of Intel lab.
281 what feature to deploy. Comma seperated list
282 [-f <lxd|dvr|sfc|dpdk|ipv6|none>]
283 none: no special feature will be enabled.
284 ipv6: ipv6 will be enabled for tenant in openstack.
285 lxd: With this feature hypervisor will be LXD rather than KVM.
286 dvr: Will enable distributed virtual routing.
287 dpdk: Will enable DPDK feature.
288 sfc: Will enable sfc feature only supported with onos deployment.
290 which Ubuntu distro to use.
291 [ -d <trusty|xenial> ]
293 OPNFV Scenarios in JOID
294 Following OPNFV scenarios can be deployed using JOID. Seperate yaml bundle will be created to deploy the individual scenario.
296 Scenario Owner Known Issues
297 os-nosdn-nofeature-ha Joid
298 os-nosdn-nofeature-noha Joid
299 os-odl_l2-nofeature-ha Joid
300 os-nosdn-lxd-ha Joid Yardstick team is working to support.
301 os-nosdn-lxd-noha Joid Yardstick team is working to support.
302 os-onos-nofeature-ha ONOSFW
303 os-onos-sfc-ha ONOSFW
309 By default debug is enabled in script and error messages will be printed on ssh terminal where you are running the scripts.
311 To Access of any control or compute nodes.
312 juju ssh <service name>
313 for example to login into openstack-dashboard container.
315 juju ssh openstack-dashboard/0
316 juju ssh nova-compute/0
317 juju ssh neutron-gateway/0
319 By default juju will add the Ubuntu user keys for authentication into the deployed server and only ssh access will be available.