On 01/03/2012 01:25 AM, Dan Wendlandt wrote: > The last netstack email about splitting Quantum repos touched a bit on > openstack-common, but I thought it was worth creating a separate > specifically on Quantum + openstack-common. I've tried to CC some of > the people that seem to be driving discussion of openstack-common > > When reviewing the Quantum codebase, there seems to be a good amount of > "infrastructure" code for both client + server that is not quantum > specific and was likely borrowed from existing projects like nova + > glance. I'd really like to get that code into something like > openstack-common for several reasons: > 1) keep quantum bloat down > 2) make sure bug fixes/enhancements made in one project benefit all projects > 3) make sure teams don't have to duplicate work writing unit tests in > each project.
Yes. I'm so much in favor of all of those bullet points. > Can someone working on openstack-common comment on the current state of > the work? Particularly, do we expect it to be a standard > github.com/openstack/ <http://github.com/openstack/> repo soon, Yes. I'm actually a little surprised it isn't already. and do > we expect it to be packaged for major distros soon? It wouldn't seem > like Quantum would want to start using it until that was the case. Yes to being packaged - but I think that it may not hit major distros until essex is properly out - so depending on it via pip-requires git url at the moment is, I believe, the way to go. > Assuming we can start depending on openstack-common, I would advocate > for a review of the quantum codease identifying chunks that either are > already in openstack-common, or we think are good candidates for > addition to openstack-common. I agree- and I think you can probably already start working on this. -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
