Re: [Openstack-operators] neutron + ceilometer = memory-hungry neutron server

On Tue, Nov 25, 2014 at 6:27 PM, Joe Gordon wrote: > > > On Mon, Nov 24, 2014 at 9:13 PM, George Shuklin > wrote: >> >> Hello. >> >> We using ceilometer to meter tenants traffic. We have some complicated >> list of exclusion list (unlimited traffic to our own networks). >> >> We've got about 100k

[Openstack-operators] [neutron] Neutron Priorities for Kilo

Note: Similar to Nova, cross-posting to operators. We've published the list of priorities for Neutron during the Kilo cycle, and it's available here [1]. The team has been discussing these since before the Paris Summit, and we're in the process of approving individual specs around these right now.

Re: [Openstack-operators] [openstack-dev] [neutron] services split starting today

Copying the operators list here to gain additional visibility for trunk chasers. On Mon, Dec 8, 2014 at 10:19 AM, Doug Wiegley wrote: > To all neutron cores, > > Please do not approve any gerrit reviews for advanced services code for > the next few days. We will post again when those reviews ca

Re: [Openstack-operators] The state of nova-network to neutron migration

On Fri, Dec 19, 2014 at 10:59 AM, Anita Kuno wrote: > > Rather than waste your time making excuses let me state where we are and > where I would like to get to, also sharing my thoughts about how you can > get involved if you want to see this happen as badly as I have been told > you do. > > Where

Re: [Openstack-operators] The state of nova-network to neutron migration

On Thu, Jan 15, 2015 at 2:19 PM, Kris G. Lindgren wrote: > Is the fact that neutron security groups don’t provide the same level > of isolation as nova security groups on your guys radar? > > Specifically talking about: > https://bugs.launchpad.net/neutron/+bug/1274034 > > That bug is actually

Re: [Openstack-operators] [Neutron] The specs process, effective operators feedback and product management

On Thu, Apr 9, 2015 at 9:52 AM, Assaf Muller wrote: > The Neutron specs process was introduced during the Juno timecycle. At the > time it > was mostly a bureaucratic bottleneck (The ability to say no) to ease the > pain of cores > and manage workloads throughout a cycle. Perhaps this is a somewh

Re: [Openstack-operators] [Large Deployers Team] neutron ask for network segments

On Fri, May 22, 2015 at 1:58 PM, Mike Dorman wrote: > Kris and I along with Belmiro drafted up a description and ask to > Neutron about the network segments topic. We just put it at the end of the > etherpad, others can review: > > https://etherpad.openstack.org/p/YVR-ops-large-deployments >

Re: [Openstack-operators] [openstack-dev] [nova] [neutron] Re: How do your end users use networking?

On Wed, Jun 17, 2015 at 1:59 AM, Armando M. wrote: > > > On 16 June 2015 at 22:36, Sam Morrison wrote: > >> >> On 17 Jun 2015, at 10:56 am, Armando M. wrote: >> >> >> >> On 16 June 2015 at 17:31, Sam Morrison wrote: >> >>> We at NeCTAR are starting the transition to neutron from nova-net and >

Re: [Openstack-operators] [openstack-dev] [nova] [neutron] Re: How do your end users use networking?

On Wed, Jun 17, 2015 at 9:08 AM, John Griffith wrote: > > > On Tue, Jun 16, 2015 at 8:20 AM, Jay Pipes wrote: > >> Adding -dev because of the reference to the Neutron "Get me a network >> spec". Also adding [nova] and [neutron] subject markers. >> >> Comments inline, Kris. >> >> On 05/22/2015 09

Re: [Openstack-operators] [openstack-dev] [nova] [neutron] Re: How do your end users use networking?

ant to talk face-to-face about > https://bugs.launchpad.net/neutron/+bug/1458890. > > > Kris Lindgren > Senior Linux Systems Engineer > GoDaddy, LLC. > > From: Kyle Mestery > Date: Wednesday, June 17, 2015 at 7:08 AM >

Re: [Openstack-operators] [openstack-dev] [Neutron][L3] [Large Deployments Team] Representing a networks connected by routers

Can you also try to have some sort of remote option? I'd like to attend this, and I'd like Carl to try and attend as well. Thanks! On Tue, Aug 4, 2015 at 8:50 AM, Ryan Moats wrote: > I will be there for my lightning talk, and I think armax and kevin_benton > will be there - it would be good to f

Re: [Openstack-operators] [openstack-dev] [Neutron][L3] [Large Deployments Team] Representing a networks connected by routers

nce tool to us? Absent any opinions, I’ll > just do a Google Hangout. > > Thanks! > Mike > > > From: Kyle Mestery > Date: Tuesday, August 4, 2015 at 8:09 AM > To: Ryan Moats > Cc: Mike Dorman, "OpenStack Development Mailing List (not for usage > questions

[Openstack-operators] [neutron] Any users of Neutron's VPN advanced service?

Operators: We (myself, Paul and Doug) are looking to better understand who might be using Neutron's VPNaaS code. We're looking for what version you're using, how long you're using it, and if you plan to continue deploying it with future upgrades. Any information operators can provide here would be

Re: [Openstack-operators] kilo/nfv-vlan-trunks

On Fri, Sep 25, 2015 at 7:49 AM, raju wrote: > Hi Team, > > I need to create trunk ports inside neutron where instances will receive > traffic from multiple vlans. > > Do I need to apply any patch to my current openstack version(kilo) to get > this feature? > > You can look here [1] for the BP wh

Re: [Openstack-operators] VPNaaS and FWaaS

On Fri, Apr 29, 2016 at 8:01 AM, Matt Jarvis wrote: > As some of you on this list may already know, there are issues in the > Neutron team with development resources on VPNaas and FWaaS, and there have > been discussions in Austin about deprecating the code from the main Neutron > codebase. The de

Re: [Openstack-operators] VPNaaS and FWaaS

On Fri, Apr 29, 2016 at 3:02 PM, Kosnik, Lubosz wrote: > Complete priority list is available on OSIC.org website and > currently there is no info about VPNaaS or FWaaS. There are mails added to > people responsible for roadmap and when you will have a complete list of > people

Re: [Openstack-operators] VPNaaS and FWaaS

On Mon, May 2, 2016 at 3:12 PM, Xav Paice wrote: > > > On 3 May 2016 at 05:03, Matt Jarvis wrote: >> >> Thanks for the clarification Kyle. >> >> On 2 May 2016 at 14:33, Kyle Mestery wrote: >>> >>> On Fri, Apr 29, 2016 at 8:01 AM, Matt Jarvis &