Hi folks, I have done a once-over on the code and identified a lot of code that I think would fit well in openstack-common.
I updated: http://wiki.openstack.org/QuantumOpenstackCommon In most cases this is code we borrowed directly from another project (nova or glance) to get our basic web service + db infrastructure working or to handle config/flags. Dan On Thu, Jan 5, 2012 at 12:11 PM, Dan Wendlandt <d...@nicira.com> wrote: > > > On Tue, Jan 3, 2012 at 11:00 AM, 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. >> > > Great, thanks for the emails, and for driving the openstack-common work. > > I have created a launchpad issue to track this, and a wiki page linked to > the launchpad issue as a "spec": > - > https://blueprints.launchpad.net/quantum/+spec/identify-openstack-common-code > - http://wiki.openstack.org/QuantumOpenstackCommon > > I have assigned myself as the owner, to make sure it gets done, but > everyone should feel free to contribute suggestions to the wiki page. > > Dan > > > >> >> 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 >> > >> > >> >> >> > > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Dan Wendlandt > Nicira Networks: www.nicira.com > twitter: danwendlandt > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
