[openstack-dev] [neutron] Bug deputy

Hi, An urgent matter has come up this week. If possible, can someone please replace me. Sorry Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:

[openstack-dev] [python3] flake8 and pycodestyle W60x warnings

pycodestyle-2.4.0 added new warnings W605 and W606, which needs to be addressed or future versions of python3 will refuse to run. https://github.com/PyCQA/pycodestyle/pull/676 (OpenStack CI's flake8 is pre pycodestyle age, flake8 version isn't managed by g-r, but that's another story. No release

[openstack-dev] [puppet] [magnum] Magnum tempest fails with 400 bad request

Hello, I was interested in getting Magnum working in gate by getting @dms patch fixed and merged [1]. The installation goes fine on Ubuntu and CentOS however the tempest testing for Magnum fails on CentOS (it not available in Ubuntu). It seems to be related to authentication against keystone bu

Re: [openstack-dev] [tripleo] [barbican] [tc] key store in base services

Jeremy Stanley wrote: [...] As a community, we're likely to continue to make imbalanced trade-offs against relevant security features if we don't move forward and declare that some sort of standardized key storage solution is a fundamental component on which OpenStack services can rely. Being abl

Re: [openstack-dev] [tripleo] [barbican] [tc] key store in base services

On 5/17/18 9:58 AM, Thierry Carrez wrote: Jeremy Stanley wrote: [...] As a community, we're likely to continue to make imbalanced trade-offs against relevant security features if we don't move forward and declare that some sort of standardized key storage solution is a fundamental component on w

Re: [openstack-dev] [tripleo] [barbican] [tc] key store in base services

On 05/17/2018 10:18 AM, Bogdan Dobrelya wrote: > On 5/17/18 9:58 AM, Thierry Carrez wrote: >> Jeremy Stanley wrote: >>> [...] >>> As a community, we're likely to continue to make imbalanced >>> trade-offs against relevant security features if we don't move >>> forward and declare that some sort o

[openstack-dev] [QA][Forum] QA onboarding session in Vancouver

Hi All, QA team is planning an onboarding session during the Vancouver Summit: - https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21646/qa-project-onboarding - Tuesday, May 22, 2018, 9:50am-10:30am - Vancouver Convention Centre West - Level Two - Room 223 Details of this s

Re: [openstack-dev] [docs] Automating documentation the tripleo way?

On 16.05.18 20:40, Doug Hellmann wrote: Weren't the folks doing the training-labs or training-guides taking a similar approach? IIRC, they ended up implementing what amounted to their own installer for OpenStack, and then ended up with all of the associated upgrade and testing burden. training-

[openstack-dev] Canceling QA office hour for next week

Hi All, As most of us will be in Vancouver summit next week, i am canceling the next week QA office hour (24th May, Thursday). We will resume the same after summit which will be on 31st May, Thursday. -gmann __ OpenStack De

Re: [openstack-dev] [puppet] [magnum] Magnum tempest fails with 400 bad request

On 05/17/2018 09:49 AM, Tobias Urdin wrote: > Hello, > > I was interested in getting Magnum working in gate by getting @dms patch > fixed and merged [1]. > > The installation goes fine on Ubuntu and CentOS however the tempest > testing for Magnum fails on CentOS (it not available in Ubuntu). > >

[openstack-dev] [horizon] No meeting on May 23rd

Hi all, Some of the team will be attending the OpenStack summit in Vancouver, so I am canceling the weekly IRC meeting for the 23rd. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ __ OpenStack Development Mailing List (no

Re: [openstack-dev] [python3] flake8 and pycodestyle W60x warnings

On 2018-05-17 16:09:12 +0900 (+0900), IWAMOTO Toshihiro wrote: [...] > OpenStack CI's flake8 is pre pycodestyle age, It's not "OpenStack CI's flake8" version. Nova's master branch is getting flake8 transitively through its test-requirement on hacking!=0.13.0,<0.14,>=0.12.0 which is causing it to s

[openstack-dev] [Cinder] Need suggestion to add split-logger functionality in cinder

Hi All, Problem description: Monty Taylor added split-logger functionality in patch[1]. This functionality splits logs in four different logs: * keystoneauth.session.request * keystoneauth.session.response * keystoneauth.session.body * keystoneauth.session.requ

[openstack-dev] [release] Release countdown for week R-14 and R-13, May 21 - June 1

Here is the countdown content for the next two weeks, to cover while the Summit takes place. Development Focus - Work on new features should be well underway. The Rocky-2 milestone is coming up quick. Hopefully teams have good representation attending the Forum. This is a great o

Re: [openstack-dev] [docs] Automating documentation the tripleo way?

On Wed, 16 May 2018 13:26:46 -0600 Wesley Hayutin wrote: > On Wed, May 16, 2018 at 3:05 PM Doug Hellmann wrote: > > > Excerpts from Wesley Hayutin's message of 2018-05-16 12:51:25 -0600: > > > On Wed, May 16, 2018 at 2:41 PM Doug Hellmann > > wrote: > > > > > > > Excerpts from Petr Kovar's mes

Re: [openstack-dev] [docs] Style guide for OpenStack documentation

On Wed, 16 May 2018 17:05:15 + Jeremy Stanley wrote: > On 2018-05-16 18:24:45 +0200 (+0200), Petr Kovar wrote: > [...] > > I'd like to propose replacing the reference to the IBM Style Guide > > with a reference to the developerWorks editorial style guide > > (https://www.ibm.com/developerwork

Re: [openstack-dev] [docs] Style guide for OpenStack documentation

On 2018-05-17 16:35:36 +0200 (+0200), Petr Kovar wrote: > On Wed, 16 May 2018 17:05:15 + > Jeremy Stanley wrote: > > > On 2018-05-16 18:24:45 +0200 (+0200), Petr Kovar wrote: > > [...] > > > I'd like to propose replacing the reference to the IBM Style Guide > > > with a reference to the devel

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

Doug Hellmann wrote on 05/14/2018 08:52:08 AM: > ... snip ... > > We still have about 50 open patches related to adding the > lower-constraints test job. I'll keep those open until the third > milestone of the Rocky development cycle, and then abandon the rest to > clear my gerrit view so it is

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

Hey Gary, my turn is coming up soon (week of June 4th), I can jump the line a bit and cover you if you or anyone can cover my currently assigned week.   Thanks,  - James Anziano   - Original message -From: Gary Kotton To: OpenStack List Cc:Subject: [openstack-dev] [neutron] Bug deputyDate:

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

Thanks! From: James Anziano Reply-To: OpenStack List Date: Thursday, May 17, 2018 at 6:21 PM To: OpenStack List Cc: OpenStack List Subject: Re: [openstack-dev] [neutron] Bug deputy Hey Gary, my turn is coming up soon (week of June 4th), I can jump the line a bit and cover you if you or anyon

[openstack-dev] [all][api] late addition to forum schedule

After some discussion on twitter and IRC, we've added a new session to the Forum schedule for next week to discuss our options for cleaning up some of the design/technical debt in our REST APIs. It's early days in the conversation, but we wanted to take advantage of our time together in person to b

[openstack-dev] [neutron] [fwaas] Neutron FWaaS weekly team meeting cancelled on May 24.

Hi All: With the Summit at Vancouver, we will cancel the FWaaS weekly meeting for May 24 14:00 UTC. We will resume as usual from May 31. Thanks Sridar __ OpenStack Development Mailing List (not for usage questions) Unsubscr

Re: [openstack-dev] [docs] Automating documentation the tripleo way?

On Thu, May 17, 2018 at 10:22 AM Petr Kovar wrote: > On Wed, 16 May 2018 13:26:46 -0600 > Wesley Hayutin wrote: > > > On Wed, May 16, 2018 at 3:05 PM Doug Hellmann > wrote: > > > > > Excerpts from Wesley Hayutin's message of 2018-05-16 12:51:25 -0600: > > > > On Wed, May 16, 2018 at 2:41 PM Dou

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, Today's meeting was brief, primarily focused on planning for the summit sessions[7][8] that the SIG will host and facilitate. The first session[7], will be a Birds of a Feather (BoF) gathering where the topics will be determined by the attendees. One topic that will

[openstack-dev] [manila] no community meeting Thurs 24 May 2018

There will be no Manila weekly meeting, Thursday May 24, given the Vancouver Summit is going on that week. -- Tom Barron __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lis

[openstack-dev] [manila] manila operator's feedback forum etherpad available

Next week at the Summit there is a forum session dedicated to Manila opertors' feedback on Thursday from 1:50-2:30pm [1] for which we have started an etherpad [2]. Please come and help manila developers do the right thing! We're particularly interested in experiences running the OpenStack sha

[openstack-dev] [security sig] No meeting May 24th

Hello, Due to members attending the OpenStack summit in Vancouver, we will be canceling the Security SIG meeting on May 24th. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@l

[openstack-dev] [nova] FYI on changes that might impact out of tree scheduler filters

CERN has upgraded to Cells v2 and is doing performance testing of the scheduler and were reporting some things today which got us back to this bug [1]. So I've starting pushing some patches related to this but also related to an older blueprint I created [2]. In summary, we do quite a bit of DB

Re: [openstack-dev] [cyborg] [nova] Cyborg quotas

Hi all,     Thanks for all the feedback. Please see below. 2018-05-17 1:24 GMT+08:00 Jay Pipes >: Placement already stores usage information for all allocations of resources. There is already even a /usages API endpoint that you can specify a project and/or u

Re: [openstack-dev] [docs] Automating documentation the tripleo way?

On 16/05/18 13:11, Ben Nemec wrote: On 05/16/2018 10:39 AM, Petr Kovar wrote: Hi all, In the past few years, we've seen several efforts aimed at automating procedural documentation, mostly centered around the OpenStack installation guide. This idea to automatically produce and verify installa

Re: [openstack-dev] [cyborg] [nova] Cyborg quotas

On 5/17/2018 3:36 PM, Nadathur, Sundar wrote: This applies only to the resources that Nova handles, IIUC, which does not handle accelerators. The generic method that Alex talks about is obviously preferable but, if that is not available in Rocky, is the filter an option? If nova isn't creatin

Re: [openstack-dev] [all][api] late addition to forum schedule

On 5/17/2018 11:02 AM, Doug Hellmann wrote: After some discussion on twitter and IRC, we've added a new session to the Forum schedule for next week to discuss our options for cleaning up some of the design/technical debt in our REST APIs. Not to troll too hard here, but it's kind of frustrating

[openstack-dev] [Glance] No team meeting during the summit week

As majority of the team is in Vancouver for the summit we will cancel next weeks meeting (24th of May). Glance team will have next meeting in IRC Thu 31st. Thanks, Erno "jokke" Kuvaja __ OpenStack Development Mailing List (no

Re: [openstack-dev] [all][api] late addition to forum schedule

On 5/17/2018 5:23 PM, Matt Riedemann wrote: Not to troll too hard here, but it's kind of frustrating to see that twitter trumps people actually proposing sessions on time and then having them be rejected. I reckon this is because there were already a pre-defined set of slots / rooms for Forum

[openstack-dev] [Neutron] [Upgrades] Cancel next IRC meeting (May 24th)

Hi, We are canceling our next Neutron Upgrades subteam meeting on May 24th, due to summit. We will resume on May 31st. Thanks, Lujin __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-d

Re: [openstack-dev] [all][api] late addition to forum schedule

On 2018-05-17 18:47:06 -0500 (-0500), Matt Riedemann wrote: > On 5/17/2018 5:23 PM, Matt Riedemann wrote: > > Not to troll too hard here, but it's kind of frustrating to see that > > twitter trumps people actually proposing sessions on time and then > > having them be rejected. > > I reckon this i

[openstack-dev] [Forum] [all] [Stable] OpenStack is "mature" -- time to get serious on Maintainers -- Session etherpad and food for thought for discussion

Folks, TL;DR The last session related to extended releases is: OpenStack is "mature" -- time to get serious on Maintainers It will be in room 220 at 11:00-11:40 The etherpad for the last session in the series on Extended releases is here: https://etherpad.openstack.org/p/YVR-openstack-maintainers

Re: [openstack-dev] [tc] [all] TC Report 18-20

Thierry Carrez [mailto:thie...@openstack.org] > > Graham Hayes wrote: > > Any additional background on why we allowed LCOO to operate like this > > would help a lot. > The group was started back when OPNFV was first getting involved with OpenStack. Many of the members came from that community.

[openstack-dev] [devstack][python/pip][octavia] pip failure during octavia/ocata image build by devstack

Hello - I'm trying to install a working local.conf devstack ocata on a new server, and some python packages have changed so I end up with this error during the build of octavia image: 2018-05-18 01:00:26.276 |   Found existing installation: Jinja2 2.8 2018-05-18 01:00:26.280 | Uninsta