Throughout this book, many examples and architectures assume that a physical network and server hardware are used for the OpenStack infrastructure. If you do not have the physical hardware available, it is possible to set up a virtual environment using software such as VMware ESX/ESXi or VirtualBox. This appendix is meant to assist with the setup of a virtual environment using VirtualBox so that many of the examples throughout the book can be followed. This appendix covers the following topics:
When configuring VirtualBox networking, the following networks and types are required:
Network Type |
Name |
Network |
Adapter Address |
DHCP |
---|---|---|---|---|
NAT |
<default> |
<default> |
<default> |
Yes |
Host-only |
vboxnet0 |
10.254.254.0/24 |
10.254.254.1 |
No |
Host-only |
vboxnet1 |
10.50.0.0/24 |
10.50.0.1 |
No |
Internal |
overlay |
172.18.0.0/24 |
n/a |
No |
Some of these networks are configured within the Preferences window of the VirtualBox application, while others are configured within the virtual machine settings window. The configuration of these networks is covered in the following sections.
To configure host-only networks within VirtualBox, open up the Preferences window. On a MacOS X machine, this can be found under the VirtualBox menu; on a Windows machine, this can be found under the File menu. By default, the General settings window will appear:
Perform the following steps to configure the host-only networks:
The first network will correspond to MGMT_NET, which is the OpenStack management and API network. The host machine, in this case the workstation running VirtualBox, needs an IP address from the network in order to communicate with the virtual OpenStack infrastructure nodes. Specify the address as 10.254.254.1
and a netmask of 255.255.255.0
.
10.50.0.0/24
:10.50.0.1
and will be able to communicate with the floating IPs that are configured throughout the book. Once the changes are saved, both networks will be listed under Host-only Networks: