Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-06-20 Thread loy wolfe
GP should support applying policy on exist openstack deployment, so neither implicit mapping nor intercepting works well. maybe the explicit associating model is best: associate EPG with exist neutron network object (policy automatically applied to all ports on it), or with single port object

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-06-13 Thread Carlos Gonçalves
Hi Sumit, My concern was related to sharing common configuration information not between GP drivers but configurations between GP and ML2 (and any other future plugins). When both are enabled, users need to configure drivers information (e.g., endpoint, username, password) twice, when applicable

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-06-13 Thread Mohammad Banikazemi
(not for usage questions) openstack-dev@lists.openstack.org, Date: 06/12/2014 01:10 PM Subject:Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver Hi Carlos, I noticed that the point you raised here had not been followed up. So if I understand correctly

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-06-12 Thread Sumit Naiksatam
Hi Carlos, I noticed that the point you raised here had not been followed up. So if I understand correctly, your concern is related to sharing common configuration information between GP drivers, and ML2 mechanism drivers (when used in the mapping)? If so, would a common configuration file

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-06-12 Thread Sumit Naiksatam
Hi Carlos, I noticed that the point you raised here had not been followed up. So if I understand correctly, your concern is related to sharing common configuration information between GP drivers, and ML2 mechanism drivers (when used in the mapping)? If so, would a common configuration file

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-05-27 Thread Mohammad Banikazemi
, Date: 05/26/2014 09:46 PM Subject:Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver On May 26, 2014 4:27 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Armando, I think there are a couple of things that are being mixed up here, at least as I see

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-05-27 Thread Armando M.
: From: Armando M. arma...@gmail.com To: OpenStack Development Mailing List, (not for usage questions) openstack-dev@lists.openstack.org, Date: 05/26/2014 09:46 PM Subject: Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver -- On May 26, 2014 4

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-05-27 Thread Carlos Gonçalves
Hi, On 27 May 2014, at 15:55, Mohammad Banikazemi m...@us.ibm.com wrote: GP like any other Neutron extension can have different implementations. Our idea has been to have the GP code organized similar to how ML2 and mechanism drivers are organized, with the possibility of having different

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-05-27 Thread Sumit Naiksatam
There seems to be a fair bit of confusion with the PoC/prototype patches. As such, and per reviewer feedback to introduce the Endpoint Group related patch sooner than later, we will start a new series. You will see this first patch land shortly, and we can incrementally make progress from there.

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-05-26 Thread Mohammad Banikazemi
...@gmail.com wrote on 05/24/2014 01:36:35 PM: From: Armando M. arma...@gmail.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org, Date: 05/24/2014 01:38 PM Subject: Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver On 24 May 2014 05

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-05-26 Thread Armando M.
List (not for usage questions) openstack-dev@lists.openstack.org, Date: 05/24/2014 01:38 PM Subject: Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver On 24 May 2014 05:20, Robert Kukura kuk...@noironetworks.com wrote: On 5/23/14, 10:54 PM, Armando M. wrote

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-05-25 Thread Jay Pipes
On 05/24/2014 01:36 PM, Armando M. wrote: I appreciate that there is a cost involved in relying on distributed communication, but this must be negligible considered what needs to happen end-to-end. If the overhead being referred here is the price to pay for having a more dependable system (e.g.

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-05-24 Thread Robert Kukura
On 5/23/14, 10:54 PM, Armando M. wrote: On 23 May 2014 12:31, Robert Kukura kuk...@noironetworks.com wrote: On 5/23/14, 12:46 AM, Mandeep Dhami wrote: Hi Armando: Those are good points. I will let Bob Kukura chime in on the specifics of how we intend to do that integration. But if what you

Re: [openstack-dev] [neutron][group-based-policy] GP mapping driver

2014-05-24 Thread Armando M.
On 24 May 2014 05:20, Robert Kukura kuk...@noironetworks.com wrote: On 5/23/14, 10:54 PM, Armando M. wrote: On 23 May 2014 12:31, Robert Kukura kuk...@noironetworks.com wrote: On 5/23/14, 12:46 AM, Mandeep Dhami wrote: Hi Armando: Those are good points. I will let Bob Kukura chime in on