Re: [Netstack] "network-refactoring-l2" branch, and Quantum

2011-07-25 Thread Sumit Naiksatam (snaiksat)
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

Re: [Netstack] "network-refactoring-l2" branch, and Quantum

2011-07-25 Thread Ishimoto, Ryu
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

Re: [Netstack] "network-refactoring-l2" branch, and Quantum

2011-07-25 Thread Sumit Naiksatam (snaiksat)
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

Re: [Netstack] "network-refactoring-l2" branch, and Quantum

2011-07-25 Thread Troy Toman
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

[Netstack] Quantum API question - port creation

2011-07-25 Thread Troy Toman
In reviewing the spec for creating ports, it is stated that it should asychronously create a port. But, it reviewing the implementation and even in the discussion of what data is returned, this does not seem to be an async operation. I would prefer to see this mirror the Nova API spec where crea

Re: [Netstack] "network-refactoring-l2" branch, and Quantum

2011-07-25 Thread Sumit Naiksatam (snaiksat)
Thanks Troy for your prompt response. Thanks for the clarification the relationship between the current notion of "project" and "tenant". On that, how does one share a network between multiple tenants/projects? To give a specific example, let's say we want to model an enterprise with multiple d

Re: [Netstack] "network-refactoring-l2" branch, and Quantum

2011-07-25 Thread Dan Wendlandt
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

Re: [Netstack] "network-refactoring-l2" branch, and Quantum

2011-07-25 Thread Dan Wendlandt
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

Re: [Netstack] "network-refactoring-l2" branch, and Quantum

2011-07-25 Thread Dan Wendlandt
Hi Sumit, This is one of the more advanced use cases that we've been considering with API authentication. At the extreme, you could imagine the Quantum API supporting a full RBAC model where the tenant is the "owner" has the right to "grant" permissions for others to do certain tasks on a network

Re: [Netstack] "network-refactoring-l2" branch, and Quantum

2011-07-25 Thread Sumit Naiksatam (snaiksat)
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