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

The release team is working on a series of patches to improve the data validation within openstack/releases. Part of that work is to apply consistent formatting rules for all of the YAML files, so it is easier to build tools that automatically update those files. To enable those consistent rules,

Re: [openstack-dev] [all][ptl][docs] adding redirects for moved pages

Excerpts from Doug Hellmann's message of 2017-08-01 12:29:38 -0400: > When we started the doc-migration projects we knew that moving all > of the content around would break a lot of external links. We said > we would deal with it if we had time at the end of the cycle. We > have put the changes

[openstack-dev] [all][ptl][docs] adding redirects for moved pages

When we started the doc-migration projects we knew that moving all of the content around would break a lot of external links. We said we would deal with it if we had time at the end of the cycle. We have put the changes into place to allow us to do that now. I'm going to explain it here, and

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

-27 22:07:33 +: > > > > On 2017-07-27 15:40:22 -0400 (-0400), Doug Hellmann wrote: > > > > [...] > > > > > Are we over-emphasizing the scale of the discovery problem? > > > > > > > > > > When I search for how to install a package on Ubun

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

Excerpts from Doug Hellmann's message of 2017-07-27 19:10:32 -0400: > Excerpts from Doug Hellmann's message of 2017-07-27 19:05:16 -0400: > > Excerpts from Jeremy Stanley's message of 2017-07-27 22:07:33 +: > > > On 2017-07-27 15:40:22 -0400 (-0400), D

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

Excerpts from Dmitry Tantsur's message of 2017-07-29 20:06:18 +0200: > On 07/28/2017 11:13 PM, Doug Hellmann wrote: > > As Thierry mentioned in his countdown email today, the release team has > > now created the stable branches for most deliverables with type > > "li

Re: [openstack-dev] [release] nominating Sean McGinnis for releases-core

Excerpts from Doug Hellmann's message of 2017-07-27 11:14:51 -0400: > Sean has been increasingly active with the release team this cycle, and > wants to contribute. I think we should go ahead and add him to the > releases-core group. > > Please respond +1/-1. > > Doug > As all of the feedback

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

As Thierry mentioned in his countdown email today, the release team has now created the stable branches for most deliverables with type "library". We have 3 exceptions: 1. python-neutronclient had a late release, so I will be branching it shortly. 2. python-barbicanclient was skipped until

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

Excerpts from Jeremy Stanley's message of 2017-07-28 13:23:32 +: > On 2017-07-28 08:34:18 -0400 (-0400), Doug Hellmann wrote: > [...] > > I wasn't able to come up with a way to disable the link without > > triggering a new build. I didn't want us to have to land a patc

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

Excerpts from Dmitry Tantsur's message of 2017-07-28 12:29:29 +0200: > On 07/28/2017 09:12 AM, Andreas Jaeger wrote: > > On 2017-07-27 21:40, Doug Hellmann wrote: > >> [...] > >> Please encourage everyone there to explore options that require the > >> least

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

Excerpts from Andreas Jaeger's message of 2017-07-28 09:12:59 +0200: > On 2017-07-27 21:40, Doug Hellmann wrote: > > [...] > > Please encourage everyone there to explore options that require the > > least amount of effort. An ideal solution is one we can implement >

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

Excerpts from Doug Hellmann's message of 2017-07-27 19:05:16 -0400: > Excerpts from Jeremy Stanley's message of 2017-07-27 22:07:33 +: > > On 2017-07-27 15:40:22 -0400 (-0400), Doug Hellmann wrote: > > [...] > > > Are we over-emphasizing the scale of the discovery prob

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

Excerpts from Jeremy Stanley's message of 2017-07-27 21:56:35 +: > On 2017-07-27 15:40:22 -0400 (-0400), Doug Hellmann wrote: > [...] > > Regarding point 2, if we don't have the space to host the content > > indefinitely, then we need to set a fixed, but longer, retention

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

Excerpts from Jeremy Stanley's message of 2017-07-27 22:07:33 +: > On 2017-07-27 15:40:22 -0400 (-0400), Doug Hellmann wrote: > [...] > > Are we over-emphasizing the scale of the discovery problem? > > > > When I search for how to install a package on Ubuntu (

Re: [openstack-dev] [all][docs] 404s on docs website after the great reorg

Excerpts from Doug Hellmann's message of 2017-07-27 14:24:53 -0400: > Excerpts from Jeremy Stanley's message of 2017-07-27 16:40:08 +: > > On 2017-07-27 12:23:39 -0400 (-0400), Sean Dague wrote: > > > In the #openstack-nova channel this morning we were debugging some cells > > > v2 things, and

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

[Moving a thread from the openstack-docs list [1] to this list for broader input.] [1] http://lists.openstack.org/pipermail/openstack-docs/2017-July/010069.html Excerpts from 's message of 2017-07-26 07:42:38 -0400: > Yesterday was a very busy day on IRC, with the discussion about the > strategy

Re: [openstack-dev] [all][docs] 404s on docs website after the great reorg

Excerpts from Jeremy Stanley's message of 2017-07-27 16:40:08 +: > On 2017-07-27 12:23:39 -0400 (-0400), Sean Dague wrote: > > In the #openstack-nova channel this morning we were debugging some cells > > v2 things, and ran into the fact that the online docs for this - > >

[openstack-dev] [release] nominating Sean McGinnis for releases-core

Sean has been increasingly active with the release team this cycle, and wants to contribute. I think we should go ahead and add him to the releases-core group. Please respond +1/-1. Doug __ OpenStack Development Mailing

[openstack-dev] [oslo][oslo.db] nominating Jay Pipes for oslo-db-core

I have noticed that Jay has been very deeply involved in several recent design discussions about oslo.db, and he obviously has a great deal of experience in the area, so even though he hasn't been actively reviewing patches recently I think he would be a good addition to the team. I have asked

Re: [openstack-dev] [relmgt] Non-candidacy for the Queens cycle Release management PTL

Excerpts from Sean McGinnis's message of 2017-07-27 08:45:16 -0500: > > > > I have multiple reasons for not running this cycle. First, as part of my > > expanded role at the Foundation my travel commitments increased a bit. > > The Release management PTL role requires regular work: I ended up

Re: [openstack-dev] [infra] Non-candidacy for Queens cycle Infrastructure PTL

Excerpts from Jeremy Stanley's message of 2017-07-25 23:37:40 +: > It has been a pleasure and a privilege to captain the good ship > Infrastructure for the past four cycles, but it's time to let > someone else take a turn at the wheel. I am confident in the ability > of my shipmates to step up

Re: [openstack-dev] [release][freezer][Release-job-failures] Pre-release of openstack/freezer-web-ui failed

Excerpts from jenkins's message of 2017-07-26 13:32:20 +: > Build failed. > > - freezer-web-ui-tarball > http://logs.openstack.org/c1/c151f2ea0c2e6e22d86b38f7916eabd2ce74c5bf/pre-release/freezer-web-ui-tarball/636/ > : FAILURE in 2m 48s > - freezer-web-ui-tarball-signing

Re: [openstack-dev] [release][monasca][designate][requirements] late library release for monasca-statsd

Excerpts from Graham Hayes's message of 2017-07-25 12:24:34 +0100: > On 25/07/17 12:12, Doug Hellmann wrote: > > The monasca team has requested a late release of monasca-statsd. > > As far as I can tell, only other team using the library is designate: > > > > $ what

[openstack-dev] [release][monasca][designate][requirements] late library release for monasca-statsd

The monasca team has requested a late release of monasca-statsd. As far as I can tell, only other team using the library is designate: $ whatuses monasca-statsd deb-designate requirements.txt monasca-statsd>=1.1.0 # Apache-2.0 designate requirements.txt

Re: [openstack-dev] [docs][neutron] doc-migration status

https://doughellmann.com/doc-migration/ and let me know which ones represent content included in other documents, I can update the burndown chart generator to reflect that. Doug > > > On Sun, Jul 23, 2017 at 1:32 PM, Doug Hellmann <d...@doughellmann.com> > wrote: > >

Re: [openstack-dev] [all] [oslo.db] [relational database users] heads up for a MariaDB issue that will affect most projects

Excerpts from Michael Bayer's message of 2017-07-23 16:39:20 -0400: > Hey list - > > It appears that MariaDB as of version 10.2 has made an enhancement > that overall is great and fairly historic in the MySQL community, > they've made CHECK constraints finally work. For all of MySQL's >

Re: [openstack-dev] [docs][neutron] doc-migration status

Excerpts from Kevin Benton's message of 2017-07-23 01:31:25 -0700: > Yeah, I was just thinking it makes it more explicit that we haven't just > skipped doing an admin guide for a particular project. Sure, you can do that. I don't think we want to link to all of those pages from the list of admin

Re: [openstack-dev] [docs][neutron] doc-migration status

tuff in a single guide? > > What is the suggested way on the networking guide as the document expert? If the admin guides for all of those repos are combined, then I can modify the burndown chart generator to not count those as needed. Let me know if that's the best approach. Doug > >

[openstack-dev] [docs][ptl] doc-migration status

We've made huge progress, and are launching the updated landing pages for docs.openstack.org as I write this. Thanks to all of the contributors who have stepped up to write nearly 1,000 patches to improve the health of our documentation! We still have around 70 URLs we expected to see after the

Re: [openstack-dev] [doc] dropping "draft" and series-specific publishing for docs.o.o

Excerpts from Doug Hellmann's message of 2017-07-20 15:11:57 -0400: > Docs team, > > We have two sets of changes happening in openstack-manuals that > will simplify managing the content there, and that will . > > Over the last couple of weeks we have removed several guides from > the repository.

Re: [openstack-dev] [openstack-doc] Attending PTG?

Excerpts from Alexandra Settle's message of 2017-07-21 13:41:58 +: > Hey everyone, > > Put your hand in the air* if you’re attending the PTG! > > Myself and the potential PTL will need to start planning shortly, and it > would be good to get an idea of numbers, and who we are planning for.

[openstack-dev] [doc] dropping "draft" and series-specific publishing for docs.o.o

Docs team, We have two sets of changes happening in openstack-manuals that will simplify managing the content there, and that will . Over the last couple of weeks we have removed several guides from the repository. The remaining guides are not version-specific, which allows us stop creating

Re: [openstack-dev] [all] Cleaning up inactive meetbot channels

Excerpts from Jeremy Stanley's message of 2017-07-19 19:24:00 +: > For those who are unaware, Freenode doesn't allow any one user to > /join more than 120 channels concurrently. This has become a > challenge for some of the community's IRC bots in the past year, > most recently the "openstack"

Re: [openstack-dev] [doc][api] need new reviewers for the api-site and developer.openstack.org

Excerpts from Alexandra Settle's message of 2017-07-19 15:42:42 +: > Hi everyone, > > As you all know, we have been changing the way the documentation team > operates. Chief among those > changes are reducing the workload on the shrinking team. The migration to > move installation, admin,

Re: [openstack-dev] [oslo.config] how to deprecate a name but still have it as conf.

Excerpts from Michael Bayer's message of 2017-07-18 13:21:30 -0400: > On Tue, Jul 18, 2017 at 1:02 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > > Option renaming was originally meant as an operatior-facing feature > > to handle renames for values com

Re: [openstack-dev] [Release-job-failures][telemetry][aodh] Tag of openstack/aodh failed

Excerpts from jenkins's message of 2017-07-17 12:09:25 +: > Build failed. > > - aodh-releasenotes > http://logs.openstack.org/bb/bbc8065ae2db109f415ff1c03f40015a75e5afe7/tag/aodh-releasenotes/1f93729/ > : FAILURE in 2m 58s > The release notes failed to build for aodh's release with the

Re: [openstack-dev] [oslo.config] how to deprecate a name but still have it as conf.

Excerpts from Michael Bayer's message of 2017-07-18 12:34:31 -0400: > In oslo.db, I'd like to rename the option "idle_timeout" to > "connection_recycle_time". > > Following the pattern of using DeprecatedOpt, we get this: > > cfg.IntOpt('connection_recycle_time', >

Re: [openstack-dev] [oslo] PTL nominations

Excerpts from ChangBo Guo's message of 2017-07-17 23:14:54 +0800: > Hi oslo folks, > > The PTL nomination week is fast approaching [0], and as you might have > guessed by the subject of this email, I am not planning to run for Queens, > I'm still in the team and give some guidance about oslo

Re: [openstack-dev] [all] New setuptools release, and the world is broken

Excerpts from Jeremy Stanley's message of 2017-07-14 16:18:04 +: > On 2017-07-14 16:05:36 + (+), Jesse Pretorius wrote: > > On 7/14/17, 4:54 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: > [...] > > > I wonder if we could convin

Re: [openstack-dev] [all] New setuptools release, and the world is broken

Excerpts from Jeremy Stanley's message of 2017-07-14 15:17:52 +: > On 2017-07-14 10:50:50 -0400 (-0400), Doug Hellmann wrote: > > Excerpts from Jesse Pretorius's message of 2017-07-14 08:32:48 +: > > > FYI if you see the following error in your job logs, you have the new

Re: [openstack-dev] [all] New setuptools release, and the world is broken

Excerpts from Jesse Pretorius's message of 2017-07-14 08:32:48 +: > FYI if you see the following error in your job logs, you have the new > setuptools to thank: > > AttributeError: Distribution instance has no attribute 'install_requires' > > I’ve registered

[openstack-dev] [docs][all] trouble enabling warning-is-error due to "already registered" warnings

tl;dr - A few project that use wsme.sphinxext or some other extensions that register similar directives multiple times have been unable to turn on the warning-is-error flag as part of the doc migration. The solution to that problem is to add some warning suppression information to the local

[openstack-dev] [all][doc] migration update

We have recovered old tagged content from https://docs.openstack.org/developer/$project and moved them to https://docs.openstack.org/$project/$version. As part of this process, we also kept any builds from the tip of the mitaka, newton, and ocata branches using those names as $version. And

Re: [openstack-dev] [release][glance] Release countdown for week R-6, July 14 - July 21

Excerpts from Thierry Carrez's message of 2017-07-13 17:44:13 +0200: > glance-store and instack haven't made a Pike release yet: if nothing is > done by July 20, one release will be forced (on master HEAD) so that we > have something to cut a stable branch from. I have prepared a patch for a

Re: [openstack-dev] [all] Announcing openstack-sigs ML

Excerpts from Melvin Hillsman's message of 2017-07-13 08:51:16 -0500: >1. Start the openstack-sigs mailing list You can subscribe by visiting http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs Doug __

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

trove to reuse database > vendor supplied containers. Performance of databases in VM's poor > compared to databases on bare-metal. > > > > Doug Hellmann: > > > Does "service VM" need to be a first-class thing? Akanda creates > > them, using

[openstack-dev] [all][docs] using openstackdocstheme

As projects review patches related to the migration project, please keep in mind that only *official* projects listed as being under TC governance [1] should use the openstackdocs theme. If your documentation is not being published to docs.openstack.org, please use a different theme. Doug [1]

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

his is not a project under the TC governance. I have removed it from the list. Thanks, Doug > > Akihiro > > 2017-07-11 2:26 GMT+09:00 Doug Hellmann <d...@doughellmann.com>: > > According to the dashboard, it looks like we still have almost 100 > > repositories with d

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

Excerpts from gordon chung's message of 2017-07-11 14:23:41 +: > > On 10/07/17 01:26 PM, Doug Hellmann wrote: > > openstack/ceilometer-powervm > > openstack/ceilometermiddleware > > i don't believe there are docs for these. ceilometermiddleware is a > simple wsg

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

Excerpts from Renat Akhmerov's message of 2017-07-11 12:08:23 +0700: > On 11 Jul 2017, 00:27 +0700, wrote: > > > openstack/mistral-dashboard > > openstack/mistral-extra > > These two are not supposed to have docs at all. We should probably just > remove the “doc” folder and corresponding CI

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

Excerpts from Anne Gentle's message of 2017-07-10 13:14:52 -0400: > On Mon, Jul 10, 2017 at 1:11 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from sfinucan's message of 2017-07-10 17:20:37 +0100: > >> On Fri, 2017-07-07 at 15:58 +0100, s

[openstack-dev] [docs] migration status

Progress After more than 580 patches, the migration is moving along very well. We do still have quite a few repositories that haven't been updated [1], though, so please help us trim that list. It's really important that we finish the migration before we create stable/pike branches to

[openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration startin

According to the dashboard, it looks like we still have almost 100 repositories with documentation that have no patches with the doc-migration topic, indicating that they have not started moving content or updating the theme. I have tried to tag those teams in the subject, but I may have missed

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

Excerpts from sfinucan's message of 2017-07-10 17:20:37 +0100: > On Fri, 2017-07-07 at 15:58 +0100, sfinu...@redhat.com wrote: > > tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just > > remove the feature at this point. However, this is going to necessitate some > >

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

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 stable/pike branch at the end of this cycle, so that we have a way to deal with bugs in existing pike releases, but I

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

Excerpts from sfinucan's message of 2017-07-07 15:58:10 +0100: > tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just > remove the feature at this point. However, this is going to necessitate some > mechanical changes for most projects with docs and this mail serves as a

Re: [openstack-dev] [tc] Status update, July 7th

Excerpts from Thierry Carrez's message of 2017-07-07 10:19:48 +0200: > > == Need for a TC meeting next Tuesday == > > I propose we have a meeting next week to discuss the next steps in > establishing the vision. I feel like we should approve it soon, > otherwise we'll get too close to the vision

[openstack-dev] [docs][ptls] redirects for migrated docsets

We've had a few folks notice that redirects from docs.o.o/$project/ to docs.o.o/$project/latest are missing. The htaccess file for those redirects is now built from a template. To appear in the list, projects need to be added to the docs repo data file [1]. We have been adding projects as we

Re: [openstack-dev] [all][tc] Wiki (was: How to deal with confusion around "hosted projects")

Excerpts from Flavio Percoco's message of 2017-07-03 16:11:44 +0200: > On 03/07/17 13:58 +0200, Thierry Carrez wrote: > >Flavio Percoco wrote: > >> Sometimes I wonder if we still need to maintain a Wiki. I guess some > >> projects still use it but I wonder if the use they make of the Wiki could >

Re: [openstack-dev] [docs][all][ptl] doc-migration status

> On Jul 3, 2017, at 10:34 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > Because we still have a lot of work to do in the openstack-manuals > repo, the documentation team has started landing patches to remove > the content that is being migrated into project reposi

Re: [openstack-dev] [docs][all][ptl] doc-migration status

> On Jul 3, 2017, at 10:34 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > After a busy week last week, we made some good progress with the > documentation migration project. We still have quite a few repositories > that haven't been started, though, so please keep w

[openstack-dev] [docs][all][ptl] doc-migration status

After a busy week last week, we made some good progress with the documentation migration project. We still have quite a few repositories that haven't been started, though, so please keep working. If you need assistance preparing or reviewing the patches, let us know with a follow-up email to this

[openstack-dev] [doc][all][ptl] doc migration issue with sphinxcontrib-pecanwsme

A couple of teams have run into a problem with the sphinxcontrib-pecanwsme extension emitting warnings which are then treated as errors when the Sphinx flag warning-is-error is set to True. For the time being, skip the step of setting that flag to True (but still try to minimize the number of

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Excerpts from Chris Friesen's message of 2017-06-29 09:35:01 -0600: > On 06/29/2017 09:23 AM, Monty Taylor wrote: > > > We are already WELL past where we can solve the problem you are describing. > > Pandora's box has been opened - we have defined ourselves as an Open > > community. > > Our only

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

Excerpts from Andreas Jaeger's message of 2017-06-28 08:45:47 +0200: > For those migrating from oslosphinx to openstackdocstheme, I strongly > advise to follow the docs for openstackdocstheme 1.11 on how to set it up: > > https://docs.openstack.org/openstackdocstheme/latest/ > > Andreas Another

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

Excerpts from Alexandra Settle's message of 2017-06-23 12:09:41 +: > Hi everyone, > > This morning (afternoon) the specification for the documentation migration > was merged. Thanks to all that took time to review :) > > You can now view here in all its glory: >

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Excerpts from Thierry Carrez's message of 2017-06-28 16:50:01 +0200: > Hi everyone, > > Two weeks ago, as a result of a discussion at the Board+TC+UC workgroup > working on "better communicating what is openstack", I started a > thread[1] about moving away from big tent terminology. The thread

Re: [openstack-dev] [stable][release] Last release date vs End of Life date

Excerpts from Tony Breeds's message of 2017-06-27 16:51:37 +1000: > Hi all, > Up 'til now we haven't set a last release date for a stable branch > approaching end of life. It seems like formalizing that would be a good > thing. > > This comes up as we need time to verify that said release

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

Excerpts from Jeremy Stanley's message of 2017-06-27 17:55:57 +: > On 2017-06-22 16:27:34 -0400 (-0400), Doug Hellmann wrote: > [...] > > The new job is configured to update the docs for all repos every > > time a patch is merged, not just when we tag releases. The server

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

to review the spec as this affects > *everyone*. > > See: https://review.openstack.org/#/c/472275/ > > I will be PTO from the 9th – 19th of June. If you have any pressing concerns, > please email me and I will get back to you as soon as I can, or, email Doug > Hellmann and

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

so if you don’t have any configuration guide instructions for example then you don’t need to create the configuration/ directory. If you add me as a reviewer, I’ll help make sure you have it organized as expected. And if you use the doc-migration tag the other folks working on the migr

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

Renat Akhmerov > @Nokia > > 23 июня 2017 г., 3:32 +0700, Doug Hellmann <d...@doughellmann.com>, писал: >> Excerpts from Alexandra Settle's message of 2017-06-08 15:17:34 +: >>> Hi everyone, >>> >>> Doug and I have written up a spec following on from

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

to review the spec as this affects > *everyone*. > > See: https://review.openstack.org/#/c/472275/ > > I will be PTO from the 9th – 19th of June. If you have any pressing concerns, > please email me and I will get back to you as soon as I can, or, email Doug > Hellmann and

Re: [openstack-dev] [stable]requirements] Bootstrapiing requirements-stable-core

Excerpts from Tony Breeds's message of 2017-06-22 11:48:09 +1000: > Hi All, > Recently it's been clear that we need a requirements-stable team. > Until npw that's been handled by the release managers and the > stable-maint-core team. > > With the merge of [1] The have the groundwork for that

[openstack-dev] [kuryr][Release-job-failures] Release of openstack/kuryr-tempest-plugin failed

It looks like the kuryr-tempest-plugin repository has a documentation job set up but no documentation. http://logs.openstack.org/1e/1ee40b0f0ee4e92209b8ccff6d74f4980f6234ab/release/kuryr-tempest-plugin-docs-ubuntu-xenial/7f096fd/console.html#_2017-06-20_17_03_00_590629 --- Begin forwarded

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Excerpts from Curtis's message of 2017-06-19 18:56:25 -0600: > On Sun, Jun 18, 2017 at 5:35 AM, Amrith Kumar wrote: > > Trove has evolved rapidly over the past several years, since integration in > > IceHouse when it only supported single instances of a few databases.

Re: [openstack-dev] [deployment][kolla][openstack-ansible][openstack-helm][tripleo] ansible role to produce oslo.config files for openstack services

Excerpts from Michał Jastrzębski's message of 2017-06-16 15:50:54 -0700: > So I'm trying to figure out how to actually use it. > > We (and any other container based deploy..) will run into some > chicken/egg problem - you need to deploy container to generate big > yaml with defaults, then you

Re: [openstack-dev] [tc] Status update, Jun 16

Excerpts from Thierry Carrez's message of 2017-06-16 11:17:30 +0200: > == Need for a TC meeting next Tuesday == > > In order to make progress on the Pike goal selection, I think a > dedicated IRC meeting will be necessary. We have a set of valid goals > proposed already: we need to decide how

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

Excerpts from Ghanshyam Mann's message of 2017-06-16 23:05:08 +0900: > On Fri, Jun 16, 2017 at 10:57 PM, Sean Dague wrote: > > On 06/16/2017 09:51 AM, Sean McGinnis wrote: > >>> > >>> It would be useful to provide detailed examples. Everything is trade > >>> offs, and having the

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

Excerpts from gordon chung's message of 2017-06-15 20:24:06 +: > > On 15/06/17 03:23 PM, Doug Hellmann wrote: > > > > We are very open with our hosting, allowing projects that have not > > yet, and may never, sign up to be governed by the TC to use our > > infr

Re: [openstack-dev] [keystone][glance][nova][neutron][horizon][cinder][osc][swift][manila][telemetry][heat][ptls][all][tc][docs] Documentation migration spec

https://review.openstack.org/#/c/472275/ > > > > I will be PTO from the 9th – 19th of June. If you have any pressing > > concerns, please email me and I will get back to you as soon as I can, or, > > email Doug Hellmann and hopefully he will be able to assist you. > >

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

Excerpts from Brian Rosmaita's message of 2017-06-15 13:04:39 -0400: > This isn't a glance-specific problem though we've encountered it quite > a few times recently. > > Briefly, we're gating on Tempest jobs that tempest itself does not > gate on. This leads to a situation where new tests can be

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

Excerpts from Jay Pipes's message of 2017-06-15 12:06:53 -0400: > On 06/15/2017 11:59 AM, Thierry Carrez wrote: > > Jay Pipes wrote: > >> While I personally agree that Fuel should be moved out of the official > >> projects list, I'd like to point out that Triple-O is virtually entirely > >> a Red

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

Excerpts from gordon chung's message of 2017-06-15 18:56:22 +: > > On 15/06/17 02:05 PM, Davanum Srinivas wrote: > > Example from https://www.meetup.com/openstack/events/237621777/ > > "Platform9 recently open-sourced Project Mors and VM HA as part of the > > OpenStack Big Tent initiative." >

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

Excerpts from Thierry Carrez's message of 2017-06-15 10:48:21 +0200: > Hi everyone, > > Part of reducing OpenStack perceived complexity is to cull projects that > have not delivered on their initial promises. Those are always difficult > discussions, but we need to have them. In this email I'd

Re: [openstack-dev] [keystone][glance][nova][neutron][horizon][cinder][osc][swift][manila][telemetry][heat][ptls][all][tc][docs] Documentation migration spec

/472275/ > > I will be PTO from the 9th – 19th of June. If you have any pressing concerns, > please email me and I will get back to you as soon as I can, or, email Doug > Hellmann and hopefully he will be able to assist you. > > Thanks, > > Alex > > [0] http://li

Re: [openstack-dev] [qa][requirements][all] removing global pins for linters

Excerpts from Sean Dague's message of 2017-06-12 07:09:12 -0400: > On 06/11/2017 11:30 AM, Doug Hellmann wrote: > > The recent thread about updating the pylint version in > > global-requirements.txt raised an issue because it was trying to > > update the pylint version f

[openstack-dev] [qa][requirements][all] removing global pins for linters

The recent thread about updating the pylint version in global-requirements.txt raised an issue because it was trying to update the pylint version for all projects using it, but some teams were not ready for the new tests in the latest version. I thought we had dealt with that kind of case in the

Re: [openstack-dev] [oslo.db] Stepping down from core

Excerpts from Roman Podoliaka's message of 2017-06-11 17:32:49 +0300: > Hi all, > > I recently changed job and hasn't been able to devote as much time to > oslo.db as it is expected from a core reviewer. I'm no longer working > on OpenStack, so you won't see me around much. > > Anyway, it's been

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

Excerpts from Flavio Percoco's message of 2017-06-09 16:52:25 +: > On Fri, Jun 9, 2017 at 11:30 AM Britt Houser (bhouser) > wrote: > > > How does confd run inside the container? Does this mean we’d need some > > kind of systemd in every container which would spawn both

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

Excerpts from Alex Schultz's message of 2017-06-09 10:54:16 -0600: > I ran into a case where I wanted to add python-tripleoclient to > test-requirements for tripleo-heat-templates but it's not in the > global requirements. In looking into adding this, I noticed that > python-tripleoclient and

Re: [openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

Excerpts from Akihiro Motoki's message of 2017-06-09 03:53:34 +0900: > Hi all, > > Is your project ready for pylint 1.7.1? > If you use pylint in your pep8 job, it is worth checked. > > Our current version of pylint is 1.4.5 but it is not safe in python 3.5. > The global-requirements update was

[openstack-dev] [release][glance][barbican][telemetry][keystone][designate][congress][magnum][searchlight][swift][tacker] unreleased libraries

We have several teams with library deliverables that haven't seen any releases at all yet this cycle. Please review the list below, and if there are changes on master since the last release prepare a release request. Remember that because of the way our CI system works, patches that land in

[openstack-dev] [release][barbican][congress][designate][neutron][zaqar] missing pike-2 milestone releases

We have several projects with deliverables following the cycle-with-milestones release model without pike 2 releases. Please check the list below and prepare those release requests as soon as possible. Remember that this milestone is date-based, not feature-based, so unless your gate is completely

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

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

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

Excerpts from Flavio Percoco's message of 2017-06-08 22:28:05 +: > Unless I'm missing something, to use confd with an OpenStack deployment on > k8s, we'll have to do something like this: > > * Deploy confd in every node where we may want to run a pod (basically > wvery node) Oh, no, no.

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

> On Jun 8, 2017, at 4:29 PM, Fox, Kevin M wrote: > > That is possible. But, a yaml/json driver might still be good, regardless of > the mechanism used to transfer the file. > > So the driver abstraction still might be useful. Why would it be useful to have oslo.config

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

Excerpts from Emilien Macchi's message of 2017-06-08 22:20:34 +0200: > On Thu, Jun 8, 2017 at 8:49 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Steven Dake (stdake)'s message of 2017-06-08 17:51:48 +: > >> Doug, > >> > >> In

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

Excerpts from Fox, Kevin M's message of 2017-06-08 20:08:25 +: > Yeah, I think k8s configmaps might be a good config mechanism for k8s based > openstack deployment. > > One feature that might help which is related to the etcd plugin would be a > yaml/json plugin. It would allow more native

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

> > Ping me in #openstack-kolla if you have more questions. > > Regards > -steve > > -Original Message- > From: Doug Hellmann <d...@doughellmann.com> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-d

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