Re: [openstack-dev] [goal][python3] more updates to the goal tools

https://review.openstack.org/#/c/593289/ should fix the similar problem you found with CommentedSeq. Doug Excerpts from super user's message of 2018-08-18 11:15:20 +0900: > The problem was fixed. > > Nguyen Hai > > On Fri, Aug 17, 2018 at 11:47 PM Doug Hellmann > wrote: >

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

Excerpts from Dan Smith's message of 2018-08-17 10:30:41 -0700: > > The subject of using placement in Cinder has come up, and since then I've > > had a > > few conversations with people in and outside of that team. I really think > > until > > placement is its own project outside of the nova

Re: [openstack-dev] [goal][python3] more updates to the goal tools

> * File > > "/home/stack/python3-first/goal-tools/.tox/venv/lib/python3.6/site-packages/cliff/command.py", > > line 184, in run* > > *return_code = self.take_action(parsed_args) or 0* > > * File > > "/home/stack/python3-first/goal-tools/goal_to

Re: [openstack-dev] [neutron] Broken pep8 job

Excerpts from Slawomir Kaplonski's message of 2018-08-17 10:16:35 +0200: > Hi, > > It looks that pep8 job in Neutron is currently broken because of new version > of bandit (1.5.0). > If You have in Your patch failure of pep8 job with error like [1] please > don’t recheck as it will not help. >

Re: [openstack-dev] [goal][python3] more updates to the goal tools

-first/goal-tools/goal_tools/python3_first/jobs.py", > line 531, in take_action* > *entry,* > * File > "/home/stack/python3-first/goal-tools/goal_tools/python3_first/jobs.py", > line 397, in merge_project_settings* > *up.get(pipeline, comments.CommentedMa

Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2

Excerpts from Tony Breeds's message of 2018-08-17 06:56:11 +1000: > On Thu, Aug 16, 2018 at 10:45:32AM -0400, Doug Hellmann wrote: > > > Is there any reason we can't uncap pbr, at least within the CI jobs? > > It might work for the docs builds but jumping a major version of

Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2

Excerpts from Andreas Jaeger's message of 2018-08-16 08:42:22 +0200: > On 2018-08-16 07:38, Tony Breeds wrote: > > On Thu, Aug 16, 2018 at 06:27:39AM +0200, Andreas Jaeger wrote: > > > >> Ocata should be retired by now ;) Let's drop it... > > > > *cough* extended maintenance *cough* ;P > > Ah,

[openstack-dev] [oslo][castellan][python3][goal] need help debugging stable/queens failure in castellan functional tests

The patch to add the zuul job settings to the castellan stable/queens branch is failing the castellan-functional-devstack job. It looks like the job fails to set up some of the services correctly (I see lots of messages about services not responding or not starting). When was that job added to

Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2

Excerpts from Andreas Jaeger's message of 2018-08-15 09:28:51 +0200: > On 08/15/2018 07:25 AM, Tony Breeds wrote: > > On Tue, Aug 14, 2018 at 04:22:16PM -0400, Doug Hellmann wrote: > > > >> Now that https://review.openstack.org/#/c/591671/ has landed, we need > >>

Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2

Excerpts from Tony Breeds's message of 2018-08-15 15:25:29 +1000: > On Tue, Aug 14, 2018 at 04:22:16PM -0400, Doug Hellmann wrote: > > > Now that https://review.openstack.org/#/c/591671/ has landed, we need > > someone to propose the backports of the constraint updates to all o

Re: [openstack-dev] [oslo][mox][python3][goal] need help with mox3 and python 3.6

Excerpts from Zane Bitter's message of 2018-08-14 16:26:09 -0500: > On 14/08/18 15:45, Doug Hellmann wrote: > > The python 3.6 unit test job has exposed an issue with mox3. It looks > > like it might just be in the test suite, but I can't tell. > > > > I'm looki

[openstack-dev] [oslo][mox][python3][goal] need help with mox3 and python 3.6

The python 3.6 unit test job has exposed an issue with mox3. It looks like it might just be in the test suite, but I can't tell. I'm looking for one of the folks who suggested we should just keep maintaining mox3 to help fix it. Please go ahead and take over the relevant patch and include

Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2

Excerpts from Doug Hellmann's message of 2018-08-13 18:30:02 -0400: > Excerpts from Matthew Thode's message of 2018-08-13 16:17:30 -0500: > > On 18-08-13 20:28:23, Andreas Jaeger wrote: > > > On 2018-08-13 19:16, Andreas Jaeger wrote: > > > > On 2018-08-13 18:40, Petr Kovar wrote: > > > > > Hi

Re: [openstack-dev] [requirements][release][osc] FFE osc-lib 1.11.1 release

Excerpts from Tony Breeds's message of 2018-08-14 15:28:07 +1000: > On Tue, Aug 14, 2018 at 12:11:53AM -0500, Matthew Thode wrote: > > > Maybe it'd be better to figure out what's using that removed method and > > those would need the update? > > Given we have per-project deps in rocky only those

Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2

Excerpts from Matthew Thode's message of 2018-08-13 16:17:30 -0500: > On 18-08-13 20:28:23, Andreas Jaeger wrote: > > On 2018-08-13 19:16, Andreas Jaeger wrote: > > > On 2018-08-13 18:40, Petr Kovar wrote: > > > > Hi all, > > > > > > > > This is a request for an FFE to release openstackdocstheme

Re: [openstack-dev] [oslo][tooz][etcd] need help debugging tooz test failure

Excerpts from Davanum Srinivas (dims)'s message of 2018-08-14 04:05:23 +0800: > Jay, Doug, > > We need to blacklist 0.2.2 and 0.2.3 (looking at changelog in) > https://github.com/dims/etcd3-gateway/releases Done in https://review.openstack.org/591517 Thanks, Doug

Re: [openstack-dev] [oslo][tooz][etcd] need help debugging tooz test failure

Excerpts from Davanum Srinivas (dims)'s message of 2018-08-14 03:50:54 +0800: > Thanks Jay. Pushed out a 0.2.4 with a revert to the offending PR > > On Tue, Aug 14, 2018 at 1:22 AM Jay Pipes wrote: > > > On 08/12/2018 04:11 PM, Doug Hellmann wrote: > > > The tooz

Re: [openstack-dev] [oslo][tooz][etcd] need help debugging tooz test failure

Excerpts from Jay Pipes's message of 2018-08-13 13:21:56 -0400: > On 08/12/2018 04:11 PM, Doug Hellmann wrote: > > The tooz tests on master and stable/rocky are failing with an error: > > > > UnicodeDecodeError: 'utf8' codec can't decode byte 0xc4 in position 0: > >

[openstack-dev] [goal][python3] week 1 update: here we go!

This is week 1 of the roll-out of the "Run under Python 3 by default" goal (https://governance.openstack.org/tc/goals/stein/python3-first.html). I intend to send a summary message like this roughly weekly to report progress on the Zuul setting migrations, because that portion of the goal needs to

Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release

Excerpts from Ghanshyam Mann's message of 2018-08-13 23:12:51 +0900: > > > > On Mon, 13 Aug 2018 23:01:33 +0900 Doug Hellmann > wrote > > Excerpts from Dmitry Tantsur's message of 2018-08-13 15:51:56 +0200: > > > On 08/13/2018 03:46 PM, Doug Hel

[openstack-dev] [tc] Technical Committee update for 13 Aug

This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at:

Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release

Excerpts from Dmitry Tantsur's message of 2018-08-13 15:51:56 +0200: > On 08/13/2018 03:46 PM, Doug Hellmann wrote: > > Excerpts from Dmitry Tantsur's message of 2018-08-13 15:35:23 +0200: > >> Hi, > >> > >> The plugins are branchless and should stay so. Let

Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release

Excerpts from Jim Rollenhagen's message of 2018-08-13 09:50:34 -0400: > // jim > > On Mon, Aug 13, 2018 at 9:46 AM, Doug Hellmann > wrote: > > > Excerpts from Dmitry Tantsur's message of 2018-08-13 15:35:23 +0200: > > > Hi, > > > > > > The p

Re: [openstack-dev] [releases][rocky][tempest-plugins][ptl] Reminder to tag the Tempest plugins for Rocky release

Excerpts from Dmitry Tantsur's message of 2018-08-13 15:35:23 +0200: > Hi, > > The plugins are branchless and should stay so. Let us not dive into this > madness > again please. You are correct that we do not want to branch, because we want the same tests running against all branches of

[openstack-dev] [oslo][tooz][etcd] need help debugging tooz test failure

The tooz tests on master and stable/rocky are failing with an error: UnicodeDecodeError: 'utf8' codec can't decode byte 0xc4 in position 0: invalid continuation byte This is unrelated to the change, which is simply importing test job settings or updating the .gitreview file. I need

Re: [openstack-dev] [all][tc][election] Timing of the Upcoming Stein TC election

Excerpts from Tony Breeds's message of 2018-08-10 07:44:42 +1000: > On Thu, Aug 09, 2018 at 05:20:53PM -0400, Doug Hellmann wrote: > > Excerpts from Tony Breeds's message of 2018-08-08 14:39:30 +1000: > > > Hello all, > > > With the PTL elections behind us

Re: [openstack-dev] [tc] [all] documenting appointed PTLs

Excerpts from Chris Dent's message of 2018-08-10 16:19:27 +0100: > > We've had several appointed PTLs this cycle, in some cases because > people forgot to nominate themselves, in other cases because > existing maintainers have been pulled away and volunteers stepped > up. Thanks to those people

Re: [openstack-dev] [all][tc][election] Timing of the Upcoming Stein TC election

Excerpts from Tony Breeds's message of 2018-08-08 14:39:30 +1000: > Hello all, > With the PTL elections behind us it's time to start looking at the > TC election. Our charter[1] says: > > The election is held no later than 6 weeks prior to each OpenStack > Summit (on or before ‘S-6’

Re: [openstack-dev] [openstack-ansible][kolla-ansible][tripleo] ansible roles: where they live and what do they do

Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600: > Ahoy folks, > > I think it's time we come up with some basic rules/patterns on where > code lands when it comes to OpenStack related Ansible roles and as we > convert/export things. There was a recent proposal to create an >

Re: [openstack-dev] [all][election][tc] Lederless projects.

Excerpts from Tony Breeds's message of 2018-08-01 10:32:50 +1000: [snip] > Need appointment : 8 (Dragonflow Freezer Loci Packaging_Rpm RefStack >Searchlight Trove Winstackers) To summarize the situation for these teams as it stands now: Omer Anson

Re: [openstack-dev] [nova][placement][oslo] Excessive WARNING level log messages in placement-api

Excerpts from Lance Bragstad's message of 2018-08-09 12:55:52 -0500: > > On 08/09/2018 12:48 PM, Doug Hellmann wrote: > > Excerpts from Matt Riedemann's message of 2018-08-09 12:18:14 -0500: > >> On 8/9/2018 11:47 AM, Doug Hellmann wrote: > >>> Excerpts from Jay

Re: [openstack-dev] [Release-job-failures][masakari][release] Pre-release of openstack/masakari failed

Excerpts from zuul's message of 2018-08-09 17:23:01 +: > Build failed. > > - release-openstack-python > http://logs.openstack.org/84/84135048cb372cbd11080fc27151949cee4e52d1/pre-release/release-openstack-python/095990b/ > : FAILURE in 8m 57s > - announce-release announce-release : SKIPPED >

Re: [openstack-dev] [nova][placement][oslo] Excessive WARNING level log messages in placement-api

Excerpts from Matt Riedemann's message of 2018-08-09 12:18:14 -0500: > On 8/9/2018 11:47 AM, Doug Hellmann wrote: > > Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400: > >> For evidence, see: > >> > >> http://logs.openstack.org/41/590041/1/check

Re: [openstack-dev] [nova][placement][oslo] Excessive WARNING level log messages in placement-api

Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400: > For evidence, see: > > http://logs.openstack.org/41/590041/1/check/tempest-full-py3/db08dec/controller/logs/screen-placement-api.txt.gz?level=WARNING > > thousands of these are filling the logs with WARNING-level log messages, >

Re: [openstack-dev] OpenStack lagging behind 2 major python versions: we need a Python 3.7 gate

Excerpts from Andrey Kurilin's message of 2018-08-09 13:35:53 +0300: > Hi Doug! > > I'm ready to port our job to openstack-zuul-jobs repo, but I expect that > Community will not accept it. > > The result of rally unittests is different between environments with python > 3.7 final release and

Re: [openstack-dev] [all][elections] Project Team Lead Election Conclusion and Results

Excerpts from Tony Breeds's message of 2018-08-08 10:20:15 +1000: > Thank you to the electorate, to all those who voted and to all > candidates who put their name forward for Project Team Lead (PTL) in > this election. A healthy, open process breeds trust in our decision > making capability thank

Re: [openstack-dev] OpenStack lagging behind 2 major python versions: we need a Python 3.7 gate

Excerpts from Andrey Kurilin's message of 2018-08-08 15:25:01 +0300: > Thanks Thomas for pointing to the issue, I checked it locally and here is > an update for openstack/rally (rally framework without in-tree OpenStack > plugins) project: > > - added unittest job with py37 env It would be

Re: [openstack-dev] Stepping down as coordinator for the Outreachy internships

Excerpts from Victoria Martínez de la Cruz's message of 2018-08-07 20:47:28 -0300: > Hi all, > > I'm reaching you out to let you know that I'll be stepping down as > coordinator for OpenStack next round. I had been contributing to this > effort for several rounds now and I believe is a good

Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

Excerpts from Doug Hellmann's message of 2018-08-01 09:27:09 -0400: > Moisés Guimarães (moguimar) did quite a bit of work on oslo.config > during the Rocky cycle to add driver support. Based on that work, > and a discussion we have had since then about general cleanup needed > in oslo.config, I

[openstack-dev] [goal][python3] more updates to the goal tools

Champions, I have made quite a few changes to the tools for generating the zuul migration patches today. If you have any patches you generated locally for testing, please check out the latest version of the tool (when all of the changes merge) and regenerate them. Doug

Re: [openstack-dev] OpenStack lagging behind 2 major python versions: we need a Python 3.7 gate

Excerpts from Thomas Goirand's message of 2018-08-07 16:11:43 +0200: > On 08/07/2018 03:24 PM, Sean Mooney wrote: > > > i think we as a community will have to decide on the minimum and > > maximum python 3 versions > > we support for each release and adjust as we go forward. > > Whatever the

Re: [openstack-dev] Paste unmaintained

Excerpts from Thomas Goirand's message of 2018-08-07 16:57:59 +0200: > On 08/02/2018 04:27 PM, Doug Hellmann wrote: > > > > The last I heard, a few years ago Ian moved away from Python to > > JavaScript as part of his work at Mozilla. The support around > > paste.dep

[openstack-dev] [python3] champions, please review the updated process

I have updated the README.rst in the goal-tools repository with an updated process for preparing, proposing, and tracking the zuul migration patches. I need the other champions to look over the instructions and let me know if any parts are confusing or incomplete. Please do that as soon as you

[openstack-dev] [tc] Technical Committee status update for 6 August

This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at:

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

Excerpts from Doug Hellmann's message of 2018-05-14 08:52:08 -0400: > Excerpts from Doug Hellmann's message of 2018-03-25 16:04:11 -0400: > > Excerpts from Doug Hellmann's message of 2018-03-22 16:16:06 -0400: > > > Excerpts from Doug Hellmann's message of 2018-03-21 16:02:06 -0400: > > > >

Re: [openstack-dev] [nova] tempest-full-py3 rename means we now run that job on test-only changes

Excerpts from Matt Riedemann's message of 2018-08-04 16:44:26 -0500: > I've reported a nova bug for this: > > https://bugs.launchpad.net/nova/+bug/1785425 > > But I'm not sure what is the best way to fix it now with the zuul v3 > hotness. We had an irrelevant-files entry in project-config for

[openstack-dev] [searchlight][tc] removing searchlight from governance

Based on the fact that the Searchlight team missed the Rocky release and Stein PTL elections, I have proposed a patch to remove the project from governance. If the project is still being actively maintained and someone wants to take over leadership, please let us know here in this thread or on the

[openstack-dev] [freezer][tc] removing freezer from governance

Based on the fact that the Freezer team missed the Rocky release and Stein PTL elections, I have proposed a patch to remove the project from governance. If the project is still being actively maintained and someone wants to take over leadership, please let us know here in this thread or on the

Re: [openstack-dev] [oslo] Proposing Zane Bitter as oslo.service core

Excerpts from Ben Nemec's message of 2018-08-03 11:58:29 -0500: > Hi, > > Zane has been doing some good work in oslo.service recently and I would > like to add him to the core team. I know he's got a lot on his plate > already, but he has taken the time to propose and review patches in >

Re: [openstack-dev] Paste unmaintained

Excerpts from Stephen Finucane's message of 2018-08-02 15:11:25 +0100: > tl;dr: It seems Paste [1] may be entering unmaintained territory and we > may need to do something about it. > > I was cleaning up some warning messages that nova was issuing this > morning and noticed a few coming from

Re: [openstack-dev] [all][election] PTL nominations are now closed

Excerpts from Thierry Carrez's message of 2018-08-02 10:58:53 +0200: > Tony Breeds wrote: > > [...] > > There are 8 projects without candidates, so according to this > > resolution[1], the TC will have to decide how the following > > projects will proceed: Dragonflow, Freezer, Loci, Packaging_Rpm,

Re: [openstack-dev] [all][election] PTL nominations are now closed

Excerpts from Omer Anson's message of 2018-08-02 12:56:37 +0300: > Hi, > > I'm sorry for the inconvenience. I completely missed the nomination period. > Is it possible to send in a late nomination for Dragonflow? At this point the TC is going to be looking for a volunteer, so if there is one

Re: [openstack-dev] [all][election] PTL nominations are now closed

Excerpts from Jeremy Stanley's message of 2018-08-02 13:13:21 +: > On 2018-08-02 10:58:53 +0200 (+0200), Thierry Carrez wrote: > [...] > > Finally, RefStack: I feel like this should be wrapped into an > > Interoperability SIG, since that project team is not producing > > "OpenStack", but

[openstack-dev] [tc] Technical Committee update for 1 Aug 2018

This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at:

[openstack-dev] [all][python3] approved python3-first goal for stein

The goal to run jobs under python3 first has been approved for Stein [1]. We are going to be using storyboard for tracking work on the goal, so I have started creating the stories and tasks. Because of the complexity of the work, I am setting up 1 story for each team, with 1 task for each

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

Excerpts from Monty Taylor's message of 2018-08-01 09:58:03 -0500: > On 08/01/2018 08:38 AM, Jeremy Stanley wrote: > > On 2018-08-01 09:58:48 -0300 (-0300), Rafael Weingärtner wrote: > >> What about Rocket chat instead of Slack? It is open source. > >> https://github.com/RocketChat/Rocket.Chat >

[openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

Moisés Guimarães (moguimar) did quite a bit of work on oslo.config during the Rocky cycle to add driver support. Based on that work, and a discussion we have had since then about general cleanup needed in oslo.config, I think he would make a good addition to the oslo.config review team. Please

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

Excerpts from Andrey Kurilin's message of 2018-08-01 15:21:37 +0300: > ср, 1 авг. 2018 г. в 14:11, Dmitry Tantsur : > > > On 08/01/2018 12:49 PM, Andrey Kurilin wrote: > > > Hey Ian and stackers! > > > > > > ср, 1 авг. 2018 г. в 8:45, Ian Wienand > > >: > > > > > >

Re: [openstack-dev] [requirements][ffe] Critical bug found in python-cinderclient

Excerpts from Sean McGinnis's message of 2018-07-31 14:15:08 -0500: > A critical bug has been found in python-cinderclient that is impacting both > horizon and python-openstackclient (at least). > > https://bugs.launchpad.net/cinder/+bug/1784703 > > tl;dr is, something new was added with a

[openstack-dev] [tc] Technical Committee update for 17 July

This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at:

[openstack-dev] [all][tc][release][election][adjutant] Welcome Adjutant as an official project!

The Adjutant team's application [1] to become an official project has been approved. Welcome! As I said on the review, because it is past the deadline for Rocky membership, Adjutant will not be considered part of the Rocky release, but a future release can be part of Stein. The team should

[openstack-dev] [all][ptl][release] deadline for non-client library releases 19 July

The deadline for releasing non-client libraries for Rocky is coming up next week on 19 July (https://releases.openstack.org/rocky/schedule.html). We have a few libraries that have no releases at all this cycle, which makes creating the stable branch problematic. Therefore, if the PTL or release

[openstack-dev] [release][ptl] Release countdown for week R-6, July 16-20

Development Focus - Teams should be focused on implementing planned work. Work should be wrapping up on non-client libraries to meet the lib deadline Thursday, the 19th. General Information --- We are now getting close to the end of the cycle. The non-client

Re: [openstack-dev] [Release-job-failures][group-based-policy] Release of openstack/group-based-policy failed

On Tue, Jul 10, 2018 at 9:21 AM, Doug Hellmann wrote: > > Excerpts from zuul's message of 2018-07-10 06:38:24 +: > >> Build failed. > >> > >> - release-openstack-python > >> http://logs.openstack.org/5b/5bbcfd7b41d39339ff9b9f8654681406d2508205/release/r

[openstack-dev] [tc] Technical Committee update for 2018-07-10

This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at:

Re: [openstack-dev] [requirements][taskflow] networkx migration

Excerpts from Matthew Thode's message of 2018-07-10 10:59:33 -0500: > On 18-07-09 15:15:23, Matthew Thode wrote: > > We have a patch that looks good, can we get it merged? > > > > https://review.openstack.org/#/c/577833/ > > > > Anyone from taskflow around? Maybe it's better to just mail the

Re: [openstack-dev] [Release-job-failures][group-based-policy] Release of openstack/group-based-policy failed

Excerpts from zuul's message of 2018-07-10 06:38:24 +: > Build failed. > > - release-openstack-python > http://logs.openstack.org/5b/5bbcfd7b41d39339ff9b9f8654681406d2508205/release/release-openstack-python/269f8ce/ > : FAILURE in 6m 31s > - announce-release announce-release : SKIPPED > -

Re: [openstack-dev] Fwd: [TIP] tox release 3.1.1

Excerpts from Ben Nemec's message of 2018-07-09 15:42:02 -0500: > > On 07/09/2018 11:16 AM, Eric Fried wrote: > > Doug- > > > > How long til we can start relying on the new behavior in the gate? I > > gots me some basepython to purge... > > I want to point out that most projects require a

Re: [openstack-dev] Fwd: [TIP] tox release 3.1.1

not sure how we're managing the version of tox we use in CI. Doug > > On 07/09/2018 11:03 AM, Doug Hellmann wrote: > > Heads-up, there is a new tox release out. 3.1 includes some behavior > > changes in the way basepython behaves (thanks, Stephen Finucan!), as > > well as oth

[openstack-dev] Fwd: [TIP] tox release 3.1.1

Heads-up, there is a new tox release out. 3.1 includes some behavior changes in the way basepython behaves (thanks, Stephen Finucan!), as well as other bug fixes. If you start seeing odd job failures, check your tox version. Doug --- Begin forwarded message from toxdevorg --- From: toxdevorg

Re: [openstack-dev] [python3][tc][infra][docs] changing the documentation build PTI to use tox

Excerpts from Zane Bitter's message of 2018-07-09 11:04:28 -0400: > On 05/07/18 16:46, Doug Hellmann wrote: > > I have a governance patch up [1] to change the project-testing-interface > > (PTI) for building documentation to restore the use of tox. > > > > We origi

[openstack-dev] [python3][tc][infra][docs] changing the documentation build PTI to use tox

I have a governance patch up [1] to change the project-testing-interface (PTI) for building documentation to restore the use of tox. We originally changed away from tox because we wanted to have a single standard command that anyone could use to build the documentation for a project. It turns out

Re: [openstack-dev] [cinder][security][api-wg] Adding http security headers

Excerpts from Jim Rollenhagen's message of 2018-07-05 12:53:34 -0400: > On Thu, Jul 5, 2018 at 12:40 PM, Nishant Kumar E < > nishant.e.ku...@ericsson.com> wrote: > > > Hi, > > > > > > > > I have registered a blueprint for adding http security headers - > >

Re: [openstack-dev] [tc] Technical Committee Update for 3 July

Excerpts from Hongbin Lu's message of 2018-07-03 22:06:41 -0400: > > > > Discussions about affiliation diversity continue in two directions. > > Zane's proposal for requirements for new project teams has stalled a > > bit. The work Thierry and Mohammed have done on the diversity tags has > >

Re: [openstack-dev] [release-announce][ironic] ironic 11.0.0 (rocky)

I want to compliment the Ironic team on writing such engaging and comprehensive release notes. Nice work! Doug Excerpts from no-reply's message of 2018-07-05 10:24:19 +: > We are gleeful to announce the release of: > > ironic 11.0.0: OpenStack Bare Metal Provisioning > > This release is

Re: [openstack-dev] [tc] Technical Committee Update for 3 July

Excerpts from Chris Dent's message of 2018-07-03 19:31:43 +0100: > On Tue, 3 Jul 2018, Doug Hellmann wrote: > > > Chris and Thierry have been discussing a technical vision for OpenStack. > > > > * https://etherpad.openstack.org/p/tech-vision-2018 > > Just so it's

[openstack-dev] [tc] Technical Committee Update for 3 July

This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at:

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

Excerpts from Takashi Yamamoto's message of 2018-07-03 13:12:53 +0900: > 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,

Re: [openstack-dev] [sqlalchemy][db][oslo.db][mistral] Is there a recommended MySQL driver for OpenStack projects?

Excerpts from Renat Akhmerov's message of 2018-07-03 18:33:44 +0700: > Hi, > > We’ve tried to address the bug [1] which is essentially caused > by the fact that we saw that MySQLDb driver wasn’t compatible with > eventlet’s green threads. In a nutshell, when we used the “eventlet” > RPC executor

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

Excerpts from Dmitry Tantsur's message of 2018-06-28 17:05:09 +0200: > On 06/27/2018 03:17 AM, Ghanshyam Mann wrote: > > Users (Not Gate) will face below issues: > > - User cannot use PluginNR with Tempest <19.0.0 (where that new interface > > was not present). And there is no PluginNR

Re: [openstack-dev] [requirements][stable][docs] updating openstackdocstheme in stable branches

Excerpts from Tony Breeds's message of 2018-06-27 12:42:47 +1000: > On Tue, Jun 26, 2018 at 09:03:40AM -0400, Doug Hellmann wrote: > > Requirements team, > > > > At some point in the next few months we're going to want to raise > > the constraint on openstackdocstheme

Re: [openstack-dev] [python3] building tools for the transition

Excerpts from Doug Hellmann's message of 2018-06-20 11:34:10 -0400: > I want to thank Nguyễn Trí Hải, Ma Lei, and Huang Zhiping for > agreeing to be a part of the goal champion team for the python3 > goal for Stein. > > The next step for us is to build some tools to make the process a > little

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

Excerpts from Doug Hellmann's message of 2018-06-26 11:19:05 -0400: > 29 out of 40 repos that have "tempest" in the name have not been > tagged via the releases repo. Not all of those are plugins. Here's > a list: > > $ for repo in $(grep openstack/ reference/projects.yaml | grep tempest | > cut

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

Excerpts from Matthew Treinish's message of 2018-06-26 10:37:54 -0400: > On Tue, Jun 26, 2018 at 10:12:30AM -0400, Doug Hellmann wrote: > > Excerpts from Matthew Treinish's message of 2018-06-26 09:52:09 -0400: > > > On Tue, Jun 26, 2018 at 08:53:21AM -0400, Doug Hellmann wrote

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

Excerpts from Matthew Treinish's message of 2018-06-26 09:52:09 -0400: > On Tue, Jun 26, 2018 at 08:53:21AM -0400, Doug Hellmann wrote: > > Excerpts from Andrea Frittoli's message of 2018-06-26 13:35:11 +0100: > > > On Tue, 26 Jun 2018, 1:08 pm Thierry Carrez, > > > w

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

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 chip away at it. For now we'll have to settle for > not

[openstack-dev] [requirements][stable][docs] updating openstackdocstheme in stable branches

Requirements team, At some point in the next few months we're going to want to raise the constraint on openstackdocstheme in all of the old branches so we can take advantage of a new feature for showing the supported status of each version of a project. That feature isn't implemented yet, but I

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

Excerpts from Andrea Frittoli's message of 2018-06-26 13:35:11 +0100: > On Tue, 26 Jun 2018, 1:08 pm Thierry Carrez, wrote: > > > Dmitry Tantsur wrote: > > > [...] > > > My suggestion: tempest has to be compatible with all supported releases > > > (of both services and plugins) OR be branched. >

Re: [openstack-dev] [Openstack-sigs] [PTG] Updates!

Excerpts from Jeremy Stanley's message of 2018-06-25 16:01:11 +: > On 2018-06-25 11:26:29 -0400 (-0400), Doug Hellmann wrote: > > Excerpts from Thierry Carrez's message of 2018-06-25 17:15:44 +0200: > > > Doug Hellmann wrote: > > > > Are we planning to have

Re: [openstack-dev] [all][requirements] we need to talk about eventlet

Excerpts from Matthew Thode's message of 2018-06-25 10:19:50 -0500: > On 18-06-25 10:58:26, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2018-06-25 09:38:28 -0500: > > > On 18-06-25 08:59:23, Doug Hellmann wrote: > > > > Excerpts from Matthew Th

Re: [openstack-dev] [Openstack-sigs] [PTG] Updates!

Excerpts from Thierry Carrez's message of 2018-06-25 17:15:44 +0200: > Doug Hellmann wrote: > > Are we planning to have space for goal teams to answer > > implementation questions? > > At previous PTGs the "goal rooms" ended up not being used (or very very > poo

[openstack-dev] [oslo][python3] testing the python3-first goal steps with oslo libraries

We have already started some of the work to move Oslo to python3-first, and I would like to work through the remaining steps as a way of testing the goal documentation. Please take a look at the documentation [1] and let me know if you have any concerns or questions about us doing that. Thanks,

Re: [openstack-dev] [all][requirements] we need to talk about eventlet

Excerpts from Matthew Thode's message of 2018-06-25 09:38:28 -0500: > On 18-06-25 08:59:23, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2018-06-24 02:42:23 -0500: > > > The short of it is that we are currently using eventlet 0.20.0. The bot > > >

[openstack-dev] [tc] Technical Committee update for 25 June

This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at:

Re: [openstack-dev] [Openstack-sigs] [PTG] Updates!

Are we planning to have space for goal teams to answer implementation questions? Doug Excerpts from Kendall Nelson's message of 2018-06-20 11:24:38 -0700: > Hello Everyone! > > Wanted to give you some updates on PTG4 planning. We have finalized the > list of SIGs/ Groups/WGs/Teams that are

Re: [openstack-dev] [all][requirements] we need to talk about eventlet

Excerpts from Matthew Thode's message of 2018-06-24 02:42:23 -0500: > The short of it is that we are currently using eventlet 0.20.0. The bot > proposes 0.22.1 which fails updates, I think we need to start bugging > projects that fail the cross test jobs. What do you think? > By "bugging" do

Re: [openstack-dev] [Release-job-failures][release][horizon] Release of openstack/xstatic-angular-material failed

Excerpts from zuul's message of 2018-06-25 12:14:34 +: > Build failed. > > - xstatic-check-version > http://logs.openstack.org/59/592a9d4c90f37cd33c6f861120f41ac8a67d909b/release/xstatic-check-version/a501dba/ > : FAILURE in 1m 31s > - release-openstack-python release-openstack-python :

Re: [openstack-dev] [heat] Need new release of heat-translator library

Excerpts from Tung Doan's message of 2018-06-21 00:35:38 +0200: > I agree with Bobh. Considering both Heat Translator and Tosca Parser under > the management of Tacker could affect other projects. We have recently > announced OpenStack Apmec [1] (MEC Orchestration Service) which > consumed these

Re: [openstack-dev] [heat] Need new release of heat-translator library

Excerpts from Zane Bitter's message of 2018-06-20 12:07:49 -0400: > On 20/06/18 11:40, Rico Lin wrote: > > I send a release patch now https://review.openstack.org/#/c/576895/ > > Also, add Bob Haddleton to this ML who is considering as PTL for > > heat-translator team > > Is it time to consider

Re: [openstack-dev] [oslo][osc][cliff][tacker] New release of cmd2 break cliff and tacker client

Excerpts from super user's message of 2018-06-20 15:49:25 +0900: > Hi everyone, > > New release of cmd2 0.9.0 seems to break cliff and python-tackerclient. > > The cmd2 library changed the way it handles parsing input commands. It now > uses a different library, which means the values passed to

<    1   2   3   4   5   6   7   8   9   10   >