================== 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/// 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: pike 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 /labconfig.yaml `` or ``   ./03-maasdeploy.sh custom http:///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) and see 1 bootstrap node and bare metal servers in the 'Ready' state on the nodes page. ------------- OPNFV Install ------------- | ``   ./deploy.sh -o pike -s nosdn -t noha -l custom -f none -d xenial -m openstack`` | ``   `` ./deploy.sh -o pike -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: openvswitch only and no other SDN. odl: OpenDayLight Boron version. opencontrail: OpenContrail SDN. Mode of Openstack deployed. [-t|--type ] noha: NO HA mode of Openstack ha: HA mode of openstack. Wihch version of Openstack deployed. [-o|--openstack ] pike: Pike version of openstack. Ocata: Ocata version of openstack. Where to deploy [-l|--lab ] 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 ] 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 ] Which model to deploy JOID introduces the various model to deploy apart from openstack for docker based container workloads. [-m|--model ] 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 ] 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 / 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.