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

Excerpts from ChangBo Guo's message of 2017-09-30 11:07:33 +0800: > pylockfile was deprecated about two years ago in [1] and it is not used > in any OpenStack Projects now [2] , we would like to retire it according > to steps of retiring a project[3]. > > >

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

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 definitely spend some time > bikeshedding about specific command invocations related to building docs > and tarballs!!! > > tl;dr I want to change the PTI for docs and

Re: [openstack-dev] [docs][ptls][install] Install guide vs. tutorial

Excerpts from Petr Kovar's message of 2017-09-29 21:09:02 +0200: > On Tue, 26 Sep 2017 18:53:04 -0500 > Jay S Bryant wrote: > > > > > > > On 9/25/2017 3:47 AM, Alexandra Settle wrote: > > > > > > > I completely agree consistency is more important, than bike > > >

Re: [openstack-dev] [Oslo][oslo.policy][glance] Bug: Glance doesn't send correctly authorization request to Oslo policy

On Sep 29, 2017, at 11:24 AM, ruan...@orange.com wrote: > > Not yet, we are not familiar with the Glance team. > Ruan > > -Original Message----- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: vendredi 29 septembre 2017 16:26 > To: openstack-dev >

Re: [openstack-dev] [all][infra] Zuul v3 migration update

Excerpts from Clark Boylan's message of 2017-09-28 18:40:41 -0700: > On Wed, Sep 27, 2017, at 03:24 PM, Monty Taylor wrote: > > Hey everybody, > > > > We're there. It's ready. > > > > We've worked through all of the migration script issues and are happy > > with the results. The cutover trigger

Re: [openstack-dev] [Oslo][oslo.policy][glance] Bug: Glance doesn't send correctly authorization request to Oslo policy

Excerpts from ruan.he's message of 2017-09-29 12:56:12 +: > Hi folks, > We are testing the http_check function in Oslo policy, and we figure out a > bug: https://bugs.launchpad.net/glance/+bug/1720354. > We believe that this is due to the Glance part since it doesn't well prepare > the

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

Excerpts from Jesse Pretorius's message of 2017-09-28 17:17:55 +: > On 9/28/17, 5:11 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > > In the past we had trouble checking those files into git and gating > > against the results being "up to date&

[openstack-dev] [oslo][castellan] oslo.config secret store drivers

I have updated the old oslo.config drivers spec [1] to remove a bunch of the information about etcd and focus on the secret store use case we discussed at the PTG in queens. I think this work is a prerequisite for the plaintext secrets spec [2] work, because castellan already depends on

[openstack-dev] [docs][ptls][all] documentation retention policy changes

At the Queens PTG in Denver the documentation team members present discussed a new retention policy for content published to docs.openstack.org. I have a spec up for review to document that policy and the steps needed to implement it. This policy will affect all projects, now that most of the

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

Excerpts from Jesse Pretorius's message of 2017-09-28 14:50:24 +: > There’s some history around this discussion [1], but times have changed and > the purpose of the patches I’m submitting is slightly different [2] as far as > I can see – it’s a little more focused and less intrusive. > >

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

Excerpts from Jay S Bryant's message of 2017-09-26 18:39:34 -0500: > On 9/26/2017 4:33 PM, Anne Bertucio wrote: > > > Release marketing is a critical part of sharing what’s new in each release, > > and we want to rework how the marketing community and projects work > > together to make the

Re: [openstack-dev] [Release-job-failures][infra] Release of openstack-infra/zuul-sphinx failed

I assume someone has already noticed that this release failed, but I'm forwarding it to the dev list just in case. Excerpts from jenkins's message of 2017-09-25 14:46:58 +: > Build failed. > > - zuul-sphinx-tarball >

Re: [openstack-dev] patches for simple typo fixes

Excerpts from Sean Dague's message of 2017-09-25 09:42:08 -0400: > On 09/25/2017 09:28 AM, Doug Hellmann wrote: > > > I'm less concerned with the motivation of someone submitting the > > patches than I am with their effect. Just like the situation we had > > with the bug

Re: [openstack-dev] [infra][docs][i18n][ptls] PDFs for project-specific docs with unified doc builds

[Topic tags added to subject line] Excerpts from Ian Y. Choi's message of 2017-09-22 07:29:23 +0900: > Hello, > > "Build PDF docs from rst-based guide documents" [1] was implemented in Ocata > cycle, and I have heard that there were a small conversation at the > Denver PTG > regarding getting

Re: [openstack-dev] patches for simple typo fixes

Excerpts from Sean Dague's message of 2017-09-25 08:24:18 -0400: > On 09/25/2017 07:56 AM, Chris Dent wrote: > > On Fri, 22 Sep 2017, Paul Belanger wrote: > > > >> This is not a good example of encouraging anybody to contribute to the > >> project. > > > > Yes. This entire thread was a bit

Re: [openstack-dev] Garbage patches for simple typo fixes

Excerpts from Qiming Teng's message of 2017-09-23 23:55:34 +0800: > To some extent, I think Zhipeng is right. There are times we as a > community have to do something beyond mentoring new developers. One of > the reasons behind these patches are from the management chain of those > companies. They

Re: [openstack-dev] Garbage patches for simple typo fixes

Excerpts from Huang Zhiteng's message of 2017-09-23 10:00:00 +0800: > On Sat, Sep 23, 2017 at 8:34 AM, Zhipeng Huang wrote: > > Hi Paul, > > > > Unfortunately I know better on this matter and it is not the matter of topic > > dispute as many people on this thread who has

Re: [openstack-dev] Garbage patches for simple typo fixes

information in a few places, with references to an extensive explanation in the project team guide. I don't think that would have helped in the current cases, but it won't hurt in the future. Doug > > Thanks, > Ildikó > IRC: ildikov > > > On 2017. Sep 22., at 12:47, Doug He

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Tony Breeds's message of 2017-09-21 20:20:22 -0500: > On Thu, Sep 21, 2017 at 12:13:23PM -0400, Doug Hellmann wrote: > > Excerpts from Tony Breeds's message of 2017-09-21 08:36:39 -0400: > > > On Wed, Sep 20, 2017 at 06:08:22PM -0400, Doug Hellmann wrote: >

Re: [openstack-dev] Garbage patches for simple typo fixes

age this instead of letting it continue to cause frustration for everyone. Doug > > On Fri, Sep 22, 2017 at 1:43 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Matt Riedemann's message of 2017-09-22 08:26:31 -0500: > >> On 9/22/2017 7:10 AM, Tom Barron wr

Re: [openstack-dev] Garbage patches for simple typo fixes

Excerpts from Matt Riedemann's message of 2017-09-22 08:26:31 -0500: > On 9/22/2017 7:10 AM, Tom Barron wrote: > > FWIW I think it is better not to attribute motivation in these cases. > > Perhaps the code submitter is trying to pad stats, but perhaps they are > > just a new contributor trying to

[openstack-dev] [oslo][oslo.config][all] who asked me about versioning or deprecating default values for config options?

Last week at the PTG someone asked me about best practices for changing or deprecating default values for configuration options. Unfortunately I failed to make any notes at the time and I'm embarrassed to say that I don't remember who it was or exactly what the use case was. If that was you, could

Re: [openstack-dev] Garbage patches for simple typo fixes

Excerpts from Tom Barron's message of 2017-09-22 08:10:35 -0400: > > On 09/21/2017 10:21 PM, Matt Riedemann wrote: > > I just wanted to highlight to people that there seems to be a series of > > garbage patches in various projects [1] which are basically doing things > > like fixing a single typo

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Excerpts from Thierry Carrez's message of 2017-09-21 17:10:52 +0200: > Sean Dague wrote: > > Agreed. We're already at 5 upgrade tags now? > > > > I think honestly we're going to need a picture to explain the > > differences between them. Based on the confusion that kept seeming to > > come during

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Tony Breeds's message of 2017-09-21 08:36:39 -0400: > On Wed, Sep 20, 2017 at 06:08:22PM -0400, Doug Hellmann wrote: > > > I like the idea. I'm not sure why, if the constraints file is only used > > for the dependency installation step, we still need tox_install.

Re: [openstack-dev] [requirements][stable] publish upper-constraints.txt periodic vs post

Excerpts from Matthew Thode's message of 2017-09-21 10:43:50 -0500: > On 17-09-20 14:09:15, Tony Breeds wrote: > > On Wed, Sep 20, 2017 at 01:43:51PM -0400, Tony Breeds wrote: > > > > > The solution I thought we decide on at the PTG is: > > > * Add a post job to all branches that publish a

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Tony Breeds's message of 2017-09-20 17:18:51 -0400: > On Wed, Sep 20, 2017 at 04:51:21PM -0400, Doug Hellmann wrote: > > Excerpts from Jeremy Stanley's message of 2017-09-20 18:59:50 +: > > > On 2017-09-20 14:46:32 -0400 (-0400), Tony Breeds wrote: > >

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Jeremy Stanley's message of 2017-09-20 18:59:50 +: > On 2017-09-20 14:46:32 -0400 (-0400), Tony Breeds wrote: > [...] > > I'd like to find a solution that doesn't need a tox_install.sh > [...] > > This wart came up when discussing Zuul v3 job translations... what > would be

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Jeremy Stanley's message of 2017-09-20 18:35:23 +: > On 2017-09-20 14:24:32 -0400 (-0400), Doug Hellmann wrote: > [...] > > it doesn't really solve the problem of having to update the > > branches every time we open one. Having tox_install.sh figure ou

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Excerpts from Dan Smith's message of 2017-09-20 10:09:54 -0700: > >> - Modify the `supports-upgrades`[3] and `supports-accessible-upgrades`[4] > >> tags > >> > >>I have yet to look into the formal process around making changes to > >>these tags but I will aim to make a start ASAP. > > >

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Tony Breeds's message of 2017-09-20 13:43:51 -0400: > On Wed, Sep 20, 2017 at 01:08:45PM -0400, Doug Hellmann wrote: > > Excerpts from Jeremy Stanley's message of 2017-09-20 13:36:38 +: > > > On 2017-09-20 08:41:14 -0400 (-0400), D

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Jeremy Stanley's message of 2017-09-20 13:36:38 +: > On 2017-09-20 08:41:14 -0400 (-0400), Doug Hellmann wrote: > [...] > > Is there any reason not to use the published files for all regular > > builds, instead of having tox.ini point to a git URL? Maybe on

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Excerpts from Lee Yarwood's message of 2017-09-20 14:29:12 +0100: > My thanks again to everyone who attended and contributed to the > skip-level upgrades track over the first two days of last weeks PTG. > I've included a short summary of our discussions below with a list of > agreed actions for

Re: [openstack-dev] [all] dashboard query changes since upgrade

Excerpts from Sean Dague's message of 2017-09-19 09:35:26 -0400: > On 09/19/2017 09:00 AM, Sean Dague wrote: > > I've been iterating through gerrit dashboards this morning trying to > > figure out why they no longer show any changes. > > > > It looks like the query: label:Code-Review>=-2,self now

Re: [openstack-dev] [docs][ptls][install] Install guide vs. tutorial

Excerpts from Sean McGinnis's message of 2017-09-19 16:57:40 -0500: > > > On 9/19/17, 2:43 PM, "Eric Fried" wrote: > > > > > > Alex- > > > > > > Regardless of what the dictionary might say, people associate the > > > word > > > "Tutorial" with a set of

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Jeremy Stanley's message of 2017-09-20 12:30:59 +: > On 2017-09-20 07:11:51 -0500 (-0500), Matthew Thode wrote: > > On 17-09-20 13:35:44, Michal Pryc wrote: > > > EOL releases for the nova component (checked neutron as well, > > > possibly many other components) have wrong

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

Excerpts from jenkins's message of 2017-09-19 19:10:12 +: > Build failed. > > - ara-tarball > http://logs.openstack.org/89/89289c511c8c48c8409dd1fb997fc24e64d1dae6/release/ara-tarball/a75a87f/ > : SUCCESS in 3m 17s > - ara-tarball-signing >

Re: [openstack-dev] Should we be using subprocess32?

Excerpts from Tony Breeds's message of 2017-09-14 16:18:35 -0600: > On Tue, Sep 12, 2017 at 11:29:22AM -0700, Joshua Harlow wrote: > > Hi folks, > > > > I know there is a bunch of usage of subprocess in openstack and especially > > since there is heavy usage of python 2.7 it made me wonder if we

Re: [openstack-dev] [docs][neutron] checking link integrity in the gate

Excerpts from Jeremy Stanley's message of 2017-09-06 19:00:05 +: > On 2017-09-06 14:46:54 -0400 (-0400), Doug Hellmann wrote: > [...] > > To be clear, if you can get Sphinx's linkchecker builder to work, > > that's a great option for this. I just don't think you real

Re: [openstack-dev] [docs][neutron] checking link integrity in the gate

Excerpts from Alexandra Settle's message of 2017-09-06 17:47:44 +: > > > On 9/6/17, 12:10 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > Excerpts from Doug Hellmann's message of 2017-09-05 13:53:40 -0400: > > Excerpts from Boden Russell's

Re: [openstack-dev] [all] tracking policy community goal for queens

Excerpts from Lance Bragstad's message of 2017-09-06 12:51:47 -0500: > Hey all, > > I reused some of Doug's doc-migration tooling to create a burndown chart To give credit where due, I in turn copied that stuff from something Sean Dague had for the API ref initiative. Doug > specifically for

Re: [openstack-dev] [docs][neutron] checking link integrity in the gate

Excerpts from Doug Hellmann's message of 2017-09-05 13:53:40 -0400: > Excerpts from Boden Russell's message of 2017-09-05 11:25:34 -0600: > > > > On 9/5/17 11:03 AM, Doug Hellmann wrote: > > > Is eventlet being initialized (or partially initialized) when a module &g

Re: [openstack-dev] [docs][neutron] checking link integrity in the gate

Excerpts from Boden Russell's message of 2017-09-05 11:25:34 -0600: > > On 9/5/17 11:03 AM, Doug Hellmann wrote: > > Is eventlet being initialized (or partially initialized) when a module > > from the application is imported for the auto-generated API > > documenta

Re: [openstack-dev] [docs][neutron] checking link integrity in the gate

Excerpts from Boden Russell's message of 2017-09-05 10:51:09 -0600: > We've (neutron) run into a few cases where our doc links become > outdated/invalid and are dead. These dead links are not detected in the > doc build today, but is something we might be interested in enabling. > > I'm no sphinx

[openstack-dev] [docs] adopting whereto as official tool maintained by docs team

As part of the work for the doc-migration project this cycle, we have expanded the way we use redirects to allow project teams to have htaccess files in tree. Since redirects can be tricky to test without a live server, I put together a tool that we can use in CI to do some minimal validation. It

Re: [openstack-dev] [relmgt] Libraries published to pypi with YYYY.X.Z versions

Excerpts from Claudiu Belu's message of 2017-08-29 14:09:32 +: > Hello, > > As many of you know, during Kilo, the neutron vendor decomposition happened, > which lead to the birth of many networking-* libraries, including > networking-hyperv. When it was time for us to make a release for

Re: [openstack-dev] [all] [oslo] schedule for Denver PTG is ready !

Excerpts from ChangBo Guo's message of 2017-08-28 23:14:05 +0800: > Please check for the draft in [1], we can adjust if you have conflicts > with other discussions. > > We have specific cross projects coding event in the Tuesday afternoon, for > more details please > check [2] and [3], please

Re: [openstack-dev] [oslo] scheduling oslosphinx for retirement at the start of queens

> On Jul 10, 2017, at 9:10 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > Oslo team, > > With all documentation now moving to use the openstackdocs theme, > I propose that we retire the oslosphinx repository during Queens. > We should go ahead and create the st

Re: [openstack-dev] [docs] Re: Install guide testing

Excerpts from Andreas Jaeger's message of 2017-08-25 16:05:41 +0200: > On 2017-08-25 15:40, Roger Luethi wrote: > > I don't know what will get changed or created until the release, but > > what I can find right now in terms of installation instructions is this: > > > >

Re: [openstack-dev] [docs] [ptls] Install guide testing

Excerpts from Alexandra Settle's message of 2017-08-25 08:57:51 +: > Hi everyone, > > The documentation team is searching for volunteers to help test and verify > the OpenStack installation instructions here: > https://docs.openstack.org/install-guide/ > > Previously this action has been

Re: [openstack-dev] [docs] Updating the docs team mission statement

Excerpts from Jay S Bryant's message of 2017-08-22 11:06:37 -0500: > > On 8/22/2017 7:30 AM, Doug Hellmann wrote: > > Excerpts from Doug Hellmann's message of 2017-08-08 08:11:25 -0400: > >> Excerpts from Thierry Carrez's message of 2017-08-08 12:28:58 +0200: > >>>

Re: [openstack-dev] [openstack][oslo][all] Clean up oslo deprecated stuff !

Excerpts from ChangBo Guo's message of 2017-08-22 20:44:18 +0800: > 2017-08-22 20:37 GMT+08:00 Doug Hellmann <d...@doughellmann.com>: > > > Excerpts from ChangBo Guo's message of 2017-08-22 15:24:44 +0800: > > > Hi ALL, > > > > > > We discussed a

Re: [openstack-dev] [openstack][oslo][all] Clean up oslo deprecated stuff !

Excerpts from ChangBo Guo's message of 2017-08-22 15:24:44 +0800: > Hi ALL, > > We discussed a little about how to avoid breaking consuming projects' gate > in oslo weekly meeting last week. The easy improvement is that clean up > deprecated stuff in oslo at the beginning of Queens. I collected

Re: [openstack-dev] [release][ptl] tools for creating new releases

Excerpts from Dmitry Tantsur's message of 2017-08-22 11:38:10 +0200: > On 08/22/2017 11:34 AM, Dmitry Tantsur wrote: > > On 08/21/2017 09:15 PM, Doug Hellmann wrote: > >> Excerpts from Doug Hellmann's message of 2017-08-21 11:21:59 -0400: > >>> Excerpts from Dmitry T

Re: [openstack-dev] [docs] Updating the docs team mission statement

Excerpts from Doug Hellmann's message of 2017-08-08 08:11:25 -0400: > Excerpts from Thierry Carrez's message of 2017-08-08 12:28:58 +0200: > > Petr Kovar wrote: > > > Hi all, > > > > > > With the core docs suite moving from openstack-manuals to individual > > > project repos as per > > >

Re: [openstack-dev] [release][ptl] tools for creating new releases

Excerpts from Doug Hellmann's message of 2017-08-21 11:21:59 -0400: > Excerpts from Dmitry Tantsur's message of 2017-08-15 14:11:05 +0200: > > On 08/08/2017 03:30 PM, Doug Hellmann wrote: > > > We realized recently that we haven't publicized some of the tools > > > in t

Re: [openstack-dev] [ironic] [release] [stable] pike release

Excerpts from Sam Betts (sambetts)'s message of 2017-08-21 10:01:35 +: > Quick reply with my thoughts in-line. > > Sam > > On 21/08/2017, 10:13, "Dmitry Tantsur" wrote: > > (adding the release and stable team just for their information) > > Thanks Julia

Re: [openstack-dev] [release][ptl] tools for creating new releases

Excerpts from Dmitry Tantsur's message of 2017-08-15 14:11:05 +0200: > On 08/08/2017 03:30 PM, Doug Hellmann wrote: > > We realized recently that we haven't publicized some of the tools > > in the releases repository very well. One tool that will be useful > > this week as you

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

Excerpts from Thierry Carrez's message of 2017-08-17 09:42:15 +0200: > Kendall Nelson wrote: > > Hello Everyone! > > > > Thank you to the electorate, to all those who voted and to all > > candidates who put their name forward for Project Team Lead (PTL) in > > this election. A healthy, open

Re: [openstack-dev] [oslo][oslo.config][ansible][tripleo][kolla][ptg] Pluggable drivers and protect plaintext secrets

Excerpts from Raildo Mascena de Sousa Filho's message of 2017-08-17 12:16:15 +: > Hi all, > > Should we reserve a room in the extra session ethercalc [0 > ] or we > already have a time slot scheduled for that discussion? > > [0]

Re: [openstack-dev] [nova][docs] O search where art thou?

Excerpts from Sean Dague's message of 2017-08-11 09:10:59 -0400: > On 08/11/2017 08:50 AM, Anne Gentle | Just Write Click wrote: > > Yeah, I need to circle back in the theme work to make sure both search > > scopes are available. My prior attempt had some wonky CSS debugging and I > > needed to

Re: [openstack-dev] [docs] importing openstack-manuals questions, looking for strategies

Excerpts from Sean Dague's message of 2017-08-09 09:39:55 -0400: > On 08/09/2017 09:24 AM, Sean Dague wrote: > > On 08/09/2017 09:19 AM, Doug Hellmann wrote: > >> Excerpts from Sean Dague's message of 2017-08-08 17:01:29 -0400: > >>> When trying to import >

Re: [openstack-dev] [docs] importing openstack-manuals questions, looking for strategies

Excerpts from Sean Dague's message of 2017-08-09 09:24:07 -0400: > On 08/09/2017 09:19 AM, Doug Hellmann wrote: > > Excerpts from Sean Dague's message of 2017-08-08 17:01:29 -0400: > >> When trying to import > >> https://github.com/opens

Re: [openstack-dev] [all][infra]Plan to support Python 3.6 ?

Excerpts from ChangBo Guo's message of 2017-08-09 21:25:07 +0800: > We received Python 3.6 related Bug recently [1][2]. That let me think > what's the plan to support Python 3.6 for OpenStack in the future. Python > 3.6 was released on December 23, 2016, has some different behaviors from >

Re: [openstack-dev] [docs] importing openstack-manuals questions, looking for strategies

Excerpts from Sean Dague's message of 2017-08-08 17:01:29 -0400: > When trying to import > https://github.com/openstack/openstack-manuals/blob/6f9fc171800e8a435011f38cd4558e900884ce86/doc/config-reference/source/compute/hypervisor-vmware.rst#L2 > into the Nova admin config reference >

Re: [openstack-dev] [release][ptl] tools for creating new releases

Excerpts from Armando M.'s message of 2017-08-08 08:48:34 -0700: > On 8 August 2017 at 06:30, Doug Hellmann <d...@doughellmann.com> wrote: > > > We realized recently that we haven't publicized some of the tools > > in the releases repository very well. One tool that will

Re: [openstack-dev] [api] [tc] Nominatimg Eric Fried for service-types-authority core

Excerpts from Chris Dent's message of 2017-08-08 16:35:18 +0100: > > I don't believe we have an established procedure for core > nominations in the service-types-authority group, so I'll just go > ahead and take the initiative. I think we should make Eric Fried > (efried on IRC) a core in that

[openstack-dev] [release][ptl] tools for creating new releases

We realized recently that we haven't publicized some of the tools in the releases repository very well. One tool that will be useful this week as you prepare your release candidates is the 'new-release' command, which edits a deliverable file to add a new release from HEAD of the given branch,

Re: [openstack-dev] [neutron][tap-as-a-service] pike branch/release

Excerpts from Takashi Yamamoto's message of 2017-08-08 10:49:09 +0900: > hi > > i'll create stable/pike (and probably a release) for tap-as-a-service > in this week. > We have a bunch of tools that expect stable branches to only be created from releases, so please do tag before branching. Doug

Re: [openstack-dev] [docs] Updating the docs team mission statement

Excerpts from Thierry Carrez's message of 2017-08-08 12:28:58 +0200: > Petr Kovar wrote: > > Hi all, > > > > With the core docs suite moving from openstack-manuals to individual > > project repos as per > > http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html, > >

Re: [openstack-dev] [nova] [docs] Ideal landing page

Excerpts from Sean Dague's message of 2017-08-07 17:07:37 -0400: > The integration of all the manual docs, plus all of our native docs > trying to get restructured a bit, has left us with a first order mess > when it comes to our front page (and the Table of Contents in the > sidebar) -

Re: [openstack-dev] [nova][docs] Concerns with docs migration

Excerpts from Clark Boylan's message of 2017-08-07 14:04:33 -0700: > On Wed, Aug 2, 2017, at 01:44 PM, Clark Boylan wrote: > > On Wed, Aug 2, 2017, at 11:37 AM, Sean Dague wrote: > > > On 08/02/2017 12:28 PM, Clark Boylan wrote: > > > > On Wed, Aug 2, 2017, at 07:55 AM, Matt Riedemann wrote: > > >

Re: [openstack-dev] [oslo][oslo.config][ansible][tripleo][kolla][ptg] Pluggable drivers and protect plaintext secrets

Excerpts from Raildo Mascena de Sousa Filho's message of 2017-08-04 19:34:25 +: > Hi all, > > We had a couple of discussions with the Oslo team related to implement > Pluggable drivers for oslo.config[0] and use those feature to implement > support to protect plaintext secret on

Re: [openstack-dev] [oslo][oslo.config] Pluggable drivers and protect plaintext secrets

mechanism. That is also supported, through value interpolation. https://docs.openstack.org/oslo.config/latest/reference/cfg.html#option-value-interpolation Doug > > Thanks, > Kevin > ____ > From: Doug Hellmann [d...@doughellmann.com] > Sent

Re: [openstack-dev] [keystone][api] Backwards incompatible changes based on config

Excerpts from Morgan Fainberg's message of 2017-08-04 14:52:18 -0700: > On Fri, Aug 4, 2017 at 2:43 PM, Kevin L. Mitchell wrote: > > On Fri, 2017-08-04 at 16:45 -0400, Kristi Nikolla wrote: > >> Is this the case even if we haven’t made any final release with the change > >> that

Re: [openstack-dev] [oslo][oslo.config] Pluggable drivers and protect plaintext secrets

Excerpts from Fox, Kevin M's message of 2017-08-04 20:21:19 +: > I would really like to see secrets separated from config. Always have... They > are two separate things. > > If nothing else, a separate config file so it can be permissioned differently. > > This could be combined with k8s

Re: [openstack-dev] [oslo][oslo.config] Pluggable drivers and protect plaintext secrets

Excerpts from Raildo Mascena de Sousa Filho's message of 2017-08-04 19:34:25 +: > Hi all, > > We had a couple of discussions with the Oslo team related to implement > Pluggable drivers for oslo.config[0] and use those feature to implement > support to protect plaintext secret on

Re: [openstack-dev] [all][ptl][stable][release] stable/pike branches created for most libraries

Excerpts from Tony Breeds's message of 2017-08-04 08:56:17 +1000: > On Thu, Aug 03, 2017 at 11:04:52AM -0400, Doug Hellmann wrote: > > Excerpts from Tony Breeds's message of 2017-08-03 12:43:04 +1000: > > > On Mon, Jul 31, 2017 at 08:00:22AM -0400, Doug Hellmann wrote: > >

Re: [openstack-dev] [ffe][requirements][monasca][heat][watcher][congress] FFE for python-monascaclient minimum version in g-r

Excerpts from witold.be...@est.fujitsu.com's message of 2017-08-03 16:07:45 +: > > -Original Message- > > From: Doug Hellmann [mailto:d...@doughellmann.com] > > Sent: Donnerstag, 3. August 2017 15:45 > > To: openstack-dev <openstack-dev@lists.openstack.org&g

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

Excerpts from Tony Breeds's message of 2017-08-03 12:20:24 +1000: > On Thu, Jul 27, 2017 at 07:05:16PM -0400, Doug Hellmann wrote: > > > That content will now live in the project trees. Perhaps part of marking > > branches in those repos EOL needs to include deleting the ins

Re: [openstack-dev] [all][ptl][tc] IMPORTANT upcoming change to technical elections

> On Aug 2, 2017, at 10:53 PM, Jeremy Stanley wrote: > > On 2017-07-17 16:17:00 + (+), Jeremy Stanley wrote: >> If you want to run or vote in upcoming elections for PTL and TC, >> make sure your Foundation Individual Membership is active and has at >> least one Email

Re: [openstack-dev] [all][ptl][stable][release] stable/pike branches created for most libraries

Excerpts from Tony Breeds's message of 2017-08-03 12:43:04 +1000: > On Mon, Jul 31, 2017 at 08:00:22AM -0400, Doug Hellmann wrote: > > Excerpts from Dmitry Tantsur's message of 2017-07-29 20:06:18 +0200: > > > Just to clarify: we cannot land the tox.ini change until the requir

Re: [openstack-dev] [tc][packaging][deb] retiring Packaging Deb project

Excerpts from Allison Randal's message of 2017-08-03 10:09:59 -0400: > Hi all, > > The Debian OpenStack packagers are gathered at the annual Debian > developer event, and discussing the future of OpenStack packaging for > Debian. There's general agreement that we'd like to go ahead and package >

Re: [openstack-dev] [release] Release countdown for week R-3, Aug 4 - Aug 11

Excerpts from Dmitry Tantsur's message of 2017-08-03 16:16:12 +0200: > Hi! > > On 08/03/2017 03:03 PM, Thierry Carrez wrote: > > Welcome to our regular release countdown email! > > > > > > > > > Actions > > --- > > > > Deliverables following the cycle-with-milestones model should post a

Re: [openstack-dev] [monasca] Stable branch for Pike

Excerpts from witold.be...@est.fujitsu.com's message of 2017-08-03 13:27:14 +: > Hello Monasca team, > > Following the Pike release schedule I would like to cut the stable branch for > Pike release early next week. We will use it to create the final release at > the end of August. > >

Re: [openstack-dev] [ffe][requirements][monasca][heat][watcher][congress] FFE for python-monascaclient minimum version in g-r

Excerpts from witold.be...@est.fujitsu.com's message of 2017-08-03 11:39:47 +: > Hello everyone, > > I would like to ask for the FFE for python-monascaclient version in global > requirements. > > The current version in Pike (1.7.0) is not fully backward compatible. The > monasca exception

Re: [openstack-dev] [release] Release countdown for week R-3, Aug 4 - Aug 11

Excerpts from Thierry Carrez's message of 2017-08-03 15:03:59 +0200: > Actions > --- > > Deliverables following the cycle-with-milestones model should post a RC1 > openstack/releases request during the week (X.0.0.0rc1), together with a > stable/pike branch request. It should include

Re: [openstack-dev] [nova][docs] Concerns with docs migration

Excerpts from Clark Boylan's message of 2017-08-02 13:44:26 -0700: > On Wed, Aug 2, 2017, at 11:37 AM, Sean Dague wrote: > > On 08/02/2017 12:28 PM, Clark Boylan wrote: > > > On Wed, Aug 2, 2017, at 07:55 AM, Matt Riedemann wrote: > > >> Now that Stephen Finucane is back from enjoying his youth

Re: [openstack-dev] [nova][docs] Concerns with docs migration

Excerpts from Sean Dague's message of 2017-08-02 14:34:40 -0400: > On 08/02/2017 12:20 PM, Doug Hellmann wrote: > > Excerpts from Akihiro Motoki's message of 2017-08-03 01:02:59 +0900: > >> 2017-08-03 0:52 GMT+09:00 Doug Hellmann <d...@doughellmann.com>: > >>&

Re: [openstack-dev] [nova][docs] Concerns with docs migration

Excerpts from Akihiro Motoki's message of 2017-08-03 01:02:59 +0900: > 2017-08-03 0:52 GMT+09:00 Doug Hellmann <d...@doughellmann.com>: > > Excerpts from Stephen Finucane's message of 2017-08-02 16:35:23 +0100: > >> On Wed, 2017-08-02 at 09:28 -0600, Chris Friesen wrote: &g

Re: [openstack-dev] [nova][docs] Concerns with docs migration

Excerpts from Stephen Finucane's message of 2017-08-02 16:35:23 +0100: > On Wed, 2017-08-02 at 09:28 -0600, Chris Friesen wrote: > > On 08/02/2017 09:22 AM, Stephen Finucane wrote: > > > On Wed, 2017-08-02 at 09:55 -0500, Matt Riedemann wrote: > > > > 3. The patch for the import of the admin guide

[openstack-dev] [release][requirements] FFE release for reno 2.5.0

We have a few projects that have modified stable branch release notes by editing the files on master, which makes those notes appear as part of the current release. Reno has a new option to address that problem by ignoring some note files, and I would like to release that version to allow project

Re: [openstack-dev] [all][docs] recruiting for help with documentation tools

Excerpts from Doug Hellmann's message of 2017-08-01 15:35:35 -0400: > With the changes we've made to docs processes upstream, every team > is going to need to build up their knowledge of how the new > documentation tools and jobs work. The docs team will still help, > but things will obviously go

Re: [openstack-dev] [all][docs] recruiting for help with documentation tools

Excerpts from Swapnil Kulkarni's message of 2017-08-02 14:35:49 +0530: > On Wed, Aug 2, 2017 at 2:25 PM, Bogdan Dobrelya <bdobr...@redhat.com> wrote: > > On 01.08.2017 21:35, Doug Hellmann wrote: > >> With the changes we've made to docs processes upstream, every team > &

Re: [openstack-dev] [SPAM] [all][docs] recruiting for help with documentation tools

Excerpts from Thierry Carrez's message of 2017-08-02 14:01:47 +0200: > Doug Hellmann wrote: > > [...] > > The areas we need help are maintaining the doc build jobs, the > > sphinx extensions in oslo.config and oslo.policy, the Sphinx theme, > > and the template build to

Re: [openstack-dev] [release][ptl] new "linter" rules for openstack/releases repository

Excerpts from Alex Schultz's message of 2017-08-01 13:56:53 -0600: > On Tue, Aug 1, 2017 at 1:45 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Alex Schultz's message of 2017-08-01 12:55:15 -0600: > >> On Tue, Aug 1, 2017 at 12:07 PM, Doug Hellman

Re: [openstack-dev] [requirements][release][oslo] FFE for oslo.policy

Excerpts from Davanum Srinivas (dims)'s message of 2017-08-01 16:38:13 -0400: > +1, i'd support this as the 2 commits in there are not in the > normal/runtime flow for oslo.policy and just touch the doc bits. +1 as well > > Thanks, > Dims > > On Tue, Aug 1, 2017 at 4:36 PM, Lance Bragstad

Re: [openstack-dev] [release][requirements][barbican][octavia][LBaaS][heat] FFE Request for python-barbicanclient library

Excerpts from Dave McCowan (dmccowan)'s message of 2017-08-01 20:48:12 +: > This note is to request a Feature Freeze Exemption (FFE) for the > python-barbicanclient library in Pike. > > Python-barbicanclient 4.5.0 was intended to be the Pike release. However, > after it was released,

Re: [openstack-dev] [release][ptl] new "linter" rules for openstack/releases repository

Excerpts from Alex Schultz's message of 2017-08-01 12:55:15 -0600: > On Tue, Aug 1, 2017 at 12:07 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > The release team is working on a series of patches to improve the > > data validation within openstack/releases. Part of that

[openstack-dev] [all][docs] recruiting for help with documentation tools

With the changes we've made to docs processes upstream, every team is going to need to build up their knowledge of how the new documentation tools and jobs work. The docs team will still help, but things will obviously go more smoothly if folks know how the tools work, now that the bulk of the

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