> The subject of using placement in Cinder has come up, and since then I've had > a > few conversations with people in and outside of that team. I really think > until > placement is its own project outside of the nova team, there will be > resistance > from some to adopt it.
I know politics will be involved in this, but this is a really terrible reason to do a thing, IMHO. After the most recent meeting we had with the Cinder people on placement adoption, I'm about as convinced as ever that Cinder won't (and won't need to) _consume_ placement any time soon. I hope it will _report_ to placement so Nova can make better decisions, just like Neutron does now, but I think that's the extent we're likely to see if we're honest. What other projects are _likely_ to _consume_ placement even if they don't know they'd want to? What projects already want to use it but refuse to because it has Nova smeared all over it? We talked about this a lot in the early justification for placement, but the demand for that hasn't really materialized, IMHO; maybe it's just me. > This reluctance on having it part of Nova may be real or just perceived, but > with it within Nova it will likely be an uphill battle for some time > convincing > other projects that it is a nicely separated common service that they can use. Splitting it out to another repository within the compute umbrella (what do we call it these days?) satisfies the _technical_ concern of not being able to use placement without installing the rest of the nova code and dependency tree. Artificially creating more "perceived" distance sounds really political to me, so let's be sure we're upfront about the reasoning for doing that if so :) --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
