<div dir="ltr">+1 to Vipul</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 1, 2013 at 9:46 PM, Michael Basnight <span dir="ltr"><<a href="mailto:mbasnight@gmail.com" target="_blank">mbasnight@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Oct 1, 2013, at 7:06 PM, Vipul Sabhaya wrote:<br>
<br>
> On Oct 1, 2013, at 3:37 PM, Michael Basnight <<a href="mailto:mbasnight@gmail.com">mbasnight@gmail.com</a>> wrote:<br>
><br>
>> On Oct 1, 2013, at 3:06 PM, Ilya Sviridov <<a href="mailto:isviridov@mirantis.com">isviridov@mirantis.com</a>> wrote:<br>
>><br>
>>><br>
>>> On Tue, Oct 1, 2013 at 6:45 PM, Tim Simpson <<a href="mailto:tim.simpson@rackspace.com">tim.simpson@rackspace.com</a>> wrote:<br>
>>> Hi fellow Trove devs,<br>
>>><br>
>>> With the Designate project ramping up, its time to refactor the ancient DNS code that's in Trove to work with Designate.<br>
>>><br>
>>> 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.<br>
>>><br>
>>> How it corelates with Trove dirrection to use HEAT for all provisioning and managing cloud resources?<br>
>>> There are BPs for Designate resource (<a href="https://blueprints.launchpad.net/heat/+spec/designate-resource" target="_blank">https://blueprints.launchpad.net/heat/+spec/designate-resource</a>) and Rackspace DNS (<a href="https://blueprints.launchpad.net/heat/+spec/rax-dns-resource" target="_blank">https://blueprints.launchpad.net/heat/+spec/rax-dns-resource</a>) as well and it looks logically to use the HEAT for that.<br>
>>><br>
>>> 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.<br>
>><br>
>> +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.<br>
>><br>
>> I would prefer, if there is no one in need, to abandon the exiting review and add it to heat support.<br>
>><br>
><br>
> 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.<br>
><br>
> 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.<br>
<br>
</div>Sounds like we have a winner.<br>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>