Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-06 Thread Monty Taylor
05, 2013 8:35 PM To: Mark McLoughlin; Douglas Mendizabal Cc: OpenStack Development Mailing List (not for usage questions); openstack...@lists.openstack.org; barbi...@lists.rackspace.com Subject: Re: [openstack-tc] [openstack-dev] Incubation Request for Barbican On 12/06/2013 01:53 AM, Mark

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-06 Thread John Wood
); openstack...@lists.openstack.org; barbi...@lists.rackspace.com Subject: Re: [openstack-tc] [openstack-dev] Incubation Request for Barbican On 12/06/2013 08:35 AM, John Wood wrote: Hello folks, Just an FYI that I've submitted a pull request [1] to replace Celery with oslo.messaging. wow

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-05 Thread Douglas Mendizabal
I agree that this is concerning. And that what's concerning isn't so much that the project did something different, but rather that choice was apparently made because the project thought it was perfectly fine for them to ignore what other OpenStack projects do and go off and do its own thing.

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-05 Thread Mark McLoughlin
On Thu, 2013-12-05 at 23:37 +, Douglas Mendizabal wrote: I agree that this is concerning. And that what's concerning isn't so much that the project did something different, but rather that choice was apparently made because the project thought it was perfectly fine for them to ignore

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-05 Thread John Wood
: OpenStack Development Mailing List (not for usage questions); openstack...@lists.openstack.org; barbi...@lists.rackspace.com Subject: Re: [openstack-tc] [openstack-dev] Incubation Request for Barbican On 12/06/2013 01:53 AM, Mark McLoughlin wrote: On Thu, 2013-12-05 at 23:37 +, Douglas Mendizabal

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-04 Thread Jarret Raim
I think this conversation has gotten away from our incubation request and into an argument about what makes a good library and when and how projects should choose between oslo and other options. I¹m happy to have the second one in another thread, but that seems like a longer conversation

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-03 Thread Flavio Percoco
On 03/12/13 03:12 +, Jarret Raim wrote: There are two big parts to this, I think. One is techincal - a significant portion of OpenStack deployments will not work with this because Celery does not work with their deployed messaging architecture. See another reply in this thread for an

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-03 Thread Doug Hellmann
On Mon, Dec 2, 2013 at 10:12 PM, Jarret Raim jarret.r...@rackspace.comwrote: There are two big parts to this, I think. One is techincal - a significant portion of OpenStack deployments will not work with this because Celery does not work with their deployed messaging architecture.

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-03 Thread Jarret Raim
I think there's something else you should take under consideration. Oslo messaging is not just an OpenStack library. It's the RPC library that all projects are relying on and one of the strong goals we have in OpenStack is to reduce code and efforts duplications. We'd love to have more people

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-03 Thread Jarret Raim
The API and developer documentation is at http://docs.openstack.org/developer/oslo.messaging/ This is great, thanks for the link. Would there be any objections to adding this to the github repo and the openstack wiki pages? I spent a bunch of time looking and wasn¹t able to turn this up.

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-03 Thread Jeremy Stanley
On 2013-12-03 16:43:32 + (+), Jarret Raim wrote: This is great, thanks for the link. Would there be any objections to adding this to the github repo I think you meant the git repo. What's a gi-thub? URL: http://git.openstack.org/cgit/openstack/oslo.messaging/tree/doc/source/ and the

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-03 Thread Russell Bryant
On 12/03/2013 11:40 AM, Jarret Raim wrote: I think there's something else you should take under consideration. Oslo messaging is not just an OpenStack library. It's the RPC library that all projects are relying on and one of the strong goals we have in OpenStack is to reduce code and efforts

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-03 Thread Russell Bryant
On 12/03/2013 01:26 PM, Russell Bryant wrote: Unless the requirements change, so far it looks like this request should be deferred a bit longer. And note that this is just my opinion, and note a statement of position on behalf of the entire TC. We can still officially consider the request at

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-02 Thread Monty Taylor
On 12/02/2013 11:53 AM, Russell Bryant wrote: On 12/02/2013 10:19 AM, Jarret Raim wrote: All, Barbican is the OpenStack key management service and we’d like to request incubation for the Icehouse release. A Rackspace sponsored team has been working for about 9 months now, including

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-02 Thread Russell Bryant
On 12/02/2013 12:46 PM, Monty Taylor wrote: On 12/02/2013 11:53 AM, Russell Bryant wrote: * Scope ** Project must have a clear and defined scope This is missing ** Project should not inadvertently duplicate functionality present in other OpenStack projects. If they do, they should

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-02 Thread Jarret Raim
* Process ** Project must be hosted under stackforge (and therefore use git as its VCS) I see that barbican is now on stackforge, but python-barbicanclient is still on github. Is that being moved soon? ** Project must obey OpenStack coordinated project interface (such as tox,

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-02 Thread Monty Taylor
On 12/02/2013 05:09 PM, Jarret Raim wrote: * Process ** Project must be hosted under stackforge (and therefore use git as its VCS) I see that barbican is now on stackforge, but python-barbicanclient is still on github. Is that being moved soon? ** Project must obey OpenStack

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-02 Thread Sylvain Bauza
Hi Jarret, 2013/12/2 Jarret Raim jarret.r...@rackspace.com It's also pretty easy for a stackforge project to opt-in to the global requirements sync job now too. Are there some docs on how to do this somewhere? I added a task for us to complete the work as part of the incubation request

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-02 Thread Dolph Mathews
On Mon, Dec 2, 2013 at 11:55 AM, Russell Bryant rbry...@redhat.com wrote: On 12/02/2013 12:46 PM, Monty Taylor wrote: On 12/02/2013 11:53 AM, Russell Bryant wrote: * Scope ** Project must have a clear and defined scope This is missing ** Project should not inadvertently

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-02 Thread Fox, Kevin M
: [openstack-dev] [openstack-tc] Incubation Request for Barbican On Mon, Dec 2, 2013 at 11:55 AM, Russell Bryant rbry...@redhat.commailto:rbry...@redhat.com wrote: On 12/02/2013 12:46 PM, Monty Taylor wrote: On 12/02/2013 11:53 AM, Russell Bryant wrote: * Scope ** Project must have a clear

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-02 Thread Russell Bryant
On 12/02/2013 06:46 PM, Dolph Mathews wrote: On Mon, Dec 2, 2013 at 11:55 AM, Russell Bryant rbry...@redhat.com mailto:rbry...@redhat.com wrote: On 12/02/2013 12:46 PM, Monty Taylor wrote: On 12/02/2013 11:53 AM, Russell Bryant wrote: * Scope ** Project must have

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-02 Thread Jarret Raim
There are two big parts to this, I think. One is techincal - a significant portion of OpenStack deployments will not work with this because Celery does not work with their deployed messaging architecture. See another reply in this thread for an example of someone that sees the inability

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-02 Thread Jarret Raim
I've been anxious to try out Barbican, but haven't had quite enough time to try it yet. But finding out it won't work with Qpid makes it unworkable for us at the moment. I think a large swath of the OpenStack community won't be able to use it in this form too. As mentioned in the other

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

2013-12-02 Thread John Wood
(not for usage questions); Russell Bryant Cc: openstack...@lists.openstack.org; cloudkeep@googlegroups. com; barbi...@lists.rackspace.com Subject: RE: [openstack-dev] [openstack-tc] Incubation Request for Barbican I've been anxious to try out Barbican, but haven't had quite enough time to try it yet