Re: [Openstack] Blueprint etiquette

2012-01-06 Thread Thierry Carrez
Andrew Bogott wrote: > I am pretty close to fully implementing the api defined in this > blueprint, here: > > https://blueprints.launchpad.net/nova/+spec/public-and-private-dns > > Alas, I'm also about to attend a meeting at which Wikimedia folks will > almost certainly agree that we need a few f

Re: [Openstack] Blueprint etiquette

2012-01-06 Thread Kiall Mac Innes
Hi Andrew, One question, can you clarify/expand on the following sentence from the blueprint? Users can create new domains or delete existing ones. When a private domain > is created it can be assigned to an availability zone. Specifically, the assignment of a domain to an availability zone. T

Re: [Openstack] Blueprint etiquette

2012-01-06 Thread Kiall Mac Innes
On Thu, Jan 5, 2012 at 10:05 PM, Andrew Bogott wrote: > I doubt that anyone but me is keeping much of an eye on this extension, > but it nonetheless feels rude for me to unilaterally modify it when it is > already a part of a release schedule. I've been keeping an eye on it... and the additions

Re: [Openstack] Blueprint etiquette

2012-01-05 Thread Andrew Bogott
OK, good to know. I've updated the blueprint, although the changes are more modest than I anticipated; basically we're just adding functionality for creation/removal of DNS domains. -Andrew On 1/5/12 2:27 PM, Vishvananda Ishaya wrote: In my mind designs like this aren't set until a they are

Re: [Openstack] Blueprint etiquette

2012-01-05 Thread Vishvananda Ishaya
In my mind designs like this aren't set until a they are part of a release, so I don't mind it being changed. I think it is sufficient to send out a notification to the mailing list letting everyone know about the changes. Vish On Jan 5, 2012, at 2:05 PM, Andrew Bogott wrote: > I am pretty c

[Openstack] Blueprint etiquette

2012-01-05 Thread Andrew Bogott
I am pretty close to fully implementing the api defined in this blueprint, here: https://blueprints.launchpad.net/nova/+spec/public-and-private-dns Alas, I'm also about to attend a meeting at which Wikimedia folks will almost certainly agree that we need a few features added to that api in or