[openstack-dev] [oslo] proposing Ken Giusti for oslo-core

Ken has been managing oslo.messaging for ages now but his participation in the team has gone far beyond that single library. He regularly attends meetings, including the PTG, and has provided input into several of our team decisions recently. I think it's time we make him a full member of the

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

Excerpts from Robert Collins's message of 2018-03-26 10:46:22 +1300: > On 26 March 2018 at 09:08, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Doug Hellmann's message of 2018-03-25 16:04:11 -0400: > >> A few of the jobs failed because the dependenc

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

Excerpts from Doug Hellmann's message of 2018-03-25 16:04:11 -0400: > A few of the jobs failed because the dependencies were wrong. In a few > cases I was able to figure out what was wrong, but I can use some help > from project teams more familiar with the code bases to debug the > remaining

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

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: > > Excerpts from Doug Hellmann's message of 2018-03-15 07:03:11 -0400: > > > > > > TL;DR > > > - > > > > > > Let's stop copying exact dependency

Re: [openstack-dev] Following the new PTI for document build, broken local builds

Excerpts from Stephen Finucane's message of 2018-03-23 17:25:42 +: > On Fri, 2018-03-23 at 12:23 -0400, Doug Hellmann wrote: > > Excerpts from Monty Taylor's message of 2018-03-23 08:03:22 -0500: > > > On 03/22/2018 05:43 AM, Stephen Finucane wrote: > > > > >

Re: [openstack-dev] Following the new PTI for document build, broken local builds

Excerpts from Monty Taylor's message of 2018-03-23 08:03:22 -0500: > On 03/22/2018 05:43 AM, Stephen Finucane wrote: > > > > That's unfortunate. What we really need is a migration path from the > > 'pbr' way of doing things to something else. I see three possible > > avenues at this point in

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

Excerpts from Doug Hellmann's message of 2018-03-21 16:02:06 -0400: > Excerpts from Doug Hellmann's message of 2018-03-15 07:03:11 -0400: > > > > TL;DR > > - > > > > Let's stop copying exact dependency specifications into all our > > projects to allow them to reflect the actual versions of

Re: [openstack-dev] Adding "not docs" banner to specs website?

Excerpts from Rochelle Grober's message of 2018-03-22 01:05:42 +: > It could be *really* useful if you could include the date (month/year > would be good enough)of the last significant patch (not including > the reformat to Openstackdocstheme). That could give folks a great > stick in the

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

Excerpts from Doug Hellmann's message of 2018-03-15 07:03:11 -0400: > > TL;DR > - > > Let's stop copying exact dependency specifications into all our > projects to allow them to reflect the actual versions of things > they depend on. The constraints system in pip makes this change > safe. We

Re: [openstack-dev] Adding "not docs" banner to specs website?

Excerpts from Jeremy Stanley's message of 2018-03-19 20:17:37 +: > On 2018-03-19 16:09:14 -0400 (-0400), Doug Hellmann wrote: > [...] > > We want them all to use the openstackdocstheme so you could look > > into creating a "subclass" of that one with the ext

Re: [openstack-dev] Adding "not docs" banner to specs website?

Excerpts from Jim Rollenhagen's message of 2018-03-19 19:06:38 +: > On Mon, Mar 19, 2018 at 3:46 PM, Jeremy Stanley wrote: > > > On 2018-03-19 14:57:58 + (+), Jim Rollenhagen wrote: > > [...] > > > What do folks think about a banner at the top of the specs website

Re: [openstack-dev] [ALL][PTLs] Community Goals for Rocky: Toggle the debug option at runtime

> On Mar 16, 2018, at 6:08 PM, Mohammed Naser wrote: > >> On Fri, Mar 16, 2018 at 5:34 PM, Jeremy Stanley wrote: >>> On 2018-03-16 21:22:51 + (+), Jim Rollenhagen wrote: >>> [...] >>> It seems mod_wsgi doesn't want python applications catching

Re: [openstack-dev] [Release-job-failures][neutron][arista] Release of openstack/networking-arista failed

This Arista release is failing because the packaging job can't run "tox -e venv" because neutron is listed in the requirements.txt for the Arista code and in the constraints file. Excerpts from zuul's message of 2018-03-16 19:50:48 +: > Build failed. > > - release-openstack-python >

Re: [openstack-dev] [ALL][PTLs] Community Goals for Rocky: Toggle the debug option at runtime

Excerpts from Jeremy Stanley's message of 2018-03-16 13:43:00 +: > On 2018-03-16 08:34:28 -0500 (-0500), Sean McGinnis wrote: > > On Mar 16, 2018, at 04:02, Jean-Philippe Evrard > > wrote: > > > > > For OpenStack-Ansible, we don't need to do anything for that > > >

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

Excerpts from Matthew Thode's message of 2018-03-15 18:36:50 -0500: > On 18-03-15 19:29:37, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2018-03-15 10:24:10 -0500: > > > On 18-03-15 07:03:11, Doug Hellmann wrote: > &g

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

Excerpts from Matthew Thode's message of 2018-03-15 10:24:10 -0500: > On 18-03-15 07:03:11, Doug Hellmann wrote: > > What I Want to Do > > - > > > > 1. Update the requirements-check test job to change the check for > >an exact matc

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

Excerpts from Jeremy Stanley's message of 2018-03-15 14:28:49 +: > On 2018-03-15 07:03:11 -0400 (-0400), Doug Hellmann wrote: > [...] > > 1. Update the requirements-check test job to change the check for > >an exact match to be a check for compatibility wit

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

Excerpts from Matthew Thode's message of 2018-03-15 10:05:50 -0500: > On 18-03-15 09:45:38, Doug Hellmann wrote: > > Excerpts from Thierry Carrez's message of 2018-03-15 14:34:50 +0100: > > > Doug Hellmann wrote: > > > > [...] > > > > TL;DR > > >

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

Excerpts from Thierry Carrez's message of 2018-03-15 14:34:50 +0100: > Doug Hellmann wrote: > > [...] > > TL;DR > > - > > > > Let's stop copying exact dependency specifications into all our > > projects to allow them to reflect the actual versions of thi

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

Excerpts from Thomas Morin's message of 2018-03-15 10:15:38 +0100: > Hi Doug, > > Doug Hellmann, 2018-03-14 23:42: > > We keep doing lots of infra-related work to make it "easy" to do > > when it comes to > > managing dependencies. There are three ways

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

Back in Barcelona for the Ocata summit I presented a rough outline of a plan for us to change the way we manage dependencies across projects so that we can stop syncing them [1]. We've made some progress, and I think it's time to finish the work so I'm volunteering to take some of it up during

Re: [openstack-dev] [reno] moved to storyboard

ablo_rojo) > > On Wed, Mar 14, 2018 at 7:51 AM Doug Hellmann <d...@doughellmann.com> wrote: > > > The bug tracker for reno has moved to storyboard: > > https://storyboard.openstack.org/#!/project/933 > > > > Doug > > > >

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

Excerpts from Tony Breeds's message of 2018-03-15 11:59:00 +1100: > On Thu, Mar 15, 2018 at 07:16:11AM +0900, Akihiro Motoki wrote: > > The current version of proposed patches which drops tox_install.sh > > works in our CI. Even if we have neutron>=12.0.0 (queens) or > > horizon>=13.0.0 (queens),

Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

Excerpts from Jay S Bryant's message of 2018-03-14 10:38:37 -0500: > > On 3/14/2018 10:04 AM, Petr Kovar wrote: > > On Tue, 13 Mar 2018 18:57:24 -0500 > > Jay S Bryant wrote: > > > >> Amy, > >> > >> The top level page for projects is referenced under documentation from > >>

[openstack-dev] [reno] moved to storyboard

The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933 Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [keystone] [oslo] new unified limit library

Excerpts from Lance Bragstad's message of 2018-03-12 11:45:28 -0500: > I missed the document describing the process for this sort of thing [0]. > So I'm back tracking a bit to go through a more formal process. > > [0] >

Re: [openstack-dev] [oslo] Oslo PTG Summary

I can’t see https://docs.google.com/presentation/d/e/2PACX-1vQpaSSm7Amk9q4sBEAUi_IpyJ4l07qd3t5T_BPZkdLWfYbtSpSmF7obSB1qRGA65wjiiq2Sb7H2ylJo/pub?start=false=false=3000=id.p

Re: [openstack-dev] [cinder] [oslo] cinder.conf generation is broken for my_ip, building non-reproducibly

Excerpts from Thomas Goirand's message of 2018-03-12 09:17:19 +0100: > Hi, > > When inspecting Cinder's (Queens release) cinder.conf, I can see: > > # Warning: Failed to format sample for my_ip > # unhashable type: 'HostAddress' This part sounds like it might be a bug in oslo.config, which does

Re: [openstack-dev] [tc] Technical Committee Status update, March 9th

Excerpts from Thierry Carrez's message of 2018-03-09 11:28:25 +0100: [...] > We started with a retrospective of how we got things done so far with > this membership. Async collaborations worked well, and the weekly > reports were seen as helpful. We should probably try to steer the topic > of

Re: [openstack-dev] [Interop-wg] [QA] [PTG] [Interop] [Designate] [Heat] [TC]: QA PTG Summary- Interop test for adds-on project

Excerpts from Zane Bitter's message of 2018-03-08 15:51:05 -0500: > On 08/03/18 12:57, Doug Hellmann wrote: > > Why would the repos be owned by anyone other than the original project > > team? > > A few reasons I think it makes sense in this instance: > > * Not e

Re: [openstack-dev] Pros and Cons of face-to-face meetings

Excerpts from Jeremy Stanley's message of 2018-03-08 18:34:51 +: > On 2018-03-08 12:16:18 -0600 (-0600), Jay S Bryant wrote: > [...] > > Cinder has been doing this for many years and it has worked > > relatively well. It requires a good remote speaker and it also > > requires the people in the

Re: [openstack-dev] [Interop-wg] [QA] [PTG] [Interop] [Designate] [Heat] [TC]: QA PTG Summary- Interop test for adds-on project

Excerpts from Zane Bitter's message of 2018-03-08 12:45:11 -0500: > On 07/03/18 08:44, Ghanshyam Mann wrote: > > I mean i am all ok with separate plugin which is more easy for QA team > > but ownership to QA is kind of going to same direction(QA team > > maintaining interop ads-on tests) in more

[openstack-dev] [ptl][release] missing queens release notes pages

We have quite a few projects that publish release notes but have not approved the patch to ensure their queens release notes are published properly. Please look for a patch from the proposal bot with the subject "Update reno for stable/queens", fix it if needed, and approve it quickly. Doug

Re: [openstack-dev] [sdk] Cleaning up openstacksdk core team

Excerpts from Monty Taylor's message of 2018-02-26 11:41:18 +: > Hey all, > > A bunch of stuff has changed in SDK recently, and a few of the > historical sdk core folks have also not been around. I'd like to propose > removing the following people from the core team: > >Everett Towes >

Re: [openstack-dev] [ptl][all][python3] collecting current status of python 3 support in projects

Excerpts from Thomas Goirand's message of 2018-02-24 21:56:43 +0100: > On 02/23/2018 12:29 AM, Doug Hellmann wrote: > > I am trying to update the wiki document with the current state of > > support for Python 3 projects as part of preparing for a discussion > > about moving

[openstack-dev] [ptl][all][python3] collecting current status of python 3 support in projects

I am trying to update the wiki document with the current state of support for Python 3 projects as part of preparing for a discussion about moving from "Python 2 first, then 3" to "Python 3 first, then 2" development. I have added the missing libraries and services (at least those managed by the

[openstack-dev] [all][release] "why do I have new tags for old versions?"

The release team is doing some housekeeping work in openstack/releases and in the course of that work we modified the deliverable files for some very old series. Including all the way back to Austin. Because those files changed, the tag-releases job ran. And because, apparently, some of the very

[openstack-dev] [ptl][all][release] published release notes may be out of date

Thomas Bechtold reported some issues with the oslo.config release notes not showing some information. As part of investigating the problem, I discovered that reno's own release notes were not up to date, either. I think the problem is a combination of a (now fixed) reno bug [1] and some unrelated

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

Excerpts from Robert Collins's message of 2018-02-20 22:58:59 +1300: > On 20 February 2018 at 04:39, Andrey Kurilin wrote: > > Can someone explain me the reason for including "tests" module into > > packages? > > Namespacing the tests makes the test ids unique which is

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

we can add a function in oslo.utils. > > On Mon, Feb 19, 2018 at 10:52 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Doug Hellmann's message of 2018-02-19 10:15:34 -0500: > >> Excerpts from Michael Bayer's message of 2018-02-19 10:00:59 -0500: > >

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

IIRC we started doing that so that consumers building their own packages can run the tests for the packages easily. I don't know how many people are doing that, and apparently at least some downstream consumers aren't packaging everything anyway so they couldn't run those tests. Excerpts from

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

Excerpts from Doug Hellmann's message of 2018-02-19 10:15:34 -0500: > Excerpts from Michael Bayer's message of 2018-02-19 10:00:59 -0500: > > Hi list - > > > > Apparently Cinder was misled by my deprecations within the > > oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and > >

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

Excerpts from Michael Bayer's message of 2018-02-19 10:00:59 -0500: > Hi list - > > Apparently Cinder was misled by my deprecations within the > oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and > in https://review.openstack.org/#/c/522290/ the assumption was made > that these

Re: [openstack-dev] [docs] About the convention to use '.' instead of 'source'.

Excerpts from Jeremy Stanley's message of 2018-02-18 16:01:52 +: > On 2018-02-18 03:55:51 -0600 (-0600), Monty Taylor wrote: > [...] > > I'd honestly argue in favor of assuming bash and using 'source' > > because it's more readable. We don't make allowances for alternate > > shells in our

Re: [openstack-dev] [QA][all] Migration of Tempest / Grenade jobs to Zuul v3 native

Excerpts from Andrea Frittoli's message of 2018-02-15 23:31:02 +: > Dear all, > > this is the first or a series of ~regular updates on the migration of > Tempest / Grenade jobs to Zuul v3 native. > > The QA team together with the infra team are working on providing the > OpenStack community

Re: [openstack-dev] [reno] an alternative approach to known issues

Excerpts from Gabriele Cerami's message of 2018-02-08 22:43:56 +: > Hi, > > sometimes it happens, while reviewing a patch, to find an issue that > is not quite a bug, because it doesn't limit functionality, but > may represent a problem in some corner case, or with some possible > future

Re: [openstack-dev] [magnum][release] release-post job for openstack/releases failed

Excerpts from Sean McGinnis's message of 2018-02-08 13:00:52 -0600: > The release job for magnum failed, but luckily it was after tagging and > branching the release. It was not able to get to the point of uploading a > tarball to http://tarballs.openstack.org/magnum/ though. > > The problem the

Re: [openstack-dev] [Release-job-failures][ironic][release] release-post job for openstack/releases failed

Excerpts from zuul's message of 2018-02-06 00:17:48 +: > Build failed. > > - tag-releases > http://logs.openstack.org/c3/c3ae8a1d87084bcee73e96e2f9e2d174ee610ed4/release-post/tag-releases/48a1f5a/ > : TIMED_OUT in 32m 09s > - publish-static publish-static : SKIPPED > After looking at the

Re: [openstack-dev] [Release-job-failures] [i18n][senlin][release] Tag of openstack/python-senlinclient failed

Excerpts from zuul's message of 2018-02-01 17:03:06 +: > Build failed. > > - publish-openstack-releasenotes > http://logs.openstack.org/f8/f84d8220a3df4421c1cfa7ee7b1e551b57c3505d/tag/publish-openstack-releasenotes/49c0e16/ > : POST_FAILURE in 5m 48s > This failure to build the senlin

Re: [openstack-dev] [requirement][cyborg]FFE - pyspdk requirement dependency

Excerpts from We We's message of 2018-01-31 01:54:04 +0800: > > Hi, > > > I have modified and resubmitted pyspdk to the pypi. Please check it. > > > Thx, > > > Helloway Is there a public source repository for the library somewhere? > > > 在 2018年1月30日，下午12:52，We We

Re: [openstack-dev] [release][searchlight] problem with release job configurations

/538321) depend on it. > > Thanks for the detailed information! > > Steve Thanks for hopping on the fix so quickly, Steve. > > On 1/29/18, 6:21 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > Both searchlight-ui has a configuration issue that the re

Re: [openstack-dev] [Release-job-failures][mistral][release][requirements] Pre-release of openstack/mistral-extra failed

Excerpts from Brad P. Crochet's message of 2018-01-30 08:16:52 -0500: > On Mon, Jan 29, 2018 at 8:02 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from zuul's message of 2018-01-30 00:40:13 +: > >> Build failed. > >> > >

Re: [openstack-dev] [Release-job-failures][mistral][release][requirements] Pre-release of openstack/mistral-extra failed

Excerpts from zuul's message of 2018-01-30 00:40:13 +: > Build failed. > > - release-openstack-python > http://logs.openstack.org/53/533a5ee424ebf6937f03d3b1d9d5b52e8ecb/pre-release/release-openstack-python/44f2fd4/ > : FAILURE in 7m 58s > - announce-release announce-release : SKIPPED >

[openstack-dev] [blazar][release] release job configuration issues

Both blazar-dashboard and blazar-nova have configuration issues blocking their release and the release team needs input from the blazar team to resolve the problems. The validation output for blazar-dashboard [2] shows that the repo is being treated as a horizon plugin but it is configured to use

[openstack-dev] [release][searchlight] problem with release job configurations

Both searchlight-ui has a configuration issue that the release team cannot fix by ourselves. We need input from the searchlight team about how to resolve it. As you'll see from [2] the release validation logic is categorizing searchlight-ui as a horizon-plugin. It is then rejecting the release

Re: [openstack-dev] [glance] PTL non-candidacy

Excerpts from Brian Rosmaita's message of 2018-01-29 14:18:18 -0500: > I've been PTL of Glance through some rocky times, but have decided not > to stand for election for the Rocky cycle. My plan is to stick > around, attend to my duties as a glance core contributor, and support > my successor in

Re: [openstack-dev] [release][requirements][horizon] django-openstack-auth retirement

Excerpts from Akihiro Motoki's message of 2018-01-30 00:36:30 +0900: > Hi the release team and the requirements team, > > I would like to have on django-openstack-auth (DOA) retirement. > In the thread of the announce of DOA retirement last week, I was > advised to release a transition package

Re: [openstack-dev] [ALL][requirements] A freeze is coming and you should be prepared

Excerpts from Matthew Thode's message of 2018-01-28 20:47:42 -0600: > On 18-01-27 21:37:53, Matthew Thode wrote: > > On 18-01-26 23:05:11, Matthew Thode wrote: > > > On 18-01-26 00:12:38, Matthew Thode wrote: > > > > On 18-01-24 22:32:27, Matthew Thode wrote: > > > > > On 18-01-24 01:29:47,

Re: [openstack-dev] [blazar][release] we need a new blazar client release

Excerpts from Doug Hellmann's message of 2018-01-26 16:41:23 -0500: > The PyPI service is now validating package metadata more strictly, and > the classifier values for python-blazarclient do not pass the validation > checks. This means the 1.0.0 package we built cannot be uploaded to > PyPI [1].

[openstack-dev] [blazar][release] we need a new blazar client release

The PyPI service is now validating package metadata more strictly, and the classifier values for python-blazarclient do not pass the validation checks. This means the 1.0.0 package we built cannot be uploaded to PyPI [1]. The fix will take several steps. 1. dmsimard has proposed [2] to master to

Re: [openstack-dev] [cliff][osc][barbican][oslo][sdk][all] avoiding option name conflicts with cliff and OSC plugins

Excerpts from Doug Hellmann's message of 2018-01-18 10:15:16 -0500: > We've been working this week to resolve an issue between cliff and > barbicanclient due to a collision in the option namespace [0]. > Barbicanclient was using the -s option, and then cliff's lister > command base class added

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

Excerpts from Matt Riedemann's message of 2018-01-26 10:08:46 -0600: > On 1/26/2018 9:57 AM, Doug Hellmann wrote: > > Ideally we would use the time at the PTG to discuss implementation > > details. > > For something like the mox one, there really are no impl

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

Excerpts from Matt Riedemann's message of 2018-01-26 09:38:18 -0600: > On 1/23/2018 12:40 PM, Chris Dent wrote: > > ## OpenStack-wide Goals > > > > There are four proposed [OpenStack-wide > > goals](https://governance.openstack.org/tc/goals/index.html): > > > > * [Add Cold upgrades > >  

[openstack-dev] [release][ptl][all] extending queens-3 milestone deadlines

This morning during the release team meeting [1] the team agreed that given the issues with CI this week it makes sense to extend the deadlines for the milestone. The queens-3 deadline for projects following the cycle-with-milestones release model is extended to Monday 29 January. The

[openstack-dev] [release][ptl][all] please approve the reno updates for queens

As part of creating branches for projects, the job proposes updates to add a "queens" page to the release notes build. The script prepares a best-effort version of the update, but local variances in the repositories means that doesn't always work. Please take the patches over and fix them, then

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

Excerpts from Saverio Proto's message of 2018-01-24 22:18:39 +0100: > > 3.34.0 is a queens series release, which makes it more likely that more > > other dependencies would need to be updated. Even backporting the > > changes to the Ocata branch and releasing it from there would require > >

Re: [openstack-dev] [openstack-ansible] Limiting pip wheel builds for OpenStack clients

Excerpts from Mooney, Sean K's message of 2018-01-24 20:30:19 +: > > > -Original Message- > > From: Major Hayden [mailto:ma...@mhtx.net] > > Sent: Wednesday, January 24, 2018 8:03 PM > > To: OpenStack Development Mailing List (not for usage questions) > >

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

ata branch and releasing it from there would require updating several other libraries. Are you using packages from Canonical, or are you building them yourself? Doug > > thank you > > Saverio > > On 22.01.18 23:20, Doug Hellmann wrote: > > Excerpts from Saverio Proto's

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

Excerpts from Saverio Proto's message of 2018-01-22 18:45:15 +0100: > Hello Doug, > > in the extra session I see just {"project": "unknown", "version": "unknown"} > > here a full line from nova-api: > > {"thread_name": "MainThread", "extra": {"project": "unknown", "version": > "unknown"},

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

esent for newton, the version you said you are using: http://git.openstack.org/cgit/openstack/oslo.log/tree/oslo_log/formatters.py?h=newton-eol#n153 Have you looked at the "extras" section of the log output? Could you provide some sample log output? Doug > > Saverio > >

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

Excerpts from Doug Hellmann's message of 2018-01-18 15:21:12 -0500: > Excerpts from Graham Hayes's message of 2018-01-18 19:25:02 +: > > > > On 18/01/18 18:52, Doug Hellmann wrote: > > > Excerpts from Graham Hayes's message of 2018-01-18 17:52:39 +: > > >&

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

Excerpts from Graham Hayes's message of 2018-01-18 19:25:02 +: > > On 18/01/18 18:52, Doug Hellmann wrote: > > Excerpts from Graham Hayes's message of 2018-01-18 17:52:39 +: > >> On 18/01/18 16:25, Doug Hellmann wrote: > >>> Excerpts from Graham Hayes

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

Excerpts from Graham Hayes's message of 2018-01-18 17:52:39 +: > On 18/01/18 16:25, Doug Hellmann wrote: > > Excerpts from Graham Hayes's message of 2018-01-18 15:33:12 +: > > > > > > > In the past the QA team agreed to accept trademark-relat

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

Excerpts from Doug Hellmann's message of 2018-01-18 11:45:28 -0500: > Excerpts from Saverio Proto's message of 2018-01-18 14:49:21 +0100: > > Hello all, > > > > well this oslo.log library looks like a core thing that is used by > > multiple projects. I feel scared hearing that bugs opened on that

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

Excerpts from Saverio Proto's message of 2018-01-18 14:49:21 +0100: > Hello all, > > well this oslo.log library looks like a core thing that is used by > multiple projects. I feel scared hearing that bugs opened on that > project are probably just ignored. > > should I reach out to the current

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

Excerpts from Graham Hayes's message of 2018-01-18 15:33:12 +: > I had hoped for more of a discussion on this before I jumped back into > this debate - but it seams to be stalled still, so here it goes. > > I proposed this initially as we were unclear on where the tests should > go - we had

[openstack-dev] [cliff][osc][barbican][oslo][sdk][all] avoiding option name conflicts with cliff and OSC plugins

We've been working this week to resolve an issue between cliff and barbicanclient due to a collision in the option namespace [0]. Barbicanclient was using the -s option, and then cliff's lister command base class added that option as an alias for sort-columns. The first attempt at resolving the

Re: [openstack-dev] [Zuul] requirements-check FAILURE

Excerpts from Matthew Treinish's message of 2018-01-17 17:16:19 -0500: > On Wed, Jan 17, 2018 at 10:01:13PM +, Kwan, Louie wrote: > > Would like to add the following module to openstack.masakari project > > > > https://github.com/pytransitions/transitions > > > > Got the following error with

Re: [openstack-dev] [tc][ptl][goals][storyboard] tracking the rocky goals with storyboard

Excerpts from Doug Hellmann's message of 2018-01-12 15:37:42 -0500: > Since we are discussing goals for the Rocky cycle, I would like to > propose a change to the way we track progress on the goals. > > We've started to see lots and lots of changes to the goal documents, > more than anticipated

Re: [openstack-dev] [tripleo] storyboard evaluation

Excerpts from Jeremy Stanley's message of 2018-01-16 16:29:32 +: > On 2018-01-16 06:55:03 -0800 (-0800), Emilien Macchi wrote: > [...] > > I created a dev instance of storyboard and imported all bugs from > > TripleO so we could have a look at how it would be if we were using > > the tool: >

Re: [openstack-dev] [oslo] not run for PTL

Excerpts from ChangBo Guo's message of 2018-01-16 18:55:26 +0800: > Hi Oslo folks, > > I taken the role of PTL in last 2 cycles, and would like to focus on coding > this cycle. > it's time to let new leader to make oslo better. So I won't be running > for PTL reelection for Rocky cycle.

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

Excerpts from Erno Kuvaja's message of 2018-01-15 12:59:44 +: > I think the worst case scenario is that we scrape together what ever > we can just to have something to say that we test it and not have > consistency nor clear responsibility of who, what and how. > (Unfortunately I think this

Re: [openstack-dev] [pbr] support v_version

Excerpts from Gaetan's message of 2018-01-15 19:29:01 +0100: > > > > > > > I guess it somehow didn't used my build of the pbr package when > > > running in gitlab pipeline. > > > > It sounds like the CE pipeline is not building packages in the same way? > > Or is using an old version of pbr? > > >

Re: [openstack-dev] [pbr] support v_version

Excerpts from Gaetan's message of 2018-01-15 17:29:01 +0100: > First, thanks a lot for your support and your kindness ! Really appreciate > that :) > > > > Do you know where I need to hack PBR to fix it? > > > > So 'pbr' correctly parses the prefixed tags, but it's just the output > > packages

Re: [openstack-dev] [pbr] support v_version

Excerpts from Jeremy Stanley's message of 2018-01-15 14:40:14 +: > On 2018-01-09 10:25:56 +0100 (+0100), Gaetan wrote: > > I have submitted this patch ([1]) that add support for v_version > > in PBR. Basically I can tag v1.0.0 instead of 1.0.0 to release > > 1.0.0. > [...] > > Looks like the

Re: [openstack-dev] [storyboard] need help figuring out how to use auth with storyboard client

Excerpts from Adam Coldrick's message of 2018-01-15 11:26:14 +: > On Fri, 2018-01-12 at 21:30 +, Jeremy Stanley wrote: > > On 2018-01-12 15:57:44 -0500 (-0500), Doug Hellmann wrote: > > > The storyboard client docs mention an "access token" [1] as > >

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

Excerpts from Doug Hellmann's message of 2018-01-08 09:55:26 -0500: > Stephen (sfinucan) has been working on pbr, oslo.config, and > oslo.policy and reviewing several of the other Oslo libraries for > a while now. His reviews are always helpful and I think he would > make a good addition to the

[openstack-dev] [storyboard] need help figuring out how to use auth with storyboard client

The storyboard client docs mention an "access token" [1] as something a client needs in order to create stories and make other sorts of changes. They don't explain what that token is or how to get one, though. Where do I get a token? How long does the token work? Can I safely put a token in a

[openstack-dev] [tc][ptl][goals][storyboard] tracking the rocky goals with storyboard

Since we are discussing goals for the Rocky cycle, I would like to propose a change to the way we track progress on the goals. We've started to see lots and lots of changes to the goal documents, more than anticipated when we designed the system originally. That leads to code review churn within

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

Excerpts from Saverio Proto's message of 2018-01-12 09:17:55 +0100: > > Which service's logs are missing the request_id? > > > If I look at neutron-server logs with my current setup I get two files: > > neutron-server.log > neutron-server.json > > the standard log file has in all neutron.wsgi

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

Excerpts from Luigi Toscano's message of 2018-01-12 10:49:55 +0100: > On Thursday, 11 January 2018 23:52:00 CET Matt Riedemann wrote: > > On 1/11/2018 10:36 AM, Colleen Murphy wrote: > > > 1) All trademark-related tests should go in the tempest repo, in > > > accordance > > > > > > with the

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

Excerpts from Saverio Proto's message of 2018-01-11 15:23:46 +0100: > Hello, > > we recently enabled the JSON logging to feed a Kibana dashboard and look > at the logs with modern tooling. > > however it looks like in our Openstack Newton deployment that some > information in the JSON files is

Re: [openstack-dev] [ceilometer] Retiring ceilometerclient

Excerpts from Monty Taylor's message of 2018-01-10 18:08:52 -0600: > On 01/10/2018 05:44 PM, Doug Hellmann wrote: > > Excerpts from Monty Taylor's message of 2018-01-10 17:40:28 -0600: > >> On 01/10/2018 04:10 PM, Jon Schlueter wrote: > >>> On Thu, Nov 23, 20

Re: [openstack-dev] [ceilometer] Retiring ceilometerclient

Excerpts from Monty Taylor's message of 2018-01-10 17:40:28 -0600: > On 01/10/2018 04:10 PM, Jon Schlueter wrote: > > On Thu, Nov 23, 2017 at 4:12 PM, gordon chung wrote: > >> > >> > >> > >> On 2017-11-22 04:18 AM, Julien Danjou wrote: > >>> Hi, > >>> > >>> Now that the Ceilometer

Re: [openstack-dev] [ceilometer] Retiring ceilometerclient

Excerpts from gordon chung's message of 2018-01-10 23:28:05 +: > > On 2018-01-10 05:10 PM, Jon Schlueter wrote: > > I would think that a discussion around retiring a project should also > > include at least enumerating > > which projects are currently consuming it [5]. That way a little bit

Re: [openstack-dev] [Release-job-failures][release][nova][infra] Release of openstack/nova failed

Excerpts from zuul's message of 2018-01-10 01:38:45 +: > Build failed. > > - release-openstack-python-without-pypi > http://logs.openstack.org/d6/d6ce901fe280004edbe2f27d8af374ff905161d6/release/release-openstack-python-without-pypi/10069b4/ > : FAILURE in 4m 23s > - announce-release

Re: [openstack-dev] [oslo][oslo.log]Re: Error will be occurred if watch_log_file option is true

Excerpts from Rikimaru Honjo's message of 2018-01-09 18:11:09 +0900: > Hello, > > On 2018/01/04 23:12, Doug Hellmann wrote: > > Excerpts from Rikimaru Honjo's message of 2018-01-04 18:22:26 +0900: > >> Hello, > >> > >> The below bug was reported in Masaka

Re: [openstack-dev] [infra][requirements][cinder] Handling requirements for driverfixes branches

Excerpts from Eric Harney's message of 2018-01-08 14:05:35 -0500: > Hi all, > > I'm trying to sort out how to run unit tests on Cinder driverfixes branches. > > These branches are similar to stable branches, but live longer (and have > a different set of rules for what changes are appropriate).

Re: [openstack-dev] [reno] questions about reno

Excerpts from Gaetan's message of 2018-01-08 17:59:55 +0100: > Hello > > Thanks for your answers! > > - unreleased notes appear in release note with a title such as "0.1.0-2". > > > Is it possible to not have any title or use "0.1.0-dev2" pattern like > > pbr ? > > > > I'm not sure why it

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

Excerpts from Doug Hellmann's message of 2018-01-08 09:55:26 -0500: > Stephen (sfinucan) has been working on pbr, oslo.config, and Oops, that's stephenfin. Sorry for the confusion. Doug __ OpenStack Development Mailing List

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