Afaict infoblox integration cannot work with "stock" openstack components. I think you'll need a service plugin and additional logic to bypass Neutron's "baked" IPAM logic, and a modified DHCP agent to support relay.
The community is working on solution for integrating neutron with 3rd party IPAM and DNS [1, 2, 3] I hope [1] and [2] will be part of the Kilo schedule (and they should be in the Kilo priorities [4]). Item [3] so far seems a bit lower priority. Salvatore [1] https://review.openstack.org/97967 [2] https://review.openstack.org/105660 [3] https://review.openstack.org/97970 [4] https://review.openstack.org/#/c/136514/ On 25 November 2014 at 16:56, lucas.g...@gmail.com <lucas.g...@gmail.com> wrote: > Thanks for all the replies, Designate looks worth investigating. I'm a > little surprised there's really no open source solution for this concern > already (other than Designate). > > I'll be checking out Designate and Infoblox and a few other solutions. > > Thanks much > > Gary > > On Tue, Nov 25, 2014 at 7:34 AM, Mike Smith <mism...@overstock.com> wrote: > >> At Overstock.com we’re using InfoBlox for IPAM and DNS management, so >> our tools hit the InfoBlox api when provisioning/destroying OpenStack >> instances. We’d love to see some pluggable DNS / IPAM management built >> into Openstack that allow you to choose from a number of different >> providers (including InfoBlox as an option) >> >> I will confess that I have not played around with Designate yet. >> >> Mike Smith >> Principal Engineer, Website Systems >> Overstock.com >> >> >> >> >> On Nov 25, 2014, at 7:20 AM, Martinx - ジェームズ <thiagocmarti...@gmail.com> >> wrote: >> >> Hi! >> >> Currently, I'm using `phpipam` but, why not use OpenStack itself (I'm >> planning that)? Isn't the DNS "only missing feature"? Which might arrives >> with Designate in K (or by integrating Samba, "as a Service", in a distant >> the future)... >> >> Best! >> >> On 25 November 2014 at 03:28, lucas.g...@gmail.com <lucas.g...@gmail.com> >> wrote: >> >>> So no one else has anything to say on these issues? Best practices? >>> how they do it? >>> >>> It seems like a legitimate question. >>> >>> Gary >>> >>> On Fri, Nov 21, 2014 at 10:52 AM, lucas.g...@gmail.com < >>> lucas.g...@gmail.com> wrote: >>> >>>> Just wondering how people handle DNS / DHCP / IPAM in their private >>>> clouds, I realize that open stack networking handles the DHCP side >>>> internally, the important piece is how do other organizations integrate >>>> with their existing DNS/IPAM solutions? >>>> >>>> So, if I have an application stack in our current environment, we'd >>>> have DNS entries set in our DNS server, along with documenting the >>>> allocation in our local IPAM solution. >>>> >>>> When we start using private cloud that becomes unwieldy (it already >>>> is) and I'm wondering what solutions other organizations have come up with. >>>> >>>> Gary Lucas >>>> >>> >>> >>> _______________________________________________ >>> Mailing list: >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> Post to : openstack@lists.openstack.org >>> Unsubscribe : >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> >>> >> _______________________________________________ >> Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : openstack@lists.openstack.org >> Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> >> >> >> ------------------------------ >> >> CONFIDENTIALITY NOTICE: This message is intended only for the use and >> review of the individual or entity to which it is addressed and may contain >> information that is privileged and confidential. If the reader of this >> message is not the intended recipient, or the employee or agent responsible >> for delivering the message solely to the intended recipient, you are hereby >> notified that any dissemination, distribution or copying of this >> communication is strictly prohibited. If you have received this >> communication in error, please notify sender immediately by telephone or >> return email. Thank you. >> > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack