I tend to agree with Erik, flexibility solves the problem for more
people, while solution 1 is likely the easiest to implement. I am not
sure that it makes sense for most people though - and would really
only work for greenfield deployments or clouds that had all of the DNS
entries relating to instances in the cloud.

First question; how are you intending on using it? Which of those
solutions works for you?

--David



On Thu, Jul 3, 2014 at 3:49 PM, Erik Weber <terbol...@gmail.com> wrote:
> To push that choice over to the operator you could add it as a
> global/zone/network option.
>
> As an operator i would prefer to have my own logic to handle cleanup, but
> this varies for everyone hence the option :-)
>
> Erik
> 3. juli 2014 21:45 skrev "Silvano Nogueira Buback" <silv...@corp.globo.com>
> følgende:
>
>> Hi guys,
>>
>>     I think you are busy because 4.4 release tasks, but I'm worried about
>> the time to 4.5 feature freeze. I put the documentation of feature in wiki
>> as requested and I hoped people read there and make some comments here.
>>
>> To help, I will put design issues that are in document, one by one, and we
>> can discuss in this thread. After each discussion I will change the
>> document.
>>
>>    I have one question about removing DNS domain when network has been
>> deleted. In my current implementation I remove DNS domain when network is
>> removed. But if the DNS domain is shared with another network or maybe is a
>> dns domain used outside ACS this can be a problem. What I can do with DNS
>> domain when network is removed:
>>
>>    1. Keep the current implementation. Always deleted DNS domain when
>>    network is removed (works well if the ACS is the only manager for the
>> DNS
>>    (one network domain per network).
>>    2. Remove DNS domain only if the domain was created by ACS. This can be
>>    a problem if someone put records after ACS creation.
>>    3. Remove DNS domain only if there is no more records there. Maybe DNS
>>    domain can stay forever there because an inconsistency that keep only
>> one
>>    record.
>>
>>
>> Which one is the best?
>>
>> []'s,
>>
>> Silvano Buback
>>
>>
>>
>> On Thu, Jun 26, 2014 at 11:34 AM, Silvano Nogueira Buback <
>> silv...@corp.globo.com> wrote:
>>
>> > Thank you David.
>> >
>> > I put design documents on wiki:
>> >
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Bind+and+PowerDNS+integration+by+Globo+DNSAPI
>> .
>> > I create an issue https://issues.apache.org/jira/browse/CLOUDSTACK-6998
>> > too.
>> >
>> > I look forward to hearing your feedbacks.
>> >
>> > []'s,
>> >
>> > Silvano Buback
>> >
>> >
>> > On Wed, Jun 25, 2014 at 5:50 PM, David Nalley <da...@gnsa.us> wrote:
>> >
>> >> On Wed, Jun 25, 2014 at 4:38 PM, Silvano Nogueira Buback
>> >> <silv...@corp.globo.com> wrote:
>> >> > Hi guys,
>> >> >
>> >> >    I finish the first version of design document:
>> >> >
>> >>
>> https://docs.google.com/document/d/1kbPQJrBC87ZtR-t7LwHFDzAmT436ShtjwKE84FVfByM/pub
>> >> > .
>> >> >
>> >> >    Someone could give me access to put design documents in wiki?
>> Bellow
>> >> the
>> >> > username of people work with Cloudstack in Globo.com and need access.
>> >> >
>> >> > snbuback silv...@corp.globo.com
>> >> > daniel.simoes daniel.sim...@corp.globo.com
>> >> > lokama - lok...@gmail.com
>> >> >
>> >> > Regards,
>> >> >
>> >> > Silvano Buback
>> >> >
>> >> >
>> >> >
>> >> > On Thu, Jun 19, 2014 at 11:29 AM, Silvano Buback <snbub...@gmail.com>
>> >> wrote:
>> >> >
>> >> >> Of course, I forgotten my account info:
>> >> >> snbuback / silv...@corp.globo.com
>> >> >>
>> >>
>> >>
>> >> Done.
>> >>
>> >> --David
>> >>
>> >
>> >
>>

Reply via email to