5 Bare Metal Installations:
6 =========================
8 Requirements as per Pharos:
9 ===========================
14 **Minimum 2 networks**
16 | ``1. First for Admin/Management network with gateway to access external network``
17 | ``2. Second for floating ip network to consume by tenants for floating ips``
19 **NOTE: JOID support multiple isolated networks for API, data as well as storage.
20 Based on your network options for Openstack.**
22 **Minimum 6 physical servers**
26 | `` Minimum H/W Spec needed``
29 | `` Hard Disk: 1(250 GB)``
30 | `` NIC: if0(Admin, Management), if1 (external network)``
32 2. Node servers (minimum 5):
34 | `` Minimum H/W Spec``
37 | `` Hard Disk: 2(1 TB preferred SSD) this includes the space for ceph as well``
38 | `` NIC: if0 (Admin, Management), if1 (external network)``
41 **NOTE: Above configuration is minimum and for better performance and usage of
42 the Openstack please consider higher spec for each nodes.**
44 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.
46 ------------------------
47 Jump node configuration:
48 ------------------------
50 1. Install Ubuntu 16.04.1 LTS server version of OS on the first server.
51 2. Install the git and bridge-utils packages on the server and configure minimum two bridges on jump host:
53 brAdm and brExt cat /etc/network/interfaces
55 | `` # The loopback network interface``
57 | `` iface lo inet loopback``
58 | `` iface if0 inet manual``
60 | `` iface brAdm inet static``
61 | `` address 10.5.1.1``
62 | `` netmask 255.255.255.0``
63 | `` bridge_ports if0``
64 | `` iface if1 inet manual``
66 | `` iface brExt inet static``
67 | `` address 10.5.15.1``
68 | `` netmask 255.255.255.0``
69 | `` bridge_ports if1``
71 **NOTE: If you choose to use the separate network for management, pulic , data and
72 storage then you need to create bridge for each interface. In case of VLAN tags
73 use the appropriate network on jump-host depend upon VLAN ID on the interface.**
76 Configure JOID for your lab
77 ===========================
79 **Get the joid code from gerritt**
81 *git clone https://gerrit.opnfv.org/gerrit/joid.git*
83 **Enable MAAS (labconfig.yaml is must and base for MAAS installation and scenario deployment)**
85 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.
87 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.
89 If enabling first time then follow it further.
90 - Create a directory in joid/labconfig/<company name>/<pod number>/ for example
92 *mkdir joid/labconfig/intel/pod7/*
94 - copy labconfig.yaml from pod6 to pod7
95 *cp joid/labconfig/intel/pod5/\* joid/labconfig/intel/pod7/*
104 1. Make sure Jump host node has been configured with bridges on each interface,
105 so that appropriate MAAS and JUJU bootstrap VM can be created. For example if
106 you have three network admin, data and floating ip then I would suggest to give names
107 like brAdm, brData and brExt etc.
108 2. You have information about the node MAC address and power management details (IPMI IP, username, password) of the nodes used for deployment.
110 ---------------------
111 modify labconfig.yaml
112 ---------------------
114 This file has been used to configure your maas and bootstrap node in a
115 VM. Comments in the file are self explanatory and we expect fill up the
116 information according to match lab infrastructure information. Sample
117 labconfig.yaml can be found at
118 https://gerrit.opnfv.org/gerrit/gitweb?p=joid.git;a=blob;f=labconfig/intel/pod6/labconfig.yaml
127 roles: [network,control]
131 mac: ["xx:xx:xx:xx:xx:xx"]
139 roles: [network,control]
143 mac: ["xx:xx:xx:xx:xx:xx"]
151 roles: [network,control]
155 mac: ["xx:xx:xx:xx:xx:xx"]
163 roles: [network,control]
167 mac: ["xx:xx:xx:xx:xx:xx"]
175 roles: [network,control]
179 mac: ["xx:xx:xx:xx:xx:xx"]
185 floating-ip-range: 10.5.15.6,10.5.15.250,10.5.15.254,10.5.15.0/24
211 Deployment of OPNFV using JOID:
212 ===============================
214 Once you have done the change in above section then run the following commands to do the automatic deployments.
220 After integrating the changes as mentioned above run the MAAS install.
221 then run the below commands to start the MAAS deployment.
223 `` ./03-maasdeploy.sh custom <absolute path of config>/labconfig.yaml ``
225 `` ./03-maasdeploy.sh custom http://<web site location>/labconfig.yaml ``
227 For deployment of Danbue release on KVM please use the following command.
229 `` ./03-maasdeploy.sh default ``
231 This will take approximately 20 minutes to couple hours depending on your
232 environment. This script will do the following:
234 1. Create 1 VMs (KVM) for Juju bootstrap.
235 2. Install MAAS on the jumphost.
236 3. Configure the MAAS to enlist and commission a VM for Juju bootstrap node.
237 4. Configure the MAAS to enlist and commission bare metal servers.
238 5. In case of virtual server deployments MAAS will create three more KVM servers and add those servers in MAAS fir deployment.
240 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.
247 | `` ./deploy.sh -o newton -s nosdn -t noha -l custom -f none -d xenial -m openstack``
250 ./deploy.sh -o newton -s nosdn -t noha -l custom -f none -d xenial -m openstack
252 NOTE: Possible options are as follows:
254 choose which sdn controller to use.
255 [-s <nosdn|odl|opencontrail|onos>]
256 nosdn: openvswitch only and no other SDN.
257 odl: OpenDayLight Boron version.
258 opencontrail: OpenContrail SDN.
259 onos: ONOS framework as SDN.
261 Mode of Openstack deployed.
263 noha: NO HA mode of Openstack
264 ha: HA mode of openstack.
266 Wihch version of Openstack deployed.
268 Newton: Newton version of openstack.
269 Mitaka: Mitaka version of openstack.
272 [-l <custom | default>] etc...
273 custom: For bare metal deployment where labconfig.yaml provided externally and not part of JOID.
274 default: For virtual deployment where installation will be done on KVM created using 03-maasdeploy.sh
276 what feature to deploy. Comma seperated list
277 [-f <lxd|dvr|sfc|dpdk|ipv6|none>]
278 none: no special feature will be enabled.
279 ipv6: ipv6 will be enabled for tenant in openstack.
280 lxd: With this feature hypervisor will be LXD rather than KVM.
281 dvr: Will enable distributed virtual routing.
282 dpdk: Will enable DPDK feature.
283 sfc: Will enable sfc feature only supported with onos deployment.
285 which Ubuntu distro to use.
286 [ -d <trusty|xenial> ]
288 Which model to deploy
289 JOID introduces the various model to deploy apart from openstack for docker based container workloads.
290 [-m <openstack|kubernetes>]
291 openstack: Openstack which will be used for KVM/LXD container based workloads.
292 kubernetes: Kubernes model will be used for docker based workloads.
294 OPNFV Scenarios in JOID
295 Following OPNFV scenarios can be deployed using JOID. Seperate yaml bundle will be created to deploy the individual scenario.
297 Scenario Owner Known Issues
298 os-nosdn-nofeature-ha Joid
299 os-nosdn-nofeature-noha Joid
300 os-odl_l2-nofeature-ha Joid Floating ips are not working on this deployment.
301 os-nosdn-lxd-ha Joid Yardstick team is working to support.
302 os-nosdn-lxd-noha Joid Yardstick team is working to support.
303 os-onos-nofeature-ha ONOSFW
304 os-onos-sfc-ha ONOSFW
305 k8-nosdn-nofeature-noha Joid No support from Functest and Yardstick
306 k8-nosdn-lb-noha Joid No support from Functest and Yardstick
308 Is the deployment done successfully?
309 ------------------------------------
310 Once deploy.sh is complete, use juju status to verify that all deployed unit are in the ready state.
314 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.
316 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.
318 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.
324 By default debug is enabled in script and error messages will be printed on ssh terminal where you are running the scripts.
326 To Access of any control or compute nodes.
327 juju ssh <service name>/<instance id>
328 for example to login into openstack-dashboard container.
330 juju ssh openstack-dashboard/0
331 juju ssh nova-compute/0
332 juju ssh neutron-gateway/0
334 All charm jog files are availble under /var/log/juju
336 By default juju will add the current user keys for authentication into the deployed server and only ssh access will be available.