Skip to main content

Contains Neutron drivers for integration with Infoblox grids for IPAM and DNS.

Project description

Contains Neutron drivers for integration with Infoblox grids for IPAM and DNS.


This release of the driver supports:

  • IPv4 and IPv6 Subnet creation, update and deletion
  • IPv4 and IPv6 address allocation and deallocation
  • Support for fixed and floating IP addresses
  • Creation and deletion of Host, A, AAAA, and PTR records during IP allocation
  • Creation of authoritative zones
  • Support for GM and CP members and Cloud API
  • Flexible mapping of OpenStack entities to network view
  • Set EAs to populate the Cloud tab in the Infoblox UI


The IPAM driver consists of two components: the networking_infoblox Python module, and the infoblox-ipam-agent. Each of these depend upon the infoblox-client [1] library.

The IPAM driver will be consulted by Neutron whenever subnet or IP allocation is needed. The driver will use RESTful API calls (aka, “Web-API” or “WAPI”) to perform these operations in Infoblox. Additionally, the driver will tag each of these entities in Infoblox with various meta-data from OpenStack, such as the tenant and the corresponding OpenStack IDs for the objects. This tagging allows the entities to show up in the Cloud tab of the UI (which is available with the Cloud Network Automation license), giving full visibility into the OpenStack cloud from within Infoblox.

The agent serves a few functions. First, it will populate the local Neutron database with data about the Infoblox grid. This enables the selection of the member and the network view to be made when allocating subnets and IP addresses, without additional WAPI calls. Second, it listens for events on the OpenStack message bus, and makes WAPI calls related to objects that are not directly part of the IPAM function.

Installation and Configuration

See the documentation link above for details on Installation and Configuration.


When a change is made to the EAs within Infoblox that are used to control the IPAM driver configuration, those changes are not automatically synchronized to OpenStack. They will be syncrhonized during subnet or network creation or when the IPAM agent is restarted.

Currently there is no script to migrate existing OpenStack installation data into Infoblox, apart from the built-in vDiscovery in Infoblox 7.2.4 or later.

Known issues

1. Subnet deletion when using the ML2 plugin will delete the subnet from Neutron but leave the subnet in Infoblox due to Neutron bug 1510653 [2]. This is fixed in the stable/liberty branch of Neutron.

  1. Once the IPAM driver create a Network View on Infoblox, the name of the Network View should not be changed. Changing Network View name on Infoblox would result in data synchronization issue. This will be addressed in a future release of the IPAM driver.
  2. If the Default Domain Name Pattern includes one of the following patterns: {tenant_name}, {network_name} or {subnet_name}, the names of of the corresponding objects should not be changed in OpenStack once they are created. Changing them would result in data synchronization issue. This will be addressed in a future release of the IPAM driver.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
networking_infoblox-2.0.2-py2-none-any.whl (158.4 kB) Copy SHA256 hash SHA256 Wheel py2 Aug 2, 2016
networking-infoblox-2.0.2.tar.gz (130.8 kB) Copy SHA256 hash SHA256 Source None Aug 2, 2016

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page