> Long term, I think AMQP could be used more widely, but I'd prefer
Speaking of the long run, don't forget about Burrow (which may
eventually replace AMQP in some cases):
http://burrow.openstack.org/introduction.html
As others have suggested, I think a focus on the REST interfaces for
communica
Thanks Dan. I just wanted to know what is the currently preferred method
of communication (given that in the long term it has scalability
implications). Your reasoning on using the RESTful interface to start
with makes sense to me.
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Monday, Jul
oy Toman [mailto:troy.to...@rackspace.com]
> *Sent:* Monday, July 25, 2011 10:41 AM
> *To:* Sumit Naiksatam (snaiksat)
> *Cc:* Ishimoto, Ryu;
> *Subject:* Re: [Netstack] "network-refactoring-l2" branch, and Quantum
>
> ** **
>
> ** **
>
> On Jul 25, 2011, at 12:
Hi Sumit,
On Mon, Jul 25, 2011 at 10:30 AM, Sumit Naiksatam (snaiksat) <
snaik...@cisco.com> wrote:
>
> **(4)**This last one is probably not specific to nova-refactoring –
> Dan mentioned the use of Quantum Client library as a possible way to
> communicate between nova and Quantum. Other nova
On Mon, Jul 25, 2011 at 4:58 AM, Ishimoto, Ryu wrote:
> Hi Sumit,
>
> Comments inline
>
> Thanks Dan for your detailed response. My question was indeed based on the
>> understanding that the current nova network managers (in the network
>> service) do perform some L3/DHCP/VPN configurations apart
ross more than one tenant?
Thanks,
~Sumit.
From: Troy Toman [mailto:troy.to...@rackspace.com]
Sent: Monday, July 25, 2011 10:41 AM
To: Sumit Naiksatam (snaiksat)
Cc: Ishimoto, Ryu;
Subject: Re: [Netstack] "network-refactoring-l2" branch, and Quantum
On Jul 25, 2011, at
On Jul 25, 2011, at 12:30 PM, Sumit Naiksatam (snaiksat) wrote:
Thank Ryu, very nice explanation, and does fall in line with what I could make
from studying the current implementation. I will let Dan also respond in case
he has any more insight. Meanwhile, a few comments/questions:
(1) Has
Thank Ryu, very nice explanation, and does fall in line with what I
could make from studying the current implementation. I will let Dan also
respond in case he has any more insight. Meanwhile, a few
comments/questions:
(1) Has anyone felt the need for Quantum to get notified when a
particul
Hi Sumit,
Comments inline
Thanks Dan for your detailed response. My question was indeed based on the
> understanding that the current nova network managers (in the network
> service) do perform some L3/DHCP/VPN configurations apart from L2
> configuration. As of today’s implementation in the netw
Thanks Dan for your detailed response. My question was indeed based on
the understanding that the current nova network managers (in the network
service) do perform some L3/DHCP/VPN configurations apart from L2
configuration. As of today's implementation in the
network-refactoring-l2 branch, one wou
Hi Sumit,
Very good questions. I'll give you my take inline, and Ryu should jump in
as well :)
Dan
On Sun, Jul 24, 2011 at 12:50 PM, Sumit Naiksatam (snaiksat) <
snaik...@cisco.com> wrote:
> Hi Ryu, Dan, and others involved,
>
> I had some questions regarding how the code base in the
> "networ
Hi Ryu, Dan, and others involved,
I had some questions regarding how the code base in the
"network-refactoring-l2" branch currently works (or is supposed to) with
Quantum.
As I understand, eventually we want to get to a point where one should
be able to run the Quantum service instead of the nova
12 matches
Mail list logo
