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

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-dsvm-neutron-src-oslo.log-ubuntu-xenial-newton, gate-tempest-dsvm-neutron-src-oslo.log-ubuntu-xenial-ocata, and

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

Excerpts from Clark Boylan's message of 2017-04-19 08:10:43 -0700: > On Wed, Apr 19, 2017, at 05:54 AM, Julien Danjou wrote: > > Hoy, > > > > So Gnocchi gate is all broken (agan) because it depends on "pbr" and > > some new release of oslo.* depends on pbr!=2.1.0. > > > > Neither Gnocchi nor

Re: [openstack-dev] [tripleo][release] release-model of tripleo-common

Excerpts from Steve Baker's message of 2017-04-19 13:05:37 +1200: > Other than being consumed as a library, tripleo-common is the home for a > number of tripleo related files, image building templates, heat plugins, > mistral workbooks. > > I have a python-tripleoclient[1] change which is failing

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

Excerpts from Michał Jastrzębski's message of 2017-04-18 13:37:30 -0700: > On 18 April 2017 at 12:41, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Steve Baker's message of 2017-04-18 10:46:43 +1200: > >> On Tue, Apr 18, 2017 at 9:57 AM, Doug Hellman

Re: [openstack-dev] [tc][elections]questions about one platform vision

Excerpts from Adam Lawson's message of 2017-04-18 10:33:32 -0700: > My personal feeling: > > We need to be very very careful. While I really respect Jay Pipes and his > commentary, I fundamentally disagree with his toolbox mindset. OpenStack is > one tool in the Enterprise toolbox. It isn't a

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

Excerpts from Steve Baker's message of 2017-04-18 10:46:43 +1200: > On Tue, Apr 18, 2017 at 9:57 AM, Doug Hellmann <d...@doughellmann.com> > wrote: > > > Excerpts from Michał Jastrzębski's message of 2017-04-12 15:59:34 -0700: > > > My dear Kollegues, > > >

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

Excerpts from Michał Jastrzębski's message of 2017-04-12 15:59:34 -0700: > My dear Kollegues, > > Today we had discussion about how to properly name/tag images being > pushed to dockerhub. That moved towards general discussion on revision > mgmt. > > Problem we're trying to solve is this: > If

Re: [openstack-dev] [tc] version document for project navigator

Excerpts from Thierry Carrez's message of 2017-04-13 18:03:41 +0200: > Monty Taylor wrote: > > On 04/13/2017 08:28 AM, Jimmy McArthur wrote: > >> Just checking on the progress of this. :) > > > > Unfortunately a good portion of the TC was away this week at the > > leadership training so getting a

Re: [openstack-dev] [tc][elections]questions about one platform vision

Excerpts from joehuang's message of 2017-04-13 00:47:53 +: > Interesting to know the idea considering OpenStack as group of > constellations. Does it mean even > Nova/Cinder/Neutron are not necessary to be tied together in some user cases? To me, the important aspect of calling OpenStack

Re: [openstack-dev] [Release-job-failures][telemetry][gnocchi] Release of openstack/python-gnocchiclient failed

, or 2. use openstack/releases to start the release (taking full advantage of the automation), or 3. remove references to the deliverables from openstack/releases so we do not have incomplete information there Doug > > [1] https://review.openstack.org/#/c/447438/ > > On Wed, Apr 12,

Re: [openstack-dev] [Release-job-failures][tricircle] Release of openstack/python-tricircleclient failed

Tricircle team, The client library release 0.1.0 had a build failure that left the release artifacts in an indeterminate state. I have retagged the same commit as 0.1.1 and am processing the new release right now. I will monitor the jobs to ensure they all succeed, or that we address any

Re: [openstack-dev] [Release-job-failures][telemetry][gnocchi] Release of openstack/python-gnocchiclient failed

Excerpts from Doug Hellmann's message of 2017-04-12 13:49:54 -0400: > Gnocchi team, > > The client release you tagged had a build failure. It looks like > the tag was pushed directly, so I will relay the results of the > debugging work but let you decide how to deal with it. > > Clark

Re: [openstack-dev] [Release-job-failures][telemetry][gnocchi] Release of openstack/python-gnocchiclient failed

Gnocchi team, The client release you tagged had a build failure. It looks like the tag was pushed directly, so I will relay the results of the debugging work but let you decide how to deal with it. Clark determined that the files on PyPI do not exactly match the files on our tarballs server.

Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

Excerpts from Monty Taylor's message of 2017-04-12 08:14:31 -0500: > Hey all, > > As I'm sure you all know, pbr is both our most pervasively used > dependency and our least well understood. Nobody ever wants to look at > the code (sorry, I can write ugly code sometimes - but also wow >

[openstack-dev] [release] pausing releases due to pypi upload issues

Earlier today several of the release jobs failed when uploading artifacts to PyPI. We're going to hold off tagging any other releases until we've confirmed that the problem is resolved. Doug __ OpenStack Development Mailing

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

Excerpts from Dulko, Michal's message of 2017-04-12 12:09:30 +: > On Wed, 2017-04-12 at 06:57 -0500, Monty Taylor wrote: > > On 04/06/2017 07:34 AM, Monty Taylor wrote: > > > > > > Hey all! > > > > > > I've started the R Release Name poll and currently am submitting > > > everyone's email

Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

Excerpts from Akihiro Motoki's message of 2017-04-11 00:09:10 +0900: > Hi neutrinos (and horizoners), > > As the title says, where would we like to have horizon dashboard for > neutron stadium projects? > There are several projects under neutron stadium and they are trying > to add dashboard

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Emilien Macchi's message of 2017-04-07 11:16:34 -0400: > I've resurrected an old spec: https://review.openstack.org/#/c/243114/ > - addressed some comments and put TODOs that Doug and I will work > together. > The target is set to Queens but we might provide some proof-of-concept >

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Emilien Macchi's message of 2017-04-06 18:17:59 -0400: > On Wed, Mar 22, 2017 at 11:23 AM, Flavio Percoco <fla...@redhat.com> wrote: > > On 15/03/17 15:40 -0400, Doug Hellmann wrote: > >> > >> Excerpts from Monty Taylor's message of 2017-03-15 04:

Re: [openstack-dev] [ironic] Translations removal

Excerpts from Jim Rollenhagen's message of 2017-03-30 15:08:13 -0400: > On Thu, Mar 30, 2017 at 2:36 PM, Doug Hellmann <d...@doughellmann.com> > wrote: > > > Excerpts from Sean McGinnis's message of 2017-03-22 10:44:05 -0500: > > > On Wed, Mar 22, 2017 at 08:42:42AM

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Paul Belanger's message of 2017-03-22 09:58:46 -0400: > On Tue, Mar 21, 2017 at 05:53:35PM -0600, Alex Schultz wrote: > > On Tue, Mar 21, 2017 at 5:35 PM, John Dickinson wrote: > > > > > > > > > On 21 Mar 2017, at 15:34, Alex Schultz wrote: > > > > > >> On Tue, Mar 21,

Re: [openstack-dev] [ironic] Translations removal

Excerpts from Sean McGinnis's message of 2017-03-22 10:44:05 -0500: > On Wed, Mar 22, 2017 at 08:42:42AM -0500, Kevin L. Mitchell wrote: > > On Tue, 2017-03-21 at 22:10 +, Taryma, Joanna wrote: > > > However, pep8 does not accept passing variable to translation > > > functions, so this

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

> On Mar 16, 2017, at 5:00 PM, Matt Riedemann <mriede...@gmail.com> wrote: > > On 3/16/2017 2:00 PM, Doug Hellmann wrote: >> >> Based on the feedback on that list, there seems to be no real support >> for maintaining the ability to translate log messages. I

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

Excerpts from Doug Hellmann's message of 2017-03-10 09:39:29 -0500: > Excerpts from Doug Hellmann's message of 2017-03-10 09:28:52 -0500: > > Excerpts from Ian Y. Choi's message of 2017-03-10 01:22:40 +0900: > > > Doug Hellmann wrote on 3/9/2017 9:24 PM: > > > >

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Monty Taylor's message of 2017-03-15 04:36:24 +0100: > On 03/14/2017 06:04 PM, Davanum Srinivas wrote: > > Team, > > > > So one more thing popped up again on IRC: > > https://etherpad.openstack.org/p/oslo.config_etcd_backend > > > > What do you think? interested in this work? > >

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Thomas Herve's message of 2017-03-15 09:41:16 +0100: > On Wed, Mar 15, 2017 at 12:05 AM, Joshua Harlow wrote: > > > * How does reloading work (does it)? > > No. There is nothing that we can do in oslo that will make services > magically reload configuration.

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

Excerpts from Mike Bayer's message of 2017-03-15 12:39:48 -0400: > > On 03/15/2017 11:42 AM, Sean Dague wrote: > > Perhaps, but in doing so oslo.db is going to get the pin and uc from > > stable/ocata, which is going to force it back to SQLA < 1.1, which will > > prevent oslo.db changes that

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

Excerpts from Doug Hellmann's message of 2017-03-14 19:20:08 -0400: > Excerpts from Clint Byrum's message of 2017-03-13 13:49:22 -0700: > > Excerpts from Doug Hellmann's message of 2017-03-13 15:12:42 -0400: > > > Excerpts from Farr, Kaitlin M.'s message of 2017-03-13 18:55:18 +: > > > >

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

Excerpts from Farr, Kaitlin M.'s message of 2017-03-13 18:55:18 +: > Proposed library name: Rename Castellan to oslo.keymanager > > Proposed library mission/motivation: Castellan's goal is to provide a > generic key manager interface that projects can use for their key > manager needs, e.g.,

Re: [openstack-dev] [puppet][tripleo][release] puppet module versioning

Excerpts from Thierry Carrez's message of 2017-03-13 15:19:40 +0100: > Doug Hellmann wrote: > > Excerpts from Alex Schultz's message of 2017-03-09 11:29:28 -0700: > >> On Thu, Mar 9, 2017 at 10:54 AM, Doug Hellmann <d...@doughellmann.com> > >> wrote: > >

Re: [openstack-dev] [TripleO][release][deployment] Packaging problems due to branch/release ordering

Excerpts from Thierry Carrez's message of 2017-03-13 15:13:18 +0100: > Jeremy Stanley wrote: > > On 2017-03-09 12:12:01 +0100 (+0100), Alan Pevec wrote: > >> 2017-03-09 10:41 GMT+01:00 Alfredo Moralejo Alonso : > >>> On Wed, Mar 8, 2017 at 12:44 PM, Steven Hardy

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

Excerpts from Doug Hellmann's message of 2017-03-10 09:28:52 -0500: > Excerpts from Ian Y. Choi's message of 2017-03-10 01:22:40 +0900: > > Doug Hellmann wrote on 3/9/2017 9:24 PM: > > > Excerpts from Sean McGinnis's message of 2017-03-07 07:17:09 -0600: > > >> On M

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

Excerpts from Ian Y. Choi's message of 2017-03-10 01:22:40 +0900: > Doug Hellmann wrote on 3/9/2017 9:24 PM: > > Excerpts from Sean McGinnis's message of 2017-03-07 07:17:09 -0600: > >> On Mon, Mar 06, 2017 at 09:06:18AM -0500, Sean Dague wrote: > >>> On 03/06/2017

Re: [openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

Excerpts from Ghanshyam Mann's message of 2017-03-10 10:55:25 +0900: > On Fri, Mar 10, 2017 at 7:23 AM, Lance Bragstad <lbrags...@gmail.com> wrote: > > > > > > > On Thu, Mar 9, 2017 at 3:46 PM, Doug Hellmann <d...@doughellmann.com> > > wrote: > &

Re: [openstack-dev] [puppet][tripleo][release] puppet module versioning

Excerpts from Alex Schultz's message of 2017-03-09 11:29:28 -0700: > On Thu, Mar 9, 2017 at 10:54 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Alex Schultz's message of 2017-03-07 12:56:17 -0700: > >> Ahoy folks, > >> > >> I would l

Re: [openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

Excerpts from Andrea Frittoli's message of 2017-03-09 20:53:54 +: > Hi folks, > > I'm trying to figure out what's the best approach to fade out testing of > deprecated API versions. > We currently host in Tempest API tests for Glance API v1, Keystone API v2 > and Cinder API v1. > > According

Re: [openstack-dev] [puppet][tripleo][release] puppet module versioning

Excerpts from Alex Schultz's message of 2017-03-07 12:56:17 -0700: > Ahoy folks, > > I would like to bring attention to deriving version numbers for puppet > modules (for packaging) as part of the release process. Today we > uncovered an issue[0] in the way that version numbers were being >

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

Excerpts from Sean McGinnis's message of 2017-03-07 07:17:09 -0600: > On Mon, Mar 06, 2017 at 09:06:18AM -0500, Sean Dague wrote: > > On 03/06/2017 08:43 AM, Andreas Jaeger wrote: > > > On 2017-03-06 14:03, Sean Dague wrote: > > >> I'm trying to understand the implications of > > >>

Re: [openstack-dev] [Neutron] ImportError: No module named neutron_lib

Excerpts from Sam's message of 2017-03-09 14:33:11 +0800: > Sorry, it's oslo_db, I'm wrong The "Drop our use of namespace packages" spec explains why. http://specs.openstack.org/openstack/oslo-specs/specs/kilo/drop-namespace-packages.html Doug > > 2017-03-09 14:22 GMT+08:00 Sam

Re: [openstack-dev] [release][tripleo][fuel][kolla][ansible] Ocata Release countdown for R+2 Week, 6-10 March

ang.lei@gmail.com> > wrote: > > > Sorry for late. But Kolla project need a new release candidate. I will > > push it today. > > > > On Tue, Mar 7, 2017 at 6:27 AM, Doug Hellmann <d...@doughellmann.com> > > wrote: > > > >> Excerpts from

Re: [openstack-dev] [cross-project][nova][cinder][designate][neutron] Common support-matrix.py

On Mon, Mar 6, 2017, at 08:42 PM, Sean Dague wrote: > On 03/06/2017 06:27 PM, Mike Perez wrote: > > On 15:55 Mar 02, Morales, Victor wrote: > >> I got this link[11] from Ankur, apparently Nova and Neutron has already > >> started a common effort > >> > >> [11]

Re: [openstack-dev] [release][tripleo][fuel][kolla][ansible] Ocata Release countdown for R+2 Week, 6-10 March

Excerpts from Doug Hellmann's message of 2017-03-06 11:00:15 -0500: > Excerpts from Doug Hellmann's message of 2017-03-02 18:24:12 -0500: > > > > Release Tasks > > - > > > > Liaisons for cycle-trailing projects should prepare their final > > release candidate tags by Monday 6 March.

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

Excerpts from Matt Riedemann's message of 2017-03-06 11:37:06 -0600: > On 3/6/2017 10:28 AM, Ian Y. Choi wrote: > > > > +1 and for such discussions including openstack-i...@lists.openstack.org > > mailing list would be also nice :) > > > > On Barcelona Design Summit, there were I18n contributor

Re: [openstack-dev] [release][tripleo][fuel][kolla][ansible] Ocata Release countdown for R+2 Week, 6-10 March

Excerpts from Doug Hellmann's message of 2017-03-02 18:24:12 -0500: > > Release Tasks > - > > Liaisons for cycle-trailing projects should prepare their final > release candidate tags by Monday 6 March. The release team will > prepare a patch showing the final release versions on

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

Excerpts from Sean Dague's message of 2017-03-06 09:06:18 -0500: > On 03/06/2017 08:43 AM, Andreas Jaeger wrote: > > On 2017-03-06 14:03, Sean Dague wrote: > >> I'm trying to understand the implications of > >> https://review.openstack.org/#/c/439500. And the comment in the linked > >> email: >

[openstack-dev] [release] Ocata Release countdown for R+2 Week, 6-10 March

That's right, one more countdown email for Ocata. Focus - The release team will be ready to tag the final releases for all cycle-trailing projects on 8 March. Release Tasks - Liaisons for cycle-trailing projects should prepare their final release candidate tags by Monday 6

Re: [openstack-dev] [requirements][neutron] bot bumping patches off gate queue

Excerpts from Ihar Hrachyshka's message of 2017-03-02 10:18:16 -0800: > Any updates on the problem? It still bumps patches off gate queue, > resetting it and backing off progress for the whole integrated gate. > Is the work followed up somewhere? Any patches to chew? I suspect this is a case

Re: [openstack-dev] [Horizon][stable][requirements] Modifying global-requirements to cap xstatic package versions

Excerpts from Clark Boylan's message of 2017-03-02 10:40:39 -0800: > On Wed, Mar 1, 2017, at 07:10 PM, Richard Jones wrote: > > Hi folks, > > > > We've run into some issues with various folks installing Horizon and > > its dependencies using just requirements.txt which doesn't limit the > >

Re: [openstack-dev] [OpenStack-docs] [docs][release][ptl] Adding docs to the release schedule

Excerpts from Alexandra Settle's message of 2017-03-02 16:25:46 +: > > > On 3/2/17, 4:08 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > Excerpts from Alexandra Settle's message of 2017-03-02 14:29:07 +: > > >

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

Excerpts from Tony Breeds's message of 2017-03-02 19:41:17 +1100: > On Thu, Mar 02, 2017 at 06:24:32PM +1100, Tony Breeds wrote: > > > I know I'm talking to myself . > > Still. > > > A project on $branch without constraints is going to get pbr 2.0.0 and then > > hit > > version conflicts

Re: [openstack-dev] [OpenStack-docs] [docs][release][ptl] Adding docs to the release schedule

Excerpts from Alexandra Settle's message of 2017-03-02 14:29:07 +: > > > From: Anne Gentle > Date: Thursday, March 2, 2017 at 2:16 PM > To: Alexandra Settle > Cc: "OpenStack Development Mailing List (not for usage questions)" >

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

Excerpts from Clint Byrum's message of 2017-03-01 10:03:34 -0800: > Excerpts from Jonathan Bryce's message of 2017-03-01 11:49:38 -0600: > > > > > On Feb 28, 2017, at 4:25 AM, Thierry Carrez wrote: > > > > > > Clint Byrum wrote: > > So, I'll ask more generally: do

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

Excerpts from Doug Hellmann's message of 2017-03-01 14:04:19 -0500: > Excerpts from Andreas Jaeger's message of 2017-03-01 19:50:51 +0100: > > On 2017-03-01 17:13, Doug Hellmann wrote: > > > Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100: > > >

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

Excerpts from Andreas Jaeger's message of 2017-03-01 19:50:51 +0100: > On 2017-03-01 17:13, Doug Hellmann wrote: > > Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100: > >> On 2017-03-01 06:26, Tony Breeds wrote: > >>> Hi All, > >>>

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100: > On 2017-03-01 06:26, Tony Breeds wrote: > > Hi All, > > Earlier today the release team tagged PBR 2.0.0. The reason for the > > major > > version bump is because warnerrors has been removed in favor of > >

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

Excerpts from Sean Dague's message of 2017-03-01 07:57:31 -0500: > On 03/01/2017 12:26 AM, Tony Breeds wrote: > > Hi All, > > Earlier today the release team tagged PBR 2.0.0. The reason for the > > major > > version bump is because warnerrors has been removed in favor of > > warning-is-error

[openstack-dev] [all][release] new version of reno coming soon

As some of you already know, I have been putting off releasing a new version of reno until after the Ocata final release was tagged. Now that Ocata is done and we're all back from the PTG, I've proposed a version 2.1.0 in [1]. As described in the reno release notes [2], this new release changes

Re: [openstack-dev] [oslo] PTG summary

Excerpts from ChangBo Guo's message of 2017-02-25 00:07:21 +0800: > Oslo folks, > > This is summary of oslo PTG schedule during one and half days. You can > check the details in etherpad link: > https://etherpad.openstack.org/p/oslo-ptg-pike > > 1. oslo.messaging: consistent names for general

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

Excerpts from Clint Byrum's message of 2017-02-27 09:35:21 -0800: > Excerpts from Dean Troyer's message of 2017-02-27 09:32:09 -0600: > > On Mon, Feb 27, 2017 at 3:31 AM, Clint Byrum wrote: > > > This is not for users who only want to see some projects. That is a well > > >

Re: [openstack-dev] [oslo] pbr and warnerrors status

Excerpts from Ben Nemec's message of 2017-02-08 10:15:57 -0600: > > On 02/08/2017 09:41 AM, Doug Hellmann wrote: > > Excerpts from Ben Nemec's message of 2017-02-08 09:20:31 -0600: > >> > >> On 02/08/2017 01:53 AM, Andreas Jaeger wrote: > >>>

Re: [openstack-dev] [requirements] Managing project requirements

Excerpts from Andreas Scheuring's message of 2017-02-24 14:09:33 +0100: > Hi, I have a couple of questions in regards of how updates of > requirements are handled and what happens if I release a new version of > a library. I read along the README [1], but a few points are still > unclear to me. >

[openstack-dev] [release][ansible] release job failure for openstack-ansible docs

This looks like an issue with the node (filesystem corruption?) but just in case it's reproducible I'm forwarding the link to the logs. Doug --- Begin forwarded message from jenkins --- From: jenkins To: release-job-failures

[openstack-dev] Ocata stable branches opened

Now that we have completed the Ocata final release, control over the stable/ocata branches have been transitioned to the stable maintenance teams. Patches going into stable/ocata should follow the stable-backport policy (see the Project Team Guide [1] for details), and it is now possible to

Re: [openstack-dev] The end of OpenStack packages in Debian?

Excerpts from Thomas Goirand's message of 2017-02-21 00:50:35 +0100: > On 02/19/2017 08:43 PM, Clint Byrum wrote: > > Excerpts from Thomas Goirand's message of 2017-02-19 00:58:01 +0100: > >> On 02/18/2017 07:59 AM, Clint Byrum wrote: > >>> Indeed, DPMT uses all the worst choices for maintaining

Re: [openstack-dev] [release] please review the Ocata final release tags

Excerpts from Jim Rollenhagen's message of 2017-02-20 14:52:36 -0500: > On Sun, Feb 19, 2017 at 8:54 PM, Doug Hellmann <d...@doughellmann.com> > wrote: > > > Release liaisons and PTLs, > > > > The patch to tag the Ocata final releases for milestone-based > &

Re: [openstack-dev] [release] please review the Ocata final release tags

Excerpts from Doug Hellmann's message of 2017-02-19 20:54:09 -0500: > Release liaisons and PTLs, > > The patch to tag the Ocata final releases for milestone-based > projects is up at [1]. Please check the patch to verify that it > matches your expectations and then sign off with a +1. > >

[openstack-dev] [release] please review the Ocata final release tags

Release liaisons and PTLs, The patch to tag the Ocata final releases for milestone-based projects is up at [1]. Please check the patch to verify that it matches your expectations and then sign off with a +1. Thanks, Doug [1] https://review.openstack.org/#/c/435816/1

Re: [openstack-dev] [release][all] Ocata release candidates frozen

s for an exception. I've approved the new release candidate. Doug > > Eric > > On 2/17/17, 8:08 AM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > >Later today we will be entering the freeze period between the release > >candidates and the final releas

[openstack-dev] [release][magnum][heat][mistral][rally][requirements] late magnum client release

The magnum team has requested a very late release of python-magnumclient [1]. Given that the request is coming 4 weeks after the client release deadline, the release team discussed it carefully and decided we have 3 options: 1. approve the new release and branch from that BEFORE the final

[openstack-dev] [release][all] Ocata release candidates frozen

Later today we will be entering the freeze period between the release candidates and the final release next Wednesday. We have a couple of releases in progress now for senlin and python-magnumclient, but after those are completed we will not be releasing anything until after the PTG. I hope to

[openstack-dev] [release] Release countdown for Ocata Final Release Week, 20-24 Feb

Focus - The release team will tag the final releases for all milestone-based projects on 22 February to coincide with the press release distributed by the Foundation marketing staff. Release Tasks - Liaisons for milestone-based projects should review the set of unreleased

Re: [openstack-dev] [tripleo] tripleo-ui release job failure

Excerpts from Jeremy Stanley's message of 2017-02-16 18:47:48 +: > On 2017-02-16 14:31:01 -0400 (-0400), Honza Pokorny wrote: > > The included logs don't give me much to go on. It fails with a pretty > > generic timeout message. I can't even determine if that happened during > > "npm

[openstack-dev] [tripleo] tripleo-ui release job failure

The job to build the npm package for tripleo-ui has failed. Doug --- Begin forwarded message from jenkins --- From: jenkins To: release-job-failures Date: Thu, 16 Feb 2017 16:51:50 + Subject: [Release-job-failures] Release of

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

at 10:13:51 > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject:  Re: [openstack-dev] [chef] Making the Kitchen Great Again: A > Retrospective on OpenStack & Chef > > > On Feb 16, 2017, at 10:07 AM, Doug He

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Excerpts from Dean Troyer's message of 2017-02-16 08:25:42 -0600: > On Thu, Feb 16, 2017 at 7:54 AM, Ian Cordasco wrote: > > It seems like a lot of people view "developing OpenStack" as more > > attractive than "making it easy to deploy OpenStack" (via the > > deployment

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Excerpts from Sylvain Bauza's message of 2017-02-16 10:55:14 +0100: > > Le 16/02/2017 10:17, Neil Jerram a écrit : > > On Thu, Feb 16, 2017 at 5:26 AM Joshua Harlow > > wrote: > > > > Radical idea, have each project (not libraries)

Re: [openstack-dev] The end of OpenStack packages in Debian?

Excerpts from Paul Belanger's message of 2017-02-15 09:51:22 -0500: > On Wed, Feb 15, 2017 at 01:43:46PM +0100, Thomas Goirand wrote: > > Hi there, > > > > It's been a while since I planed on writing this message. I couldn't > > write it because the situation makes me really sad. At this point,

[openstack-dev] [release][monasca][senlin] unreleased deliverables

We have two deliverables, monasca-ceilometer and senlin-dashboard, that have no releases at all this cycle. The deadline for preparing a release for cycle-with-intermediary projects is tomorrow, 16 Feb. If those deliverables are going to be considered part of the Ocata release, please prepare

[openstack-dev] [release][telemetry][magnum][monasca][cinder][senlin][swift][tacker] missing stable/ocata branches

We have several cycle-with-intermediary deliverables without stable/ocata branches (see below). Please submit the patch to openstack/releases to create the branch as soon as possible. Doug DeliverableTeam Ocata Release Type Model

Re: [openstack-dev] [all][logos] License for new project mascots

Excerpts from Doug Hellmann's message of 2017-02-14 16:34:55 -0500: > Excerpts from Fox, Kevin M's message of 2017-02-14 18:55:51 +: > > Are there hosted images we can link to? > > Maybe we can add the logos to the team pages published through the > governance repo. > > Doug Here's an

Re: [openstack-dev] [all][logos] License for new project mascots

Excerpts from Fox, Kevin M's message of 2017-02-14 18:55:51 +: > Are there hosted images we can link to? Maybe we can add the logos to the team pages published through the governance repo. Doug > > Thanks, > Kevin > > From: Heidi Joy Tretheway

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

Excerpts from Takashi Yamamoto's message of 2017-02-14 07:31:34 +0900: > hi, > > On Tue, Feb 14, 2017 at 1:54 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Takashi Yamamoto's message of 2017-02-06 10:32:10 +0900: > >> On Wed, Feb 1, 2017 at 9:

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

Excerpts from Takashi Yamamoto's message of 2017-02-06 10:32:10 +0900: > On Wed, Feb 1, 2017 at 9:46 AM, Takashi Yamamoto <yamam...@midokura.com> > wrote: > > hi, > > > > On Fri, Jan 27, 2017 at 7:46 AM, Doug Hellmann <d...@doughellmann.com> > > wr

Re: [openstack-dev] [rally][release] How rally release version

Excerpts from Andrey Kurilin's message of 2017-02-13 12:14:31 +0200: > Hi Jeffrey, > > Rally team do not use "releases" repo at all, that is why information at > [2] is outdated. > Our release workflow is making a proper tag and pushing it via Gerrit. I > find it more convenient. Please propose

Re: [openstack-dev] [designate] Status of the project

Excerpts from Jay Pipes's message of 2017-02-09 21:33:03 -0500: > On 02/09/2017 02:19 PM, Hayes, Graham wrote: > > > > Where too now then? > > === > > > > Well, this is where I call out to people who actually use the project - > > don't > > jump ship and use something else

Re: [openstack-dev] [oslo] pbr and warnerrors status

Excerpts from Andreas Jaeger's message of 2017-02-10 13:57:03 +0100: > On 02/08/2017 05:22 PM, Jay Faulkner wrote: > > [...] > > IMO, I’d suggest skipping this and just fixing the broken attribute. > > Projects that are impacted by the change simply need to merge a one-line > > change to set

[openstack-dev] [release] Release countdown for week R-1, 13-17 Feb

Focus - We are in the release candidate phase of the cycle. All project teams should be fixing last minute release-critical bugs and testing the prepared release candidates for their deliverables. Release Tasks - Please land translation patches as quickly as possible so we can

Re: [openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

e goal or if it needs to be handled as a longer term initiative. Doug > > 2017-02-09 3:20 GMT+08:00 Doug Hellmann <d...@doughellmann.com>: > > > Excerpts from Joshua Harlow's message of 2017-02-08 10:01:27 -0800: > > > Doug Hellmann wrote: > > > > Excerpts f

Re: [openstack-dev] [ironic][qa][grenade] Release blocked on grenade job not testing from newton

Excerpts from Sean Dague's message of 2017-02-09 07:51:41 -0500: > On 02/09/2017 07:00 AM, Jim Rollenhagen wrote: > > Hey folks, > > > > Ironic plans to release Ocata this week, once we have a couple small patches > > and a release note cleanup landed. > > > > However, our grenade job is now

Re: [openstack-dev] [release][all] HELP NEEDED: test failures blocking requirements ocata branch and opening of pike

Excerpts from Doug Hellmann's message of 2017-02-08 23:54:06 -0500: > The patch to update the XStatic package versions [1] is blocked by a > patch to remove nova-docker from the requirements project sync list [2], > which is in turn running into issues in the >

[openstack-dev] [release][all] HELP NEEDED: test failures blocking requirements ocata branch and opening of pike

The patch to update the XStatic package versions [1] is blocked by a patch to remove nova-docker from the requirements project sync list [2], which is in turn running into issues in the gate-grenade-dsvm-neutron-multinode-ubuntu-xenial job [3]. We need some folks who understand these tests and

Re: [openstack-dev] [release][all] started branching tools and requirements

Excerpts from Doug Hellmann's message of 2017-02-08 08:29:45 -0500: > We have started the process of branching devstack, grenade, and the > requirements repo. This may introduce some instability into the gate > until we are finished. Please join #openstack-release if you would like > to follow

Re: [openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

Excerpts from Joshua Harlow's message of 2017-02-08 10:01:27 -0800: > Doug Hellmann wrote: > > Excerpts from ChangBo Guo's message of 2017-02-08 10:41:04 +0800: > >> Thanks Doug and amoralej, we should avoid this :(． > >> > >> One more thought about mox3: Is

Re: [openstack-dev] [oslo] pbr and warnerrors status

Excerpts from Ben Nemec's message of 2017-02-08 09:20:31 -0600: > > On 02/08/2017 01:53 AM, Andreas Jaeger wrote: > > On 2017-02-08 00:56, Ian Cordasco wrote: > >> > >> > >> On Feb 7, 2017 5:47 PM, "Joshua Harlow" >> > wrote: > >> > >>

Re: [openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

as that mox3 was already deprecated and all new tests should use mock instead. Converting the existing tests can be non-trivial because of the differences in how the two libraries work, but it would help us move off of mox3. Doug > > 2017-02-07 23:00 GMT+08:00 Doug Hellmann <

[openstack-dev] [release][all] started branching tools and requirements

We have started the process of branching devstack, grenade, and the requirements repo. This may introduce some instability into the gate until we are finished. Please join #openstack-release if you would like to follow along. Doug

[openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

The stable/ocata branch for mox3 was created from 0.19.0 and then 0.20.0 was released from master. Because that repository sees a very low rate of changes, and because the current stable/ocata branch only contained the patch to update the .gitreview file, we decided to recreate the branch to

[openstack-dev] [release] preparing to branch requirements and open pike

We have 4 cycle-with-milestone projects without any release candidates: - cinder - manila - searchlight - zaqar We're waiting to have those candidates tagged before we go ahead with the next step and branch the requirements, devstack, and grenade to let us open the pike development cycle. It

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Excerpts from Octave J. Orgeron's message of 2017-02-03 09:54:53 -0700: > Comments below.. > > On 2/2/2017 6:22 PM, Doug Hellmann wrote: > >> Yes, this is major undertaking and major driver for Oracle to setup a > >> 3rd party CI so that we can automate regre

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Excerpts from Mike Bayer's message of 2017-02-03 09:41:11 -0500: > > On 02/02/2017 05:28 PM, Octave J. Orgeron wrote: > > That refers to the total length of the row. InnoDB has a limit of 65k > > and NDB is limited to 14k. > > > > A simple example would be the volumes table in Cinder where the

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