Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Flavio Percoco's message of 2017-06-08 18:27:51 +0200: > On 08/06/17 18:23 +0200, Flavio Percoco wrote: > >On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: > >>On 06.06.2017 18:08, Emilien Macchi wrote: > >>>Another benefit is that confd will generate a configuration file when >

Re: [openstack-dev] [Openstack-operators] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Emilien Macchi's message of 2017-06-07 16:42:13 +0200: > On Wed, Jun 7, 2017 at 3:31 PM, Doug Hellmann <d...@doughellmann.com> wrote: >> >> On Jun 7, 2017, at 7:20 AM, Emilien Macchi <emil...@redhat.com> wrote: >> >> On Tue, Jun 6

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

> On Jun 7, 2017, at 7:20 AM, Emilien Macchi wrote: > > On Tue, Jun 6, 2017 at 6:08 PM, Emilien Macchi > wrote: >> Following-up the session that we had in Boston: >>

[openstack-dev] [reno] we need help reviewing patches to reno

I am looking for one or two people interested in learning about how reno works to help with reviews. If you like graph traversal algorithms and/or text processing, have a look at the code in the openstack/reno repository and let me know if you're interested in helping out. Doug

[openstack-dev] [release][infra][python3] how to handle release tools for python 3

As we discussed in the team meeting today, I have filed reviews to add a Python 3.5 unit test job to the release-tools repository: https://review.openstack.org/470350 update semver module for python 3.5 https://review.openstack.org/470352 add python 3.5 unit test job for release-tools

Re: [openstack-dev] [qa][tc][all] Tempest to reject trademark tests

Excerpts from Matthew Treinish's message of 2017-06-01 20:51:24 -0400: > On Thu, Jun 01, 2017 at 11:57:00AM -0400, Doug Hellmann wrote: > > Excerpts from Thierry Carrez's message of 2017-06-01 11:51:50 +0200: > > > Graham Hayes wrote: > > > > On 01/06/17 01:30, Matthe

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

Excerpts from jenkins's message of 2017-05-31 20:26:33 +: > Build failed. > > - puppet-nova-releasenotes > http://logs.openstack.org/d9/d913ccd1ea88f3661c32b0fcfdac58d749cd4eb2/tag/puppet-nova-releasenotes/cefa30a/ > : FAILURE in 2m 13s > This failure only prevented the release notes from

Re: [openstack-dev] [swift][release][Release-job-failures] Tag of openstack/swift failed

Excerpts from jenkins's message of 2017-05-31 22:46:21 +: > Build failed. > > - swift-releasenotes > http://logs.openstack.org/e9/e9032fbea361df790901022740ac837a2a02daa0/tag/swift-releasenotes/687d120/ > : FAILURE in 1m 47s > This failure was just with publishing the release notes after

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

Excerpts from Chris Dent's message of 2017-06-01 11:09:56 +0100: > On Wed, 31 May 2017, Doug Hellmann wrote: > > Yeah, it sounds like the current organization of the repo is not > > ideal in terms of equal playing field for all of our project teams. > > I would be fine wi

Re: [openstack-dev] [qa][tc][all] Tempest to reject trademark tests

Excerpts from Thierry Carrez's message of 2017-06-01 11:51:50 +0200: > Graham Hayes wrote: > > On 01/06/17 01:30, Matthew Treinish wrote: > >> TBH, it's a bit premature to have the discussion. These additional > >> programs do > >> not exist yet, and there is a governance road block around this.

Re: [openstack-dev] [tc][ptl][all] Potential Queens Goal: Continuing Python 3.5+ Support

Excerpts from Emilien Macchi's message of 2017-06-01 15:31:10 +0200: > On Wed, May 31, 2017 at 10:38 PM, Mike wrote: > > Hello everyone, > > > > For this thread we will be discussing continuing Python 3.5+ support. > > Emilien who has been helping with coordinating our efforts

Re: [openstack-dev] [requirements] Do we care about pypy for clients (broken by cryptography)

Excerpts from Monty Taylor's message of 2017-05-31 07:34:03 -0500: > On 05/31/2017 06:39 AM, Sean McGinnis wrote: > > On Wed, May 31, 2017 at 06:37:02AM -0500, Sean McGinnis wrote: > >> We had a discussion a few months back around what to do for cryptography > >> since pycrypto is basically dead

Re: [openstack-dev] [qa] [tc] [all] more tempest plugins (was Re: [tc] [all] TC Report 22)

Excerpts from Chris Dent's message of 2017-05-31 11:22:50 +0100: > On Wed, 31 May 2017, Graham Hayes wrote: > > On 30/05/17 19:09, Doug Hellmann wrote: > >> Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100: > >>> Note that this goal only applies

[openstack-dev] [tc][kolla][stable][security][infra][all] guidelines for managing releases of binary artifacts

Based on two other recent threads [1][2] and some discussions on IRC, I have written up some guidelines [3] that try to address the concerns I have with us publishing binary artifacts while still allowing the kolla team and others to move ahead with the work they are trying to do. I would

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Excerpts from Matthew Thode's message of 2017-05-30 16:11:41 -0500: > On 05/30/2017 04:08 PM, Emilien Macchi wrote: > > On Tue, May 30, 2017 at 8:36 PM, Matthew Thode > > wrote: > >> We have a problem in requirements that projects that don't have the > >>

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Excerpts from Matthew Thode's message of 2017-05-30 13:36:02 -0500: > We have a problem in requirements that projects that don't have the > cycle-with-intermediary release model (most of the cycle-with-milestones > model) don't get integrated with requirements until the cycle is fully > done.

Re: [openstack-dev] [tc] [all] TC Report 22

Excerpts from Chris Dent's message of 2017-05-30 18:16:25 +0100: > > There's no TC meeting this week. Thierry did a second weekly status > report[^1]. There will be a TC meeting next week (Tuesday, 6th June > at 20:00 UTC) with the intention of discussing the proposals about > postgreSQL (of

Re: [openstack-dev] [oslo][all][logging] logging debugging improvement work status

The oslo.log changes to include exception details are in version 3.27.0. Doug Excerpts from ChangBo Guo's message of 2017-05-27 16:22:27 +0800: > Thanks Doug, I will release it on next Monday. > > 2017-05-25 22:15 GMT+08:00 Doug Hellmann <d...@doughellmann.com>: > &g

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

t Akhmerov <renat.akhme...@gmail.com> > wrote: > > > Thanks Doug. We’ll look into this. > > > > @Tuan, is there any roadblocks with the patch you’re working on? [1] > > > > [1] https://review.openstack.org/#/c/455407/ > > > > > > Renat >

[openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

The new work to add the exception information and request ID tracing depends on using both oslo.context and oslo.log to have all of the relevant pieces of information available as log messages are emitted. In the course of reviewing the "done" status for those initiatives, I noticed that although

[openstack-dev] [oslo][all][logging] logging debugging improvement work status

One outcome from the forum session about improving logging debugging was agreement that the proposal to add more details about exceptions to the logs. The spec [1] was updated and has been approved, and the patches to implement the work in oslo.log have also been approved [2]. The changes should

Re: [openstack-dev] [release] Issues with reno

Excerpts from Doug Hellmann's message of 2017-05-23 12:10:56 -0400: > Excerpts from Matt Riedemann's message of 2017-05-22 21:48:37 -0500: > > I think Doug and I have talked about this before, but it came up again > > tonight. > > > > There seems to be an issue where release notes for the

Re: [openstack-dev] [ptg] Strawman Queens PTG week slicing

Excerpts from Thierry Carrez's message of 2017-05-24 16:44:44 +0200: > Doug Hellmann wrote: > > Two questions about theme-based initiatives: > > > > I would like to have a discussion about the work to stop syncing > > requirements and to see if we can make progress on t

Re: [openstack-dev] [ptg] Strawman Queens PTG week slicing

Excerpts from Thierry Carrez's message of 2017-05-24 12:10:17 +0200: > Hi everyone, > > In a previous thread[1] I introduced the idea of moving the PTG from a > purely horizontal/vertical week split to a more > inter-project/intra-project activities split, and the initial comments > were

Re: [openstack-dev] [tc][all] Missing answers on Pike release goals

Excerpts from John Dickinson's message of 2017-05-23 09:12:29 -0700: > > I can sympathize with the "do it tomorrow" turns into 6 weeks later... > > Part of the issue for me, personally, is that a governance patch > does *not* feel simple or lightweight. I assume (in part based on > experience)

Re: [openstack-dev] [release] Issues with reno

Excerpts from Matt Riedemann's message of 2017-05-22 21:48:37 -0500: > I think Doug and I have talked about this before, but it came up again > tonight. > > There seems to be an issue where release notes for the current series > don't show up in the published release notes, but unreleased

Re: [openstack-dev] [release][tc][infra][security][stable] Proposal for shipping binaries and containers

Excerpts from Davanum Srinivas (dims)'s message of 2017-05-23 10:44:30 -0400: > Team, > > Background: > For projects based on Go and Containers we need to ship binaries, for Can you elaborate on the use of the term "need" here. Is that because otherwise the projects can't be consumed? Is it the

Re: [openstack-dev] [tc][all] Missing answers on Pike release goals

Excerpts from Sean McGinnis's message of 2017-05-23 08:58:08 -0500: > > > > > > - Is it that the reporting process is too heavy ? (requiring answers > > > from projects that are obviously unaffected) > > > > I've thought about this, OSC was unaffected by one of the goals but > > not the other, so

Re: [openstack-dev] [tc][all] Missing answers on Pike release goals

Excerpts from Jeremy Stanley's message of 2017-05-23 13:57:53 +: > On 2017-05-23 05:40:05 -0500 (-0500), Dean Troyer wrote: > > On Tue, May 23, 2017 at 4:59 AM, Thierry Carrez > > wrote: > [...] > > > - Is it that the reporting process is too heavy ? (requiring answers

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

Excerpts from Jeremy Stanley's message of 2017-05-22 19:16:34 +: > On 2017-05-22 12:31:49 -0600 (-0600), Alex Schultz wrote: > > On Mon, May 22, 2017 at 10:34 AM, Jeremy Stanley wrote: > > > On 2017-05-22 09:06:26 -0600 (-0600), Alex Schultz wrote: > > > [...] > > >> We ran

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

Excerpts from Anne Gentle's message of 2017-05-22 12:36:29 -0500: > > On May 22, 2017, at 9:09 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > > > Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: > >>> On 05/22/2017 11:39 AM, Alexa

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

Excerpts from Michał Jastrzębski's message of 2017-05-22 10:42:44 -0700: > [snip] > > So from Kolla perspective, since our dev guide is really also > operators guide (we are operators tool so we're kinda "special" on > that front), we'd love to handle both deployment guide, user manuals > and all

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

Excerpts from Dmitry Tantsur's message of 2017-05-22 16:54:30 +0200: > On 05/22/2017 04:09 PM, Doug Hellmann wrote: > > Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: > >> On 05/22/2017 11:39 AM, Alexandra Settle wrote: > >>> Hi everyone, >

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

Excerpts from jenkins's message of 2017-05-22 10:49:09 +: > Build failed. > > - puppet-nova-tarball > http://logs.openstack.org/89/89c58e7958b448364cb0290c1879116f49749a68/release/puppet-nova-tarball/fe9daf7/ > : FAILURE in 55s > - puppet-nova-tarball-signing puppet-nova-tarball-signing :

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

Excerpts from Anne Gentle's message of 2017-05-22 08:08:40 -0500: > On Mon, May 22, 2017 at 4:39 AM, Alexandra Settle > wrote: > > > Hi everyone, > > > > > > > > The documentation team are rapidly losing key contributors and core > > reviewers. We are not alone, this is

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: > On 05/22/2017 11:39 AM, Alexandra Settle wrote: > > Hi everyone, > > > > The documentation team are rapidly losing key contributors and core > > reviewers. > > We are not alone, this is happening across the board. It is

Re: [openstack-dev] [oslo] Can we stop global requirements update?

Excerpts from Mehdi Abaakouk's message of 2017-05-19 10:23:09 +0200: > On Thu, May 18, 2017 at 03:16:20PM -0400, Mike Bayer wrote: > > > > > >On 05/18/2017 02:37 PM, Julien Danjou wrote: > >>On Thu, May 18 2017, Mike Bayer wrote: > >> > >>>I'm not understanding this? do you mean this? > >> > >>In

Re: [openstack-dev] [ptg] ptgbot: how to make "what's currently happening" emerge

Excerpts from Thierry Carrez's message of 2017-05-18 11:57:04 +0200: > Hi again, > > For the PTG events we have, by design, a pretty loose schedule. Each > room is free to organize their agenda in whatever way they see fit, and > take breaks whenever they need. This flexibility is key to keep our

Re: [openstack-dev] [all][keystone][product] api keys/application specific passwords

Excerpts from Adrian Turjak's message of 2017-05-18 13:34:56 +1200: > Fully agree that expecting users of a particular cloud to understand how > the policy stuff works is pointless, but it does fall on the cloud > provider to educate and document their roles and the permissions of > those roles.

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Michał Jastrzębski's message of 2017-05-17 11:36:40 -0700: > On 17 May 2017 at 11:04, Doug Hellmann <d...@doughellmann.com> wrote: > > > You've presented some positive scenarios. Here's a worst case > > situation that I'm worried about. > > > > Sup

Re: [openstack-dev] [tc][swg] Updates on the TC Vision for 2019

Excerpts from Colette Alexander's message of 2017-05-17 14:29:07 -0400: > Hi everyone! > > Just wanted to send the community some updates on the vision front and also > get a discussion with the members of the technical committee going here for > next steps on what we're up to with the TC Vision

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Michał Jastrzębski's message of 2017-05-17 07:47:31 -0700: > On 17 May 2017 at 04:14, Chris Dent wrote: > > On Wed, 17 May 2017, Thierry Carrez wrote: > > > >> Back to container image world, if we refresh those images daily and they > >> are not versioned or

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Thierry Carrez's message of 2017-05-17 12:19:22 +0200: > Sean Dague wrote: > > On 05/16/2017 02:39 PM, Doug Hellmann wrote: > >> Excerpts from Michał Jastrzębski's message of 2017-05-16 09:51:00 -0700: > >>> One thing I struggle with is...well

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Chris Dent's message of 2017-05-17 12:14:40 +0100: > On Wed, 17 May 2017, Thierry Carrez wrote: > > > Back to container image world, if we refresh those images daily and they > > are not versioned or archived (basically you can only use the latest and > > can't really access past

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Michał Jastrzębski's message of 2017-05-16 11:38:19 -0700: > On 16 May 2017 at 11:27, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Michał Jastrzębski's message of 2017-05-16 09:46:19 -0700: > >> So another consideration. Do you think who

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Michał Jastrzębski's message of 2017-05-16 09:51:00 -0700: > On 16 May 2017 at 09:40, Clint Byrum wrote: > > > > What's at stake isn't so much "how do we get the bits to the users" but > > "how do we only get bits to users that they need". If you build and push > >

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Michał Jastrzębski's message of 2017-05-16 08:20:17 -0700: > On 16 May 2017 at 08:12, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Michał Jastrzębski's message of 2017-05-16 06:52:12 -0700: > >> On 16 May 2017 at 06:20, Flavio Percoco &

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Jeremy Stanley's message of 2017-05-16 17:41:28 +: > On 2017-05-16 11:17:31 -0400 (-0400), Doug Hellmann wrote: > > Excerpts from Sam Yaple's message of 2017-05-16 14:11:18 +: > [...] > > > If you build images properly in infra, then y

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Michał Jastrzębski's message of 2017-05-16 09:46:19 -0700: > So another consideration. Do you think whole rule of "not building > binares" should be reconsidered? We are kind of new use case here. We > aren't distro but we are packagers (kind of). I don't think putting us > on equal

[openstack-dev] [all][release] sphinx 1.6.1 behavior changes triggering job failures

We now have 2 separate bugs related to changes in today's Sphinx 1.6.1 release causing our doc jobs to fail in different ways. https://bugs.launchpad.net/pbr/+bug/1691129 describes a traceback produced when building the developer documentation through pbr.

Re: [openstack-dev] [tc][all] Do we need a #openstack-tc IRC channel

Excerpts from Sean McGinnis's message of 2017-05-16 10:17:35 -0500: > On Tue, May 16, 2017 at 09:38:34AM -0400, Davanum Srinivas wrote: > > Folks, > > > > See $TITLE :) > > > > Thanks, > > Dims > > > > My preference would be to have an #openstack-tc channel. > > One thing I like about the

Re: [openstack-dev] [all][keystone][product] api keys/application specific passwords

Excerpts from Chris Dent's message of 2017-05-16 15:16:08 +0100: > On Tue, 16 May 2017, Monty Taylor wrote: > > > FWIW - I'm un-crazy about the term API Key - but I'm gonna just roll with > > that until someone has a better idea. I'm uncrazy about it for two reasons: > > > > a) the word "key"

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Sam Yaple's message of 2017-05-16 14:11:18 +: > I would like to bring up a subject that hasn't really been discussed in > this thread yet, forgive me if I missed an email mentioning this. > > What I personally would like to see is a publishing infrastructure to allow > pushing

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Michał Jastrzębski's message of 2017-05-16 06:52:12 -0700: > On 16 May 2017 at 06:20, Flavio Percoco wrote: > > On 16/05/17 14:08 +0200, Thierry Carrez wrote: > >> > >> Flavio Percoco wrote: > >>> > >>> From a release perspective, as Doug mentioned, we've avoided

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Flavio Percoco's message of 2017-05-16 10:07:52 -0400: > On 16/05/17 09:45 -0400, Doug Hellmann wrote: > >Excerpts from Flavio Percoco's message of 2017-05-15 21:50:23 -0400: > >> On 15/05/17 11:49 -0700, Michał Jastrzębski wrote: > >> >On 15 May 2017 at

Re: [openstack-dev] [nova] [glance] [cinder] [neutron] [keystone] - RFC cross project request id tracking

Excerpts from Chris Dent's message of 2017-05-16 15:28:11 +0100: > On Sun, 14 May 2017, Sean Dague wrote: > > > So, the basic idea is, services will optionally take an inbound > > X-OpenStack-Request-ID which will be strongly validated to the format > > (req-$uuid). They will continue to always

Re: [openstack-dev] [tc][all] Do we need a #openstack-tc IRC channel

Excerpts from Sean Dague's message of 2017-05-16 10:49:54 -0400: > On 05/16/2017 09:38 AM, Davanum Srinivas wrote: > > Folks, > > > > See $TITLE :) > > > > Thanks, > > Dims > > I'd rather avoid #openstack-tc and just use #openstack-dev. > #openstack-dev is pretty low used environment (compared

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Flavio Percoco's message of 2017-05-15 21:50:23 -0400: > On 15/05/17 11:49 -0700, Michał Jastrzębski wrote: > >On 15 May 2017 at 11:19, Davanum Srinivas wrote: > >> Sorry for the top post, Michal, Can you please clarify a couple of things: > >> > >> 1) Can folks

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

nt Mailing List (not for usage > > questions)" <openstack-dev@lists.openstack.org> > > > Date: Monday, May 15, 2017 at 7:00 PM > > > To: "OpenStack Development Mailing List (not for usage questions)" > > <openstack-dev@lists.openstack.org> > &g

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Luigi Toscano's message of 2017-05-16 11:50:53 +0200: > On Monday, 15 May 2017 21:12:16 CEST Doug Hellmann wrote: > > Excerpts from Michał Jastrzębski's message of 2017-05-15 10:52:12 -0700: > > > > > On 15 May 2017 at 10:34, Doug Hellmann <d...@doughellm

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Thierry Carrez's message of 2017-05-16 14:08:07 +0200: > Flavio Percoco wrote: > > From a release perspective, as Doug mentioned, we've avoided releasing > > projects > > in any kind of built form. This was also one of the concerns I raised when > > working on the proposal to

Re: [openstack-dev] [oslo][concurrency] lockutils lock fairness / starvation

Excerpts from Legacy, Allain's message of 2017-05-15 19:20:46 +: > > -Original Message- > > From: Doug Hellmann [mailto:d...@doughellmann.com] > > Sent: Monday, May 15, 2017 2:55 PM > <...> > > > > Excerpts from Legacy, Allain's message of

[openstack-dev] [oslo][logging] improvements to log debugging ready for review

I have updated the Oslo spec for improving the logging debugging [1] and the patch series that begins the implementation [2]. Please put these on your review priority list. Doug [1] https://review.openstack.org/460112 [2] https://review.openstack.org/#/q/topic:improve-logging-debugging

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

require more maintenance work upstream. > On 15 May 2017 at 10:34, Doug Hellmann <d...@doughellmann.com> wrote: > > Last week at the Forum we had a couple of discussions about > > collaboration between the various teams building or consuming > > container images.

Re: [openstack-dev] [oslo][oslo.messaging] Call to deprecate the 'pika' driver in the oslo.messaging project

Excerpts from Davanum Srinivas (dims)'s message of 2017-05-15 14:27:36 -0400: > On Mon, May 15, 2017 at 2:08 PM, Ken Giusti wrote: > > Folks, > > > > It was decided at the oslo.messaging forum at summit that the pika > > driver will be marked as deprecated [1] for removal. > >

Re: [openstack-dev] [oslo][concurrency] lockutils lock fairness / starvation

Excerpts from Legacy, Allain's message of 2017-05-15 18:35:58 +: > Can someone comment on whether the following scenario has been discussed > before or whether this is viewed by the community as a bug? > > While debugging a couple of different issues our investigation has lead > us down the

[openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Last week at the Forum we had a couple of discussions about collaboration between the various teams building or consuming container images. One topic that came up was deciding how to publish images from the various teams to docker hub or other container registries. While the technical bits seem

Re: [openstack-dev] [api][neutron][nova][Openstack-operators][interop] Time for a bikeshed - help me name types of networking

Excerpts from Jay Pipes's message of 2017-05-15 12:40:17 -0400: > On 05/14/2017 01:02 PM, Monty Taylor wrote: > > ** Bikeshed #1 ** > > > > Are "internal" and "external" ok with folks as terms for those two ideas? > > Yup, ++ from me on the above. > > > ** Bikeshed #2 ** > > > > Anybody have a

Re: [openstack-dev] [nova] [glance] [cinder] [neutron] [keystone] [heat] [telemetry] - RFC cross project request id tracking

Excerpts from Zane Bitter's message of 2017-05-15 11:43:07 -0400: > On 15/05/17 10:35, Doug Hellmann wrote: > > Excerpts from Sean Dague's message of 2017-05-15 10:01:20 -0400: > >> On 05/15/2017 09:35 AM, Doug Hellmann wrote: > >>> Excerpts from Sean Dague's messag

Re: [openstack-dev] [nova] [glance] [cinder] [neutron] [keystone] [heat] [telemetry] - RFC cross project request id tracking

Excerpts from Sean Dague's message of 2017-05-15 10:01:20 -0400: > On 05/15/2017 09:35 AM, Doug Hellmann wrote: > > Excerpts from Sean Dague's message of 2017-05-14 07:04:03 -0400: > >> One of the things that came up in a logging Forum session is how much > >> effort

Re: [openstack-dev] [nova] [glance] [cinder] [neutron] [keystone] - RFC cross project request id tracking

Excerpts from Sean Dague's message of 2017-05-14 07:04:03 -0400: > One of the things that came up in a logging Forum session is how much > effort operators are having to put into reconstructing flows for things > like server boot when they go wrong, as every time we jump a service > barrier the

Re: [openstack-dev] [tripleo][logging] oslo.log fluentd native logging

Excerpts from Dan Prince's message of 2017-05-10 17:41:12 -0400: > On Mon, 2017-04-24 at 07:47 -0400, Joe Talerico wrote: > > Hey owls - I have been playing with oslo.log fluentd integration[1] > > in > > a poc commit here [2]. Enabling the native service logging is nice > > and > > tracebacks no

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Excerpts from Jeremy Stanley's message of 2017-05-08 20:18:35 +: > On 2017-05-08 11:24:00 -0600 (-0600), Octave J. Orgeron wrote: > [...] > > none of those products that those drivers are written for are open > > sourced and they meet less resistance to committing code upstream. > > So I have

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Excerpts from Davanum Srinivas (dims)'s message of 2017-05-08 06:12:51 -0400: > On Mon, May 8, 2017 at 3:52 AM, Bogdan Dobrelya <bdobr...@redhat.com> wrote: > > On 06.05.2017 23:06, Doug Hellmann wrote: > >> Excerpts from Thierry Carrez's message of 2017-05-04 16:14:07

Re: [openstack-dev] [tc][all] Should the Technical Committee meetings be dropped?

Excerpts from Flavio Percoco's message of 2017-05-07 09:49:41 -0400: > On 05/05/17 08:45 -0400, Sean Dague wrote: > >On 05/04/2017 01:10 PM, Flavio Percoco wrote: > > > >> Some of the current TC activities depend on the meeting to some extent: > >> > >> * We use the meeting to give the final ack

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Excerpts from Thierry Carrez's message of 2017-05-04 16:14:07 +0200: > Chris Dent wrote: > > On Wed, 3 May 2017, Drew Fisher wrote: > >> "Most large customers move slowly and thus are running older versions, > >> which are EOL upstream sometimes before they even deploy them." > > > > Can someone

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Excerpts from Octave J. Orgeron's message of 2017-05-05 15:35:16 -0600: > Hi Matt, > > And this is actually part of the problem for vendors. Many Oracle > engineers, including myself, have tried to get features and fixes pushed > upstream. While that may sound easy, the reality is that it

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Excerpts from Zane Bitter's message of 2017-05-04 20:09:35 -0400: > On 04/05/17 10:14, Thierry Carrez wrote: > > Chris Dent wrote: > >> On Wed, 3 May 2017, Drew Fisher wrote: > >>> "Most large customers move slowly and thus are running older versions, > >>> which are EOL upstream sometimes before

Re: [openstack-dev] OpenStack moving both too fast and too slow at the same time

Excerpts from Drew Fisher's message of 2017-05-03 14:00:53 -0600: > This email is meant to be the ML discussion of a question I brought up > during the TC meeting on April 25th.; [1] Thanks for starting this thread, Drew. I'll try to respond, but I know a lot of folks are preparing for the summit

Re: [openstack-dev] [devstack] [all] systemd in devstack by default

Excerpts from Sean Dague's message of 2017-05-03 16:16:29 -0400: > Screen is going away in Queens. > > Making the dev / test runtimes as similar as possible is really > important. And there is so much weird debt around trying to make screen > launch things reliably (like random sleeps) because

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

Excerpts from Sean Dague's message of 2017-05-03 13:23:11 -0400: > On 05/03/2017 01:02 PM, Doug Hellmann wrote: > > Excerpts from Thierry Carrez's message of 2017-05-03 18:16:29 +0200: > >> Ed Leafe wrote: > >>> On May 3, 2017, at 2:41 AM, Thierry Carrez

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

Excerpts from Thierry Carrez's message of 2017-05-03 18:16:29 +0200: > Ed Leafe wrote: > > On May 3, 2017, at 2:41 AM, Thierry Carrez wrote: > > > >> In the current > >> system, TC members (or really, anyone in the community) can add to the > >> "Open discussion" section

[openstack-dev] [forum] extra session rooms at the forum

We have a full forum schedule planned, but based on past experience it's inevitable that something was missed, the scheduled slots won't be quite long enough for some deeper discussions, and that new topics will come up during the week. To accommodate those extra discussions, we have 3 session

Re: [openstack-dev] [puppet] Deprecating Postgresql support

Excerpts from Emilien Macchi's message of 2017-04-27 07:38:17 -0400: > Greetings, > > We didn't see anyone using Postgresql when deploying Puppet OpenStack: > - no feedback on ML or IRC > - no bug report in Launchpad > > Postgresql support (or call it how you want) is also removed upstream > in

Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check validation of UUID length

Excerpts from Sean Dague's message of 2017-04-26 10:55:14 -0400: > On 04/26/2017 10:47 AM, Doug Hellmann wrote: > > Excerpts from Sean Dague's message of 2017-04-26 09:01:32 -0400: > >> On 04/26/2017 08:36 AM, Doug Hellmann wrote: > >>> Excerpts from Kekane, Abhishek

Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check validation of UUID length

Excerpts from Sean Dague's message of 2017-04-26 09:01:32 -0400: > On 04/26/2017 08:36 AM, Doug Hellmann wrote: > > Excerpts from Kekane, Abhishek's message of 2017-04-26 07:00:22 +: > >> Hi All, > >> > >> As per suggested by @jay_pipes's > >> if

[openstack-dev] [all] looking for feedback on proposals to improve logging

I am looking for some feedback on two new proposals to add IDs to log messages. The tl;dr is that we’ve been talking about adding unique IDs to log messages for 5 years. I myself am still not 100% convinced the idea is useful, but I would like us to either do it or definitively say we won't ever

Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check validation of UUID length

Excerpts from Kekane, Abhishek's message of 2017-04-26 07:00:22 +: > Hi All, > > As per suggested by @jay_pipes's > if val.count('-') not in (0, 4): > raise TypeError > > It is not sufficient solution because "is_uuid_like" returns only True or > False. > For example, > > If user

Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check validation of UUID length

Excerpts from Jay Pipes's message of 2017-04-24 10:44:47 -0400: > On 04/24/2017 09:45 AM, Jadhav, Pooja wrote: > > Solution 3: > > > > We can check UUID in central place means in "is_uuid_like" method of > > oslo_utils [4]. > > This gets my vote. It's a bug in the is_uuid_like() function, IMHO,

Re: [openstack-dev] [Release-job-failures][mistral] Release of openstack/python-mistralclient failed

A recent patch in python-mistralclient added a release note that was poorly formatted, so it broke announcement job for the 3.1.0 release. I've proposed a fix for the note file in https://review.openstack.org/459341 and I've proposed the project-config changes to add the jobs to avoid allowing

Re: [openstack-dev] [nova][oslo.utils] Bug-1680130 Check validation of UUID length

Excerpts from Jadhav, Pooja's message of 2017-04-24 13:45:07 +: > Hi Devs, > > I want your opinion about bug: https://bugs.launchpad.net/nova/+bug/1680130 > > When user passes incorrect formatted UUID, volume UUID like: > -----(please note double hyphen) for

Re: [openstack-dev] [oslo] do we still need non-voting tests for older releases?

s://review.openstack.org/#/c/448431 > > 2017-04-20 0:42 GMT+08:00 Doug Hellmann <d...@doughellmann.com>: > > > I noticed again today that we have some test jobs running for some > > of the Oslo libraries against old versions of services (e.g., > > gate-tempest

Re: [openstack-dev] [oslo] Can we stop global requirements update?

Excerpts from Joshua Harlow's message of 2017-04-20 22:31:19 -0700: > Doug Hellmann wrote: > > Excerpts from gordon chung's message of 2017-04-20 17:12:26 +: > >> On 20/04/17 01:32 AM, Joshua Harlow wrote: > >>> Wasn't there also some decision made in austin (?)

Re: [openstack-dev] [release][monasca] Release of openstack/monasca-kibana-plugin failed

m/openstack/monasca-kibana- > > plugin/blob/master/package.json, from "0.0.5" to "1.0.1". > > 2. Cherry pick to Ocata. > > 3. Then apply a new release tag for Ocata for 1.0.1 in, > > https://review.openstack.org/#/c/433823/1/deliverables/ocata/

Re: [openstack-dev] [release][monasca] Release of openstack/monasca-kibana-plugin failed

e. Doug > > Regards --Roland > > On 4/20/17, 1:41 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > >Excerpts from Doug Hellmann's message of 2017-04-20 15:26:47 -0400: > >> The version of monasca-kibana-plugin in package.json does not m

Re: [openstack-dev] [release][monasca] Release of openstack/monasca-kibana-plugin failed

Excerpts from Doug Hellmann's message of 2017-04-20 15:26:47 -0400: > The version of monasca-kibana-plugin in package.json does not match the > new tag, and that caused the publish job to fail. I'm available to help > debug or to quickly release an update after the problem is fixed.

[openstack-dev] [release][monasca] Release of openstack/monasca-kibana-plugin failed

The version of monasca-kibana-plugin in package.json does not match the new tag, and that caused the publish job to fail. I'm available to help debug or to quickly release an update after the problem is fixed. Doug --- Begin forwarded message from jenkins --- From: jenkins

Re: [openstack-dev] [oslo] Can we stop global requirements update?

Excerpts from gordon chung's message of 2017-04-20 17:12:26 +: > > On 20/04/17 01:32 AM, Joshua Harlow wrote: > > Wasn't there also some decision made in austin (?) about how we as a > > group stated something along the line of co-installability isn't as > > important as it once was (and may

Re: [openstack-dev] [oslo] Can we stop global requirements update?

'll subscribe to the review and follow along. Doug > > Regards, > Matt > > On Thu, Apr 20, 2017 at 2:34 AM, Doug Hellmann <d...@doughellmann.com> > wrote: > > > Excerpts from Clark Boylan's message of 2017-04-19 08:10:43 -0700: > > > On Wed, Apr 19, 20

Re: [openstack-dev] [release-announce] [oslo] pbr 3.0.0

We've bumped pbr to a new major release. In the past this has triggered issues for projects capping pbr, so please check your requirements list and remove any caps if you have them. Projects following the global-requirements process should also ready be clear of caps. Doug Excerpts from

<    5   6   7   8   9   10   11   12   13   14   >