I wonder if we can use some of the architecture of the new code and move the current implementation to that model. It'd preserve the existing functionality, set us up for the new implementation, and fits in with 'cleanup' for E4, etc.
On Feb 1, 2012, at 2:41 PM, Vishvananda Ishaya <vishvana...@gmail.com> wrote: > I am all for pulling this out, but I'm a bit concerned with the fact that we > have nothing to replace it with. There are some groups still trying to use > it. MercadoLibre is trying to use it for example. I know you guys are trying > to replace this with something better, but it would be nice not to break > people for 7+ months > > > So I guess I have some questions: > 1.a) is the current implementation completely broken? > > 1.b) if yes, is it fixable > > 2) If we do remove this, what can we tell people that need something like > zones between now and the Folsom release? > > Vish > On Feb 1, 2012, at 12:16 PM, Sandy Walsh wrote: > >> As part of the new (and optional) Zones code coming down the pipe, part of >> this is to remove the old Zones implementation. >> >> More info in the merge prop: >> https://review.openstack.org/#change,3629 >> >> So, can I? can I? Huh? >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
