|
1 year ago | |
---|---|---|
devstack | 3 years ago | |
doc/source | 2 years ago | |
etc/init.d | 4 years ago | |
networking_infoblox | 2 years ago | |
tools | 1 year ago | |
.coveragerc | 4 years ago | |
.gitignore | 5 years ago | |
.gitreview | 1 year ago | |
.mailmap | 5 years ago | |
.testr.conf | 5 years ago | |
CONTRIBUTING.rst | 5 years ago | |
HACKING.rst | 5 years ago | |
LICENSE | 5 years ago | |
README.rst | 3 years ago | |
babel.cfg | 5 years ago | |
openstack-common.conf | 5 years ago | |
requirements.txt | 2 years ago | |
setup.cfg | 4 years ago | |
setup.py | 5 years ago | |
test-requirements.txt | 4 years ago | |
tox.ini | 3 years ago |
Contains Neutron drivers for integration with Infoblox grids for IPAM and DNS.
This release of the driver supports:
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
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.
See the documentation link above for details on Installation and Configuration.
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.