On 01/04/2012 02:31 PM, Jay Pipes wrote: > I am 100% behind this effort. In fact, Glance can/should be a perfect > candidate to test this kind of common code. > > AFAICT, the things that need to be done to make this a reality are: > > 1) Get openstack-common gated in Gerrit > 2) Get it packaged and installable via apt-get and pip > 3) Identify a project to start replacing pieces with openstack-common modules > > I am volunteering Glance to be #3. > > When can #1 and #2 be ready to go?
I've been chatting with Jason and I can get #1 ready to go today. We don't actually need #2 to be done before you start doing #3 with glance (yay for pip-requires and git urls) I'll send you a glance patch for consuming the openstack-common repo as soon as I get it moved over. Monty > -jay > > On Tue, Jan 3, 2012 at 12:00 PM, Mark McLoughlin <mar...@redhat.com> wrote: >> Hi Dan, >> >> I've just now posted the plans Jason and I have for openstack-common >> here: >> >> http://wiki.openstack.org/CommonLibrary >> >> Thanks for poking us into doing it! :) >> >> Any help you can give would be awesome. Even a wiki page listing the >> APIs Quantum has that you think should be in openstack-common would be >> great. >> >> Cheers, >> Mark. >> >> On Tue, 2012-01-03 at 01:25 -0800, 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. >>> >>> 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/repo soon, 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. >>> >>> 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. >>> >>> Dan >>> >>> >> >> > -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
