Re: [openstack-dev] [taas] rocky

i've just created 4.0.0 and rocky branch. On Wed, Sep 26, 2018 at 6:55 PM Takashi Yamamoto wrote: > > hi, > > it seems we forgot to create rocky branch. > i'll make a release and the branch sooner or later, unless someone >

Re: [openstack-dev] [neutron][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

hi, what kind of jobs should it be? eg. unit tests, tempest, etc... On Sun, Sep 30, 2018 at 9:43 AM Miguel Lavalle wrote: > > Dear networking Stackers, > > During the recent PTG in Denver, we discussed measures to prevent patches > merged in the Neutron repo breaking Stadium and related

[openstack-dev] [taas] rocky

hi, it seems we forgot to create rocky branch. i'll make a release and the branch sooner or later, unless someone beat me to do so. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [neutron] tox-siblings alternative for local testing

hi, after a recent change [1] , neutron-fwaas' unit tests need an unreleased version of neutron. (the one including the corresponding change [2]) while it's handled by tox-siblings on the gate, it requires extra steps if you want to run the tests locally. is there any preferred solution for

[openstack-dev] [taas] cancel the weekly meeting officially

hi, please see https://review.openstack.org/#/c/578328/ and comment on it if you have any opinions. thank you. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [neutron] Bug deputy report

hi, Here's a report of my week. I will not attend the neutron meeting due to an overlapping schedule. (sorry!) Issues I failed to triage. Needs a help from someone familiar with DVR. https://bugs.launchpad.net/neutron/+bug/1783470 get_subnet_for_dvr returns SNAT mac instead of gateway in

Re: [openstack-dev] [taas] LP project changes

i went through existing bugs and prioritized them. i'd recommend the others to do the same. there are not too many of them. i also updated series and milestones. On Mon, Jul 2, 2018 at 7:02 PM, Takashi Yamamoto wrote: > hi, > > I created a LP team "tap-as-a-service-drivers&quo

Re: [openstack-dev] [neutron] Stable review

hi, On Thu, Jul 12, 2018 at 6:13 PM, Tony Breeds wrote: > On Thu, Jul 12, 2018 at 03:53:22PM +0900, Takashi Yamamoto wrote: >> hi, >> >> queens branch of networking-midonet has had no changes merged since >> its creation. >> the following commit would tell you

[openstack-dev] [neutron] Stable review

hi, queens branch of networking-midonet has had no changes merged since its creation. the following commit would tell you how many gate blockers have been accumulated. https://review.openstack.org/#/c/572242/ it seems the stable team doesn't have a bandwidth to review subprojects in a timely

[openstack-dev] [neutron] autodoc and tox-siblings

hi, - networking-midonet uses autodoc in their doc. build-openstack-sphinx-docs runs it. - build-openstack-sphinx-docs doesn't use tox-siblings. thus the job uses released versions of dependencies. eg. neutron, neutron-XXXaas, os-vif, etc - released versions of dependencies and networking-midonet

[openstack-dev] [taas] LP project changes

hi, I created a LP team "tap-as-a-service-drivers", whose initial members are same as the existing tap-as-a-service-core group on gerrit. I made the team the Maintainer and Driver of the tap-as-a-service project. This way, someone in the team can take it over even if I disappeared suddenly. :-)

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

On Tue, Jun 26, 2018 at 10:13 PM, Doug Hellmann wrote: > Excerpts from Lance Bragstad's message of 2018-06-25 22:51:37 -0500: >> Thanks a bunch for digging into this, Tony. I'll follow up with the >> oauthlib maintainers and see if they'd be interested in these changes >> upstream. If so, I can

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

On Thu, Jun 21, 2018 at 12:13 PM, Tony Breeds wrote: > On Wed, Jun 20, 2018 at 08:54:56PM +0900, Takashi Yamamoto wrote: > >> do you have a plan to submit these changes on gerrit? > > I didn't but I have now: > > * https://review.openstack.org/577028 > * https://

Re: [openstack-dev] [neutron] Ports port_binding attribute is changing to an iterable

hi, On Thu, Jun 7, 2018 at 4:32 AM, Miguel Lavalle wrote: > Dear OpenStack Networking community of projects, > > As part of the implementation of multiple port bindings in the Neutron > reference implementation >

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

hi, On Thu, May 17, 2018 at 12:51 PM, Tony Breeds wrote: > On Wed, May 16, 2018 at 04:14:36PM -0500, Matthew Thode wrote: >> On 18-05-16 17:07:09, Doug Hellmann wrote: >> > Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500: >> > > Sphinx has breaking changes (yet again) and we

Re: [openstack-dev] [tap-as-a-service] core reviewer update

i just made the change as i haven't got any concerns. welcome, kaz! On Thu, May 31, 2018 at 2:36 PM, Takashi Yamamoto wrote: > hi, > > i plan to add Kazuhiro Suzuki to tap-as-a-service-core group. [1] > he is one of active members of the project. > he is also the origina

[openstack-dev] [tap-as-a-service] core reviewer update

hi, i plan to add Kazuhiro Suzuki to tap-as-a-service-core group. [1] he is one of active members of the project. he is also the original author of tap-as-a-service-dashboard. i'll make the change after a week unless i hear any objections/concerns. [1]

Re: [openstack-dev] [tap-as-a-service] publish on pypi

thank you. done. https://pypi.org/project/tap-as-a-service/ On Fri, Mar 30, 2018 at 8:27 AM, Clark Boylan <cboy...@sapwetik.org> wrote: > On Wed, Mar 28, 2018, at 7:59 AM, Takashi Yamamoto wrote: >> hi, >> >> i'm thinking about publishing the latest release

Re: [openstack-dev] [neutron] Bug deputy report

oops, i forgot to add the critical one. Critical https://bugs.launchpad.net/neutron/+bug/1765008 Tempest API tests failing for stable/queens branch On Tue, Apr 24, 2018 at 9:11 PM, Takashi Yamamoto <yamam...@midokura.com> wrote: > hi, > > here's a summary of this week. > >

[openstack-dev] [neutron] Bug deputy report

hi, here's a summary of this week. RFEs for drivers team: https://bugs.launchpad.net/neutron/+bug/1766380 [RFE] Create host-routes for routed networks (segments) https://bugs.launchpad.net/neutron/+bug/1764738 routed provider networks limit to one host Medium:

[openstack-dev] [tap-as-a-service] publish on pypi

hi, i'm thinking about publishing the latest release of tap-as-a-service on pypi. background: https://review.openstack.org/#/c/555788/ iirc, the naming (tap-as-a-service vs neutron-taas) was one of concerns when we talked about this topic last time. (long time ago. my memory is dim.) do you have

[openstack-dev] [tap-as-a-service] queens

hi, 1. i'm going to create a release and stable branch for tap-as-a-service/queens. 2. to clean up the queue before a release, i approved a bunch of patches today without waiting for two +2s. given the current review bandwidth, i guess we should relax the policy. how do you think? 3. what to do

Re: [openstack-dev] [all][infra] Automatically generated Zuul changes (topic: zuulv3-projects)

On Thu, Feb 1, 2018 at 2:59 AM, James E. Blair wrote: > Hi, > > Occasionally we will make changes to the Zuul configuration language. > Usually these changes will be backwards compatible, but whether they are > or not, we still want to move things forward. > > Because Zuul's

Re: [openstack-dev] [neutron][l3][flavors][floatingip]

a floating-ip is associated to a router only if it's associated to a fixed-ip. consider the case where there are two routers sharing a public network. On Tue, Jan 23, 2018 at 11:09 AM, Bhatia, Manjeet S wrote: > Hi Neutrinos, > > > > I am working on L3 flavors driver

Re: [openstack-dev] [neutron] Stepping down from core

On Sat, Dec 16, 2017 at 4:01 AM, Armando M. wrote: > Hi neutrinos, > > To some of you this email may not come as a surprise. it was a surprise to me. > > During the past few months my upstream community engagements have been more > and more sporadic. While I tried hard to

Re: [openstack-dev] [neutron] Bug deputy report

hi, thank you. do you have anything to hand off to the next bug deputy (me) ? On Mon, Dec 25, 2017 at 3:31 PM, Luo, Lujin wrote: > Hello everyone, > > I was on bug deputy between 2017.12.18 and 2017.12.25. I am sending a short > summary of the bugs reported during

Re: [openstack-dev] [neutron][networking-ovn] Stable branch maintainers for networking-ovn

On Wed, Dec 20, 2017 at 7:18 PM, Lucas Alvares Gomes wrote: > Hi, > >>> Hi all, >>> >>> Just sending this email to try to understand the model for stable branch >>> maintenance in networking-ovn (potentially other neutron drivers too). >>> >>> Right now, only members of

Re: [openstack-dev] [neutron] [networking-ovn] Non voting jobs for networking-ovn on neutron.

hi, On Mon, Dec 4, 2017 at 10:20 PM, Miguel Angel Ajo Pelayo wrote: > > Hi Folks, > I wanted to rise this topic, I have been wanting to do it from long > ago, > but preferred to wait until the zuulv3 stuff was a little bit more stable, > may > be now it's a good time. >

Re: [openstack-dev] [neutron][networking-odl]

On Wed, Nov 8, 2017 at 3:15 PM, Bhatia, Manjeet S <manjeet.s.bha...@intel.com> wrote: > > >> -Original Message- >> From: Takashi Yamamoto [mailto:yamam...@midokura.com] >> Sent: Tuesday, November 7, 2017 10:13 PM >> To: Bhatia, Manjeet S <manjeet.s

Re: [openstack-dev] [neutron][networking-odl]

hi, On Thu, Nov 2, 2017 at 9:01 AM, Bhatia, Manjeet S wrote: > Hello Neutrinos, > > > > I’ve been trying service profile flavors for L3 in neutron to register the > driver, > > the method I’ve been using is below > > > > I have this added to neutron.conf > >

Re: [openstack-dev] [neutron][networking-midonet] Core reviewers change proposal

Hi, On Fri, Oct 20, 2017 at 10:10 PM, Takashi Yamamoto <yamam...@midokura.com> wrote: > Hi, > > Unless anyone objects, I'll remove the following people from the list > of networking-midonet core reviewers. > > - Joe Mills > - Michael Micucci > > They made great

Re: [openstack-dev] [neutron][vpnaas] core reviewer proposal

Hi, On Fri, Oct 20, 2017 at 10:10 PM, Takashi Yamamoto <yamam...@midokura.com> wrote: > Hi, > > Unless anyone objects, i'll add the following people to neutron-vpnaas > core reviewers. [1] > > - Cao Xuan Hoang <hoan...@vn.fujitsu.com> > - Akihiro Motoki <amot..

[openstack-dev] [neutron][networking-midonet] Core reviewers change proposal

Hi, Unless anyone objects, I'll remove the following people from the list of networking-midonet core reviewers. - Joe Mills - Michael Micucci They made great contributions in the past (thank you!) but have not reviewed any patches in the last 6 months. [2] [1]

[openstack-dev] [neutron][vpnaas] core reviewer proposal

Hi, Unless anyone objects, i'll add the following people to neutron-vpnaas core reviewers. [1] - Cao Xuan Hoang - Akihiro Motoki - Miguel Lavalle Hoang is the most active contributor for the project these days. I don't bother

Re: [openstack-dev] [all] Update on Zuul v3 Migration - and what to do about issues

On Thu, Oct 5, 2017 at 8:58 PM, Pierre Riteau wrote: > On 29 Sep 2017, at 15:58, Monty Taylor wrote: > > tl;dr - If you're having issues with your jobs, check the FAQ, this email > and followups on this thread for mentions of them. If it's an issue

Re: [openstack-dev] [Neutron] Denver Team Dinner

+1 On Wed, Sep 13, 2017 at 2:56 AM, IWAMOTO Toshihiro wrote: > +1 > thanks for organizing! > > On Wed, 13 Sep 2017 14:18:45 +0900, > Brian Haley wrote: >> >> +1 >> >> On 09/12/2017 10:44 PM, Ihar Hrachyshka wrote: >> > +1 >> > >> > On Tue, Sep 12, 2017 at 9:44 PM, Kevin

Re: [openstack-dev] [neutron] out-of-tree l3 service providers

ecessary fields are same as AFTER_xxx. > Dragon flow folks seems to have their own spec. > > thanks, > > On Mon, Jul 31, 2017 at 02:10:07PM +0900, > Takashi Yamamoto <yamam...@midokura.com> wrote: > >> hi, >> >> On Mon, Jul 24, 2017 at 8:49 AM, Kevin Bento

Re: [openstack-dev] [neutron][vpnaas] pike rc

done http://git.openstack.org/cgit/openstack/neutron-vpnaas/tag/?h=11.0.0.0rc1 https://review.openstack.org/#/q/status:open+project:openstack/neutron-vpnaas+branch:stable/pike+topic:create-pike On Tue, Aug 8, 2017 at 10:46 AM, Takashi Yamamoto <yamam...@midokura.com> wrote: > hi, >

Re: [openstack-dev] [neutron][tap-as-a-service] pike branch/release

done. http://git.openstack.org/cgit/openstack/tap-as-a-service/tag/?h=2.0.0 https://review.openstack.org/#/q/status:open+project:openstack/tap-as-a-service+branch:stable/pike+topic:create-pike On Tue, Aug 8, 2017 at 10:07 PM, Takashi Yamamoto <yamam...@midokura.com> wrote: > hi, > &

Re: [openstack-dev] [neutron][vpnaas] pike rc

enstack.org/#/c/491429/ my understanding is it's necessary for hosted projects because they are not managed by openstack/releases. unlike neutron-vpnaas, networking-hyperv is an official project. [2] [2] https://github.com/openstack/governance/commit/c84d0a702f536a43324212f803e0a43a640c9b56 > > >&g

Re: [openstack-dev] [neutron][tap-as-a-service] pike branch/release

hi, On Tue, Aug 8, 2017 at 9:14 PM, Doug Hellmann wrote: > Excerpts from Takashi Yamamoto's message of 2017-08-08 10:49:09 +0900: >> hi >> >> i'll create stable/pike (and probably a release) for tap-as-a-service >> in this week. >> > > We have a bunch of tools that expect

[openstack-dev] [neutron][tap-as-a-service] pike branch/release

hi i'll create stable/pike (and probably a release) for tap-as-a-service in this week. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [neutron][networking-l2gw] pike

hi, who is planning to make stable/pike for networking-l2gw? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [neutron][vpnaas] pike rc

hi, can anyone with an appropriate permission create a stable/pike and pike rc1 for neutron-vpnaas? stable/pike 11.0.0.0rc1 openstack/neutron-vpnaas 8278615c1f35f98447a3f9692a78ab45e90ee8c6 thank you. __ OpenStack

Re: [openstack-dev] [neutron] FFE for midonet v2 plugin removal

On Tue, Aug 1, 2017 at 8:01 AM, Takashi Yamamoto <yamam...@midokura.com> wrote: > hi, > > I'm not sure if changes like this requires an FFE, but just in case. > I'd like to request an FFE for midonet v2 plugin removal. > > - patches are ready for review: https://review.

[openstack-dev] [neutron] FFE for midonet v2 plugin removal

hi, I'm not sure if changes like this requires an FFE, but just in case. I'd like to request an FFE for midonet v2 plugin removal. - patches are ready for review: https://review.openstack.org/#/c/486790/ - https://bugs.launchpad.net/networking-midonet/ - this is a removal of an

Re: [openstack-dev] [neutron] out-of-tree l3 service providers

ight? AFTER_DELETE might be tricky as we probably need to provide flavor info to subscribers. > > On Thu, Jul 13, 2017 at 3:01 AM, Takashi Yamamoto <yamam...@midokura.com> > wrote: >> >> hi, >> >> today i managed to play with l3 flavors. >> i

[openstack-dev] [neutron][vpnaas] driver removal

hi, some of drivers in neutron-vpnaas don't have maintainers. [1] unless someone steps up, we might end up with removing those drivers. especially, VyattaIPsecDriver will likely be removed in near future, as it requires a special agent [2] which is difficult to maintain for those who are not

[openstack-dev] [neutron] out-of-tree l3 service providers

hi, today i managed to play with l3 flavors. i wrote a crude patch to implement midonet flavor. [1] [1] https://review.openstack.org/#/c/483174/ a good news is it's somehow working. a bad news is it has a lot of issues, as you can see in TODO comments in the patch. given these issues, now i

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

On Wed, May 31, 2017 at 10:12 PM, Akihiro Motoki wrote: > Hi all, > > As discussed last month [1], we agree that each neutron-related > dashboard has its own repository. > I would like to move this forward on FWaaS and VPNaaS > as the horizon team plans to split them out as

Re: [openstack-dev] [neutron][networking-midonet] networking-midonet core reviewer proposal

as i haven't heard any objections, i went ahead and added them to the list. [1] [1] https://review.openstack.org/#/admin/groups/607,members On Wed, Apr 26, 2017 at 12:07 PM, Ryu Ishimoto <r...@midokura.com> wrote: > > +1 ! > > On Wed, Apr 26, 2017 at 11:41 AM Takas

Re: [openstack-dev] [neutron] Changes in QoS service plugin

On Fri, Apr 28, 2017 at 6:03 AM, Sławek Kapłoński wrote: > Hello, > > Some time ago my patch [1] was merged. It changes list of supported > qos_rule_types to dict with rule types as keys and list of supported > parameters and values for each rule type. > Additionally now

[openstack-dev] [neutron][networking-midonet] networking-midonet core reviewer proposal

unless anyone objects, i'll add the following people to networking-midonet project's core reviewers. - Antonio Ojea - Brandon Berg - Xavi León http://stackalytics.com/report/contribution/networking-midonet/30 http://stackalytics.com/report/contribution/networking-midonet/90

Re: [openstack-dev] [devstack] uwsgi for API services

On Thu, Apr 13, 2017 at 9:01 PM, Sean Dague wrote: > One of the many reasons for getting all our API services running wsgi > under a real webserver is to get out of the custom ports for all > services game. However, because of some of the limits of apache > mod_wsgi, we really

Re: [openstack-dev] [neutron] Engine facade

hi, On Tue, Apr 4, 2017 at 4:09 PM, Gary Kotton wrote: > Hi, > > The problem that we have is that any foreign key usage under transactions is > now broken. An example of an exception that is raised is: > > > > DBReferenceError: (sqlite3.IntegrityError) FOREIGN KEY

Re: [openstack-dev] [qa][neutron-fwaas][networking-bgpvpn][nova-lxd] Removing old data_utils from Tempest

thank you for heads up. On Wed, Mar 15, 2017 at 2:18 AM, Ken'ichi Ohmichi wrote: > Hi, > > Many projects are using data_utils library which is provided by > Tempest for creating test resources with random resource names. > Now the library is provided as stable interface

Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octa

hi, On Mon, Feb 27, 2017 at 8:34 PM, Andrea Frittoli wrote: > Hello folks, > > TL;DR: if today you import manager,py from tempest.scenario please maintain > a copy of [0] in tree until further notice. > > Full message: > -- > > One of the priorities for

Re: [openstack-dev] Problem in visualizing port-mirroring information

On Tue, Feb 28, 2017 at 4:05 PM, Manik Bindlish wrote: > Hi All, > > > > I am facing an issue in visualizing port-mirroring information. > > > > 1.)Created 2 VMs: > > VM1: ubuntu3(10.0.0.3, floating IP: 192.168.200.252) – Tap service created > > VM2:

[openstack-dev] [neutron] vpnaas driver maintainers

hi, i want to document who cares which drivers. https://review.openstack.org/#/c/436081/ please comment on the review if you know an appropriate contact person for each drivers. btw, is the following a driver for neutron-vpnaas? i couldn't find documentation.

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

+1 2017/02/18 4:21 "Kevin Benton" : Hi all, I'm organizing a Neutron social event for Thursday evening in Atlanta somewhere near the venue for dinner/drinks. If you're interested, please reply to this email with a "+1" so I can get a general count for a reservation. Cheers,

Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

On Thu, Feb 9, 2017 at 7:47 AM, Takashi Yamamoto <yamam...@midokura.com> wrote: > i plan to cut a release for networking-midonet once relevant projects get > ready. > ie. neutron-vpnaas, tap-as-a-service https://review.openstack.org/#/c/429437/ > > On Thu, Feb 9, 2017

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

from Takashi Yamamoto's message of 2017-02-06 10:32:10 +0900: >> >> On Wed, Feb 1, 2017 at 9:46 AM, Takashi Yamamoto <yamam...@midokura.com> >> >> wrote: >> >> > hi, >> >> > >> >> > On Fri, Jan 27, 2017 at 7:46 AM, Doug Hell

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

hi, On Tue, Feb 14, 2017 at 1:54 AM, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from Takashi Yamamoto's message of 2017-02-06 10:32:10 +0900: >> On Wed, Feb 1, 2017 at 9:46 AM, Takashi Yamamoto <yamam...@midokura.com> >> wrote: >> > hi, >&

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

done. vinay or anil, can you update launchpad? i don't have permission. On Wed, Feb 8, 2017 at 3:36 PM, Soichi Shigeta wrote: > > Hi Yamamoto, > >We discussed this on today's IRC and agreed to make an ocata release. > >Best regards, >Soichi > > > >>

Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

i plan to cut a release for networking-midonet once relevant projects get ready. ie. neutron-vpnaas, tap-as-a-service On Thu, Feb 9, 2017 at 1:16 AM, Armando M. wrote: > > > On 2 February 2017 at 16:09, Armando M. wrote: >> >> Hi neutrinos, >> >> I have put

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

On Wed, Feb 1, 2017 at 9:51 AM, Takashi Yamamoto <yamam...@midokura.com> wrote: > hi, > >>> That's great to hear Yamamoto. Since you are already a neutron-core I assume >>> you are already intimate with the work required to strengthen the VPNaaS >>> proje

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

thank you. On Mon, Feb 6, 2017 at 3:51 PM, Gary Kotton <gkot...@vmware.com> wrote: > Hi, > Yes, I will go and do this. > Thanks > Gary > > On 2/6/17, 4:05 AM, "Takashi Yamamoto" <yamam...@midokura.com> wrote: > > hi, > > is anyone g

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

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

On Wed, Feb 1, 2017 at 9:46 AM, Takashi Yamamoto <yamam...@midokura.com> wrote: > hi, > > On Fri, Jan 27, 2017 at 7:46 AM, Doug Hellmann <d...@doughellmann.com> wrote: >> Excerpts from Takashi Yamamoto's message of 2017-01-26 11:42:48 +0900: >>> hi, >>&

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

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

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

hi, >> That's great to hear Yamamoto. Since you are already a neutron-core I assume >> you are already intimate with the work required to strengthen the VPNaaS >> project. I have added you to [4] and you can lean on me for any changes that >> needs reviewing. i wrote a scenario test.

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

t; Excerpts from Dariusz Śmigiel's message of 2017-01-13 09:11:01 -0600: >> >> 2017-01-12 21:43 GMT-06:00 Takashi Yamamoto <yamam...@midokura.com>: >> >> > hi, >> >> > >> >> > On Wed, Nov 16, 2016 at 11:02 AM, Armando M. <arma.

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

hi, On Sat, Jan 14, 2017 at 2:17 AM, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from Dariusz Śmigiel's message of 2017-01-13 09:11:01 -0600: >> 2017-01-12 21:43 GMT-06:00 Takashi Yamamoto <yamam...@midokura.com>: >> > hi, >> > >> > On

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

hi, On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote: > Hi > > As of today, the project neutron-vpnaas is no longer part of the neutron > governance. This was a decision reached after the project saw a dramatic > drop in active development over a prolonged period of time. >

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

On Thu, Dec 1, 2016 at 1:02 AM, Armando M. <arma...@gmail.com> wrote: > > > On 27 November 2016 at 20:50, Takashi Yamamoto <yamam...@midokura.com> > wrote: >> >> On Wed, Nov 16, 2016 at 11:02 AM, Armando M. <arma...@gmail.com> wrote: >> > H

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

driver are you using? > > > Cheers, > Lingxian Kong (Larry) > > On Mon, Nov 28, 2016 at 5:50 PM, Takashi Yamamoto <yamam...@midokura.com> > wrote: >> >> On Wed, Nov 16, 2016 at 11:02 AM, Armando M. <arma...@gmail.com> wrote: >> > Hi >>

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

u! it's great to hear the project has more demands. > > > Cheers, > Lingxian Kong (Larry) > > On Mon, Nov 28, 2016 at 5:50 PM, Takashi Yamamoto <yamam...@midokura.com> > wrote: >> >> On Wed, Nov 16, 2016 at 11:02 AM, Armando M. <arma...@gmail.com>

Re: [openstack-dev] [release] Re: [neutron][networking-midonet] [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

On Tue, Nov 29, 2016 at 11:53 AM, Takashi Yamamoto <yamam...@midokura.com> wrote: > release team, > > can we (networking-midonet) branch stable/newton from a past commit > with a RC tag, backport some changes [1], and then cut the first release > on the branch? to answ

Re: [openstack-dev] [neutron] [tap-as-a-service] stable/newton 'broken'

On Mon, Nov 28, 2016 at 8:37 PM, Takashi Yamamoto <yamam...@midokura.com> wrote: > Anil, > > do you have any opinion? > > i'm thinking to branch stable/newton at around > 675af77205d4e404bc7c185c13ab6d86f300d185 after taas meeting, i went ahead and create the branch.

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

On Thu, Dec 1, 2016 at 1:02 AM, Armando M. <arma...@gmail.com> wrote: > > > On 27 November 2016 at 20:50, Takashi Yamamoto <yamam...@midokura.com> > wrote: >> >> On Wed, Nov 16, 2016 at 11:02 AM, Armando M. <arma...@gmail.com> wrote: >> > H

Re: [openstack-dev] [release] Re: [neutron][networking-midonet] [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

, ...) On Fri, Nov 25, 2016 at 11:32 PM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > >> On 25 Nov 2016, at 15:23, Takashi Yamamoto <yamam...@midokura.com> wrote: >> >> On Fri, Nov 25, 2016 at 8:02 PM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: >>> >&g

Re: [openstack-dev] [neutron] [tap-as-a-service] stable/newton 'broken'

Anil, do you have any opinion? i'm thinking to branch stable/newton at around 675af77205d4e404bc7c185c13ab6d86f300d185 On Thu, Nov 24, 2016 at 6:25 PM, Takashi Yamamoto <yamam...@midokura.com> wrote: > hi, > > On Thu, Nov 24, 2016 at 6:00 PM, Gary Kotton <gkot...@vmware.com

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

On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote: > Hi > > As of today, the project neutron-vpnaas is no longer part of the neutron > governance. This was a decision reached after the project saw a dramatic > drop in active development over a prolonged period of time. > >

Re: [openstack-dev] [neutron][networking-midonet] [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

On Fri, Nov 25, 2016 at 8:02 PM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > >> On 25 Nov 2016, at 11:02, Takashi Yamamoto <yamam...@midokura.com> wrote: >> >> On Fri, Nov 25, 2016 at 6:54 PM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: >>>

Re: [openstack-dev] [neutron][networking-midonet] [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

On Fri, Nov 25, 2016 at 6:54 PM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > >> On 25 Nov 2016, at 09:25, Takashi Yamamoto <yamam...@midokura.com> wrote: >> >> On Fri, Nov 25, 2016 at 5:18 PM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: >>>

Re: [openstack-dev] [neutron][networking-midonet] [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

On Fri, Nov 25, 2016 at 5:18 PM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > >> On 25 Nov 2016, at 05:26, Takashi Yamamoto <yamam...@midokura.com> wrote: >> >> hi, >> >> networking-midonet doesn't have stable/newton branch yet. >> newton jobs

Re: [openstack-dev] [neutron][networking-midonet] Fwd: [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

On Fri, Nov 25, 2016 at 4:36 PM, Takashi Yamamoto <yamam...@midokura.com> wrote: > On Fri, Nov 25, 2016 at 4:28 PM, Andreas Jaeger <a...@suse.com> wrote: >> On 11/25/2016 05:26 AM, Takashi Yamamoto wrote: >>> networking-midonet doesn't have stable/newton branch

Re: [openstack-dev] [neutron][networking-midonet] Fwd: [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

On Fri, Nov 25, 2016 at 4:28 PM, Andreas Jaeger <a...@suse.com> wrote: > On 11/25/2016 05:26 AM, Takashi Yamamoto wrote: >> networking-midonet doesn't have stable/newton branch yet. >> newton jobs failures are false alarms. > > Then let's remove these jobs, sure. i'll s

Re: [openstack-dev] [neutron][networking-midonet] Fwd: [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

hi, networking-midonet doesn't have stable/newton branch yet. newton jobs failures are false alarms. branching has been delayed because development of some futures planned for newton has not been completed yet. the plan is to revert ocata-specific changes after branching newton. On Fri, Nov

Re: [openstack-dev] [neutron] [tap-as-a-service] stable/newton 'broken'

iew or whatever. how do you think? > > On 11/24/16, 10:00 AM, "Takashi Yamamoto" <yamam...@midokura.com> wrote: > > can you give me an example of breakage? > > On Thu, Nov 24, 2016 at 4:19 PM, Gary Kotton <gkot...@vmware.com> wrote: > > Hi

Re: [openstack-dev] [neutron] stable/newton 'broken'

can you give me an example of breakage? On Thu, Nov 24, 2016 at 4:19 PM, Gary Kotton wrote: > Hi, > > The change https://review.openstack.org/#/c/386845/ that landed yesterday > has caused a breakage in stable/newton. This is due to the fact that the > following projects do

Re: [openstack-dev] [stable][neutron][midonet] midonet liberty gate failure

hi, On Thu, Nov 3, 2016 at 2:18 AM, Ihar Hrachyshka wrote: > Hi YAMAMOTO (and other midokura folks), > > I spotted unit tests in the branch are failing due to upper constraints not > applied. So I backported the fix as: > https://review.openstack.org/#/c/392698/ Sadly, it

Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

+1 On Sat, Oct 15, 2016 at 3:30 AM, Miguel Lavalle wrote: > Dear Neutrinos, > > I am organizing a social event for the team on Thursday 27th at 19:30. After > doing some Google research, I am proposing Raco de la Vila, which is located > in Poblenou:

Re: [openstack-dev] [neutron][stadium] Query regarding procedure for inclusion in Neutron Stadium

hi, On Sat, Sep 24, 2016 at 9:06 AM, Armando M. <arma...@gmail.com> wrote: > > > On 22 September 2016 at 22:36, Takashi Yamamoto <yamam...@midokura.com> > wrote: >> >> hi, >> >> On Fri, Sep 23, 2016 at 4:20 AM, Armando M. <arma...@gmail.com&g

Re: [openstack-dev] [neutron][stadium] Query regarding procedure for inclusion in Neutron Stadium

hi, On Fri, Sep 23, 2016 at 4:20 AM, Armando M. wrote: > > > On 22 September 2016 at 00:46, reedip banerjee wrote: >> >> Dear Neutron Core members, >> >> I have a query regarding the procedure for inclusion in the Neutron >> Stadium. >> I wanted to know if

Re: [openstack-dev] [neutron][taas] On TaaS not capturing some packets between two VMs on the same host

hi, On Sat, Sep 3, 2016 at 7:32 AM, Anil Rao wrote: > Hello, > > Here is an update on the issue of not being able to capture packets flowing > between two VMs on the same host. it it about bug 1529595 ? https://bugs.launchpad.net/tap-as-a-service/+bug/1529595 > >

[openstack-dev] [neutron][taas] making a taas release for mitaka or not

hi, we tap-as-a-service project had a plan to make a release compatible with mitaka. however, - it's a bit late for mitaka already - the reference implementation needs to be adapted to l2 agent extension but no much progress yet so, a question is, if we still want to make a release for mitaka,

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

majop...@redhat.com> wrote: >>> >>> I agree, let's try to find a timeslot that works. >>> >>> using #openstack-neutron with the meetbot works, but it's going to >>> generate a lot of noise. >>> >>> On Tue, May 17, 2016 at 11:47 AM, Ihar Hrach

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

On Mon, May 16, 2016 at 10:25 PM, Takashi Yamamoto <yamam...@midokura.com> wrote: > hi, > > On Mon, May 16, 2016 at 9:00 PM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: >> +1 for earlier time. But also, have we booked any channel for the meeting? >> Hijacking #op

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

d for everyone around >> the globe:-) >> The first meeting will still be UTC 1700 ~ UTC 1800 May 17 on Neutron >> channel. >> In the meeting, we can see if we can reach consensus on a new meeting time. >> >> Cathy >> >> -Original Message---

  1   2   >