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 wrote: > On Fri, Nov 25, 2016 at 4:28 PM, Andreas Jaeger wrote: >> On 11/25/2016 05:26 AM, Takashi Yamamoto wrote: >>> networking-midonet doesn't have stable/newton branch yet. >>> newton jobs failures are

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 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 submit project-config

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

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, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409

[openstack-dev] [Horizon] End of week wrap-up

Hi folks, This was a bit of a slow-ish week given the number of folks away for Thanksgiving. We had low-turnout Horizon meeting and cancelled the Horizon/Keystone cross-project meeting. In the team meeting[1] we covered: - The patch priority review list, which looks a lot like last week :-( - We

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

Armando, have a happy holiday! From: "Armando M." Reply-To: OpenStack List Date: Thursday, November 24, 2016 at 11:09 PM To: OpenStack List Subject: Re: [openstack-dev] [neutron] stable/newton 'broken'

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

Thanks for the notification. We are looking into it. On 11/25/2016 8:09 AM, Ihar Hrachyshka wrote: Hi, Seems like newton branch of networking-odl is pulling neutron from master. Whoever is responsible for the subproject, please fix. Begin forwarded message: *From: *"A mailing list for the

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

I agree to tap-as-a-service being tech-preview for this release to get over this issue , if it is still relevant. On Fri, Nov 25, 2016 at 2:39 AM, Armando M. wrote: > > > On 24 November 2016 at 11:12, Gary Kotton wrote: > >> The breakage is due to the

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

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Nov. 25 2016

1) Roll Call 2) OPNFV: CI Progress 3) OPNFV: Escalator Support 4) nominate Ya to be daisycloud-core core reviewer. 5) Newton B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] 答复: RE: RE: [vitrage] about aodh alarm notification

EmThe solution goes back to my first question. Snapshot service calls get_all, and caches all the alarms. But listener service can't get the cache because there are two services and can't share the cache. BR, dwj "Weyl, Alexey (Nokia - IL)" 2016-11-24 23:50

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

Hi, could anyone from the midonet subproject take ownership of repo stable branches? Newton branch is broken for weeks with no apparent actions from the core team side. > Begin forwarded message: > > From: "A mailing list for the OpenStack Stable Branch test reports." >

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

Hi, Seems like newton branch of networking-odl is pulling neutron from master. Whoever is responsible for the subproject, please fix. > Begin forwarded message: > > From: "A mailing list for the OpenStack Stable Branch test reports." > > Subject:

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

On 24 November 2016 at 11:12, Gary Kotton wrote: > The breakage is due to the fact that the projects do not have > stable/newton branches cut. > This is something that I would have expected the neutron team to take care > of as long as it was under the stadium/tent or

Re: [openstack-dev] [keystone][ceilometer] 'ceilometer -d meter-list' hangs in "Making authentication request to keystone"

Hi We have root caused the issue. It is due to longer MTU setting in the VMs and because VxLAN tunneling is used for VM to VM communication on different compute nodes, the encapsulated packets are going beyond MTUs in the underlying network and getting fragmented and causing the connection

Re: [openstack-dev] [Congress] Magnum_driver

Hi Tim, I solved the problem with: tox --recreate -e py27 Now I no have the error on the import. The unit test still has some errors, but I don't know why.. Anyway, I've this error when I try to add the magnum_driver: 2016-11-24 20:56:27.191 INFO congress.datasources.datasource_driver [-]

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

Sukdev has updated the group ☺ Happy holidays From: Gary Kotton Reply-To: OpenStack List Date: Thursday, November 24, 2016 at 9:12 PM To: OpenStack List Subject: Re: [openstack-dev] [neutron]

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

The breakage is due to the fact that the projects do not have stable/newton branches cut. This is something that I would have expected the neutron team to take care of as long as it was under the stadium/tent or whatever we want to call it. The fact that the l2gw was removed may have been an

Re: [openstack-dev] [neutron] neutron-lib impact

On 24 November 2016 at 10:16, Neil Jerram wrote: > To be clear, when I said 'catching such issues', what I meant was: > 'letting me know promptly that I now need to update networking-calico'. > We're asking folks to take a number of steps to properly communicate potential issues

Re: [openstack-dev] [neutron] neutron-lib impact

To be clear, when I said 'catching such issues', what I meant was: 'letting me know promptly that I now need to update networking-calico'. I absolutely did not mean any kind of delaying or blocking a neutron or neutron-lib change. Thanks, Neil On Thu, Nov 24, 2016 at 5:43 PM Kevin Benton

Re: [openstack-dev] [neutron] neutron-lib impact

On 24 November 2016 at 09:41, Kevin Benton wrote: > Yeah, in this case I don't think it would have helped because it was > removing several things from neutron simultaneously. The only thing that > would have stopped that would have been jobs from all sub projects voting > on

Re: [openstack-dev] [neutron] neutron-lib impact

Yeah, in this case I don't think it would have helped because it was removing several things from neutron simultaneously. The only thing that would have stopped that would have been jobs from all sub projects voting on each neutron change. On Nov 24, 2016 10:02, "Armando M."

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

On 24 November 2016 at 02:38, Thierry Carrez wrote: > Gary Kotton wrote: > > Please see - http://logs.openstack.org/82/401882/1/check/gate-vmware- > nsx-python27-db-ubuntu-xenial/1ac0686/console.html#_2016-11- > 24_06_58_38_520273 > > Here we are pulling trunk as there is

Re: [openstack-dev] [neutron] neutron-lib impact

On 24 November 2016 at 05:27, Neil Jerram wrote: > But I think a periodic check for a Neutron/neutron-lib-using project (such > as networking-calico) would still be a decent way of catching such issues, > wouldn't it? > It depends, and it would. There are many factors at play,

Re: [openstack-dev] [tripleo] CI scenarios design - how to add more services

On Thu, Nov 24, 2016 at 11:08 AM, Juan Antonio Osorio wrote: > I don't have a strong opinion about any option, as long as we have something > in place I'm happy. > > But regarding option 1.A: what would be done for newton once these templates > are moved to t-h-t. Would they

Re: [openstack-dev] [heat][sahara][magnum][tripleo] Scaling nested stack validation

On Wed, Nov 23, 2016 at 11:58 PM, Zane Bitter wrote: > We discussed $SUBJECT at the summit as one of the main performance problems > that people are running into when trying to create very large autoscaling > groups, as projects like Sahara, Magnum, TripleO, OpenShift are wont

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

I have worked around the issue by pegging the l2gw and tap-aas to specific commits. This is a hack at the moment and will update as soon as the branches are cut. Thanks and happy holidays On 11/24/16, 4:11 PM, "Gary Kotton" wrote: On 11/24/16, 12:38 PM,

Re: [openstack-dev] [tripleo] CI scenarios design - how to add more services

I don't have a strong opinion about any option, as long as we have something in place I'm happy. But regarding option 1.A: what would be done for newton once these templates are moved to t-h-t. Would they be backported? What about mitaka? On 24 Nov 2016 17:55, "Carlos Camacho Gonzalez"

Re: [openstack-dev] [Performance][shaker]

Hi Ilya, Thanks for your answer, let me know your findings. In any case I'll be glad to help if needed. Matt ps : I just realized that I missed a proper subjet to the thread :(. If this thread continue it's maybe better to change that. - Mail original - > De: "Ilya Shakhat"

Re: [openstack-dev] [tripleo] CI scenarios design - how to add more services

I think would be cool to go with option, +1 to 1.A IMHO, - Easier to read. - Easier to maintain. - We don't make backports, instead we guarantee backwards compatibility. - We'll re-use experience from Puppet OpenStack CI. On Wed, Nov 23, 2016 at 10:13 PM, Giulio Fidente

Re: [openstack-dev] [vitrage] about aodh alarm notification

It seems that you will need to have a cache for that issue. Due to the fact that AODH alarms aren’t deleted, and stay alive (in AODH) when their state is changed to ok (but in this case aren’t supposed to appear in Vitrage), and then when the state is changed back to error (‘alarm’) they are

Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

This is also a latest dnsmask for uname -a Linux cloudx-24.rdmz.labs.mlnx 3.10.0-327.el7.x86_64 #1 SMP Thu Oct 29 17:29:29 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux bash-4.2$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.2 (Maipo) #neutron-sanity-check --config-file

Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

> On 24 Nov 2016, at 15:31, Jens Rosenboom wrote: > > 2016-11-24 15:08 GMT+01:00 Lenny Verkhovsky : >> Hi, >> >> The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI > > What OS is the CI running on? Can you show the output of "dnsmasq

Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

RH7.2 #dnsmasq --version Dnsmasq version 2.66 Copyright (c) 2000-2013 Simon Kelley Compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth This software comes with ABSOLUTELY NO WARRANTY. Dnsmasq is free software, and you are welcome to

Re: [openstack-dev] [Rally][all] Gitter as an alternative way for communication

On Thursday, 24 November 2016 16:20:32 CET Andrey Kurilin wrote: > Hi folks! > > I'm happy to announce our new chats at gitter.im : > > - https://gitter.im/rally-dev/Lobby # main chat for regular > communication > - https://gitter.im/rally-dev/statuses # chat for gerrit notifications > >

Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

2016-11-24 15:08 GMT+01:00 Lenny Verkhovsky : > Hi, > > The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI What OS is the CI running on? Can you show the output of "dnsmasq --version" and "neutron-sanity-check" on a CI node?

Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

+1 – we need to figure out if this flag is supported by specific dnsmasq versions On 11/24/16, 4:15 PM, "Ihar Hrachyshka" wrote: > On 24 Nov 2016, at 15:08, Lenny Verkhovsky wrote: > > Hi, > The DHCP Agent commit[1] added a lot

Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

10x > -Original Message- > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > Sent: Thursday, November 24, 2016 4:16 PM > To: OpenStack Development Mailing List (not for usage questions) d...@lists.openstack.org> > Subject: Re: [openstack-dev] [openstack][neutron] DHCP agent:

[openstack-dev] [Rally][all] Gitter as an alternative way for communication

Hi folks! I'm happy to announce our new chats at gitter.im : - https://gitter.im/rally-dev/Lobby # main chat for regular communication - https://gitter.im/rally-dev/statuses # chat for gerrit notifications These chats are configured with a simple bot which syncs messages between Gitter

Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

> On 24 Nov 2016, at 15:08, Lenny Verkhovsky wrote: > > Hi, > The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI > > > [1] https://review.openstack.org/#/c/393007/ We probably revert the patch: https://review.openstack.org/#/c/401985/ Ihar

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

On 11/24/16, 12:38 PM, "Thierry Carrez" wrote: Gary Kotton wrote: > Please see - http://logs.openstack.org/82/401882/1/check/gate-vmware-nsx-python27-db-ubuntu-xenial/1ac0686/console.html#_2016-11-24_06_58_38_520273 > Here we are pulling trunk as there is no

[openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

Hi, The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI [1] https://review.openstack.org/#/c/393007/ [2] http://13.69.151.247/41/346041/24/check-cinder/Cinder-ISER-ISCSI/ec78a29/logs/q-dhcp.log.gz [3] 2016-11-23 06:37:49.950 28150 DEBUG neutron.agent.linux.utils

Re: [openstack-dev] [nova] [telemetry] PostgreSQL gate broken

On 11/24/2016 05:57 AM, Julien Danjou wrote: Hi, It seems Nova broke its PostgreSQL support recently, and that impacts Telemetry as we do gate on PostgreSQL. I opened a bug: https://bugs.launchpad.net/nova/+bug/1644513 Could somebody from Nova indicates if this is something you want to fix

Re: [openstack-dev] [keystone] Pike PTL

You were an awesome PTL! thanks for all the work. BR On Wed, Nov 23, 2016 at 6:04 PM, Henry Nash wrote: > Steve, > > It’s been a pleasure working with you as PTL - an excellent tenure. Enjoy > taking some time back! > > Henry > > On 21 Nov 2016, at 19:38, Steve Martinelli

Re: [openstack-dev] [neutron] neutron-lib impact

But I think a periodic check for a Neutron/neutron-lib-using project (such as networking-calico) would still be a decent way of catching such issues, wouldn't it? On Thu, Nov 24, 2016 at 12:58 AM Kevin Benton wrote: > The issue we had is different than breaking changes in

Re: [openstack-dev] [nova] [telemetry] PostgreSQL gate broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 24/11/2016 11:57, Julien Danjou a écrit : > Hi, > > It seems Nova broke its PostgreSQL support recently, and that > impacts Telemetry as we do gate on PostgreSQL. I opened a bug: > > https://bugs.launchpad.net/nova/+bug/1644513 > > Could

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

Thanks for everything Marek, good times when we debugged federation issues! :) On Wed, Nov 23, 2016 at 1:05 PM, Henry Nash wrote: > Echoing the comments of others. - thanks for all your hard work and > expertise. > > Henry > > On 23 Nov 2016, at 15:05, Lance Bragstad

[openstack-dev] [Security] Weekly meeting canceled due to thanksgiving

All, I should have sent the notification out earlier however today's weekly IRC meeting is cancelled as most of our group are american and on vacation today. Have a great day. -Rob __ OpenStack Development Mailing List (not

Re: [openstack-dev] [all][infra] Proposed changes to unit-test setup

On 22 November 2016 18:56, John Dickinson wrote: > > On 22 Nov 2016, at 10:47, Andreas Jaeger wrote: > > > When we (infra) changed the unit test jobs to not set up databases by > > default, we created special python-db and tox-db jobs that set up both > > MySQL and PostgreSQL databases. And

Re: [openstack-dev] [Performance][shaker]

Hi Matt, Out of the box Shaker doesn't support such topology. It shouldn't be hard to implement though. Let me check what needs to be done. Thanks, Ilya 2016-11-24 13:49 GMT+03:00 Matthieu Simonin : > Hello, > > I'm looking to shaker capabilities and I'm wondering if

[openstack-dev] [nova] [telemetry] PostgreSQL gate broken

Hi, It seems Nova broke its PostgreSQL support recently, and that impacts Telemetry as we do gate on PostgreSQL. I opened a bug: https://bugs.launchpad.net/nova/+bug/1644513 Could somebody from Nova indicates if this is something you want to fix quickly or if we should just stop caring about

[openstack-dev] [Performance][shaker]

Hello, I'm looking to shaker capabilities and I'm wondering if this kind of accomodation (see attachment also) can be achieved Ascii (flat) version : CN1 (2n VMs) <- n flows -> CN2 (2n VMs) CN1 (2n VMs) <- n flows -> CN3 (2n VMs) CN2 (2n VMs) <- n flows -> CN3 (2n VMs) In this situation

Re: [openstack-dev] [Nova] Stepping back

Le 22/11/2016 17:39, Andrew Laski a écrit : > I should have sent this weeks ago but I'm a bad person who forgets > common courtesy. My employment situation has changed in a way that does > not afford me the necessary time to remain a regular contributor to > Nova, or the broader OpenStack

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

Gary Kotton wrote: > Please see - > http://logs.openstack.org/82/401882/1/check/gate-vmware-nsx-python27-db-ubuntu-xenial/1ac0686/console.html#_2016-11-24_06_58_38_520273 > Here we are pulling trunk as there is no stable version to use Is neutron stable/newton really broken (like your subject

[openstack-dev] [cinder][oslo] ZeroMQ support with multibackend

Hi, Cinder is lacking ZeroMQ messaging support in multibackend configurations. This is due to the fact that we're abusing ``Target.server`` property by appending "@backend" suffix to the hostname. This works just fine in RabbitMQ, as it routes messages using queue names, but fails in ZeroMQ when

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

+1 In newton we did integrations in the vmware_nsx repository with this (it’s a super useful project and having the ability to do a copy port helps debug and triage issues) Please let us know what you decide On 11/24/16, 11:43 AM, "Soichi Shigeta" wrote:

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

Hi, > taas folks, > given increasing demands (networking-midonet also will depend on it) > i guess it makes sense to create newton branch. > if we don't think it's mature enough, we can call it experimental or > tech-preview or whatever. > how do you think? It sounds nice idea. +1 (maybe

[openstack-dev] 答复: RE: [vitrage] about aodh alarm notification

Hi Weyl Alexey, Another question: If we received the alarm.creation notification with the 'ok' state, we filter it and don't create vertex in the Graph. The next received the alarm state_change notification, all the other alarm details are missing in the vertex. How can I handle this? Thanks~

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

hi, On Thu, Nov 24, 2016 at 6:00 PM, Gary Kotton wrote: > Please see - > http://logs.openstack.org/82/401882/1/check/gate-vmware-nsx-python27-db-ubuntu-xenial/1ac0686/console.html#_2016-11-24_06_58_38_520273 > Here we are pulling trunk as there is no stable version to use

[openstack-dev] 答复: RE: [vitrage] about aodh alarm notification

Hi Weyl, Alexey, Oh, I made the issue complicated. Thanks for your explaintion~ I'll try again. Thank you very much~ BR, dwj "Weyl, Alexey (Nokia - IL)" 2016-11-24 16:25 收件人 "dong.wenj...@zte.com.cn" , "Afek, Ifat (Nokia - IL)"

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

Please see - http://logs.openstack.org/82/401882/1/check/gate-vmware-nsx-python27-db-ubuntu-xenial/1ac0686/console.html#_2016-11-24_06_58_38_520273 Here we are pulling trunk as there is no stable version to use On 11/24/16, 10:00 AM, "Takashi Yamamoto" wrote: can you

Re: [openstack-dev] [vitrage] about aodh alarm notification

Hi Dong, Good question, I will explain how you can handle this problem in Vitrage. You don't need the cache mechanism here, it is much more simplier. When you get a new alarm with get_all or by notification of 'alarm.creation' you will create the alarm with its correct data \ properties. Then

[openstack-dev] [devstack] Need some suggestion for a patch on liberty branch

Hi all, I am writing to ask suggestion about how to move one patch [1] forward. This patch is to fix a problem that tempest configuration on liberty is not setting "api_extensions", and any test case that verifies API extensions NOT on Liberty will get a FALSE POSITIVE (because we used "all"

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