Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

2017-02-05 Thread pranab boruah
Hi Numan, Thanks for the input. I did a fresh install again and used an older OVS 2.6 package.(not using the TOT). Things are working now. Pranab On 2 February 2017 at 19:19, Numan Siddique wrote: > > > On Thu, Feb 2, 2017 at 6:05 PM, pranab boruah

Re: [openstack-dev] [neutron][networking-l2gw] ocata release?

2017-02-05 Thread Gary Kotton
Done - https://review.openstack.org/gitweb?p=openstack/networking-l2gw.git;a=shortlog;h=refs/heads/stable/ocata A luta continua On 2/6/17, 8:51 AM, "Gary Kotton" wrote: Hi, Yes, I will go and do this. Thanks Gary On 2/6/17, 4:05 AM, "Takashi

Re: [openstack-dev] [neutron][networking-l2gw] ocata release?

2017-02-05 Thread Takashi Yamamoto
thank you. On Mon, Feb 6, 2017 at 3:51 PM, Gary Kotton wrote: > Hi, > Yes, I will go and do this. > Thanks > Gary > > On 2/6/17, 4:05 AM, "Takashi Yamamoto" wrote: > > hi, > > is anyone going to cut ocata release/branch for networking-l2gw? > >

Re: [openstack-dev] [horizon] [neutron] Horizon support for Neutron Trunks - PTL approval needed

2017-02-05 Thread Richard Jones
That idea has merit, though I don't know what the scope for such a 'neutron-ui' might be. I'm definitely supportive of the Neutron Trunks UI efforts, but it'd be good to get an answer on this scope question before rolling along and creating the project. Richard On 6 February 2017 at 12:14,

Re: [openstack-dev] [neutron][networking-l2gw] ocata release?

2017-02-05 Thread Gary Kotton
Hi, Yes, I will go and do this. Thanks Gary On 2/6/17, 4:05 AM, "Takashi Yamamoto" wrote: hi, is anyone going to cut ocata release/branch for networking-l2gw? __ OpenStack

Re: [openstack-dev] OpenStack Summit Boston-CFP closes February 6th

2017-02-05 Thread Tom Fifield
Should be good for another 24.5 hours now :) Get those presentations in! On 廿十七年二月六日 暮 01:26, shubham sharma wrote: Hi, I am in IST timezone (UTC+5:30) and I am getting error in submitting proposal with following error. " *Warning!* Call for Presentations is closed!. " Anybody else facing

Re: [openstack-dev] OpenStack Summit Boston-CFP closes February 6th

2017-02-05 Thread shubham sharma
Hi, I am in IST timezone (UTC+5:30) and I am getting error in submitting proposal with following error. " *Warning!* Call for Presentations is closed!. " Anybody else facing this issue? Regards Shubham On Thu, Feb 2, 2017 at 12:44 AM, Erin Disney wrote: > Hi Everyone- > >

[openstack-dev] [neutron][networking-l2gw] ocata release?

2017-02-05 Thread Takashi Yamamoto
hi, is anyone going to cut ocata release/branch for networking-l2gw? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

2017-02-05 Thread Takashi Yamamoto
On Wed, Feb 1, 2017 at 9:46 AM, Takashi Yamamoto wrote: > hi, > > On Fri, Jan 27, 2017 at 7:46 AM, Doug Hellmann wrote: >> Excerpts from Takashi Yamamoto's message of 2017-01-26 11:42:48 +0900: >>> hi, >>> >>> On Sat, Jan 14, 2017 at 2:17 AM, Doug

Re: [openstack-dev] [horizon] [neutron] Horizon support for Neutron Trunks - PTL approval needed

2017-02-05 Thread Kevin Benton
If the horizon team would like neutron features to live outside, I wonder if it would make more sense to create a new 'neutron-ui' repo instead of it being trunk specific. That way we don't have to come up with a new repo for every new feature that needs a horizon UI. On Feb 3, 2017 09:26, "Bence

[openstack-dev] [neutron][taas] ocata

2017-02-05 Thread Takashi Yamamoto
tap-as-a-service folks, unless anyone objects, i'll make a ocata release and thus stable branch this week. (otherwise the CI of consuming subprojects will break) __ OpenStack Development Mailing List (not for usage

[openstack-dev] [trove] trove 7.0.0.0rc1 (ocata)

2017-02-05 Thread no-reply
Hello everyone, A new release candidate for trove for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/trove/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

2017-02-05 Thread Matt Riedemann
On 2/5/2017 1:19 PM, Clint Byrum wrote: Also I wonder if there's ever been any serious consideration given to switching to protobuf? Feels like one could make oslo.versionedobjects a wrapper around protobuf relatively easily, but perhaps that's already been explored in a forum that I wasn't

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

2017-02-05 Thread Clint Byrum
Excerpts from Matt Riedemann's message of 2017-02-04 16:09:56 -0600: > On 2/2/2017 4:01 PM, Sean Dague wrote: > > > > The only services that are running on Apache in standard gate jobs are > > keystone and the placement api. Everything else is still the > > oslo.service stack (which is basically