[openstack-dev] [Nova][neutron][NFV] Mid cycle sprints

Hi, +1 for Paris, since a mid-cycle sprint is already being hosted and organised by eNovance :) Sylvain - Original Message - > From: "Dmitry" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Sunday, June 15, 2014 3:40:43 PM > Subject: Re: [openstack-dev]

[openstack-dev] [Neutron][L3] FFE request: L3 HA VRRP

Hi all, I would like to request a FFE for the following patches of the L3 HA VRRP BP : https://blueprints.launchpad.net/neutron/+spec/l3-high-availability https://review.openstack.org/#/c/64553/ https://review.openstack.org/#/c/66347/ https://review.openstack.org/#/c/68142/ https://review.openst

Re: [openstack-dev] [Neutron] L3 HA VRRP concerns

Hi everyone, Sorry for the late reply, I was on vacation :) See, inline comments -Sylvain - Original Message - > From: "Assaf Muller" > 1) Is there a way through the API to know, for a given router, what agent is > hosting > the active instance? This might be very important for admins

[openstack-dev] [Neutron] set network admin_state_up to false

Hi, I'm working on this bug : https://bugs.launchpad.net/neutron/+bug/1237807 and I'm wondering how we should address this issue, below my suggestions/thoughts Currently when the admin_state_up of a network is set to false, the only thing which is done is that the dhcp instance of this networ

[openstack-dev] [Neutron] L3 agent external networks

Hi, I was reviewing this patch (https://review.openstack.org/#/c/52884/) from Oleg and I thought that is a bit tricky to deploy an l3 agent with automation tools like Puppet since you have to specify the uuid of a network that doesn't already exist. It may be better to bind a l3 agent to an net

Re: [openstack-dev] Distributed Virtual Router Discussion

Hi Swaminathan, I'm interested as well. On our side we are working on this BP https://blueprints.launchpad.net/neutron/+spec/l3-high-availability Suggestions are welcome. Regards, Sylvain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.or

Re: [openstack-dev] Change in openstack/neutron[master]: Add method to get iptables traffic counters

From: "Brian Haley" To: "Sylvain Afchain" Cc: openstack-dev@lists.openstack.org Sent: Monday, July 22, 2013 10:30:32 PM Subject: Re: Change in openstack/neutron[master]: Add method to get iptables traffic counters Sylvain, Something like this would require no marking: # ipt

Re: [openstack-dev] Change in openstack/neutron[master]: Add method to get iptables traffic counters

ou were marking them on input to be matched by something on > output > I'd feel different, but for just counting bytes we should be able to do it > another way. I can get back to you next week on figuring this out. Ok, I'll take a look too. Thanks. Sylvain. - Origina

Re: [openstack-dev] Change in openstack/neutron[master]: Add method to get iptables traffic counters

Hi Brian, For iptables rules, see below Yes the only way to setup metering labels/rules is the neutronclient. I agree with you about the future enhancement. Regards, Sylvain - Original Message - From: "Brian Haley" To: "Sylvain Afchain" Cc: openstack-dev@list

Re: [openstack-dev] Change in openstack/neutron[master]: Add method to get iptables traffic counters

Hi Brian, You're right It could be easier with your approach to get and keep the traffic counters. I will add a new method to get the details of traffic counters of a chain. https://review.openstack.org/35624 Thoughts? Regards, Sylvain. - Original Message - From: "Sylva

Re: [openstack-dev] Change in openstack/neutron[master]: Add method to get iptables traffic counters

a chain to get its traffic. My approach is I don't want the counters of a specific rule but I want to count the traffic going through the chain. Thoughts? Regards, Sylvain. - Original Message - From: "Brian Haley" To: "sylvain afchain" Cc: openstack-dev@lists.op