openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #13155
Re: Configuring Openstack (Essex) to use existing Dynamic DNS servers
You could check griddynamic's nova-dns project. It works with powerdns, but
dns backend is implemented as a plugin, so you can easily integrate your
own dns app.
Regards,
Márton Kiss, CTO
Xemeti
On Jun 13, 2012 3:43 AM, "Mitchell Broome" <mitchell.broome@xxxxxxxxx>
wrote:
> I didn't find anything that caught my eye either. I'm not sure if
> it's the kind of thing your looking for but I ended up writing my own
> integration. Basically, I'm watching the qpid queue (haven't tried
> rabbitmq) for messages related to the creation and deletion of
> instances and pushing the data into mysql that powerdns is using as a
> backend. I'm still using dnsmasq for the dhcp. It's still very much
> a work in progress but it 's been working fine in my test environment
> for a few weeks now.
>
> If you want, you can give it a try at:
> https://github.com/mbroome/openstackdns
>
>
> On Tue, Jun 12, 2012 at 12:31 PM, Lillie Ross-CDSR11
> <Ross.Lillie@xxxxxxxxxxxxxxxxxxxxx> wrote:
> > All,
> >
> > I'm finally starting the upgrade to our internal cloud to the Essex
> release that's part of Ubuntu 12.04LTS. I'd like to setup the cloud to
> register instance names with our existing internal DNS servers. While
> there's some mention of this searching the Web, I haven't stumbled across
> anything definitive.
> >
> > My guess is that I need to replace the default dnsmasq server with an
> alternate backend such as nsupdate, however I'm unsure how the overall
> DHCP/DNS plumbing is configured. Are there any pointers and/or design
> documents that I could be pointed towards to give me a better understanding
> to help me implement this functionality?
> >
> > Also, I see that there appears to be a nova-compute extension in the
> current development branch that appears to provide this functionality if
> I've read things correctly. However I'd rather rely upon released packages
> for our essex deployment, rather than pulling in code from the development
> trunk.
> >
> > Anyways, any pointers would be appreciated.
> >
> > Thanks in advance, and regards,
> > Ross
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openstack
> > More help : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
References