Redhat OpenStack 5.0 and PLUMgrid OpenStack Networking Suite 2.0 Installation Hands-on lab guide Oded Nahum Principal Systems Engineer PLUMgrid EMEA November 2014 Page 1
Page 2
Table of Contents Table of Contents... 3 Overview... 4 Exercise 1: Preparing the Infrastructure host... 7 Exercise 2: Creating, Installing and configuring the RHOS Installer VM... 8 Exercise 3: Creating Redhat OpenStack Deployment... 9 Exercise 4: Creating and Provisioning the RHOS Controller VM... 14 Exercise 5: Creating and provisioning the RHOS Compute VM... 20 Exercise 6: Preparing the RHOS setup to install PLUMgrid... 25 Exercise 7: Creating and Configuring PLUMgrid Lifecycle Management VM (LCM)... 28 Exercise 8: Adding PLUMgrid packages and configuration to the RHOS Installer... 32 Exercise 9: Post setup configurations and initial testing... 38 Appendix 1: Troubleshooting... 42 Appendix 2: TBD... 42 Page 3
Overview Hands-on Training Module Objective Provide hands-on experience with the installation, configuration and basic operation of Redhat OpenStack 5.0 and PLUMgrid OpenStack Networking Suite 2.0 Prerequisites Basic understanding of Linux, Virtualization, and some networking concepts Basic knowledge of using vi editor and command line interface tools VNC Viewer for remote access to the Infrastructure host. Audience PLUMgrid and Redhat SE s, customers and partners Lab Environment Details The lab environment uses a single physical host (Infrastructure host) that is used host and run all components of the solution as Virtual Machines, this type of deployment is also known as an All in one, our lab uses a CentOS 6.6 in desktop mode as the infrastructure host, the host needs to have at least one active internet connection (Private IP is OK) Here is a high level diagram that descried the lab setup Internet Infrastructure host (CentOS 6.6) RHOS Installer RHOS Controller Compute1 PG LCM Host Network (WiFi or ETH) Management network (Virtual) External network (Virtual) Page 4
List of Hosts and Virtual machines used in this lab VM Name IP Address Description / OS Infrastructure host TBD Infrastructure host: CentOS 6.6, Desktop (VNC) Virtual Machine Manager, KVM rhos-installer 192.168.100.20 RHEL 6.5 VM, RHEL OSP Installer (aka, Satellite or Foreman) rhos-controller DHCP OpenStack controller and PLUMgrid director rhos-compute1 DHCP OpenStack compute node, PLUMgrid IOVisor edge/gateway lcm 192.168.100.15 PLUMgrid Lifecycle Management VM PG Director VIP 192.168.100.200 A Virtual IP used to access PLUMgrid management console DHSC Range 192.168.100.50 192.168.100.70 DHCP Range used by the rhos-installer for node provisioning RHEL 7 Web repo See infra host IP RHEL 7 Installation files (ISO) hosted on a web accessible URL Required Lab Credentials The login credentials required to connect to the environment and complete the lab exercises. Machine Username Password Description Infra host root rhos-installer VM root plumgrid rhis-installer UI admin plumgrid rhos-controller VM root plumgrid rhos-controller UI admin plumgrid (Horizon) rhos-compute root plumgrid lcm root plumgrid PG Management Console plumgrid plumgrid Page 5
Hardware, software Redhat subscription requirements Infrastructure host As mention above the infrastructure host is a machines used to host all other VMs needed to build RHOS 5.0 and PLUMgrid OpenStack networking Suite 2.0, as such the infrastructure host needs to have at least the following minimum requirements: 16 GB RAM (more is better and needed if you want to have more than one compute node) 250 GB Disk space Virtualization support One active network connection with internet access Note Screenshots and workflows provided in this guide are based on CentOS 6.6 in Desktop mode and Virtual Machine Manager, however, this setup can also be built using other flavors such as Ubuntu, Mac OS with VMware Fusion, Windows with VMware Workstation or Virtualbox, etc. Software RHEL 6.5 Installation ISO RHEL 7 Installation ISO PLUMgrid LCM VM Image Redhat Subscription access and needed repo s The following repo s are needed for rhos-installer (RHEL 6.5) rhel-6-server-rpms rhel-6-server-openstack-foreman-rpms rhel-server-rhscl-6-rpms The following repo s are need for the rhos-controller and rhos-compute (RHEL 7) rhel-7-server-openstack-5.0-rpms rhel-7-server-rpms rhel-ha-for-rhel-7-server-rpms Page 6
Exercise 1: Preparing the Infrastructure host Overview For the purpose of this training the infrastructure host has been pre-provisioned and configured. Please proceed to exercise 3 Step by step guidance Estimated time to complete this lab: 1 minutes. Step Action 1. Please proceed to exercise 3 Summary Key Takeaways NOTES The key takeaways for this exercise are: Page 7
Exercise 2: Creating, Installing and configuring the RHOS Installer VM Overview For the purpose of the training the rhos-installer VM has been pre-created and configured, please proceed to exercise 3 Step by step guidance Estimated time to complete this lab: 1 minutes. Step Action 1. Please proceed to exercise 3 Summary Key Takeaways NOTES The key takeaways for this exercise are: Page 8
Exercise 3: Creating Redhat OpenStack Deployment Overview In this exercise we will create an OpenStack deployment using RHEL OSP Installer, once a deployment is created we can start the provisioning process of the RHOS 5. Nodes (Controller and compute nodes) Step by step guidance Estimated time to complete this lab: 5 minutes. Step Action 1. From your VNC desktop open a Firefox browser windows and navigate to http://192.168.100.20 Confirm the cert warning and login to the RHOS Installer using the following credentials: User: admin Password: plumgrid 2. From the UI menu navigate to OpenStack Installer -> New Deployment Page 9
3. Set Deployment Name: my_rhos_5 Still on the same page scroll down and change the Service Password option to: Use single password for all service Set password: plumgrid Click Next 4. Click on New Subnet Create the New Subnet using these values: Name: External DHCP Server: External DHCP Network Subnet: 172.16.20.0/24 Click Create Subnet Page 10
5. From Available Network Traffic Types drag and drop the networks types: Tenant -> Default External -> External Your screen should look like this: Click Next 6. Click Next to accept all defaults on the Service Overview screen Page 11
7. Under the Service Configuration screen click on Cinder (left side) Check the LVM option Click Submit 8. You should now see this screen 9. You re Done! Summery Key Takeaways The key takeaways for this exercise are: Page 12
NOTES Page 13
Exercise 4: Creating and Provisioning the RHOS Controller VM Overview In this exercise we will create a new VM to host the RHOS controller, the VM will be set to PXE boot and will be automatically provisioned by the RHOS Installer Step by step guidance Estimated time to complete this lab: 30 minutes. 1. From your desktop Open Virtual Machine Manager, Click on Create New VM 2. Name the VM rhos-controller and use the option to Network Boot (PXE) Click Forward 3. Set OS type to: Linux and Version to RHEL 7 or later Click Forward Page 14
4. Set VM Memory (RAM) to : 4096 and CPUs: 4 Note 8 GB RAM is preferred if you have resources on the infrastructure host Click Forward 5. Set the disk size to: 30 GB (Minimum) Click Forward Page 15
6. Check the Advanced Options and make sure that the Network selected is pgmgmt (ignore the earning message) And the Virt Type is KVM Click Finish 7. The VM will boot in to PXE mode and register itself with the rhos-installer, this can take 2-3 minutes, when complete you will see this screen. Page 16
8. Switch to the rhos-installer UI at http://192.168.100.20, login if needed. Navigate to Hosts -> Discovered Hosts, you should see the new VM registered Note down the name of the VM. Navigate to OpenStack Installer -> Deployments and click on the my_rhos_5 deployment 9. Click on the + sign next to Controller (Neutron), check the VM name you noted in the previous step Click Assign Hosts Page 17
10. Navigate to Hosts -> All Hosts, click on Edit next to your newly assigned host Change the name of the host to rhos-controller Click Submit Note - You might get a warning about IP conflict, Click ACK and then click Overwrite 11. Navigate back to OpenStack Installer -> Deployment -> my_rhos_5 and click on Deploy (top right corner of the screen) And Click Deploy again This will reboot the rhos-controller VM and the node provisioning will start, depending on the resources available this can take 5-10 minutes, the status and progress of the provisioning process can be observed from the rhos-installer UI or from the VM console. Once you see the login prompt to the VM login with root/plumgrid The provisioning of OpenStack services can be viewed by running this command: journalctl -f -u puppet Wait for the process to complete. Done. Page 18
12. To verify that the rhos-controller has been installed open a new browser windows and navigate to the IP address of the VM, you can find the IP of the rhos-controller VM form the rhos-installer UI, Hosts -> All Hosts and click on the rhos-controller VM. 13. Log in to Redhat OpenStack Dashboard UI user: admin password: plumgrid 14. You re Done! Summary Key Takeaways NOTES The key takeaways for this exercise are: Page 19
Exercise 5: Creating and provisioning the RHOS Compute VM Overview In this exercise we will create a new VM to host the RHOS Compute node, the VM will be set to PXE boot and will be automatically provisioned by the RHOS Installer, To save on resources of the infrastructure host we will use this VM as a compute Node and as a PLUMgrid Gateway, however, If you do have enough RAM, CPU and Disk you can create mode nodes as compute nodes only. Step by step guidance Estimated time to complete this lab: 30 minutes. Page 20
1. From your desktop open Virtual Machine Manager and create a new VM with the following parameters: Name: rhos-compute1 Boot device: Network (PXE) OS Type: Linux Version: RHEL 7 or later Memory (RAM) : 4096 CPUs: 4 Disk Size: 50 GB (Minimum, you can allocate more if you have) Important! Make sure you check the Customize configuration before install and that you select the pgmgmt network. Click Finish Page 21
2. We will use the compute1 VM as a gateway and need to add a 2 nd Network Interface, From the VM configuration windows click on Add Hardware. Note If you are creating a compute node only than skip this step 2-3 3. Click on Network on the left side of the window, Select External network from the drop down list Click Finish Page 22
4. Click Begin Installation Confirm that the VM is booting into PXE mode and you can see the Foreman Discovery Screen 5. Wait for 2-3 minutes for the initial boot to complete and switch back to the rhos-installer UI. Navigate to Hosts -> Discovered Hosts Note down the name of the new VM 6. Navigate to OpenStack Installer -> Deployments and click on my_rhos_5 deployment 7. Click on the + sign next to Compute (Neutron), check the VM name you noted down in the previous step Click Assign Hosts Page 23
8. Navigate to Hosts -> All Hosts and click on Edit next to your new assigned VM 9. Change the VM name to rhos-compute1 Click Submit Note - You might get a warning about IP conflict, Click ACK and then click Overwrite 10. Navigate to OpenStack Installer -> Deployments and click on my_rhos_5 deployment Click Deploy (top right corner of the screen) This will reboot the rhos-compute1 VM and the node provisioning will start, depending on the resources available this can take 5-10 minutes, the status and progress of the provisioning process can be observed from the rhos-installer UI or from the VM console. Once you see the login prompt to the VM login with root/plumgrid The provisioning of OpenStack services can be viewed by running this command: journalctl -f -u puppet Page 24
11. To verify that the compute1 node provisioning is complete log in to RHOS Dashboard and click on Hypervisors You should see the new node listed. 12. You re Done! Summary Key Takeaways The key takeaways for this exercise are: Exercise 6: Preparing the RHOS setup to install PLUMgrid Overview Before PLUMgrid configuration and packages can be added to a running Redhat OpenStack Cloud some additional modification needs to take place, this include changing the MTU of the network interfaces that connect to the Fabric network (pgmgmt) to 1580, setting SELinux to permissive and stopping the puppet agent Step by step guidance Estimated time to complete this lab: 10 minutes. Page 25
1. SSH or Console to the rhos-controller VM, login with root/plumgrid Run this commands: setenforce 0 Edit the SELinux config file and change the SELINUX value to: permissive vi /etc/selinux/config Change the MTU size of the NIC connected to the pgmgmt network, edit the ifcfg-eth1 file and add MTU=1580 to the file vi /etc/sysconfig/network-scripts/ifcfg-eth0 Note make sure you are changing the correct network interface Restart the network service: systemctl restart network Stop the puppet agent systemctl stop puppet Verify that the MTU change is reflected by running Ifconfig eth0 2. Repeat the same process for the rhos-compute1 node. Note the rhos-compute1 node has 2 network interfaces, we only need to change the one connected to the pgmgmt network Page 26
3. Summary Key Takeaways NOTES The key takeaways for this exercise are: Page 27
Exercise 7: Creating and Configuring PLUMgrid Lifecycle Management VM (LCM) Overview Step by step guidance Estimated time to complete this lab: xx minutes. 1. The lcm VM image has been preloaded to the infrastructure host and can be found at /home/images From your desktop open Virtual Machine Manager and create a new VM 2. Name the VM lcm and use Import existing disk image option Click Forward 3. Browse to /home/images and locate the lcm.qcow2 image and click on it. Set OS Type to: Linux Version: RHEL 6 Click Froward Page 28
4. Set the Memory (RAM) to 2048 MB and CPUs to: 2 Click Forward 5. Click on Advanced Options and change the selected network to: pgmgmt Click Finish 6. Wait for the VM to boot up, once you get the login prompt login in with User: root Password: plumgrid Edit the network setting by running this command: vi /etc/sysconfig/network-scripts/ifcfg-eth0 Use these values: IPADDR=192.168.100.15 GATEWAY=192.168.100.1 DNS1=192.168.100.20 Page 29
7. Save and exit the file. Restart network service by running this command: service network restart Check internet connectivity and name resolution by pinging www.google.com ping www.google.com Change the host file by running this command: vi /etc/hosts Delete the 2 lines starting with ::1 and 33.x, add a new line: 192.168.100.15 lcm.mycloud.local lcm Your file should look like this: Edit the hostname by running this command: vi /etc/sysconfig/network Change the hostname to: HOSTNAME=lcm.mycloud.local 8. Reboot the VM and log back in once the VM is up. 9. Update the packages on the VM by running this command: yum update When the upgrade process is complete reboot the VM and log back in once the VM is up. Page 30
10. Run this command to start the LCM installer: bash /opt/pg/var/www/files/lvm-installer.sh The LCM Installer wizard will start and will ask you some questions, use these answers: Enter customer name: Customer1 Enter site name: Site1 Is this a RHOS setup? (default [yes]): yes Enter RHEL-OSP Installer IP address: 192.168.100.20 Enter RHEL-OSP Installer admin password: plumgrid The installer will kick off the installation process and you will see a lot on lines running on the screen, this can take 4-5 minutes to complete. The LCM Installer will create a repo site that is used to store PLUMgrid packages, check if the repo is create by opening a new browser windows and navigating to: http://192.168.100.15:81 you should see something like this: 11. LCM Setup in complete. 12. Summary Key Takeaways NOTES The key takeaways for this exercise are: Page 31
Exercise 8: Adding PLUMgrid Packages and Configuration to the RHOS Installer Overview In this exercise we will add the PLUMgrid configuration (puppet classes) to the RHOS Installer and update the nodes to apply the new settings Step by step guidance Estimated time to complete this lab: 30 minutes. Page 32
1. SSH or Console to the rhos-installer VM, login with User: root Password: plumgrid Run this command: bash <(curl -s http://192.168.100.15:81/files/rhos-pg-installer.sh) this will kick off the Installer wizard and you will be asked several questions, use these answers: Would you like to set the repository now? yes Enter LCM Repository Base URL: http://192.168.100.15:81 Enter the RHEL OSP Installer environment name: production Enter RHEL-OSP Installer hostgroup name: base_redhat_7/my_rhos_5 Enter 1 or 3 PLUMgrid Director IPs (separated by commas or space): 192.168.100.5x (Note this should be the same IP as the rhos-controller, make sure you use the correct IP) Enter PLUMgrid Virtual IP: 192.168.100.200 Enter PLUMgrid Network: 192.168.100.0/24 Enter PLUMgrid Console Username: plumgrid Enter PLUMgrid Console Password: plumgrid Enter RHEL-OSP Installer Admin Password: plumgrid When the process completes successfully you will see this screen: Page 33
2. Open a browser windows and navigate to the rhos-installer UI at http://192.168.100.20 Login with User: admin Password: plumgrid Navigate to Hosts -> All Hosts ad click on the rhos-controller.mycloud.local node. On the node details window click on Edit Click on the Puppet Classes tab, you should see the 2 new classes that are added, plumgrid and sal This is an indication that the PLUMgrid puppet classes were added successfully 3. SSH or Console to the rhos-controller VM, login as User: root Password: plumgrid Run this command to run the puppet agent and update the configuration puppet agent vt This will kick of the installation and configuration of the PLUMgrid Director that will run as an LXC container on top of the rhos-controller VM, it can take several minutes to complete. Be patient J 4. When the process complete open a browser windows and navigate to https://192.168.100.200 (make sure you use https and not http) confirm the certificate warning / exception Login to the PLUMgrid console with: User: plumgrid Password: plumgrid Page 34
5. You will immediately get a warning that this is not a licenses system, click OK and then Click Configure License 6. Copy / paste the text below to the license window: EkfD3Zy+jQAeQTbfR8c0g4SiPZtk88znt3sXI4GQUOeewPd517QjIavvBmf/YQr7uEC9hXb+Wl8hjZMwn7yyscwL/CqJC9oI/kUwX1 vljsscvmub2kpmhtsoyszjgdd3sx9n0voesdxfoxkx7wzejyoqmppl4obkbrij4+uzjevgkix0sznon/k8p8zpamtcb5b95i/th88ha 8wQ9GwQfX/rRRc0ZwOCqUlAJy7l9sxRuRL1KgtLcsfDvwnoNcAeRIlWDtTNVt8XTC1T5LrNmv582Xrs+jNdd7swCXYTCuWlcLpv Sjwz+mrMXcm9DlIln+/V+4gcWPxbyyExrJkP1FACKPBsAtGjFYQPoJAvO4gJKZq8gOcFneErbQ7p4S+VuTKm/WlIyVddrGXaobo 8Q7TcyJWufQI4suTvtEGbPibo3Q6Ydtk8deP45CzeWmKmC4LJFvajUgLRiul7HfSlbReod9m2zWiK7nw3zMH4n6UO0cYLRZAzaD6a Ro7uTprYEgA1kCvNMRwBUX8CDkJ8eQ8cwNQe68nC6ZYvGGc6+fkcAynANAv3px54v5oZDtYmL2M5JlVCFoC4S4nhY1Jhj391fU ZJv6Ac5gCtqeXNM+a7q1p+7AQpYUws6L86TsKJYY5cR0SamWdCcbeUbXVd/t1UjcbhWOvd+QAkBwEHDhg= Click OK 7. Next step is to configure and install PLUMgrid on the compute1 node, since this node is acting as both a compute node and PLUMgrid gateway we need to first configure the 2 nd NIC to be used for external connectivity. From rhos-installer UI navigate to Hosts -> All Hosts and click on rhoscompute1.mycloud.local Click on Edit Click on the Network tab Scroll down until you see the 2 nd NIC, ignore any other interface that start with br or tun, this should look like this: Note down the interface identifier, most likely it will be eth1 Page 35
8. Click on Parameters tab, the first parameter on the list is called gateway_devs, click on Override Scroll down to the bottom of the page and add the following value: [ eth1 ] Click Submit 9. SSH or Console to the rhos-compute1 VM Run the following command: puppet agent vt This will kick of the installation and configuration of the of the rhos-compue1 VM, it can take several minutes to complete. Be patient J 10. When the process is complete switch back to PLUMgrid management console (UI) Click on Zone View and refresh the browser You should see both the RHOS controller / PG Director and the compute / gateway node 11. You re Done! Summary Page 36
Key Takeaways NOTES The key takeaways for this exercise are: Page 37
Exercise 9: Post Setup configurations and initial testing Overview In this exercise will run few port installation configurations and testing of the system. Step by step guidance Estimated time to complete this lab: xx minutes. Step Action 1. PLUMgrid must be in sync with Neutron DB, to make sure this is working OK we will need to delete the default security groups that was present before PLUMgrid was added, not to worry, OpenStack will re-create these groups immediately. To do that follow these steps 2. SSH to the rhos-controller VM, log in as root/plumgrid Run this command: source keystonerc_admin This will load the admin credentials that will be used by the OpenStack CLI client Run this command: neutron security-group-delete `neutron security-group-list grep default cut -f 2 -d' '` 3. Switch to the RHOS Dashboard, login ad admin/plumgrid Click on Project and then click on Access and Security 4. For the Default Security Group click on Manage Rules Page 38
Step Action 5. Click on Add Rule, Add a new rule will the following parameters Rule: All ICMP Direction: Ingress Remote: CIDR CIDR: 0.0.0.0/0 Click Add 6. If the rule is added successfully than add another rule with the following parameters: Rule: All ICMP Direction: Egress Remote: CIDR CIDR: 0.0.0.0/0 7. Switch Back to the PLUMgrid Management Console, Click on Virtual Domain View and refresh the browser windows, you should see a new Virtual domain created and a new (Still blank) Neutron-based topology This is an indication that the DB s are in sync 8. Creating an External (Provider) Network - Switch back to RHOS Dashboard and Click on Admin and then click on Networks 9. Click on +Create Network Page 39
Step Action 10. Add a New Network using these parameters: Name: External_Network Project: Admin Admin State: Checked External Network: Checked Click Create Network 11. Click on the newly created network and then click on +Create Subnet, Add the new Subnet with these values: Name: External Subnet Network Address: 172.16.200/24 IP Version: IPv4 Gateway IP: 172.16.20.1 Click Next Enable DHCP: Uncheck Allocation pool: 172.16.20.10,172.16.20.50 DNS Name Server: 8.8.8.8 12. 13. 14. 15. 16. 17. 18. 19. 20. Click Create Page 40
Summary Key Takeaways NOTES The key takeaways for this exercise are: Page 41
Appendix 1: Troubleshooting Overview Troubleshooting Overview Step by step guidance Estimated time to complete this lab: 5 minutes. Step Action 1. 2. 3. 4. 5. 6. Summary Key Takeaways NOTES The key takeaways for this exercise are: Appendix 2: TBD Overview TBD Step by step guidance Estimated time to complete this lab: 5 minutes. Page 42
Step 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Action Summary Key Takeaways NOTES The key takeaways for this exercise are: Page 43
Revision History Revision Change Description Updated By Date 0.9 Original Version Oded Nahum 25/11/2014 Page 44