Applies To:Show Versions
About OpenStack servers
BIG-IQ Cloud includes a feature that provides you with the tools you need to manage OpenStack private cloud resources. These management tasks include discovering, creating, starting, and stopping BIG-IP VE virtual machines and application servers running in the private cloud.
You can use this feature to accommodate seasonal traffic fluctuations for which you might need to periodically add devices or application servers (referred to as, cloud bursting) or retract devices or application servers.
Network requirements for communication with OpenStack cloud services
Before you can manage devices residing in an OpenStack private cloud, you must establish proper communication between the BIG-IQ Cloud and OpenStack controller node. Generally, this means defining a network route between the BIG-IQ Cloud internal VLAN and the public Internet, or the OpenStack private cloud endpoint.
The BIG-IQ Cloud connector for OpenStack parses the OpenStack cloud's network naming convention as follows:
- Any network that contains the name mgmt, management, internal, or external is assumed to indicate a network type (management always-on management network, internal network, and external network, respectively). If there are multiple networks, BIG-IQ Cloud uses the first network it finds with those names to communicate with the OpenStack cloud.
- If there are no networks with those names, BIG-IQ Cloud assigns the network type based on the order in which the network was discovered. For example, if BIG-IQ Cloud discovers networks 10.10.10.0/24, 188.8.131.52/24, and 30.30.30/24, it assigns them as follows:
- Management network 10.10.10.0/24
- External network 184.108.40.206/24
- Internal network 220.127.116.11/24
This is important to know, because when you create a new application server in OpenStack through BIG-IQ Cloud, you are allowed to select the internal or external network, but not the management network.
For specific instructions about how to configure your network for OpenStack, refer to the OpenStack documentation.
OpenStack Compute edits required to use BIG-IP VE systems
Before you create BIG-IP VE systems in an OpenStack environment, you must edit a file on each OpenStack Compute node. If you do not edit this file, any BIG-IP VE system you configure fails to start.
- Log in to the command line of each OpenStack Compute node and edit /etc/nova/release to read as follows: [Nova] vendor = Red Hat product = Bochs package = RHEL 6.3.0 PC
- Restart the OpenStack Compute node services.
Associating an OpenStack connector with devices
- Log in to BIG-IQ Cloud with your administrator user name and password.
- Hover on the Connectors header and click the + icon when it appears.
- In the Name and Description fields, type a name and description. You can use the name and description to help you organize network resources into logical groups based on certain criteria, such as the location or application.
- From the Cloud Provider list, select OpenStack.
- In the OpenStack Controller Node URI field, type the URI for the OpenStack controller node.
- In the OpenStack User Name field, type the user name for the OpenStack administrator.
- In the OpenStack Tenant Name and OpenStack Password fields, type the tenant (also known as, project) name and password.
- Click the Save button at the top of the New Connector header.