Package: networking-infoblox
Contains Neutron drivers for integration with Infoblox grids for IPAM and DNS.Free software: Apache licenseSource:http://git.openstack.org/cgit/openstack/networking-infobloxBugs:http://bugs.launchpad.net/networking-infobloxInstallation:https://opendev.org/x/networking-infoblox/src/branch/master/doc/source/installation.rst(Please use python 3.8 to avoid issues with package version conflicts)Configuration Guide:https://opendev.org/x/networking-infoblox/src/branch/master/doc/source/configuration_guide.rstFeaturesThis release of the driver supports:IPv4 and IPv6 Subnet creation, update and deletionIPv4 and IPv6 address allocation and deallocationSupport for fixed and floating IP addressesCreation and deletion of Host, A, AAAA, and PTR records during IP allocationCreation of authoritative zonesSupport for GM and CP members and Cloud APIFlexible mapping of OpenStack entities to network viewSet EAs to populate the Cloud tab in the Infoblox UISupport for Neutron Xena release (release 19.0.0 of the Driver)Authentication:Support for keystone v3 configuration:Support for Domain scope authenticationSupport for Project scope authenticationSupport for keystone SSL configurationDropped support for OpenStack Queens, RockySupported versions: Xena, WallabyOverviewThe IPAM driver consists of two components: thenetworking_infobloxPython
module, and theinfoblox-ipam-agent. Each of these depend upon theinfoblox-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 ConfigurationSee the documentation link above for details on Installation and Configuration or check doc/source/…Known issuesWhen deploying an instance with a domain label exceeding 63 characters, an unknown
host record name appears in the zone on NIOS. This is due to the NIOS restriction
of max 63 characters for domain labels.If a DNS zone is deleted, the corresponding network entry in NIOS must be deleted
prior to running the synchronization tool. Otherwise the synchronization would fail.If a host record from a DNS zone is deleted, the corresponding port entry in NIOS
must be deleted prior to running the synchronization tool. Otherwise the synchronization
would fail.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.If theDefault Domain Name Patternincludes 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.[1]https://pypi.python.org/pypi/infoblox-client