Re: [OpenStack-Infra] [all][infra] Zuul logs are in swift

On Thu, Aug 15, 2019 at 10:04:53AM -0700, James E. Blair wrote: > Hi, > > We have made the switch to begin storing all of the build logs from Zuul > in Swift. > > Each build's logs will be stored in one of 7 randomly chosen Swift > regions in Fort Nebula, OVH, Rackspace, and Vexxhost. Thanks to

Re: [openstack-dev] Stepping down from Neutron core team

On Sun, Dec 02, 2018 at 11:08:25PM +0900, Hirofumi Ichihara wrote: > I’m stepping down from the core team because my role changed and I cannot > have responsibilities of neutron core. Thank you very much for all of the insightful reviews over the years. Good luck on your next adventure!

Re: [openstack-dev] Ironic integration CI jobs

On Tue, Oct 30, 2018 at 05:36:09PM -0700, Julia Kreger wrote: > ironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa - This job > essentially just duplicates the functionality already covered in other > jobs, including the grenade job. FYI this job runs in the Neutron check queue

Re: [openstack-dev] [neutron][stable] Stable Core Team Update

On Tue, Oct 02, 2018 at 10:41:58AM -0500, Miguel Lavalle wrote: > I want to nominate Bernard Cafarrelli as a stable core reviewer for Neutron > and related projects. Bernard has been increasing the number of stable > reviews he is doing for the project [1]. Besides that, he is a stable >

[openstack-dev] [neutron] Bug deputy report week of Sept 24

All, Here is my Bug Deputy report for the week of 9/24 - 10/1. It was a busy week! It is my recollection that prety much anything that doesn't have a patchset next to it is probably unowned and available for working. High priority == * https://bugs.launchpad.net/bugs/1794406 -

Re: [openstack-dev] [neutron] Core status

On Wed, Sep 19, 2018 at 06:19:44PM +, Gary Kotton wrote: > I have recently transitioned to a new role where I will be working on other > parts of OpenStack. Sadly I do not have the necessary cycles to maintain my > core responsibilities in the neutron community. Nonetheless I will continue

[openstack-dev] [python3] tempest and grenade conversion to python 3.6

which of these options properly reflects the state of affairs? If the answer is "C" then perhaps we can start a discussion on that migration. Thanks! Nate Johnston __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon

On Thu, Aug 30, 2018 at 08:28:40AM -0400, Doug Hellmann wrote: > Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300: > > On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston > > wrote: > > > > > Progress is also being tracked in a wiki p

[openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon

valle said, "If not now, when?" So please expect to see changes landing in your projects under the topic "python3-first". If these cause issues for you please feel free to reach out to either me or the python 3 goal champions. Progress is also being tracked in a wiki page [4]. Tha

Re: [openstack-dev] [goal][python3] week 3 update

ng. I know that over time we have done a fair amount of work to get ready for the python3 transition, so if any anomalies come up as the patches get generated for Neutron please feel free to reach out to me to get them resolved. Nate Johnston

Re: [openstack-dev] Appointing Slawek Kaplonski to the Neutron Drivers team

On Mon, Aug 27, 2018 at 11:42:47AM -0500, Miguel Lavalle wrote: > Dear Neutron team, > > In order to help the Neutron Drivers team to perform its very important job > of guiding the community to evolve the OpenStack Networking architecture to > meet the needs of our current and future users [1],

[openstack-dev] [neutron][fwaas] Investigation into debian/l3/wsgi/fwaas error

with any of the previously listed constraints on this scenario. So I am going to copy Brian Haley for his L3 expertise, as well as the 3 FWAaaS cores to see if this directs their thoughts in any particular direction. I hope to continue the investigation tomorrow. Thanks, Nate Johnston njohnston

[openstack-dev] Stepping down from Neutron roles

All, I have been delaying this long enough... sadly, due to changes in direction I am no longer able to spend time working on OpenStack, and as such I need to resign my duties as Services lieutenant, and liaison to the Infra team. My time in the Neutron and FWaaS community has been one of the

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

Thank you Armando for your leadership in transforming the Stadium, for always being being helpful and patient shepherding a gaggle of small projects. You set an example for how to deal with difficult Layer 8 and Layer 9 issues[1]. Thank you for your leadership and your service. --N. [1]

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

The neutron-fwaas team is an active and enthusiastic participant in the Neutron stadium, and is targeting FWaaS v2 to complete in the Ocala release. Once FWaaS v2 is complete, the neutron-fwaas team will start deprecating FWaaS v1 in the Pike cycle. --N. On Sun, Dec 18, 2016 at 9:56 PM zhi

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

Carl, Thanks for all of the help and encouragement you have given to me, especially in the L3 arena. Sometimes what can seem like a small thing to someone deeply versed in a project is a real lifeline for a newer contributor. I look forward to seeing where your story goes from here. Thanks,

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

On Sat, Oct 29, 2016 at 08:41:42AM +, Nate Johnston wrote: > Hello neutron-fwaas team, > > With the expiration of Daylight Savings Time imminent in the USA, I would like > to propose that we change the meeting time for the neutron-fwaas IRC meeting > from the current value of

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

On Tue, Nov 01, 2016 at 01:17:25PM +0100, Ihar Hrachyshka wrote: > Armando M. wrote: > > > >Slight variation, call it option 6: > > > >1) Identify the most impacted (coupled) project affected by these changes. > >2) Fix it in order to provide folks with a recipe for how to

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

Hello neutron-fwaas team, With the expiration of Daylight Savings Time imminent in the USA, I would like to propose that we change the meeting time for the neutron-fwaas IRC meeting from the current value of 0400 UTC. Here are a few proposals: First proposed time: 1300 UTC Tokyo (UTC+0900):

[openstack-dev] [neutron] neutron-qos meeting cancelled until 11/15

All, I am cancelling the neutron-qos meeting for this week, as well as the week right after the summit. So the next neutron-qos meeting will be on 11/15. I look forward to seeing you all in Barcelona! Thanks, --N. __

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

I responded to Miguel privately, but I'll be there as well! --N. On Fri, Oct 14, 2016 at 01:30:57PM -0500, Miguel Lavalle wrote: > set=UTF-8 > > 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

Re: [openstack-dev] [Neutron] Adding ihrachys to theneutron-drivers team

I made the same assumption! Congrats Ihar! --N. On Mon, Sep 19, 2016 at 12:33:06PM +, John Davidge wrote: > Honestly, I had assumed Ihar was on the Drivers team already :) > > A great addition to the team, and much deserved! > > From: Paul Michali

Re: [openstack-dev] Election Season, PTL and TC September/October 2016

On Tue, Sep 13, 2016 at 07:48:06AM -0500, Sean McGinnis wrote: > On Tue, Sep 13, 2016 at 05:14:56PM +1000, Tony Breeds wrote: > > On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: > > > > > Lastly, election officials are also reachable through the > > > #openstack-election

[openstack-dev] Neutron Bug Deputy report

Neutrinos, Since the Neutron mid-cycle has pre-empted the usual team meeting, I am issuing my report as bug deputy for the week of August 8-16 in email form. There were five critical bugs filed last week, two of which are still outstanding. They are: 1.

Re: [openstack-dev] [kolla] Usage of Reno - all devs please read

On Tue, Jun 28, 2016 at 11:47:58PM +0800, Jeffrey Zhang wrote: > On Tue, Jun 28, 2016 at 9:23 PM, Hui Kang wrote: > > > Do you mind giving some example of such reno release note? Thanks. > > ​like this https://review.openstack.org/#/c/235398/ .​ The instructions are

Re: [openstack-dev] [neutron][general] Multiple implementation of /usr/bin/foo stored at the same location, leading to conflicts

On Wed, Jun 22, 2016 at 05:55:48PM +0200, Thomas Goirand wrote: > Does neutron-fwaas also use "neutron" as launchpad package for bug report? Yes we do, just add the 'fwaas' tag to the bug. Thanks! --N. __ OpenStack

Re: [openstack-dev] [rally] "Failed to create the requested number of tenants" error

Rally deployment configuration > (this can be obtained via command "rally deployment config") is correct. > Please use correct deployment configuration in opposite to envvars like > OS_AUTH_URL while using Rally > > > On Fri, Jun 10, 2016 at 5:25 PM, Nate Johnston <ope

Re: [openstack-dev] [rally] "Failed to create the requested number of tenants" error

ms like you didn't setup admin endpoint for keystone in that region. > > Best regards, > Boris Pavlovic > > On Thu, Jun 9, 2016 at 12:41 PM, Nate Johnston <openstackn...@gmail.com> > wrote: > > > Rally folks, > > > > I am working with an engineer to get h

[openstack-dev] [rally] "Failed to create the requested number of tenants" error

Rally folks, I am working with an engineer to get him up to speed on Rally on a new development. He is trying out running a few tests from the samples directory, like samples/tasks/scenarios/nova/list-hypervisors.yaml - but he keeps getting the error "Completed: Exit context: `users`\nTask

[openstack-dev] [neutron][fwaas] neutron-fwaas meeting reminder

All, Now that the FWaaS team has a brand new sparkling meeting time, I wanted to remind anyone who is interested to join us on #openstack-meeting-3 for a discussion about the state of Firewall as a Service. The meeting is Wednesday at 0400 UTC. For your convenience, this is what that translates

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

FWaaS team, After a day of looking at the tests currently failing in the FWaaS repo, I believe I have the issue narrowed down considerably. First, to restate what is going on. If you check out the neutron-fwaas repository and run `tox -e py27` in it, you will get six errors all in the

[openstack-dev] [neutron] neutron-qos meeting cancelled this week

All, Because many of us are still recovering from the summit or on vacation, we are cancelling the neutron-qos meeting for tomorrow. We will resume with the next meeting, on May 18th. Thanks, --N. __ OpenStack Development

Re: [openstack-dev] [neutron] Social at the summit

A few of us made it in, but the number that they can for is probably only one or two more. --N. On Thursday, April 28, 2016, Kyle Mestery wrote: > Folks, unfortunately this will have to be postponed. I was too busy doing > a standup routine with Armando to find another

Re: [openstack-dev] [neutron] Social at the summit

Count me in. --N. On Monday, April 25, 2016, Kyle Mestery wrote: > Ihar, Henry and I were talking and we thought Thursday night makes sense > for a Neutron social in Austin. If others agree, reply on this thread and > we'll find a place. > > Thanks! > Kyle > >

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

A new contributor's point of view... My first summit was Tokyo, so I have no comparison between how things are and they way they used to be. But by the end of Friday, I and the other people I spoke to - both first-time participants and veterans - had the same sentiment: we wished that the