If you are a Network Engineer, one day you may be asked to roll out F5 ADC in the OpenStack environment. But hey, OpenStack may look new and scary to you, as it was for me. You’ve probably learned on Devcentral (https://devcentral.f5.com/s/wiki/openstack.openstack_heat.ashx) that Heat is a primary OpenStack orchestration service, and that Heat and the F5 Heat Plugins are useful for rolling out and configuring F5 BIG-IP Virtual Edition (VE) on top of the OpenStack environment.
Let’s say that you've decided to accustom yourself with Heat and F5 Heat Plugins, but you do not have access to any OpenStack test or development environments, and/or you do not have admin rights to install the F5 Heat Plugins in OpenStack. If so, this series of articles is for you.
Please note, that OpenStack is a moving target. By the time I was writing this article, Mitaka was the supported OpenStack release. See https://releases.openstack.org/ for further information.
This is what you need to create your small, single-host OpenStack lab environment:
Some hardware or virtual machine with >=4 cores, 16G of RAM and Intel VT-x/EPT or AMD-V/RVI support. In my case, it was an old Dell laptop that IT department intended to scrap. 😉
A decent Internet connection.
In case of bare metal deployment, you need a home router. In my case it was my old WRT54gl.
Ask your F5 Partner or F5 representatives for a couple of VE 45-day evaluation licenses.
To sum up, it cost me 0$ to build my own OpenStack lab environment.
This is what you will get:
Fully functional OpenStack Mitaka environment
Heat and F5 Heat Plugins
F5 VE as guest machine
Direct access to F5 GUI, CLI, Virtual Servers from your laptop or any other devices connected to the home router
Possibility to test F5 VE setup from inside or outside of OpenStack
[HW] – actions to be done for the bare metal deployment [VMware] – actions to be done for the VMware guest machine deployment no square bracket – do it regardless of whether it’s a physical or VMware deployment.
Download and Install the Operating System
Check if you have Intel VT-x/EPT or AMD-V/RVI turned on in your bios. Sample screenshot:
[HW] Store the CentOS image on a USB stick. The simplest method is to use some other Linux box. dd if=CentOS-6.5-x86_64-bin-DVD1.iso of=/dev/sdb In the above command, /dev/sdb is an USB device; your USB device name will most likely be different. To find out the USB device name, observe/var/log/syslog, or /var/log/messages, while connecting the USB drive to the Linux machine. Further info at: https://wiki.centos.org/HowTos/InstallFromUSBkey
[VMware] Create a custom VMware workstation virtual machine. Set everything to default except:
Guest Operating system: RedHat Enterprise Linux 7 64-bit.
Number of processors: 4
Memory for this Virtual Machine [RAM]: 16384MB (16G)
Use Network address translation. You should review and alter the VMware network configuration. Let’s assume that the NAT network is 10.128.10.0/24, where a default route and DNS is set to 10.128.10.2, turn off DHCP.
Maximum disk size: 200GB
IMPORTANT: Turn on a nested VM support by: Edit virtual machine settings -> Processors -> enable Virtualize Intel VT-x/EPT or AMD-V/RVI NOTE: If you see different GUI options, read this article: https://communities.vmware.com/docs/DOC-8970
For the sake of performance, disable memory page trimming:
Install CentOS. Boot the USB drive [HW] or connect the CentoOS .iso image to the VMware guest machine [VMware].
Configure the OS
Choose English as the language.
Set your local time zone. Correct time will ease troubleshooting.
Disable a Security Policy:
Set your hostname to: mitaka.f5demo.com and configure the network interface:
Turn on “Automatically connect to this network when it is available”:
Configure IPv4 address, mask, default route and DNS:
Check if the network interface is switched on:
[optional] Disable KDUMP (from the main screen)
Open INSTALLATION DESTINATION from the main screen and choose “Partition disk automatically”:
Hit “Begin Installation”.
Set root password to “default”. You need to hit “DONE” button twice to make CentOS accept the weak password. A user account is not required.
CentOS will prompt you to reboot.
Permit ssh root login.
Uncomment PermitRootLogin yes at /etc/ssh/sshd_config
Reboot the ssh service systemctl restart sshd.service
Configure the host
Now, you should be able to log in to your OpenStack host with an ssh client (e.g., putty or iTerm2), so you can copy/paste the rest of the commands.