[openstack-dev] [neutron] [fwaas] Neutron FWaaS weekly team meeting cancelled on May 24.

Hi All: With the Summit at Vancouver, we will cancel the FWaaS weekly meeting for May 24 14:00 UTC. We will resume as usual from May 31. Thanks Sridar __ OpenStack Development Mailing List (not for usage questions) Unsubscr

Re: [openstack-dev] [neutron][neutron-fwaas] Request for inclusion of bug fixes in RC

Thanks An. The team has been working with An to review and validate these changes – we believe we are close to the final version and should be able to merge by tomorrow barring any unforeseen surprises. So pls consider adding these to the RC as they address some critical issues as outlined below

Re: [openstack-dev] [neutron][horizon] FWaaS/VPNaaS dashboard split out from horizon

Thanks Akihiro. From an FWaaS perspective, in agreement with Takashi on points below. On repository name, I am not religious as long as we keep things consistent. Thanks Sridar On 6/1/17, 12:59 AM, "Takashi Yamamoto" wrote: >On Wed, May 31, 2017 at 10:12 PM, Akihiro Motoki >wrote: >> Hi all,

[openstack-dev] [neutron][fwaas] Weekly FWaaS meeting cancelled next week due to the Summit.

Hi All: We will skip the weekly FWaaS meeting for next week with many of us traveling to the summit. Thanks Sridar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.ope

Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

Hi All: >From and FWaaS perspective - we also think (a) would be ideal. Thanks Sridar From: Kevin Benton mailto:ke...@benton.pub>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Monday, April 10, 2017 at 4:20 PM To: OpenStack List mailto:openstack-dev@lists.opensta

[openstack-dev] [neutron][fwaas] No FWaaS Meeting this week.

Hi All: Skipping this weeks FWaaS IRC meeting with some members at/traveling to PTG. We will resume next week as usual. Thanks Sridar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-de

Re: [openstack-dev] [neutron-fwaas] issue with firewall and sfc

Hi Vikash: The support for VM ports is in progress and we should have that completed fairly early in Pike. We have had some prelim thoughts on integration with SFC but have not come to that point yet. If u have some interest, u are also welcome to join our weekly meeting [1] and we can discuss

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

Sad to see u step down, thanks so much Armando for taking a "How can I help remove any roadblocks so we can move forward" approach to leadership. As part of a smaller project, ur support has certainly helped us make progress. Thanks Sridar PS: I was wondering if there will be a farewell speech

[openstack-dev] [neutron][fwaas] Weekly FWaaS meetings cancelled next 2 weeks.

Hi All: We will skip the weekly FWaaS meetings on Dec 27 and Jan 3 with the Holiday Season. We will start back on Jan 10 as usual. Happy Holidays to all. Thanks Sridar __ OpenStack Development Mailing List (not for usage q

Re: [openstack-dev] [neutron] Where will Neutron go in future?

h-south traffic belongs to FWaaS, isn't it? :) Thanks Zhi Chang 2016-12-20 1:45 GMT+08:00 Sridar Kandaswamy (skandasw) mailto:skand...@cisco.com>>: Hi Zhi: FWaaS has been seen more as an edge (on L3 ports) use case as opposed to SG which is on a VM port. Also, as u can see there ar

Re: [openstack-dev] [neutron] Where will Neutron go in future?

Hi Zhi: FWaaS has been seen more as an edge (on L3 ports) use case as opposed to SG which is on a VM port. Also, as u can see there are differences in the attributes on the Rule specification at the most basic level. At this point, we are working thru the implementation of FWaaS on L2 ports so

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

+1. From the neutron-fwaas perspective, Nate has been instrumental in driving our integration with neutron on the agent extension framework, neutron-lib as well as on CI. Thanks Sridar From: Kevin Benton mailto:ke...@benton.pub>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.o

Re: [openstack-dev] [neutron][fwaas] neutron-fwaas meeting time change

Thanks Nate. Based on further conversations and with the time change I think what we intended was: 14:00 UTC Tokyo: 11:00pm Bengaluru: 07:30pm US (EST): 09:00am US (PST): 06:00am I am fine with Mon or Tue. Thanks Sridar On 11/14/16, 12:07 PM, "Nate Johnston" wrote: >On Sat, Oct 29, 20

Re: [openstack-dev] [neutron] Cloud Provider Security Groups

Hi All: Thanks Kevin. David, yes I think we have a model that will work for u and would definitely want to discuss this more with u. I do hope that this can also help refine some of our thoughts. U can join us in our weekly IRC [1] (next one is tomorrow) and we can create an agenda item for mor

[openstack-dev] [fwaas] Weekly meeting cancelled on Oct 25th due to the Summit.

Hi All: We will cancel the FWaaS meeting next week due to the summit and resume the week after on Nov 1 as usual. Thanks and Safe travels. Sridar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [neutron][FWaaS] __init__ arguments issue status

Hi All: In digging thru this, yes with the neutron change, it changed the MRO as below and thus the issue. (, , , , , , <—— the issue is at this point where we have a mismatch with args , , ) Nate, Margaret – thanks for digging thru this – lets get together during the day to discuss th

Re: [openstack-dev] [neutron][fwaas][vpnaas][lbaas][octavia] summit summary - future of the advanced services

Hi All: Doug, thanks for the update and agree. On fwaas - we have some new contributors who are enthusiastic to make things happen in N. But if contributor priorities change and we struggle - will reach out to expedite the removal. Thanks Sridar On 5/5/16, 9:56 AM, "Doug Wiegley" wrote: >Egad

Re: [openstack-dev] [neutron][fwaas] how a disabled firewall should behave

Hi Takashi: There were discussions around this sometime in the H cycle w.r.t the reference implementation. IIRC, the consensus was that if a Firewall is configured, the points of insertion should be conservative and drop all traffic when admin_state_up is False. Only removing the Firewall will pas

Re: [openstack-dev] [neutron][vpnaas] VPNaaS project status

Could not agree more. Thanks very much Paul. And thanks also for always being a sounding board for common things across FWaaS and VPNaaS. Thanks Sridar From: Madhusudhan Kandadai mailto:madhusudhan.openst...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date

Re: [openstack-dev] [neutron][fwaas] openstack summit meetup

There are two slots (combined with LBaaS) Thu, Oct 29, 11am and the follow on at 11:50am [1]. Thanks Sridar [1] http://mitakadesignsummit.sched.org/overview/type/neutron From: Oğuz Yarımtepe mailto:oguzyarimt...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>>

[openstack-dev] [neutron][fwaas] FWaaS IRC meetings to happen alternate Wed (no mtg today).

Hi All: Just a reminder to FWaaS meeting attendees, as discussed in last weeks FWaaS IRC [1], with all the PTO’s going on and the need for time to build up on the SG alignment discussions – it was felt that it would be good to go to an alternate week format. So the next meeting will be on Jun 1

Re: [openstack-dev] [neutron] [fwaas] - Collecting use cases for API improvements

Hi All: Thanks German for articulating this – we did have this discussion on last Fri as well on the need to have more user inputs. FWaaS has been in a bit of a Catch22 situation with the experimental state. Regarding feature velocity – it has definitely been frustrating and we also lost contr

Re: [openstack-dev] [neutron][fwaas] neutron/agent/firewall.py

+1 Mathieu. Paul, this is not related to FWaaS. Thanks Sridar On 12/19/14, 2:23 PM, "Mathieu Gagné" wrote: >On 2014-12-19 5:16 PM, Paul Michali (pcm) wrote: >> >> This has a FirewallDriver and NoopFirewallDriver. Should this be moved >> into the neutron_fwaas repo? >> > >AFAIK, FirewallDriver

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Octavia's API becoming spun out LBaaS

Hi Doug: On 10/26/14, 6:01 PM, "Doug Wiegley" wrote: >Hi Brandon, > >> 4. I brought this up now so that we can decide whether we want to >> discuss it at the advanced services spin out session. I don't see the >> harm in opinions being discussed before the summit, during the summit, >> and more

Re: [openstack-dev] [Neutron] Simple proposal for stabilizing new features in-tree

______ From: Sridar Kandaswamy (skandasw) [skand...@cisco.com<mailto:skand...@cisco.com>] Sent: Thursday, August 14, 2014 3:07 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Simple proposal for stabilizing new features in-

Re: [openstack-dev] [Neutron] Simple proposal for stabilizing new features in-tree

Hi Aaron: There is a certain fear of another cascading chain of emails so with hesitation i send this email out. :-) 1) I could not agree with u more on the issue with the logs and the pain with debugging issues here. Yes for sure bugs do keep popping up but often times, (speaking for fwaas)

Re: [openstack-dev] [Neutron] Group Based Policy and the way forward

Hi All: +1 Ivar. Yes the timing of the alternate proposal does make the notion of spec reviews seem like a process tick mark with no seeming benefit. It is indeed unfair to the folks who have put in a lot of effort with an approved spec to have a workflow change pulled on them so late in the cy

Re: [openstack-dev] [neutron] Spec exceptions are closed, FPF is August 21

Hi All: There is no doubt the cores are quite stretched and it does take a finite amount of time to absorb the context and the content of the multitude of patches on any given core reviewer¹s queue. Life happens for everyone and things slip thru the cracks, but this suggestion on a timeline fo

Re: [openstack-dev] [Neutron] FWaaS: Support for explicit commit

Hi All: In discussing with some more folks from a deployment perspective - managing rules for PCI compliance and Audit requirements is quite important. And as is pointed below by Sumit, this can help enable a gate for any audit checks before actually applying it on the backend. Another use cas