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

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 oslo-core team. As per our usual practice, please reply here with a +1 or -1

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

Excerpts from Gaetan's message of 2018-01-06 13:33:20 +0100: > Hello > > I played this week with reno and i really like it, but I have a bunch of > question: > - 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"

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

Excerpts from Rikimaru Honjo's message of 2018-01-04 18:22:26 +0900: > Hello, > > The below bug was reported in Masakari's Launchpad. > I think that this bug was caused by oslo.log. > (And, the root cause is a bug of pyinotify using by oslo.log. The detail is > written in the bug report.) > > *

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

Excerpts from zuul's message of 2018-01-03 14:46:48 +: > Build failed. > > - publish-openstack-releasenotes > http://logs.openstack.org/bf/bfe7b055d19537f2c59125678410b3d25d2cb61d/tag/publish-openstack-releasenotes/1d51c55/ > : FAILURE in 5m 04s > Based on

Re: [openstack-dev] [castellan] Removing Keystoneauth Dependency in Castellan Discussion

Excerpts from Gage Hugo's message of 2017-12-19 11:14:18 -0600: > On Tue, Dec 12, 2017 at 5:34 PM, Doug Hellmann <d...@doughellmann.com> > wrote: > > > Excerpts from Dave McCowan (dmccowan)'s message of 2017-12-12 21:36:51 > > +: > > > > >

Re: [openstack-dev] [oslo] Oslo team updates

Excerpts from ChangBo Guo's message of 2018-01-02 11:53:02 +0800: > In last two cycles some people's situation changed, can't focus on Oslo > code review, so I propose some changes in Oslo team. Remove following > people, thanks their past hard wok to make Oslo well, and welcome them back > if

Re: [openstack-dev] [all] Switching to longer development cycles

> On Dec 13, 2017, at 6:44 PM, Clint Byrum wrote: > > Excerpts from Thierry Carrez's message of 2017-12-13 17:17:26 +0100: >> Hi everyone, >> >> Over the past year, it has become pretty obvious to me that our >> self-imposed rhythm no longer matches our natural pace. It feels

Re: [openstack-dev] [all] Switching to longer development cycles

Excerpts from Arkady.Kanevsky's message of 2017-12-14 02:44:24 +: > How about add to our biannual questionnaire how often customer upgrade their > openstack environment? There is quite a bit of information about deployments in the latest user survey [1], starting on page 24. Page 29 shows

Re: [openstack-dev] [all] Switching to longer development cycles

Excerpts from Ed Leafe's message of 2017-12-13 16:07:50 -0600: > On Dec 13, 2017, at 12:13 PM, Tim Bell wrote: > > > There is a risk that deployment to production is delayed, and therefore > > feedback is delayed and the wait for the ‘initial bug fixes before we > > deploy to

Re: [openstack-dev] [all] Switching to longer development cycles

Excerpts from Thierry Carrez's message of 2017-12-13 22:26:49 +0100: > Doug Hellmann wrote: > > Excerpts from Michael Still's message of 2017-12-13 10:59:37 -0800: > >> Do we continue to support the previous two releases as stable branches? > >> Doesn't that mean we d

Re: [openstack-dev] [all] Switching to longer development cycles

Excerpts from Michael Still's message of 2017-12-13 10:59:37 -0800: > Do we continue to support the previous two releases as stable branches? > Doesn't that mean we double the amount of time we need to keep older CI > setups around? Isn't that already a pain point for the stable teams? > >

Re: [openstack-dev] [castellan] Removing Keystoneauth Dependency in Castellan Discussion

Excerpts from Dave McCowan (dmccowan)'s message of 2017-12-12 21:36:51 +: > > On 12/12/17, 3:15 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > >Excerpts from Dave McCowan (dmccowan)'s message of 2017-12-12 19:56:49 > >+: > >>

Re: [openstack-dev] [castellan] Removing Keystoneauth Dependency in Castellan Discussion

Excerpts from Dave McCowan (dmccowan)'s message of 2017-12-12 19:56:49 +: > > On 12/12/17, 10:38 AM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > > > >> On Dec 12, 2017, at 9:42 AM, Paul Bourke <paul.bou...@oracle.com> wrote: > >

Re: [openstack-dev] [castellan] Removing Keystoneauth Dependency in Castellan Discussion

e “current” user talking to them so they can access that user’s secrets from Barbican. Removing the keystoneauth stuff from the driver would therefore break all of those applications. Doug > > -Paul > > [0] https://github.com/openstack/castellan/tree/master/castellan/key_manager >

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

om> wrote: > > >On Fri, Dec 08, 2017 at 04:06:15PM -0600, Doug Hellmann wrote: > >> Excerpts from zuul's message of 2017-12-08 21:56:33 +: > >> > Build failed. > >> > > >> > - release-openstack-python-without-pypi > >>http://

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

Excerpts from zuul's message of 2017-12-08 21:56:33 +: > Build failed. > > - release-openstack-python-without-pypi > http://logs.openstack.org/08/080df7f0b147dc8290cc9ceb513ba5d8c1f8f295/pre-release/release-openstack-python-without-pypi/8c423e5/ > : FAILURE in 5m 53s > - announce-release

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

Excerpts from corvus's message of 2017-12-06 15:33:29 -0800: > Chris Dent writes: > > > The expansion of the Foundation was talked about at the summit in > > Sydney, but having something happen this quickly was a bit of a > > surprise, leading to some [questions in > >

Re: [openstack-dev] [Release-job-failures][heat] Release of openstack/python-heatclient failed

Excerpts from zuul's message of 2017-12-07 15:00:43 +: > Build failed. > > - release-openstack-python > http://logs.openstack.org/7a/7a54c5881cdd26d89775b638628c3f9c909a33a6/release/release-openstack-python/e5594bb/ > : SUCCESS in 5m 41s > - announce-release >

Re: [openstack-dev] Removing Keystoneauth Dependency in Castellan Discussion

tanding the real motivation for removing the dependency. Is it just someone's notion of cleaning things up? Or is there a runtime issue of some sort? Doug [1] http://git.openstack.org/cgit/openstack/castellan/tree/castellan/key_manager/barbican_key_manager.py#n140 > > On Tue, Dec 5, 2

Re: [openstack-dev] Removing Keystoneauth Dependency in Castellan Discussion

Excerpts from ARORA, ROHAN's message of 2017-12-05 14:37:49 +: > So from my understanding now, we are wanting to remove the HARD dependency on > Keystoneauth, not to remove it completely since that would break the barbican > client. Currently seeing if we just remove the dependency from >

Re: [openstack-dev] Removing Keystoneauth Dependency in Castellan Discussion

Excerpts from ARORA, ROHAN's message of 2017-12-04 21:47:45 +: > Wanted to start a thread to discuss the potential removal of the Keystoneauth > dependency from Castellan. Whether it is needed or not, approaches we might > want to take, etc. > From my understanding, Tin, Gage, and Ade

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

Excerpts from Joshua Harlow's message of 2017-11-27 11:44:54 -0800: > Doug Hellmann wrote: > > Excerpts from Joshua Harlow's message of 2017-11-27 10:54:02 -0800: > >> Flavio Percoco wrote: > >>> Greetings, > >>> > >>> Last Thursday[0]

Re: [openstack-dev] [all] Dublin PTG format

Excerpts from Thierry Carrez's message of 2017-11-27 11:58:04 +0100: > Hi everyone, > > We are in the final step in the process of signing the contract with the > PTG venue. We should be able to announce the location this week ! > > So it's time to start preparing. We'll have 5 days, like in

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

Excerpts from Joshua Harlow's message of 2017-11-27 10:54:02 -0800: > Flavio Percoco wrote: > > Greetings, > > > > Last Thursday[0], at the TC office hours, we brainstormed a bit around > > the idea > > of having a tech blog. This idea came first from Joshua Harlow and it > > was then > > briefly

Re: [openstack-dev] [OpenStack-docs] [all] Changes to releasenotes and docs build jobs

sphinx/issues/4259 > [3] > http://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/sphinx/tasks/main.yaml#n15 > [4] https://review.openstack.org/#/c/509297/ > > Doug Hellmann wrote on 11/23/2017 12:05 AM: >> Excerpts from Monty Taylor's message of 2017-11-22 07

Re: [openstack-dev] [all] Changes to releasenotes and docs build jobs

Excerpts from Monty Taylor's message of 2017-11-22 07:39:45 -0600: > * We use -W for all releasenotes builds - this means warnings are always > errors for releasenotes. That shouldn't bother anyone, as most of the > releasenotes content is generated by reno anyway. For projects that never had

Re: [openstack-dev] [doc][infra][stable] we are ready to restore stable/mitaka for openstack-manuals

Excerpts from Doug Hellmann's message of 2017-11-20 11:32:53 -0500: > As we agreed in the new documentation retention policy spec [1], I need > to restore the stable/mitaka branch for the openstack/openstack-manuals > repository and then trigger a build of the mitaka version of the guides. > I

Re: [openstack-dev] [release][ptl] Improving the process for release marketing

Excerpts from Michael Johnson's message of 2017-11-21 08:52:17 -0800: > Is there a template for this? I wouldn't want to have 12 different > formatting styles for the page (Yes, I'm looking at Amrith and the > blinking red text. grin) > > Michael I think just keep it simple and it will be fine

Re: [openstack-dev] [oslo][oslo.config] pluggable drivers for oslo.config spec ready for review

Excerpts from Jay Pipes's message of 2017-11-20 11:02:33 -0500: > On 11/20/2017 10:19 AM, Doug Hellmann wrote: > > The spec for adding pluggable drivers to oslo.config is ready for a > > final queens review [1]. The latest draft should be simpler to implement > > (imp

[openstack-dev] [doc][infra][stable] we are ready to restore stable/mitaka for openstack-manuals

As we agreed in the new documentation retention policy spec [1], I need to restore the stable/mitaka branch for the openstack/openstack-manuals repository and then trigger a build of the mitaka version of the guides. I have a local patch ready that works, so I believe the next steps are to create

[openstack-dev] [oslo][oslo.config] pluggable drivers for oslo.config spec ready for review

The spec for adding pluggable drivers to oslo.config is ready for a final queens review [1]. The latest draft should be simpler to implement (important given where we are in the schedule) at the expense of always requiring at least one configuration file to specify the location of other

[openstack-dev] [tc] Keynote: Governance and Trust -- from Company Led to Community Led - Sarah Novotny - YouTube

This keynote talk about the evolution of governance in the kubernetes community and the CNCF more broadly discusses some interesting parallels with our own history. https://m.youtube.com/watch?feature=youtu.be=Apw_fuTEhyA

Re: [openstack-dev] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed

Excerpts from Akihiro Motoki's message of 2017-11-16 01:32:00 +0900: > 2017-11-15 1:06 GMT+09:00 Andreas Jaeger <a...@suse.com>: > > On 2017-11-14 17:03, Doug Hellmann wrote: > >> Excerpts from Andreas Jaeger's message of 2017-11-14 09:31:48 +0100: > >>> On 2

Re: [openstack-dev] [Openstack-operators] Upstream LTS Releases

Excerpts from Fox, Kevin M's message of 2017-11-15 00:37:26 +: > I can think of a few ideas, though some sound painful on paper Not really > recommending anything, just thinking out loud... > > One idea is that at the root of chaos monkey. If something is hard, do it > frequently. If

Re: [openstack-dev] Upstream LTS Releases

Excerpts from Chris Friesen's message of 2017-11-14 15:50:08 -0600: > On 11/14/2017 02:10 PM, Doug Hellmann wrote: > > Excerpts from Chris Friesen's message of 2017-11-14 14:01:58 -0600: > >> On 11/14/2017 01:28 PM, Dmitry Tantsur wrote: > >> > >>>> T

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

Excerpts from zuul's message of 2017-11-14 20:13:45 +: > Unable to freeze job graph: Unable to modify final job publish-openstack-releasenotes branches: None source: > openstack-infra/project-config/zuul.d/jobs.yaml@master#26> attribute > required_projects={'openstack/neutron':

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

Excerpts from Clark Boylan's message of 2017-11-14 09:04:07 -0800: > > On Tue, Nov 14, 2017, at 09:01 AM, Doug Hellmann wrote: > > Excerpts from zuul's message of 2017-11-14 16:24:33 +: > > > Build failed. > > > > > > - release-openstack-python-withou

Re: [openstack-dev] Upstream LTS Releases

Excerpts from Chris Friesen's message of 2017-11-14 14:01:58 -0600: > On 11/14/2017 01:28 PM, Dmitry Tantsur wrote: > > >> The quality of backported fixes is expected to be a direct (and only?) > >> interest of those new teams of new cores, coming from users and operators > >> and > >> vendors.

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

Excerpts from zuul's message of 2017-11-14 16:24:33 +: > Build failed. > > - release-openstack-python-without-pypi > http://logs.openstack.org/17/175bd53e7b18a9dc4d42e60fe9225a5748eded34/pre-release/release-openstack-python-without-pypi/7a9474c/ > : POST_FAILURE in 14m 47s > -

Re: [openstack-dev] [Release-job-failures][zuul][infra][trove] Tag of openstack/trove-dashboard failed

Excerpts from Clark Boylan's message of 2017-11-14 08:31:15 -0800: > On Tue, Nov 14, 2017, at 08:09 AM, Doug Hellmann wrote: > > Excerpts from zuul's message of 2017-11-14 16:01:20 +: > > > Unable to freeze job graph: Unable to modify final job > > publish-opensta

Re: [openstack-dev] Upstream LTS Releases

Excerpts from Bogdan Dobrelya's message of 2017-11-14 17:08:31 +0100: > >> The concept, in general, is to create a new set of cores from these > >> groups, and use 3rd party CI to validate patches. There are lots of > >> details to be worked out yet, but our amazing UC (User Committee) will > >>

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

Excerpts from Davanum Srinivas (dims)'s message of 2017-11-15 03:04:38 +1100: > Flavio, Saverio, > > Agree, that review may be a good example of what could be done. More info > below. > > Saverio said - "with the old Stable Release thinking this patch would > not be accepted on old stable

Re: [openstack-dev] [Release-job-failures][zuul][infra][trove] Tag of openstack/trove-dashboard failed

Excerpts from zuul's message of 2017-11-14 16:01:20 +: > Unable to freeze job graph: Unable to modify final job publish-openstack-releasenotes branches: None source: > openstack-infra/project-config/zuul.d/jobs.yaml@master#26> attribute > required_projects={'openstack/horizon':

Re: [openstack-dev] [api] APIs schema consumption discussion

Excerpts from Gilles Dubreuil's message of 2017-11-14 10:15:02 +1100: > Hi, > > Follow-up conversation from our last "API SIG feedback and discussion > session" at Sydney Summit [1], about APIs schema consumption. > > Let's summarize the current situation. > > Each OpenStack project has an

Re: [openstack-dev] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed

Excerpts from Andreas Jaeger's message of 2017-11-14 09:31:48 +0100: > On 2017-11-13 22:09, Doug Hellmann wrote: > > Excerpts from zuul's message of 2017-11-13 20:37:18 +: > >> Unable to freeze job graph: Unable to modify final job >> publish-openstack-releasenot

Re: [openstack-dev] [Release-job-failures][neutron] Tag of openstack/neutron-fwaas-dashboard failed

Excerpts from zuul's message of 2017-11-13 20:37:18 +: > Unable to freeze job graph: Unable to modify final job publish-openstack-releasenotes branches: None source: > openstack-infra/project-config/zuul.d/jobs.yaml@master#26> attribute > required_projects={'openstack/horizon':

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

Excerpts from Alex Schultz's message of 2017-11-13 09:45:20 -0700: > On Mon, Nov 13, 2017 at 8:02 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from zuul's message of 2017-11-13 09:24:15 +: > >> Build failed. > >> > >> - release-openst

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

Excerpts from zuul's message of 2017-11-13 09:24:15 +: > Build failed. > > - release-openstack-puppet > http://logs.openstack.org/08/087081b12493632186b60dc2c5ab6c95ade61ef6/release/release-openstack-puppet/a7bbd5c/ > : POST_FAILURE in 1m 33s > - announce-release announce-release : SKIPPED

Re: [openstack-dev] [Release-job-failures][puppet] Release of openstack/puppet-ceilometer failed

Excerpts from zuul's message of 2017-11-13 09:17:54 +: > Build failed. > > - release-openstack-puppet > http://logs.openstack.org/0d/0d3bfc02991ac28527980462e709d796e3305c50/release/release-openstack-puppet/ddcbbb6/ > : POST_FAILURE in 1m 33s > - announce-release announce-release : SKIPPED

Re: [openstack-dev] [Release-job-failures][puppet] Release of openstack/puppet-gnocchi failed

Excerpts from zuul's message of 2017-11-13 09:21:31 +: > Build failed. > > - release-openstack-puppet > http://logs.openstack.org/dc/dce26ec244199a83724bdcbfbb4665652ea37698/release/release-openstack-puppet/6d26826/ > : POST_FAILURE in 2m 18s > - announce-release announce-release : SKIPPED

Re: [openstack-dev] [Release-job-failures][puppet] Release of openstack/puppet-glance failed

Excerpts from zuul's message of 2017-11-13 09:23:16 +: > Build failed. > > - release-openstack-puppet > http://logs.openstack.org/7a/7a2e3aa6531521076b4b785dbdc2943f67953db6/release/release-openstack-puppet/5bcb484/ > : POST_FAILURE in 1m 29s > - announce-release announce-release : SKIPPED

Re: [openstack-dev] [Release-job-failures][puppet] Release of openstack/puppet-magnum failed

Excerpts from zuul's message of 2017-11-13 09:25:04 +: > Build failed. > > - release-openstack-puppet > http://logs.openstack.org/52/5294a365d29a7c6745856aae5d78f09c709f7fc1/release/release-openstack-puppet/fd776d7/ > : POST_FAILURE in 1m 36s > - announce-release announce-release : SKIPPED

Re: [openstack-dev] Upstream LTS Releases

Excerpts from Samuel Cassiba's message of 2017-11-08 08:27:12 -0800: > On Tue, Nov 7, 2017 at 3:28 PM, Erik McCormick > wrote: > > Hello Ops folks, > > > > This morning at the Sydney Summit we had a very well attended and very > > productive session about how to go

Re: [openstack-dev] [oslo][tripleo][puppet] Logging format: let's discuss a bit about default format, format configuration and so on

Excerpts from Juan Antonio Osorio's message of 2017-11-06 15:18:33 +0200: > Proposed a patch to be able to enable the JSON formatter via an oslo.log > configuration parameter: > > https://review.openstack.org/#/c/517882/ That's approved, thanks! We should make sure we have a release note before

Re: [openstack-dev] Logging format: let's discuss a bit about default format, format configuration and so on

Excerpts from Juan Antonio Osorio's message of 2017-11-04 00:11:47 +0200: > > On 3 Nov 2017 19:59, "Doug Hellmann" <d...@doughellmann.com> wrote: > > > > Excerpts from Cédric Jeanneret's message of 2017-11-01 14:54:34 +0100: > > > Dear Stackers, >

Re: [openstack-dev] Logging format: let's discuss a bit about default format, format configuration and so on

Excerpts from Cédric Jeanneret's message of 2017-11-01 14:54:34 +0100: > Dear Stackers, > > While working on my locally deployed Openstack (Pike using TripleO), I > was a bit struggling with the logging part. Currently, all logs are > pushed to per-service files, in the standard format "one line

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

Excerpts from Richard.Pioso's message of 2017-10-30 23:11:31 +: > > From: Dmitry Tantsur [mailto:dtant...@redhat.com] > > > Cons: > > 1. more work for both the requirements team and the vendor teams > > Please elaborate on the additional work you envision for the vendor teams. > > > 2.

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

Excerpts from Dmitry Tantsur's message of 2017-10-30 17:51:49 +0100: > Hi all, > > So far driver requirements [1] have been managed outside of > global-requirements. > This was mostly necessary because some dependencies were not on PyPI. This is > no > longer the case, and I'd like to

Re: [openstack-dev] [release] Release countdown for week R-17, October 28 - November 3

Excerpts from Sean McGinnis's message of 2017-10-26 13:46:23 -0500: > With much anticipation, our regular release countdown email. > > Development Focus > - > > Now that the Queens-1 milestone is passed*, teams should now be focused on > feature development and completion of

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

Excerpts from Jeremy Stanley's message of 2017-10-26 13:30:53 +: > On 2017-10-26 14:42:35 +0200 (+0200), Flavio Percoco wrote: > [...] > > I personally don't think the campaing period was too short. I saw > > enough interactions between candidates and the rest of the > > community, which was

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

Excerpts from Doug Hellmann's message of 2017-10-24 09:42:25 -0400: > The neutron queens milestone release is held up right now because > some of the repositories are using a release job template that isn't > recognized by the validation code in the releases repository. I'm > trying to decide

Re: [openstack-dev] [release][ptl] Releases repo frozen

Excerpts from Sean McGinnis's message of 2017-10-17 10:37:25 -0500: > Just a heads up that the releases repo is frozen while we work through some > zuul v3 migration issues. Jobs are passing, but some of the important > post-release processing that needs to happen will require a little more >

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

Excerpts from Jeremy Stanley's message of 2017-10-24 15:05:34 +: > On 2017-10-24 09:42:25 -0400 (-0400), Doug Hellmann wrote: > [...] > > It looks like the publish-to-pypi-neutron template modifies > > publish-to-pypi by adding openstack/neutron to the required-rep

Re: [openstack-dev] [oslo][bilean][cue][poppy] Remove the parameter enforce_type from set_override and set_default

Excerpts from ChangBo Guo's message of 2017-10-24 14:27:11 +0800: > We plan to remove the parameter enforce_type from set_override and > set_default in oslo.config [1]. we have been blocking its usage in > bilean, cue, poppy for a long time. patchs were posted in these projects > [2][3][4].

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

Excerpts from Thierry Carrez's message of 2017-10-24 13:47:32 +0200: > Colleen Murphy wrote: > > On Sat, Oct 21, 2017 at 9:00 AM, Diana Clarke > > > wrote: > > > > Congrats on being elected to the TC, Colleen! > > > > You

[openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

The neutron queens milestone release is held up right now because some of the repositories are using a release job template that isn't recognized by the validation code in the releases repository. I'm trying to decide between adding the custom job template to the validation code or changing the

Re: [openstack-dev] Fwd: [Distutils][pbr][devstack][qa] Announcement: Pip 10 is coming, and will move all internal APIs

Excerpts from Clark Boylan's message of 2017-10-20 13:14:13 -0700: > On Fri, Oct 20, 2017, at 11:17 AM, Clark Boylan wrote: > > On Fri, Oct 20, 2017, at 07:23 AM, Doug Hellmann wrote: > > > It sounds like the PyPI/PyPA folks are planning some major changes to > &g

[openstack-dev] Fwd: [Distutils][pbr] Announcement: Pip 10 is coming, and will move all internal APIs

It sounds like the PyPI/PyPA folks are planning some major changes to pip internals, soon. I know pbr uses setuptools, and I don't think it uses pip, but if someone has time to verify that it would be helpful. We'll also want to watch out for breakage in normal use of pip 10. If they're making

Re: [openstack-dev] [Release-job-failures][release][neutron][powervm] Pre-release of openstack/networking-powervm failed

We are still working on fixing up the release jobs to work after the zuulv3 migration. Please do not tag releases until we announce that it is OK. Excerpts from zuul's message of 2017-10-19 20:04:07 +: > Build failed. > > - trigger-readthedocs >

Re: [openstack-dev] [oslo][mistral] Mistral expressions package

willing to take responsibility for a new repository. Maybe one of you can add it to the meeting agenda for next week? Dogu > > Thanks > > Renat Akhmerov > @Nokia > > On 10 Oct 2017, 22:11 +0700, Doug Hellmann <d...@doughellmann.com>, wrote: > > Excerpts f

Re: [openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

Excerpts from Zane Bitter's message of 2017-10-16 18:10:20 -0400: > On 14/10/17 11:47, Doug Hellmann wrote: > > Excerpts from Zane Bitter's message of 2017-10-13 15:21:14 -0400: > >> Replying to myself here, to avoid singling anyone in particular out. I > >> want to rep

Re: [openstack-dev] [all][elections] Voting for the TC Election is now open

Excerpts from Kendall Nelson's message of 2017-10-15 00:12:26 +: > Hello All, > > Voting for the TC Election is now open and will remain open until 23:45 > October 20th, 2017 UTC. > > We are selecting 6 TC members, please rank all candidates in your order of > preference. > > You are

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

Excerpts from Colleen Murphy's message of 2017-10-15 11:38:47 +0200: > On Fri, Oct 13, 2017 at 2:45 PM, Flavio Percoco wrote: > > > Greetings, > > > > Some of you, TC candidates, expressed concerns about diversity and > > inclusiveness > > (or inclusivity, depending on your

Re: [openstack-dev] [tc][election] Question for all candidates in TC election: What will you do if you don't win?

Excerpts from Amrith Kumar's message of 2017-10-15 08:15:51 -0400: > Full disclosure, I'm running for election as well. I intend to also > provide an answer to the question I pose here, one that I've posed > before on #openstack-tc in an office hours session. > > Question 1: > > "There are M

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

Excerpts from Emilien Macchi's message of 2017-10-13 15:02:10 -0700: > Greeting folks, > > I hope we can get attention from stable-maint, release-managers and > installers projects. > > > ## Background > > Some projects tried hard to follow stable policy but it didn't finish > well:

Re: [openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

Excerpts from Zane Bitter's message of 2017-10-13 15:21:14 -0400: > Replying to myself here, to avoid singling anyone in particular out. I > want to rephrase the question, because people are overwhelmingly either > failing to understand or refusing to answer it in the way I intended it. > >

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

Excerpts from Amrith Kumar's message of 2017-10-13 13:32:54 -0400: > Flavio, > > Some months back I looked at a slide that Thierry showed at a meeting; > it showed contributor statistics and it showed that there were a large > number of contributors who made exactly 1 commit which sometimes got >

Re: [openstack-dev] [tc][election] Question for the candidates

Excerpts from Ed Leafe's message of 2017-10-12 13:38:03 -0500: > In the past year or so, has there been anything that made you think “I wish > the TC would do something about that!” ? If so, what was it, and what would > you have wanted the TC to do about it? > > -- Ed Leafe > The main issue

Re: [openstack-dev] [tc][election] Question for the candidates

> > > > -Clay > > 2017-05-30 Guidelines for Managing Releases of Binary Artifacts [1]. > > It would have to be 469265[2] that Doug Hellmann proposed after the OpenStack > Summit in Boston. There has been a lot of passionate people in the community > that

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

Excerpts from Flavio Percoco's message of 2017-10-13 14:45:28 +0200: > Greetings, > > Some of you, TC candidates, expressed concerns about diversity and > inclusiveness > (or inclusivity, depending on your taste) in your candidacy. I believe this > is a > broad, and some times ill-used, topic

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

he gating > issues are fixed? > > Thanks, > Eric Berglund > > Doug Hellmann <d...@doughellmann.com> wrote on 10/12/2017 10:08:31 AM: > > > From: Doug Hellmann <d...@doughellmann.com> > > To: openstack-dev@lists.openstack.org > > Date: 10/12/2017 10:

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

Given the gate issues right now, it's probably best to hold off trying to create releases. Excerpts from jenkins's message of 2017-10-12 13:47:41 +: > Build failed. > > - nova-powervm-tarball >

Re: [openstack-dev] [all] Zuul v3 Rollout Update - devstack-gate issues edition

Excerpts from Jeremy Stanley's message of 2017-10-12 14:18:38 +: > On 2017-10-12 16:28:33 +1100 (+1100), Ian Wienand wrote: > [...] > > - logs issues > > > > Should be behind us. The logs partition ran out of inodes, causing > > log upload failures. Pruning jobs should have rectified this.

Re: [openstack-dev] [pbr] Migration to Storyboard

Excerpts from Jeremy Stanley's message of 2017-10-11 16:29:31 +: > On 2017-10-11 12:05:33 -0400 (-0400), Doug Hellmann wrote: > [...] > > We have a bunch of open bugs. It would be good to triage those to see > > which, if any, need to be migrated. > [...] > > We

Re: [openstack-dev] [pbr] Migration to Storyboard

Excerpts from Stephen Finucane's message of 2017-10-11 15:05:50 +0100: > The Python packaging ecosystem is shifting under our feet and we have a couple > of things in pbr we need to look at over the next few months (Pipfiles, pyenv, > changes in setuptools setup.cfg, ...). We should probably track

Re: [openstack-dev] [docs] Flagging deprecated releases

Excerpts from Jimmy McArthur's message of 2017-10-10 15:40:05 -0500: > > > Doug Hellmann <mailto:d...@doughellmann.com> > > October 10, 2017 at 2:46 PM > > > > > > When I was updating the landing pages and adding the old release series, > > I i

Re: [openstack-dev] [packaging][all] Sample Config Files in setup.cfg

Excerpts from Thomas Goirand's message of 2017-10-10 22:03:44 +0200: > On 10/10/2017 01:16 PM, Jesse Pretorius wrote: > > Regardless, given that this is not functionality currently> available for > > setuptools, distutils or pbr it would seem > > that this functionality (or another applicable

Re: [openstack-dev] [packaging][all] Sample Config Files in setup.cfg

Excerpts from Thomas Goirand's message of 2017-10-10 21:28:35 +0200: > On 10/10/2017 01:21 PM, Jesse Pretorius wrote: > > > > > > On 10/10/17, 12:08 PM, "Jesse Pretorius" > > wrote: > > > >>$ python setup.py install --skip-build --root /tmp/keystone > >>

Re: [openstack-dev] [docs] Flagging deprecated releases

Excerpts from Jimmy McArthur's message of 2017-10-10 14:15:52 -0500: > Hi all - > > I'm following up on the PTG action item to add a CSS banner for older > releases (e.g. https://releases.openstack.org/newton/index.html). Does > anyone have specific language they'd like to see here or should I

Re: [openstack-dev] [oslo][mistral] Mistral expressions package

Excerpts from HADDLETON, Robert W (Bob)'s message of 2017-10-09 19:41:58 -0500: > On 10/9/2017 2:35 PM, Doug Hellmann wrote: > > Excerpts from Bob Haddleton's message of 2017-10-09 11:35:16 -0500: > >> Hello Oslo team: > >> > >> The Mistral project has an

Re: [openstack-dev] [docs] Evidence of Success

This draft looks really good. I left a few comments on the etherpad. Excerpts from Jimmy McArthur's message of 2017-10-05 10:33:48 -0500: > Sorry for the Google Docs link btw. That's where Petr and I were > initially collaborating. I've moved this back to the etherpad referenced > in

Re: [openstack-dev] [tc][docs][release] Updating the PTI for docs and tarballs

Excerpts from Monty Taylor's message of 2017-10-05 08:45:52 -0500: > On 09/30/2017 10:40 AM, Doug Hellmann wrote: > > Excerpts from Monty Taylor's message of 2017-09-30 10:20:08 -0500: > >> Hey everybody, > >> > >> Oh goodie, I can hear you say, let's definite

Re: [openstack-dev] [oslo][mistral] Mistral expressions package

Excerpts from Bob Haddleton's message of 2017-10-09 11:35:16 -0500: > Hello Oslo team: > > The Mistral project has an expressions package [0] that is used to > evaluate inline expressions using a context. It has a pluggable > architecture that presently supports Jinja and YAQL expression >

Re: [openstack-dev] [Oslo][Designate][Congress] Problem with from_dict overrides and new oslo.context release

Excerpts from Ben Nemec's message of 2017-10-09 12:03:24 -0500: > Hi, > > I brought up the fix[1] I proposed for [2] in the Oslo meeting today, > and it led to some good discussion that we wanted to take to a broader > audience. In particular, the projects that are affected by the bug. > >

[openstack-dev] [tc][election] TC candidacy

I am announcing my candidacy for a position on the OpenStack Technical Committee. I started contributing to OpenStack in 2012, and I am currently employed by Red Hat to work on OpenStack with a focus on long-term project concerns. I have served on the Technical Committee for the last four years

Re: [openstack-dev] [packaging][all] Sample Config Files in setup.cfg

Excerpts from Jesse Pretorius's message of 2017-10-03 15:57:17 +: > On 10/3/17, 3:01 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > >> Given that this topic has gone through several cycles of discussion and > >> has never gone anywhere, does

Re: [openstack-dev] [packaging][all] Sample Config Files in setup.cfg

Excerpts from Jesse Pretorius's message of 2017-10-03 09:02:19 +: > On 10/2/17, 1:45 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > >etc implies they should be edited, though, and we're trying to move away > >from that at least for the paste

Re: [openstack-dev] [tc] [election] NON nomination for TC

Excerpts from Sean Dague's message of 2017-10-02 12:03:44 -0400: > I'd like to announce that after 4 years serving on the OpenStack > Technical Committee, I will not be running in this fall's > election. Over the last 4 years we've navigated some rough seas > together, including the transition to

Re: [openstack-dev] [all][oslo] Retiring openstack/pylockfile

Or https://github.com/jazzband Now we need a project to list all of the organizations full of unmaintained software... > On Oct 2, 2017, at 12:12 PM, Joshua Harlow wrote: > > Yup, +1 from me also, > > Honestly might just be better to put

Re: [openstack-dev] [packaging][all] Sample Config Files in setup.cfg

Excerpts from Jesse Pretorius's message of 2017-10-02 08:38:06 +: > On 9/29/17, 6:26 PM, "Jeremy Stanley" wrote: > > On 2017-09-29 18:39:18 +0200 (+0200), Thomas Bechtold wrote: > > There is /etc [1] > [...] > > >Not really, no, because the system-context

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