Open Stack

+1 to Vipul


On Tue, Oct 1, 2013 at 9:46 PM, Michael Basnight <mbasnight at gmail.com>wrote:

> On Oct 1, 2013, at 7:06 PM, Vipul Sabhaya wrote:
>
> > On Oct 1, 2013, at 3:37 PM, Michael Basnight <mbasnight at gmail.com>
> wrote:
> >
> >> On Oct 1, 2013, at 3:06 PM, Ilya Sviridov <isviridov at mirantis.com>
> wrote:
> >>
> >>>
> >>> On Tue, Oct 1, 2013 at 6:45 PM, Tim Simpson <tim.simpson at rackspace.com>
> wrote:
> >>> Hi fellow Trove devs,
> >>>
> >>> With the Designate project ramping up, its time to refactor the
> ancient DNS code that's in Trove to work with Designate.
> >>>
> >>> The good news is since the beginning, it has been possible to add new
> drivers for DNS in order to use different services. Right now we only have
> a driver for the Rackspace DNS API, but it should be possible to write one
> for Designate as well.
> >>>
> >>> How it corelates with Trove dirrection to use HEAT for all
> provisioning and managing cloud resources?
> >>> There are BPs for Designate resource (
> https://blueprints.launchpad.net/heat/+spec/designate-resource) and
> Rackspace DNS (
> https://blueprints.launchpad.net/heat/+spec/rax-dns-resource) as well and
> it looks logically to use the HEAT for that.
> >>>
> >>> Currently Trove has logic for provisioning instances, dns driver,
> creation of security group, but with switching to HEAT way, we have
> duplication of the same functionality we have to support.
> >>
> >> +1 to using heat for this. However, as people are working on heat
> support right now to make it more sound, if there is a group that
> wants/needs DNS refactoring now, I'd say lets add it in. If no one is in
> need of changing what's existing until we get better heat support, then we
> should just abandon the review and leave the existing DNS code as is.
> >>
> >> I would prefer, if there is no one in need, to abandon the exiting
> review and add it to heat support.
> >>
> >
> > I would hate to wait til we have full Heat integration before getting
> Designate support, considering Heat does not yet have Designate support.
>  My vote is to move forward with a DNS driver in trove that can be
> deprecated once everything works with Heat.
> >
> > As far as supporting only Designate, I would be fine with a driver
> interface that could potentially wrap Designate as well as Rax DNS.  Given
> that both will be somewhat temporary, I don't see a reason why we have to
> rip out rsdns at this point.
>
> Sounds like we have a winner.
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131002/5adb3525/attachment.html>