[openstack-dev] [release] skipping meeting today

With several members of the team unavailable today, and the release candidates still slowly trickling in, I think it makes more sense for us to catch up with each other Monday than to have our regular meeting today. I'll look for folks in #openstack-release around 14:00 UTC Monday. Doug

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

Excerpts from Octave J. Orgeron's message of 2017-02-02 15:08:14 -0700: > Comments below.. > > On 2/2/2017 1:08 PM, Doug Hellmann wrote: > > Excerpts from Octave J. Orgeron's message of 2017-02-02 12:16:15 -0700: > >> Hi Doug, > >> > >> Comm

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

Excerpts from Octave J. Orgeron's message of 2017-02-02 12:16:15 -0700: > Hi Doug, > > Comments below.. > > Thanks, > Octave > > On 2/2/2017 11:27 AM, Doug Hellmann wrote: > > Excerpts from Octave J. Orgeron's message of 2017-02-02 09:40:23 -0700: > >> Hi

[openstack-dev] [release] Release countdown for week R-2, 6-10 Feb

Focus - We are in the release candidate phase of the cycle. All project teams should be fixing last minute release-critical bugs and testing the prepared release candidates for their deliverables. Release Tasks - The translation team will be increasing their work over the next

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

behavior need to know about the storage engine? Doug > > Thanks, > Octave > > On 2/2/2017 6:46 AM, Doug Hellmann wrote: > > Excerpts from Octave J. Orgeron's message of 2017-02-01 20:33:38 -0700: > >> Hi Folks, > >> > >> I'm working on

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

Excerpts from Octave J. Orgeron's message of 2017-02-01 20:33:38 -0700: > Hi Folks, > > I'm working on adding support for MySQL Cluster to the core OpenStack > services. This will enable the community to benefit from an > active/active, auto-sharding, and scale-out MySQL database. My approach

Re: [openstack-dev] [neutron] [release] misleading release notes

Excerpts from Dean Troyer's message of 2017-02-01 22:41:46 -0600: > On Wed, Feb 1, 2017 at 8:13 PM, Armando M. wrote: > > I suspect what happens is that someone revises the content at a later date > > and reno associated the last timestamp of the release note with release > >

Re: [openstack-dev] [neutron] [release] misleading release notes

Excerpts from Armando M.'s message of 2017-02-01 18:13:46 -0800: > Hi, > > There is something puzzling about release notes. I don't see 8.0.0 [1], and > it looks like features released in Mitaka are being advertised as Newton > features [2]. For instance, [3] 'Agent availability zones' shows as a

Re: [openstack-dev] [requirements] changing the order of values in upper-constraints.txt

Excerpts from Andreas Jaeger's message of 2017-02-01 15:37:15 +0100: > On 2017-02-01 15:27, Doug Hellmann wrote: > > [...] > > Another option was to have the release bot continually propose > > updates to the same patch, like we do with the global requirements > >

[openstack-dev] [python3][ptg][goal] planning for python 3 discussions at the PTG

I've set up an etherpad for planning the python 3 goal work at the PTG [1]. We have space set aside for Monday and Tuesday, but I know some (all?) of the people involved will have multiple topics they need to cover those days so I also think it would be a good idea for us to coordinate who can be

Re: [openstack-dev] [requirements] changing the order of values in upper-constraints.txt

Excerpts from Tony Breeds's message of 2017-02-01 21:18:54 +1100: > On Wed, Jan 18, 2017 at 04:34:56PM -0500, Doug Hellmann wrote: > > When I tried to merge the upper-constraints updates for the library > > releases we did today, I ran into quite a lot of merge conflicts &g

Re: [openstack-dev] [requirements][ffe] Jinja2 2.9.5 upper constraint

Excerpts from Major Hayden's message of 2017-01-30 11:55:39 -0600: > Hello there, > > I just submitted a patch[0] to bump Jinja2's upper constraint to 2.9.5. > > We previously set the upper constraint to 2.8.1[1] when a change appeared > that broke Ansible. The bug caused the `groupby` filter

[openstack-dev] [release] libraries that still need stable/ocata branches

We are now past the library release freeze, and all libraries should have their final release and be ready for a stable/ocata branch. The following libraries have not yet branched: $ list-deliverables --no-stable-branch -v --model cycle-with-intermediary --type library ceilometermiddleware

Re: [openstack-dev] [OpenStack][Dev] Changes coming to Product WG & Enterprise WG

Excerpts from Barrett, Carol L's message of 2017-01-27 15:56:21 +: > After 35+ yrs in the Technology Industry, I have decided it's time for a > change. I will be retiring from Intel on February 2nd. > > OpenStack has been a highlight of my career and I owe much of that to you > all. It's

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

Excerpts from Takashi Yamamoto's message of 2017-01-26 11:42:48 +0900: > hi, > > On Sat, Jan 14, 2017 at 2:17 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Dariusz Śmigiel's message of 2017-01-13 09:11:01 -0600: > >> 2017-01-12 21:43 GMT

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

Excerpts from jenkins's message of 2017-01-26 19:26:35 +: > Build failed. > > - puppet-watcher-tarball > http://logs.openstack.org/3d/3dd9ce72aadf433ee5a0381c78e641691bcce8eb/release/puppet-watcher-tarball/75519e7/ > : SUCCESS in 2m 20s The tarball generated had version number 10.1.0

[openstack-dev] [release] Release countdown for week R-3 (Ocata RC1 Target), 30 Jan - 3 Feb

Focus - This week is the Release Candidate target deadline for all milestone-based projects. Only bug fixes and previously agreed feature freeze extensions should be merged into master branches. The RC1 is only 1 week after feature freeze, which is different from our usual 2 week freeze

Re: [openstack-dev] [requirements][docs] updating the minimum version of sphinx

Excerpts from Andreas Jaeger's message of 2017-01-25 08:40:16 +0100: > On 2017-01-25 08:24, Andreas Jaeger wrote: > > On 2017-01-25 05:03, Matthew Thode wrote: > >> On 01/24/2017 09:57 PM, Matthew Thode wrote: > >>> Basically I'd like to ask the docs people if they are fine with updating > >>>

Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable

Excerpts from Ian Cordasco's message of 2017-01-24 14:55:31 -0500: > -Original Message- > From: Michał Jastrzębski > Reply: OpenStack Development Mailing List (not for usage questions) >

Re: [openstack-dev] [release][stable] nominating Alan Pevec (apevec) for stable release core

Excerpts from Doug Hellmann's message of 2017-01-18 09:16:53 -0500: > Based on Tony's recommendation, and Alan's recent review work, I > am nominating Alan Pevec (apevec) to have core reviewer rights on > stable releases in the openstack/releases repository. > > Release team, please either +1 or

[openstack-dev] [release][ptl][telemetry][barbican][cloudkitty][congress][glance][ironic][magnum][manila][murano][neutron][searchlight][vitrage] last chance to release a client next week

We have quite a few client libraries for which there are no Ocata releases at all: python-aodhclient python-barbicanclient python-brick-cinderclient-ext python-cloudkittyclient python-congressclient python-glanceclient python-ironic-inspector-client python-magnumclient python-manilaclient

[openstack-dev] [release][ptl] Release countdown for week R-4 (Ocata-3 Milestone), Jan 23-27

We're rapidly approaching the end of the Ocata cycle. There are several deadlines coming up within the next few weeks, so please review the schedule and make sure you understand how they affect your teams. Focus - This week begins Feature Freeze for all milestone-based projects. No feature

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

Excerpts from Mikhail Fedosin's message of 2017-01-19 12:48:13 +0300: > Hi Matt! > > This should be discussed, for sure, but there is a lot of potential. In > general, it depends on how far we are willing to go. In the minimum > approximation we can seamlessly replace Glance with Glare and

[openstack-dev] [requirements] changing the order of values in upper-constraints.txt

When I tried to merge the upper-constraints updates for the library releases we did today, I ran into quite a lot of merge conflicts with the Oslo libraries. I'm exploring options for reducing the likelihood that those sorts of conflicts will occur with a few patches that change how we generate

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

Excerpts from Mikhail Fedosin's message of 2017-01-18 19:54:01 +0300: > Hello! > > In this letter I want to tell you the current status of Glare project and > discuss its future development within the entire OpenStack community. > > In the beginning I have to say a few words about myself - my

Re: [openstack-dev] [requirements][nova][horizon][release] unable to update constraint for python-novaclient to 7.0.0

Nice work tracking that down, thanks! Excerpts from Diana Clarke's message of 2017-01-18 12:19:35 -0500: > Fixed. I'm a big girl now, lol. > > Cheers, > > --diana > > On Wed, Jan 18, 2017 at 9:42 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > The autom

[openstack-dev] [requirements][nova][horizon][release] unable to update constraint for python-novaclient to 7.0.0

The automatically produced patch to update the constraints to include python-novaclient 7.0.0 are failing on the horizon test job. Can someone please look into whether that is still actually an issue so we can be sure of including the client release in Ocata? Thanks, Doug

[openstack-dev] [release][stable] nominating Alan Pevec (apevec) for stable release core

Based on Tony's recommendation, and Alan's recent review work, I am nominating Alan Pevec (apevec) to have core reviewer rights on stable releases in the openstack/releases repository. Release team, please either +1 or raise any concerns you have. Doug

[openstack-dev] [release][ptl] final reminder about non-client library releases

The deadline for non-client library releases is Thursday 19 Jan. We do not grant Feature Freeze Extensions for any libraries, so that is a hard freeze date. Any feature work that requires updates to non-client libraries should be prioritized so it can be completed by that time. We have quite a

Re: [openstack-dev] [release][requirements] disable constraint bot updates for our own libraries

Excerpts from Dmitry Tantsur's message of 2017-01-17 18:48:59 +0100: > On 01/17/2017 04:55 PM, Doug Hellmann wrote: > > In this review for the ironic-inspector-client newton release [1], Alan > > pointed out that the new release was pulled into our master requirements > > be

Re: [openstack-dev] [release][requirements] disable constraint bot updates for our own libraries

Excerpts from Jeremy Stanley's message of 2017-01-17 18:15:59 +: > On 2017-01-17 18:48:59 +0100 (+0100), Dmitry Tantsur wrote: > [...] > > In theory there is nothing wrong with this, as 1.10 is the latest > > release indeed. In practice, that means pulling in something with > > stable/newton

Re: [openstack-dev] [devstack] issues with requiring python3 only tool?

Excerpts from Sean Dague's message of 2017-01-17 11:50:39 -0500: > On 01/17/2017 11:46 AM, Victor Stinner wrote: > > Le 17/01/2017 à 17:36, Sean Dague a écrit : > >> When putting the cli interface on it, I discovered python3's argparse > >> has subparsers built in. This makes building up the cli

Re: [openstack-dev] [security] FIPS compliance

Excerpts from Ian Cordasco's message of 2017-01-17 05:59:13 -0600: > On Tue, Jan 17, 2017 at 4:11 AM, Yolanda Robla Mota > wrote: > > Hi, in previous threads, there have been discussions about enabling FIPS, > > and the problems we are hitting with md5 inside OpenStack: > >

[openstack-dev] [release][requirements] disable constraint bot updates for our own libraries

In this review for the ironic-inspector-client newton release [1], Alan pointed out that the new release was pulled into our master requirements because the constraints bot saw it as a newer release. That doesn't seem like something we want to have happen, as a general case. Should we update the

[openstack-dev] [release][all][ptl][stable] the process for creating stable/ocata branches

As mentioned previously [1], it is now possible for teams to set up stable branches when they are ready. We will be taking advantage of this new capability as we approach the end of the Ocata cycle and start preparing final releases. The release team will not be automatically setting up branches

Re: [openstack-dev] [congress][oslo.config][keystone] NoSuchOptError: no such option project_domain_name in group [keystone_authtoken]

Excerpts from Eric K's message of 2017-01-12 14:31:58 -0800: > On a freshly stacked devstack (Jan 12), attempting to access > `cfg.CONF.keystone_authtoken.project_domain_name` gave the error: > NoSuchOptError: no such option project_domain_name in group > [keystone_authtoken] > > I¹m a little

[openstack-dev] [release][ptl] not planning to serve as release PTL for Pike

I announced this at the release team meeting on 6 Jan, but thought I should also post to the list as well: I do not plan to serve as the Release Management team PTL for the Pike release cycle. It has been my pleasure to serve as PTL, and we've almost finished the automation work that I

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

Excerpts from Dariusz Śmigiel's message of 2017-01-13 09:11:01 -0600: > 2017-01-12 21:43 GMT-06:00 Takashi Yamamoto : > > hi, > > > > On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote: > >> Hi > >> > >> As of today, the project neutron-vpnaas is no

Re: [openstack-dev] [release] Release countdown for week R-5, Jan 16-20

p://git.openstack.org/cgit/openstack/releases/tree/README.rst#n66 > [2] https://releases.openstack.org/ocata/schedule.html > > Best Regards > Chaoyi Huang (joehuang) > > > From: Doug Hellmann [d...@doughellmann.com] > Sent: 13 Jan

[openstack-dev] [release] Release countdown for week R-5, Jan 16-20

Focus - Feature work and major refactoring should be starting to wrap up as we approach the third milestone and various feature and release freeze dates. The deadline for non-client library releases is Thursday 19 Jan. We do not grant Feature Freeze Extensions for any libraries, so that is a

Re: [openstack-dev] [release] subscribe to the OpenStack release calendar

Excerpts from Doug Hellmann's message of 2017-01-06 15:19:35 -0500: > > > On Jan 6, 2017, at 1:14 PM, Julien Danjou <jul...@danjou.info> wrote: > > > > On Fri, Jan 06 2017, Doug Hellmann wrote: > > > > Hi Doug, > > > >> The link for the

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Steven Dake (stdake)'s message of 2017-01-11 14:50:31 +: > Thierry, > > I am not a big fan of the separate gerrit teams we have instituted inside the > Kolla project. I always believed we should have one core reviewer team > responsible for all deliverables to avoid not just

Re: [openstack-dev] [tc][goals] Microversions in OpenStack projects

Excerpts from LAM, TIN's message of 2017-01-09 21:43:55 +: > As noted in [1], "Add microversion to REST APIs" is one of the cross-project > community goals. Given the scope and the fact there is still discussion on > what "microversion" means to each project and the exact technical >

[openstack-dev] [py3][devstack] being explicit about enabling python 3 for services

At the BCN summit, one of the suggestions for enabling Python 3 in devstack was to provide an explicit whitelist of services that should be run under Python 3. The first phase of that is in [1], which adds both a white and black list. The automatic detection using the python classifiers is

Re: [openstack-dev] [release] subscribe to the OpenStack release calendar

> On Jan 6, 2017, at 1:14 PM, Julien Danjou <jul...@danjou.info> wrote: > > On Fri, Jan 06 2017, Doug Hellmann wrote: > > Hi Doug, > >> The link for the Ocata schedule is >> https://releases.openstack.org/ocata/schedule.ics >> >> We wil

[openstack-dev] [release] subscribe to the OpenStack release calendar

The release team has made it possible to subscribe to an ICS version of the Ocata release schedule. This means you can have the full schedule of countdown weeks and various cross-project deadlines visible in your normal calendaring application, and receive updates automatically. The link for the

[openstack-dev] [release] Release countdown for week R-6, 2-6 Jan

Happy New Year, everyone! Focus - Feature work and major refactoring should be well under way as we approach the third milestone and various feature and release freeze dates. The deadline for non-client library releases is R-5 (19 Jan). We do not grant Feature Freeze Extensions for any

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Michał Jastrzębski's message of 2017-01-05 11:45:49 -0800: > I think total separation of projects would require much larger > discussion in community. Currently we agreed on having kolla-ansible > and kolla-k8s to be deliverables under kolla umbrella from historical > reasons. Also I

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Sam Yaple's message of 2017-01-05 18:22:54 +: > On Thu, Jan 5, 2017 at 6:12 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > > Excerpts from Sam Yaple's message of 2017-01-05 17:02:35 +: > > > On Thu, Jan 5, 2017 at 4:54 PM, Jeremy Stanley &l

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Sam Yaple's message of 2017-01-05 17:02:35 +: > On Thu, Jan 5, 2017 at 4:54 PM, Jeremy Stanley wrote: > > > On 2017-01-05 16:46:36 + (+), Sam Yaple wrote: > > [...] > > > I do feel this is slightly different than whats described. Since it is > > not >

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Sam Yaple's message of 2017-01-05 15:58:45 +: > Involving kolla-ansible and kolla-kubernetes in a decision about kolla-salt > (or kolla-puppet, or kolla-chef) is silly since the projects are unrelated. > That would be like involving glance when cinder has a new service because >

Re: [openstack-dev] [all][py3][swift][devstack] USE_PYTHON3 works! (well somewhat)

Excerpts from John Dickinson's message of 2017-01-03 12:00:07 -0800: > > On 3 Jan 2017, at 10:38, Doug Hellmann wrote: > > > Excerpts from John Dickinson's message of 2017-01-03 09:02:19 -0800: > >> > >> On 2 Jan 2017, at 13:06, Davanum Srinivas wrote: > >

Re: [openstack-dev] [oslo] Not running for Oslo PTL for Pike

Excerpts from Joshua Harlow's message of 2017-01-03 12:03:44 -0800: > Hi Oslo folks (and others), > > Happy new year! > > After serving for about a year I think it's a good opportunity for > myself to let another qualified individual run for Oslo PTL (seems > common to only go for two terms

Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects

Excerpts from Andreas Jaeger's message of 2017-01-03 19:29:25 +0100: > On 01/03/2017 05:59 PM, Anne Gentle wrote: > > > > What happens is you get a special notification and link to > > CONTRIBUTING.txt (or rst, but only after comparing branches) as in this > > screenshot: > > > >

Re: [openstack-dev] [all][py3][swift][devstack] USE_PYTHON3 works! (well somewhat)

Excerpts from John Dickinson's message of 2017-01-03 09:02:19 -0800: > > On 2 Jan 2017, at 13:06, Davanum Srinivas wrote: > > > Folks, > > > > Short Story : > > [1] has merged in devstack, it adds support for a python 3.5 based > > up/down devstack test that just starts services and brings them

Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects

Excerpts from Anne Gentle's message of 2017-01-03 10:26:28 -0600: > On Tue, Jan 3, 2017 at 12:04 AM, Andreas Jaeger wrote: > > > On 01/03/2017 04:01 AM, Anne Gentle wrote: > > > [...] > > > Doug, I think the include in Sphinx can be a raw txt file? Then we get > > > the best of

Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects

Excerpts from Andreas Jaeger's message of 2017-01-03 07:04:51 +0100: > On 01/03/2017 04:01 AM, Anne Gentle wrote: > > [...] > > Doug, I think the include in Sphinx can be a raw txt file? Then we get > > the best of both worlds - rendered on both docs.openstack.org > >

Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects

Excerpts from Paul Belanger's message of 2016-12-24 15:23:35 -0500: > On Wed, Dec 21, 2016 at 10:17:42AM -0600, Ian Cordasco wrote: > > -Original Message- > > From: Andrey Kurilin > > Reply: OpenStack Development Mailing List (not for usage questions) > >

Re: [openstack-dev] [nova] Consistency in versioned notification payloads

Excerpts from Matt Riedemann's message of 2016-12-30 16:23:24 -0600: > While reviewing patches today to add versioned notifications for CRUD > operations on aggregates and flavors I've come across some inconsistency. > > The existing non-versioned notification for aggregate.delete just sends >

[openstack-dev] [release] Release countdown for week R-8, 26-30 Dec

Focus - Feature work and major refactoring should be well under way as we pass the second milestone. The deadline for non-client library releases is R-5 (19 Jan). We do not grant Feature Freeze Extensions for any libraries, so that is a hard freeze date. Any feature work that requires

Re: [openstack-dev] [release] reno 2.0.0

Excerpts from Doug Hellmann's message of 2016-12-21 15:54:44 -0500: > This new version of reno is a major rewrite of the repository scanner > logic and includes some breaking changes to the internal API (the > command line remains the same). Those changes broke the release > announcement job, and

Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects

Excerpts from Ian Cordasco's message of 2016-12-22 06:46:29 -0600: > > There is some ambiguity right now with projects as to where to put > easy-to-find documentation (even if it is just a brief paragraph with > a link to longer-form documentation) into our repositories. Let's > focus on that

[openstack-dev] [release] reno 2.0.0

This new version of reno is a major rewrite of the repository scanner logic and includes some breaking changes to the internal API (the command line remains the same). Those changes broke the release announcement job, and we're working on getting that fixed. In the mean time, I wanted to make sure

Re: [openstack-dev] Proposing Steve Martinelli for project-team-guide core

Excerpts from Thierry Carrez's message of 2016-12-20 16:18:15 +0100: > Hi everyone, > > As you probably know, the OpenStack Project Team Guide is a piece of > documentation geared towards project teams, to help them navigate the > troubled and complex waters of being an official OpenStack team: >

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Excerpts from Emilien Macchi's message of 2016-11-29 19:39:03 -0500: > 3) Choose Goals for Pike. > Some of us already did, but we might want to start looking at what > Goals we would like to achieve during Pike cycle. > I was thinking at giving a score to the Goals, that could be > calculated by

[openstack-dev] [release][ptl][all] release freeze 26-30 Dec

Most of the release team will be on PTO the week of 26-30 Dec, so there are not likely to be any releases performed that week. Please plan accordingly. Doug __ OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [release] Release countdown for week R-9, 19-23 Dec

All milestone-based deliverables have been tagged with the Ocata-2 milestone tags. Thank you, liaisons, for handling the milestone so smoothly! Focus - Feature work and major refactoring should be well under way as we pass the second milestone. The deadline for non-client library releases

[openstack-dev] [release] team meetings 23 Dec and 30 Dec canceled

As we discussed in today's meeting, the release team meetings for 23 Dec and 30 Dec are canceled. Our next team meeting will be 6 Jan. Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [release][ptl][all] self-service branch management

ble to script them. Doug > > Best Regards > Chaoyi Huang (joehuang) > > ____ > From: Doug Hellmann [d...@doughellmann.com] > Sent: 14 December 2016 21:45 > To: openstack-dev > Subject: [openstack-dev] [release][ptl][all] self-serv

Re: [openstack-dev] [kolla][tc] Video Meetings - input requested

Excerpts from Michał Jastrzębski's message of 2016-12-15 14:57:10 -0600: > I will defend this thing as something what we needed at the time. > Sometimes heated up video discussion helps to resolve > misunderstandings which otherwise could grow up and become conflicts > in community, which would

Re: [openstack-dev] [kolla][tc] Video Meetings - input requested

Excerpts from Zane Bitter's message of 2016-12-15 15:16:07 -0500: > The next 'generation' of core reviewers will acquire their knowledge > largely from discussions between the current cores. It's important to > the long-term health of the project not to cut them off from those > discussions,

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Excerpts from Sean Dague's message of 2016-12-15 11:58:42 -0500: > One of the big things to consider is which of these items directly > support one of the key PWG issues: "painless upgrades" > > The following items: movinging paste.ini out of config, new style > olso.policy (in code), and

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Excerpts from Jean-Philippe Evrard's message of 2016-12-15 09:11:12 +: > Hello, > > Maybe this will sound dumb … > > I received this email on openstack-dev mailing list. I don’t know if it was > sent to any other place, because it’s basically agreeing on development to be > done, which

Re: [openstack-dev] [release][ptl][all] self-service branch management

Excerpts from Emilien Macchi's message of 2016-12-14 15:34:27 -0500: > On Wed, Dec 14, 2016 at 8:45 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > [Sending again due to mail delivery issues.] > > > > The release team is pleased to announce that the branch automati

Re: [openstack-dev] [kolla][tc] Video Meetings - input requested

fact, or both. Maybe it would be constructive to brainstorm ways to address the complaints. Doug > > Still waiting for "punch other person in the face over IP" device... > > On 14 December 2016 at 11:05, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Mich

Re: [openstack-dev] [kolla][tc] Video Meetings - input requested

Excerpts from Michał Jastrzębski's message of 2016-12-14 09:56:46 -0600: > OK, I think we had some grave misunderstandings here. > > 1. ad-hoc meetings *are not* and *were never meant to be* replacement > for weekly meetings. Kolla community is single community across all > its deliverables and

Re: [openstack-dev] [OpenStack-Infra] [all][stable][ptls] Tagging liberty as EOL

Excerpts from Vladyslav Drok's message of 2016-12-14 17:11:56 +0200: > On Wed, Dec 14, 2016 at 3:48 PM, Ian Cordasco > wrote: > > > -Original Message- > > From: Joshua Hesketh > > Reply: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] Golang technical requirements

Excerpts from Dean Troyer's message of 2016-12-14 08:15:08 -0600: > On Wed, Dec 14, 2016 at 7:46 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > FWIW, some of the deployment tool communities (ansible and puppet, > > I think) rely on git repos without external

Re: [openstack-dev] [release][ptl][all] self-service branch management

Excerpts from Jeremy Stanley's message of 2016-12-14 14:28:30 +: > On 2016-12-14 08:51:29 -0500 (-0500), Ian Cordasco wrote: > [...] > > I do have one question, will creating the branch's end-of-life > > eventually work the same way? For example, Glance's projects were > > missed in the recent

Re: [openstack-dev] [oslo] Propose to normalize namespaces

Excerpts from Morales, Victor's message of 2016-12-02 19:07:25 +: > Hey there, > > There is a mismatch of namespaces in neutron which uses AGENT and agent which > is addressed by Ihar in the patch[1]. That raised the question is > olo-config-generator should be normalize this namespaces,

Re: [openstack-dev] Golang technical requirements

Excerpts from Dean Troyer's message of 2016-12-13 12:45:07 -0600: > Release Deliverables > > OpenStack still officially considers the tarballs generated during the > release rpocess to be our official deliverable. Many downstream > consumers, however, bypass those and go directly to the tagged >

[openstack-dev] [release] Release countdown for week R-10, 12-16 Dec

Focus - Feature work and major refactoring for bug fixes should be well under way as we reach the second milestone deadline of Thursday 15 Dec. Release Actions --- Submit the tag request for the Ocata 2 milestone by 15 Dec. Several projects missed the Ocata-1 deadline. Keep in

[openstack-dev] [release][ptl][all] self-service branch management

The release team is pleased to announce that the branch automation work is now complete, and that teams can now manage feature and stable branch creation through the openstack/releases repository. Creating a branch is very similar to creating a release: Edit the appropriate file in the releases

[openstack-dev] [release] Release countdown for week R-11, 5-9 Dec

Focus - We've passed the first milestone, so teams should be focused on feature development. The second milestone deadline is Thursday 15 Dec. General Notes - All release announcements are now being sent to the new openstack-releases mailing list instead of openstack-dev or

Re: [openstack-dev] [ptl][release] ocata release management communication

Excerpts from Rob C's message of 2016-11-30 18:38:53 +: > [Resending without the PTLs in CC because it got my mail stuck in the spam > filters] > > I'm struggling to find good info on when the adjusted PTL nomination cycle > starts. > > I've checked here:

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Excerpts from Emilien Macchi's message of 2016-11-29 19:39:03 -0500: > A few months ago, our community started to find and work on > OpenStack-wide goals to "achieve visible common changes, push for > basic levels of consistency and user experience, and efficiently > improve certain areas where

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

Excerpts from Clint Byrum's message of 2016-12-02 09:44:40 -0800: > Excerpts from Tony Breeds's message of 2016-12-02 15:26:40 +1100: > > On Thu, Dec 01, 2016 at 08:41:54AM -0800, Joshua Harlow wrote: > > > Keen, Joe wrote: > > > > I¹ll look into testing the newest version of kafka-python and see

Re: [openstack-dev] [release] Release management team draft logo

ine up with what I expect to see for markings on a border collie, so I'm tentatively OK with this pending seeing the color version. Doug > > On Fri, Dec 2, 2016 at 4:05 AM, Thierry Carrez <thie...@openstack.org> > wrote: > > > Doug Hellmann wrote: > > > Release t

Re: [openstack-dev] [all] Creating a new IRC meeting room ?

Excerpts from Thierry Carrez's message of 2016-12-02 11:35:05 +0100: > So I'm now wondering how much that artificial scarcity policy is hurting > us more than it helps us. I'm still convinced it's very valuable to have > a number of "meetings rooms" that you can lurk in and be available for >

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Kevin Benton's message of 2016-11-30 03:23:04 -0700: > >I'll let someone from the Neutron team fill in the details behind their > >decision, > because I don't want to misrepresent them. > > I can shed a bit of light on this since I'm a core and had been working for > a driver

Re: [openstack-dev] Golang technical requirements

[Sending again due to mail delivery issues.] Excerpts from Dean Troyer's message of 2016-12-13 12:45:07 -0600: > Release Deliverables > > OpenStack still officially considers the tarballs generated during the > release rpocess to be our official deliverable. Many downstream > consumers,

[openstack-dev] [release] Release countdown for week R-10, 12-16 Dec

[Sending again due to mail delivery issues.] Focus - Feature work and major refactoring for bug fixes should be well under way as we reach the second milestone deadline of Thursday 15 Dec. Release Actions --- Submit the tag request for the Ocata 2 milestone by 15 Dec. Several

[openstack-dev] [release][ptl][all] self-service branch management

[Sending again due to mail delivery issues.] The release team is pleased to announce that the branch automation work is now complete, and that teams can now manage feature and stable branch creation through the openstack/releases repository. Creating a branch is very similar to creating a

[openstack-dev] [release] Release management team draft logo

Release team, please take a look at the attached logo and let me know what you think. Doug > Begin forwarded message: > > From: Heidi Joy Tretheway > Subject: Release management team draft logo > Date: December 1, 2016 at 2:29:05 PM EST > To: Doug Hellmann <d...@doughell

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Sam Betts (sambetts)'s message of 2016-11-29 21:00:06 +: > There are a couple of reasons we want to become an official OpenStack project. > > From a project perspective, we want to be recognized that the project isn’t > just a “public source” repo for Cisco’s drivers but is a

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Chris Friesen's message of 2016-11-29 11:55:30 -0600: > On 11/29/2016 10:55 AM, Doug Hellmann wrote: > > > I agree that clearly documenting who supports each driver, and how > > tightly integrated that team is with the core team will be important. > > That wi

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Anita Kuno's message of 2016-11-29 12:37:21 -0500: > On 2016-11-29 11:27 AM, Jeremy Stanley wrote: > > I think we also need to look harder at the reasons for driver-only > > developer teams seeking official status. If it's because they want > > to be part of the community and help

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Zane Bitter's message of 2016-11-29 12:36:03 -0500: > On 29/11/16 10:28, Doug Hellmann wrote: > > Excerpts from Chris Friesen's message of 2016-11-29 09:09:17 -0600: > >> On 11/29/2016 08:03 AM, Doug Hellmann wrote: > >>> I'll rank my preferred solut

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Flavio Percoco's message of 2016-11-29 17:19:15 +0100: > On 28/11/16 13:33 -0500, Doug Hellmann wrote: > >5. Consider driver teams to be a completely different animal, defined > > in drivers.yaml instead of projects.yaml (grey option) [6] > > > >

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Chris Friesen's message of 2016-11-29 09:09:17 -0600: > On 11/29/2016 08:03 AM, Doug Hellmann wrote: > > I'll rank my preferred solutions, because I don't actually like any of > > them. > > Just curious...what would you "actually like"? > > Chr

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