On 05/07/2012 04:08 PM, Russell Bryant wrote:
On 05/07/2012 03:40 PM, Doug Hellmann wrote:
The metering project will probably want to take advantage of this work.
How far along is it, and how can we help?
I can speak to the nova.rpc part, at least.
I've been working on it some with hopes
The metering project will probably want to take advantage of this work. How
far along is it, and how can we help?
On Fri, Apr 6, 2012 at 6:56 AM, Swaminathan Venkataraman
venkat...@gmail.com wrote:
Hi,
I've created a blueprint for this. Please take a look and let me know your
comments.
On Apr 3, 2012, at 8:00 AM, Russell Bryant wrote:
[…]
3) nova.local
This looks like a good candidate for moving to openstack-common and
switching all usage of nova.local to be openstack.common.local.
Yeah, this one might be kind of weird, because it's used to set the 'nova
context',
Hi,
I've created a blueprint for this. Please take a look and let me know your
comments.
https://blueprints.launchpad.net/openstack-common/+spec/notifier
thanks,
Venkat
On Tue, Apr 3, 2012 at 11:13 PM, Jay Pipes jaypi...@gmail.com wrote:
On 04/03/2012 01:40 PM, John Garbutt wrote:
However,
@lists.launchpad.net
[mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net]
On Behalf Of Chris Behrens
Sent: 02 April 2012 23:53
To: Russell Bryant
Cc: Duncan McGreggor; openstack@lists.launchpad.net; Chris Behrens
Subject: Re: [Openstack] Moving nova.rpc into openstack.common
Awesome
Russell Bryant wrote:
I proposed a session to discuss this a bit at the summit:
http://summit.openstack.org/sessions/view/95
There are a lot of ways this could be approached. I'm going to try to
write up a proposal at some point to get a discussion moving.
Note that there is also the
Hi,
I'm actively working on the notification part. I did some analysis on the
code and dependencies and was planning to submit a blueprint by end of the
week. We can use that to finalize the interface for the notification. The
rpc implementation is rich (compared to just what we need for
Hi,
I'm actively working on the notification part. I did some analysis on the
code and dependencies and was planning to submit a blueprint by end of the
week. We can use that to finalize the interface for the notification. The
rpc implementation is rich (compared to just what we need for
Thanks for sharing this information. For the future, I think this type
of analysis and discussion is something that is great to have on the
mailing list instead of just a private group. I wish I had seen it sooner.
The code in nova.rpc seems useful enough that it very well may be used
Hey Russell,
On Mon, 2012-04-02 at 16:26 -0400, Russell Bryant wrote:
Greetings,
There was a thread on this list a little while ago about moving the
notification drivers that are in nova and glance into openstack.common
since they provide very similar functionality, but have implementations
On 04/03/2012 09:36 AM, Russell Bryant wrote:
Thanks for sharing this information. For the future, I think this type
of analysis and discussion is something that is great to have on the
mailing list instead of just a private group. I wish I had seen it sooner.
In Venkat's defense, I believe
On 04/03/2012 11:16 AM, Mark McLoughlin wrote:
4) nova.exception
nova.rpc defines two exceptions based on NovaException. They could be
based on OpenstackException from openstack-common, instead. There's
also an RPC exception defined in nova.exception, but that can be moved
into nova.rpc with
On 04/03/2012 12:23 PM, Jay Pipes wrote:
On 04/03/2012 09:36 AM, Russell Bryant wrote:
Thanks for sharing this information. For the future, I think this type
of analysis and discussion is something that is great to have on the
mailing list instead of just a private group. I wish I had seen
However, I'm not sure how people would feel about having both
openstack.common.exception and nova.exception in the tree since they
overlap quite a bit. I like being able to do work in pieces, but
having them both in the tree leaves the code in an odd state, so we
need some end goal in
On 04/03/2012 01:40 PM, John Garbutt wrote:
However, I'm not sure how people would feel about having both
openstack.common.exception and nova.exception in the tree since they
overlap quite a bit. I like being able to do work in pieces, but
having them both in the tree leaves the code in an odd
Greetings,
There was a thread on this list a little while ago about moving the
notification drivers that are in nova and glance into openstack.common
since they provide very similar functionality, but have implementations
that have diverged over time. Is anyone actively working on this? If
so,
I started looking into moving the notification drivers as well, but punted
because of the reliance on multiple things, RPC included. For us, it's a
nice to have but not a need.
As for your plan, it seems sensible to me.
On 4/2/12 3:26 PM, Russell Bryant rbry...@redhat.com wrote:
Greetings,
+1
Thanks for exploring this, Russell!
Next step: getting a common REST API abstraction in place that all the
projects can use... ;-)
d
On Mon, Apr 2, 2012 at 4:26 PM, Russell Bryant rbry...@redhat.com wrote:
Greetings,
There was a thread on this list a little while ago about moving the
Seems like a sensible plan. Carrot can go now. I marked it deprecated so we
can remove in folsom. I can take care of this today, even.
On Apr 2, 2012, at 3:02 PM, Duncan McGreggor dun...@dreamhost.com wrote:
+1
Thanks for exploring this, Russell!
Next step: getting a common REST API
19 matches
Mail list logo