networking-infoblox 1.0.0

Features

This release of the drivers supports:

• A single network view named ‘default’

• IPv4 Subnet creation and deletion

• IPv4 address allocation and deallocation as a Fixed Address

Configuring Infoblox

Infoblox must be set up with a network view named ‘default’. This network view will be used for all OpenStack IPAM.

Setting up a separate user in Infoblox for use by OpenStack is recommended.

A Subnet ID extensible attribute must be defined. It will be used to store the Neutron subnet ID on each network created.

Configuring Neutron

The grid connectivity and credentials configuration must be added to the neutron.conf file in infoblox and infoblox-dc stanzas. The infoblox stanza contains a list of grids, and then each there is an infoblox-dc containing the appropriate configuration for each grid. Support for multiple grids is not yet available.

Additionally, the ipam_driver option must be set in neutron.conf to infoblox.

Example configuration:

ipam_driver = infoblox

[infoblox]
cloud_data_center_id = 1

[infoblox-dc:1]
grid_master_host = 172.23.25.175
admin_user_name = admin
admin_password = infoblox
wapi_version = 1.4

Enabling in DevStack

To enable use of Infoblox in DevStack, add this repository as a plugin:

enable_plugin networking-infoblox https://git.openstack.org/openstack/networking-infoblox.git

You may set the configuration options above in your local.conf by using the corresponding variables:

Limitations

• IPv6 is not supported

• Subnet update (to change allocation pools) is not supported

• Cloud Platform appliances (Cloud API) is not supported

• Only a single network view ‘default’ may be used

• Overlapping IP addresses is not supported even between tenants (due to the network view limitation).

Known issues

Subnet deletion when using the ML2 plugin will delete the subnet from Neutron but leave the subnet in Infoblox due to Neutron bug 1510653 [1]. A patch [2] for this bug is available for the master branch.