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

I'll rank my preferred solutions, because I don't actually like any of them. Excerpts from Doug Hellmann's message of 2016-11-28 13:33:56 -0500: > 6. A resolution requiring projects that consume drivers to host all >proposed drivers. (red option) [7] > >This would require teams with

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

The OpenStack community wants to encourage collaboration by emphasizing contributions to projects that abstract differences between vendor-specific products, while still empowering vendors to integrate their products with OpenStack through drivers that can be consumed by the abstraction layers.

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

egards > Chaoyi Huang (joehuang) That sounds good. I know the timing may be a little tight for you. Let me know if I can help with any of the analysis. Doug > > ____ > From: Doug Hellmann [d...@doughellmann.com] > Sent: 16 November 2016 23:35 >

[openstack-dev] [release] 25 Nov team meeting canceled

Several of us will be on holiday this week and we don't have anything pressing to discuss, so let's skip this meeting and resume next week on 2 December. Doug __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [docs][upgrades] time to add official docs for upgrading services?

Excerpts from Steve Martinelli's message of 2016-11-17 20:36:46 -0500: > In the keystone docs we have notes about how to upgrade between releases > [1], so does the nova team [2]. > > Is it time we create an official guides to [3] for this subject? > > [1]

Re: [openstack-dev] [neutron][osc] Openstack client, Openstack SDK and neutronclient consistency

Excerpts from Sławek Kapłoński's message of 2016-11-16 22:36:41 +0100: > Hello, > > Few days ago someone reported bug [1] and I started checking it. I found > that when I'm trying to create QoS policy with neutronclient or OSC then > name parameter is neccessary. > But this parameter is not

[openstack-dev] [all][ptls][tc][goals] acknowledging community goals for Ocata

We still have quite a few teams who have not acknowledged the goal for Ocata. Remember, *all* teams are expected to respond, even if there is no work to be done. The most important feature of this new process is communication, which won't happen if teams don't participate. Please take a few

Re: [openstack-dev] [release][networking-bigswitch] tagging a branch and releasing on tarballs.openstack.org

Excerpts from Aditya Vaja's message of 2016-11-16 01:50:39 +0530: > Hi All, > [Redirect to a more specific mailing list if applicable] > I’m trying to tag a release on the networking-bigswitch project for > stable/newton branch and see if it pops up on >

[openstack-dev] [monasca][release] Release of openstack/monasca-grafana-datasource 1.0.0 failed

It looks like the monasca-grafana-datasource repository isn't set up in the way our release job expects for publishing nodejs projects. >From the log: 2016-11-15 14:03:26.945891 | + npm install 2016-11-15 14:03:27.287904 | npm ERR! install Couldn't read dependencies 2016-11-15 14:03:27.289483 |

Re: [openstack-dev] [kolla][release] Version numbers for kolla-ansible repository.

Excerpts from Steven Dake (stdake)'s message of 2016-11-08 21:41:26 +: > > On 11/8/16, 9:08 AM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > >Excerpts from Steven Dake (stdake)'s message of 2016-11-08 13:08:11 +: > >> Hey folks, > >

Re: [openstack-dev] [release] change in plan for releases repo data model updates

Excerpts from Doug Hellmann's message of 2016-11-08 12:28:28 -0500: > At the summit we said we would move the data that tells us the type > and release model for each deliverable out of the governance > repository and into the releases repository where it is easier to > change over time, but that

[openstack-dev] [release] Release countdown for week R-14, 14-18 Nov, Ocata-1 milestone

Focus - Teams should be focusing on wrapping up incomplete work left over from the end of the Newton cycle, finalizing and announcing plans from the summit, and completing specs and blueprints. The first milestone deadline is Thursday 17 Nov. General Notes - Keep in mind that

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Excerpts from Pete Zaitcev's message of 2016-11-10 11:00:27 -0700: > On Wed, 9 Nov 2016 11:14:32 + (GMT) > Chris Dent wrote: > > > The conversations about additional languages in this community have > > been one our most alarmingly regressive and patronizing. They

[openstack-dev] [tc][ux] UX team extra-ATCs expired

UX team, In the process of cleaning up expired ATCs in the governance repository, https://review.openstack.org/#/c/388170/ removed all of the names of extra-atcs for the UX project. If any of those folks would not otherwise be considered ATC, they can be added back with new expiration dates

[openstack-dev] [release] change in plan for releases repo data model updates

At the summit we said we would move the data that tells us the type and release model for each deliverable out of the governance repository and into the releases repository where it is easier to change over time, but that we needed to think more about what might break by making that change. After

Re: [openstack-dev] [kolla][release] Version numbers for kolla-ansible repository.

Excerpts from Steven Dake (stdake)'s message of 2016-11-08 13:08:11 +: > Hey folks, > > As we split out the repository per our unanimous vote several months ago, we > have a choice to make (I think, assuming we are given latitude of the > release team who is in the cc list) as to which

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Excerpts from Flavio Percoco's message of 2016-11-08 08:33:41 -0800: > On 08/11/16 16:20 +, Hayes, Graham wrote: > >On 08/11/2016 15:55, Doug Hellmann wrote: > >> Excerpts from Hayes, Graham's message of 2016-11-08 13:04:08 +: > >>> On 08/11/2016 10:30, Th

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Excerpts from Hayes, Graham's message of 2016-11-08 13:04:08 +: > On 08/11/2016 10:30, Thierry Carrez wrote: > > Ash wrote: > >> [...] > >> Here's another take on the situation. If there are people who genuinely > >> wish to see a CI pipeline that can support something like Go, perhaps > >>

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Excerpts from Joshua Harlow's message of 2016-11-07 15:53:51 -0800: > > > > Concretely - oslo.config is important because it shapes what the config > > files look like. The implementation language of a particular service > > shouldn't change what our config files look like, yeah? > > Standards

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Excerpts from Flavio Percoco's message of 2016-11-07 11:32:06 -0800: > On 07/11/16 12:16 -0600, Monty Taylor wrote: > >On 11/07/2016 11:58 AM, Hayes, Graham wrote: > >> On 07/11/2016 17:14, Flavio Percoco wrote: > >>> Greetings, > >>> > >>> I literally just posted a thing on my blog with some

Re: [openstack-dev] [oslo] New and next-gen libraries (a BCN followup)

Excerpts from Jim Rollenhagen's message of 2016-11-04 10:50:34 -0400: > On Thu, Nov 3, 2016 at 3:04 PM, Joshua Harlow wrote: > > Jay Faulkner wrote: > >>> > >>> On Nov 3, 2016, at 11:27 AM, Joshua Harlow wrote: > >>> > >>> Just as a followup from the

Re: [openstack-dev] [monasca] License for monasca-statsd

Excerpts from Chuck Short's message of 2016-11-03 15:03:44 -0400: > Hi, > > I was looking at packaging monasca-statsd since it is a dependency for > designate, however when I look at the license for it,it says Apache-2. > However the LICENSE file included in the source is that the software is >

[openstack-dev] [requirements][infra] Fwd: [TIP] new tox-dev mailing list on python

At the summit last week there were some discussions about limitations of tox and how they affect our use of constraints. It looks like contributing to tox may be getting easier, so it's possible that some of the ideas floated at the summit (like adding separate install commands or a "prepare

Re: [openstack-dev] [all][i18n] how to indicate non-translatable identifiers in translatable strings?

Excerpts from Ian Y. Choi's message of 2016-11-04 00:58:30 +0900: > Hello, > > I am from I18n team. Please see inline for my comments. > > Doug Hellmann wrote on 11/3/2016 2:19 AM: > > Excerpts from Brian Rosmaita's message of 2016-11-02 16:34:45 +: > >> Th

[openstack-dev] [release] Release countdown for week R-15, 7 - 11 Nov

Welcome back from summit! As we did last cycle, the release team will be sending reminder emails as we count down toward the Ocata release. If all goes as planned, these emails will be sent just before the week mentioned in the subject (on my Thursday, but some of you live in the future).

[openstack-dev] [release][ptl][all] proposed change to Ocata final release date

One piece of feedback the release team received during the summit was that downstream packagers would benefit from having more time during the final release week to prepare the packages after we tag the final versions of projects using milestone-based releases. To help them out, we would like to

[openstack-dev] [release] release team plans for Ocata

Last week at the summit the release team reviewed our notes from Newton and worked on plans for changes to be implemented during Ocata. * Branch automation Now that tag management is handled through reviews on openstack/releases, we want to add the other major release-related task: branch

Re: [openstack-dev] [neutron][oslo] proposal to resolve a rootwrap problem for XenServer

Excerpts from Jianghua Wang's message of 2016-11-02 15:52:22 +: > Thanks Doug. Please see my response inline starts with . > > Jianghua > > -Original Message----- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Wednesday, November 2, 2016 9:31 P

Re: [openstack-dev] [all][i18n] how to indicate non-translatable identifiers in translatable strings?

Excerpts from Brian Rosmaita's message of 2016-11-02 16:34:45 +: > This issue came up during a code review; I've asked around a bit but > haven't been able to find an answer. > > Some of the help output for utility scripts associated with Glance aren't > being translated, so Li Wei put up a

Re: [openstack-dev] [all][release] Release announcements

Excerpts from Thierry Carrez's message of 2016-11-02 17:33:51 +0100: > Hi everyone, > > In Barcelona the release team has been discussing how to improve release > announcements. Posting them on openstack-dev (for libs) and > openstack-announce (for main services) has proven to be pretty noisy, >

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

Excerpts from Brandon Logan's message of 2016-11-01 22:56:45 +: > On Tue, 2016-11-01 at 13:13 +0100, Ihar Hrachyshka wrote: > > Brandon Logan wrote: > > > > > Hello Neutrinos, > > > I've come across an issue that I'd like to get input/opinions > > > on.  I've > >

Re: [openstack-dev] [neutron][oslo] proposal to resolve a rootwrap problem for XenServer

Excerpts from Jianghua Wang's message of 2016-11-02 04:14:48 +: > Ihar and Tony, > Thanks for the input. > In order to run command in dom0, it uses XenAPI to create a session which > can be used to remotely call a plugin - netwrap which is located in dom0. The > netwrap plugin is executed

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

PTLs, As we did for the Mitaka and Newton cycles, I want to start this cycle by making sure the expectations for communications with the release team are clear to everyone so there is no confusion or miscommunication about any of the process or deadlines. This email is being sent to the

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

Excerpts from Ihar Hrachyshka's message of 2016-11-01 13:13:41 +0100: > Brandon Logan wrote: > > > Hello Neutrinos, > > I've come across an issue that I'd like to get input/opinions on. I've > > been reviewing some of the centralize config options reviews and have >

Re: [openstack-dev] Endpoint structure: a free-for-all

> On Oct 21, 2016, at 7:22 AM, Chris Dent wrote: > >> On Wed, 19 Oct 2016, Sean Dague wrote: >> >> The reason we have volume, volumev2, and volumev3 is that no one actually >> wants the unversioned volume endpoint. You can't do anything with it. >> Everyone wants the

[openstack-dev] [release][ptl] pausing releases until 1 Nov

It's late in the week and the release and infra teams need to see to our travel preparations. I am declaring the releases repository frozen until the Tuesday after summit, 1 Nov. If there are critical security related issues that require a release before 1 Nov, please contact me directly via

[openstack-dev] [release][fuel][tripleo][kolla][ansible] newton finals for cycle-trailing projects

I have prepared a proposed set of tags for the final releases for cycle-trailing projects that are using pre-release versions [1]. Please review the tags for your deliverables and ensure they are correct. The release team will approve and tag the releases by the end of the day tomorrow. Thanks!

Re: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

release team do that automatically? I will take care of the final patch. I'll prepare it later today and then we will approve it tomorrow. Doug > > Regards > -steve > > On 10/7/16, 12:16 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: > > >This week we ta

Re: [openstack-dev] [requirements][lbaas] gunicorn to g-r

Excerpts from Doug Wiegley's message of 2016-10-18 12:53:18 -0600: > > > On Oct 18, 2016, at 12:42 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > > > I expect you could take over a corner of the dev lounge or some > > other space to hold a BoF to at l

Re: [openstack-dev] [requirements][lbaas] gunicorn to g-r

Excerpts from Doug Wiegley's message of 2016-10-18 12:21:20 -0600: > > > On Oct 18, 2016, at 12:10 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > > > Excerpts from Doug Wiegley's message of 2016-10-18 12:00:35 -0600: > >> > >>>

[openstack-dev] [all][tc][horizon][ux][qa][release] cleaning up extra-atcs list

We have a handful of people listed for ATC status under the "extra-atcs" lists in the governance repository for whom the expiration date has passed. I've prepared a patch to clean up the lists [1] and added the PTLs for the related projects so they can confirm or indicate their intent to renew the

Re: [openstack-dev] [requirements][lbaas] gunicorn to g-r

Excerpts from Doug Wiegley's message of 2016-10-18 12:00:35 -0600: > > > On Oct 18, 2016, at 11:30 AM, Doug Hellmann <d...@doughellmann.com> wrote: > > > > Excerpts from Doug Wiegley's message of 2016-10-18 09:59:54 -0600: > >> > >>> On O

Re: [openstack-dev] [requirements][lbaas] gunicorn to g-r

Excerpts from Doug Wiegley's message of 2016-10-18 09:59:54 -0600: > > > On Oct 18, 2016, at 5:14 AM, Ian Cordasco wrote: > > > > > > > > -Original Message- > > From: Thierry Carrez > > > Reply: OpenStack

[openstack-dev] [tripleo][release] Tripleo Newton RC3 available

Hello everyone, A new release candidate for Tripleo for the end of the Newton cycle is available. You can find the RC3 source code tarballs at: https://tarballs.openstack.org/instack-undercloud/instack-undercloud-5.0.0.0rc3.tar.gz

Re: [openstack-dev] [oslo] Propose support generate IPv4 and IPv6 random address( or network) for documentation(test?)

ithub.com/openstack/manila/blob/master/manila_tempest_tests/tests/api/base.py#L828 > > [2] > > https://github.com/openstack/manila/blob/master/manila_tempest_tests/tests/api/test_replication.py#L76 > > > > Doug Hellmann <d...@doughellmann.com <mailto:d...@doughellmann.com&g

Re: [openstack-dev] [oslo] Propose support generate IPv4 and IPv6 random address( or network) for documentation(test?)

ecause that seems like a way to end up having two tests try to use the same address at the same time. If that did happen, would it cause conflicts or race conditions for the manila tests? > > Doug Hellmann <d...@doughellmann.com>于2016年10月17日周一 下午10:13写道： > > > Excerpts from TommyLike

[openstack-dev] [ptl][release] Ocata release liasons

It's time to update the release liaison list for the Ocata release. By default, the release liaison is the PTL and we can continue with that assumption for this cycle again. If you would like to hand those duties off to someone else, please update the wiki page appropriately [1]. Please also

Re: [openstack-dev] [oslo] Propose support generate IPv4 and IPv6 random address( or network) for documentation(test?)

Excerpts from TommyLike Hu's message of 2016-10-17 09:56:15 +: > When I handle some stuff related to Manila recently, I found a case which > may be suitable for Oslo, Anyhow I put it in the maillist so it can be > discussed before I put it in action. > In testcase, we need a function(maybe 2)

[openstack-dev] [ptl][oslo][goals] cross-project workshop on Ocata goal

As part of our community goal process [1], we will have a workshop at the summit next week to discuss implementation details for the "Remove Incubated Oslo Code" goal [2] and to connect folks who plan to do the work with guides for migrating to the relevant Oslo libraries. Please ensure that your

[openstack-dev] [release] no meeting until 4 Nov

As discussed in today's release team meeting, we have travel next week and the summit the following week. We will skip holding our team meeting until the week after the summit, 4 Nov. Doug __ OpenStack Development Mailing

Re: [openstack-dev] [oslo] To PTG or not to be that is the question!

Excerpts from Joshua Harlow's message of 2016-10-13 09:02:06 -0700: > Hi oslo folks, > > It appears we also need to discuss and decide on whether oslo and its > associated folks want to try to go to the PTG (project team gathering) > or do folks in oslo not feel such a thing would be needed? >

[openstack-dev] [tc] governance review dashboard

Since we have some new members this term, I thought I would share the TC review dashboard link I set up a while back in case others find it useful. It organizes reviews based on formal-vote items and whether or not you have responded to the current draft.

Re: [openstack-dev] [tripleo] PTG space request

Excerpts from Eoghan Glynn's message of 2016-10-13 05:45:59 -0400: > > > >>> I would like to request for some space dedicated to TripleO project > > >>> for the first OpenStack PTG. > > >>> > > >>> https://www.openstack.org/ptg/ > > >>> > > >>> The event will happen in February 2017 during the

Re: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

les modified in a patch). Doug > > Best regards, > Alexey Shtokolov > > On Fri, Oct 7, 2016 at 10:16 PM, Doug Hellmann <d...@doughellmann.com> > wrote: > > > This week we tagged the final releases for projects using the > > cycle-with-milestones release mod

Re: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

lity. That's consistent with what we do for the milestone-based projects. Doug > > Regards > -steve > > > From: Doug Hellmann <d...@doughellmann.com> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-d

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200: > Greetings, > > One of the common complains about the existing project organization in the big > tent is that it's difficult to wrap our heads around the many projects there > are, their current state (in/out the big tent),

Re: [openstack-dev] [all][elections] Results of the TC Election

Excerpts from John Davidge's message of 2016-10-10 13:24:18 +: > On 10/10/16, 5:36 AM, Monty Taylor wrote: > > >It's really nice to see that we had an increase in turnout percentage > >even in the face of having our largest electorate yet. > > > >Thanks for all your great work!!! > > > >Monty

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Excerpts from Sean Dague's message of 2016-10-10 09:23:43 -0400: > On 10/10/2016 08:37 AM, Doug Hellmann wrote: > > > We had a lot of feedback that the unstructured discussion time from > > the Friday "meetups" at the summits were the most productive time

Re: [openstack-dev] [openstack-infra] gerrit branch

Excerpts from Gary Kotton's message of 2016-10-10 12:26:24 +: > Hi, > Maybe someone can help out here. We are trying to create an initial release > for vmware-nsxlib. I am following the instructions on > http://docs.openstack.org/infra/manual/creators.html > When I try and push the tag I

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Excerpts from Duncan Thomas's message of 2016-10-10 14:47:12 +0300: > On 7 October 2016 at 19:53, Clint Byrum wrote: > > > > > My hope was that it would be "the summit without the noise". Sounds like > > it will be "the summit without the noise, or the organization". > > > >

[openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

This week we tagged the final releases for projects using the cycle-with-milestones release model. Projects using the cycle-trailing model have two more weeks before their final release tags are due. In the time between now and then, we expect those projects to be preparing and tagging release

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Excerpts from Matt Riedemann's message of 2016-10-06 13:52:09 -0500: > On 10/6/2016 12:23 PM, Clint Byrum wrote: > > Excerpts from Matt Riedemann's message of 2016-10-06 11:33:35 -0500: > >> This is just a follow up email to the discussion about nova's > >> participation in the Project Team

Re: [openstack-dev] [all][i18n] Translation of releasenotes

Excerpts from Andreas Jaeger's message of 2016-10-06 21:05:41 +0200: > All repositories that have translations enabled, are pushing their > releasenotes to our translation server and we have currently > translations for 19 of these repositories. > > I've worked with the i18n team on publishing

[openstack-dev] Release countdown for week R+1, 10-14 Oct

The main portion of the Newton release is complete. Thank you all for the hard work you put into the release this cycle! Focus - All project teams should be preparing for the summit in Barcelona. General Notes - Stable and independent releases will resume on 10 Oct. Let the

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Excerpts from Ed Leafe's message of 2016-10-04 16:38:50 -0500: > On Oct 4, 2016, at 4:21 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > >> 1) Allow time between the nominations and the voting. Half of the > >> candidates don’t announce until the las

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Excerpts from Ed Leafe's message of 2016-10-04 14:31:45 -0500: > On Oct 4, 2016, at 11:54 AM, Thierry Carrez wrote: > > >> In French, "prétendre" has a connotation of "profess" or simply > >> "say", which is very different from the more negative connotation > >> of

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Excerpts from John Davidge's message of 2016-10-04 14:44:00 +: > Thierry Carrez wrote: > > >Edward Leafe wrote: > >> [...] > >> The current candidacy essay would now be posted in the campaign > >> period, > >>rather than at the time of nomination, and should exclude the sort > >>of >

Re: [openstack-dev] [oslo] Adding ozamiatin to oslo-core

Excerpts from Joshua Harlow's message of 2016-10-03 10:42:49 -0700: > Greetings all stackers, > > I propose that we add Oleksii Zamiatin[1] to the oslo-core[2] team. > > Oleksii has been actively contributing to oslo for a while now, both in > helping make oslo better via code contribution(s)

Re: [openstack-dev] [oslo] Adding gdavoian to oslo-core

Excerpts from Joshua Harlow's message of 2016-10-03 10:40:46 -0700: > Greetings all stackers, > > I propose that we add Gevorg Davoian[1] to the oslo-core[2] team. > > Gevorg has been actively contributing to oslo for a while now, both in > helping make oslo better via code contribution(s) and

Re: [openstack-dev] [tacker][ptl] Leave of Absence

Excerpts from Sridhar Ramaswamy's message of 2016-10-03 23:26:16 -0700: > Tackers, > > I'd like to inform I'll be away from work / the community for about 4 - 6 > weeks to attend to an urgent medical need. This also means I won't be able > to attend the upcoming Barcelona summit. I'll terribly

Re: [openstack-dev] [tc] open question to the candidates

Excerpts from John Dickinson's message of 2016-10-03 14:26:00 -0700: > > On 3 Oct 2016, at 12:31, Doug Hellmann wrote: > > > > I think that's the balance we want to > > have: listen to input, collect information, then clearly set the > > direction without over-

Re: [openstack-dev] [tc] open question to the candidates

Excerpts from gordon chung's message of 2016-10-03 15:30:56 +: > hi, > > as there are many candidates this TC election, i figured i'd ask a > question to better understand the candidates from the usual sales pitch > in self-nominations. hopefully, this will give some insights into the >

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Excerpts from Clay Gerrard's message of 2016-10-03 10:18:43 -0700: > On Mon, Oct 3, 2016 at 9:46 AM, Edward Leafe wrote: > > > After the nominations close, the election officials will assign each > > candidate a non-identifying label, such as a random number, and those > >

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Excerpts from Hayes, Graham's message of 2016-10-03 17:35:44 +: > On 03/10/2016 17:49, Edward Leafe wrote: > > So the period of self-nominations for the Technical Committee seats has > > ended, and the voting has begun. I've been a very close observer of this > > process for several cycles,

Re: [openstack-dev] [release][ptl] please review versions for final newton release

Excerpts from Doug Hellmann's message of 2016-09-30 14:57:53 -0400: > I have prepared a patch to openstack/releases to re-tag all of the > current release candidates using their final release version numbers. > > I could use some assistance reviewing the results to ensure that I > have not left

[openstack-dev] [release][ptl] please review versions for final newton release

I have prepared a patch to openstack/releases to re-tag all of the current release candidates using their final release version numbers. I could use some assistance reviewing the results to ensure that I have not left anything out and that the version numbers are all correct. This patch also

[openstack-dev] [release][horizon] horizon Newton RC3 available

Hello everyone, A new release candidate for horizon for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/horizon/horizon-10.0.0.0rc3.tar.gz Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [release][ceilometer] ceilometer Newton RC3 available

Hello everyone, A new release candidate for ceilometer for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/ceilometer/ceilometer-7.0.0.0rc3.tar.gz Unless release-critical issues are found that warrant a release candidate respin,

[openstack-dev] [release][ptl] Release countdown for week R-0, 3-7 Oct

Focus - This is the final release week. We're almost there! Most project teams should be preparing for the summit in Barcelona. General Notes - The release management team will tag the final Newton release on 6 October (project teams do not need to take any action). We will

Re: [openstack-dev] [all][oslo] Parse ISO8601 (open) time intervals

Excerpts from milanisko k's message of 2016-09-29 09:48:40 +: > út 27. 9. 2016 v 18:05 odesílatel Doug Hellmann <d...@doughellmann.com> > napsal: > > > Excerpts from milanisko k's message of 2016-09-27 12:30:09 +: > > > Hello Stackers! > > > > &g

[openstack-dev] [release][glance] glance Newton RC2 available

Hello everyone, A new release candidate for glance for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/glance/glance-13.0.0.0rc2.tar.gz Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [release][freezer] freezer Newton RC2 available

Hello everyone, A new release candidate for freezer for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer/freezer-3.0.0.0rc2.tar.gz Unless release-critical issues are found that warrant a release candidate respin, these

[openstack-dev] [release][murano] murano Newton RC2 available

Hello everyone, A new release candidate for murano for the end of the Newton cycle is available! You can find the source code tarballs at: https://tarballs.openstack.org/murano/murano-3.0.0.0rc2.tar.gz https://tarballs.openstack.org/murano-agent/murano-agent-3.0.0.0rc2.tar.gz

[openstack-dev] [release][neutron] neutron Newton RC2 available

Hello everyone, A new release candidate for neutron for the end of the Newton cycle is available! You can find the source code tarballs at: https://tarballs.openstack.org/neutron-dynamic-routing/neutron-dynamic-routing-9.0.0.0rc2.tar.gz

[openstack-dev] TC nomination

Stackalytics: http://stackalytics.com/?user_id=doug-hellmann Foundation Profile: http://www.openstack.org/community/members/profile/359 Freenode: dhellmann Website: https://doughellmann.com [1] http://governance.openstack.org/goals/index.html [2] http://governance.openstack.org/goals/ocata/remove

Re: [openstack-dev] [all][oslo] Parse ISO8601 (open) time intervals

Excerpts from milanisko k's message of 2016-09-27 12:30:09 +: > Hello Stackers! > > The ironic inspector project keeps track of introspection finished_at time > stamps. > We're just discussing how to reasonably query time ranges over the API[1] > to serve matching introspection statuses to

[openstack-dev] [release][heat] heat Newton RC2 available

Hello everyone, A new release candidate for heat for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/heat/heat-7.0.0.0rc2.tar.gz Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [release][keystone] keystone Newton RC2 available

Hello everyone, A new release candidate for keystone for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/keystone/keystone-10.0.0.0rc2.tar.gz Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [all][release][nova][magnum][murano][horizon][searchlight][trove] newton translations

There are several projects with open translations from the import job this morning. These may trigger additional release candidates, which will need to be filed by Thursday. Please keep an eye on the existing patches [1], as well as any others coming this week, and merge them quickly. Then set up

[openstack-dev] [release][zaqar] zaqar Newton RC2 available

Hello everyone, A new release candidate for zaqar for the end of the Newton cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/zaqar/zaqar-3.0.0.0rc2.tar.gz Unless release-critical issues are found that warrant a release candidate respin, this candidate

Re: [openstack-dev] How people handle the ML (bring your patterns/best practices)

Excerpts from Joshua Harlow's message of 2016-09-23 11:03:24 -0700: > Since I've heard this a few times over the years (the ML is to hard to > read, to much volume, to hard to keep track, to hard/this or that and > so-on), > > I thought it would make sense to start to document what folks that

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

cgit/openstack/openstack-salt-specs/ is the > > > work being done elsewhere? > > > 6. Is there an effort to add stuff to the CI jobs running on > > openstack > > > infrastructure? (can't seem to find much > > > http://codesearch.openstack.org/?q=salt=nope=zuul

[openstack-dev] [release][trove] trove and trove-dashboard Newton RC2 available

Hello everyone, The release candidates for trove and trove-dashboard for the end of the Newton cycle is available! You can find the RC2 source code tarballs at: https://tarballs.openstack.org/trove/trove-6.0.0.0rc2.tar.gz

[openstack-dev] [all] call for help debugging release-critical upgrade issue

One of the steps we need to go through to finish this release is to set up the stable/newton branch in devstack-gate. The patch to do that [1] is consistently hitting timeout errors in some of the jobs, waiting for VMs to be visible after they boot, as well as another issue that looks like a race

[openstack-dev] [release] Release countdown for week R-1, 26-30 Sept

Focus - All teams should be working on release-critical bugs before the final release. General Notes - 29 Sept is the deadline for new release candidates or releases from intermediary projects. After that point we will enter a quiet period before tagging the last release

Re: [openstack-dev] [ptl] code churn and questionable changes

Excerpts from Amrith Kumar's message of 2016-09-22 15:18:06 +: > > > -Original Message- > > From: Boris Bobrov [mailto:bbob...@mirantis.com] > > Sent: Wednesday, September 21, 2016 10:35 AM > > To: OpenStack Development Mailing List (not for usage questions) > >

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

Excerpts from Dave Walker's message of 2016-09-21 22:53:10 +0100: > On 21 September 2016 at 22:41, Kyle Mestery wrote: > > > On Wed, Sep 21, 2016 at 3:35 PM, Thierry Carrez > > wrote: > > > Chivers, Doug wrote: > > >> My concern is with the original

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

Excerpts from Filip Pytloun's message of 2016-09-21 20:36:42 +0200: > On 2016/09/21 13:23, Doug Hellmann wrote: > > The idea of splitting the contributor list comes up pretty regularly > > and we rehash the same suggestions each time. Given that what we > > have now worked

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

. Possibly this is wrong, but I didn’t sign up as a > contributor to spend all my spare time reading mailing lists. > > Regards > > Doug > > _ > Doug Chivers > Chief Security Architect, Helion OpenStack > > > On 21/09/2016,

[openstack-dev] [all][tc] etherpad for collecting goal info

This week at the TC meeting someone (Anne?) pointed out that the name of the etherpad with the list of community-wide goals wasn't ideal ("ocata-tc-goals" includes the cycle name and the "tc" component gives the impression that these are goals of the "TC" rather than that the pad was used by the

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