> If we're going to do the extraction in Stien, which we said we'd do in > Dublin, we need to start that as early as possible to iron out any > deployment bugs in the switch. We can't wait until the 2nd or 3rd > milestone, it would be too risky.
I agree that the current extraction plan is highly risky and that if it's going to happen, we need plenty of time to clean up the mess. I imagine what Sylvain is getting at here is that if we followed the process of other splits like nova-volume, we'd be doing this differently. In that case, we'd freeze late in the cycle when freezing is appropriate anyway. We'd split out placement such that the nova-integrated one and the separate one are equivalent, and do the work to get it working on its own. In the next cycle new changes go to the split placement only. Operators are able to upgrade to stein without deploying a new stein service first, and can switch to the split placement at their leisure, separate from the release upgrade process. To be honest, I'm not sure how we got to the point of considering it acceptable to be splitting out a piece of nova in a single cycle such that operators have to deploy a new thing in order to upgrade. But alas, as has been said, this is politically more important than ... everything else. --Dan __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev