[openstack-dev] [release][collectd-openstack-plugins] Schedule new release?

Hello, it has been some time, since collectd-ceilometer-plugin[1] has been renamed to collectd-openstack-plugins[2] and since there has been a release. What is required to trigger a new release here? Thank you, Matthias [1] https://github.com/openstack/collectd-ceilometer-plugin [2]

Re: [openstack-dev] Nominating Luis Tomás Bolívar for kuryr-kubernetes core

On Thu, 2018-09-20 at 18:33 +0200, Daniel Mellado wrote: > Hi All, > > Id like to nominate Luis Tomás for Kuryr-Kubernetes core. > > He has been contributing to the project development with both features > and quality reviews at core reviewer level, as well as being the stable > branch liaison

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

On Thu, 20 Sep 2018 18:43:00 +0900 John Garbutt wrote > tl;dr+1 consistent names > I would make the names mirror the API... because the Operator setting them > knows the API, not the codeIgnore the crazy names in Nova, I certainly hate > them Big +1 on consistent naming which

[openstack-dev] [release-schedule] about release Series

Hello, Is the content in https://releases.openstack.org/ is the latest? There are some question here, why Queens cycles is longer then Rocy cycles. The Rocy cycles is too shot of live, even less than six month? May be the "estimated 2019-02-23" is a slip of pen? Should it be

Re: [openstack-dev] [Openstack-sigs] [First Contact] SIG PTG Summary

On Thu, Sep 20, 2018 at 1:23 PM Kendall Nelson wrote: Organization Guide > > === > > Back in Sydney, we started discussing creating a guide for organizations > to educate them on what their contributors need to be effective and > successful members of the community. There is a patch

Re: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the lists!

Doug Hellmann wrote: I'm inclined to include it and either use a direct mailing or the [tc] tag on the new discuss list to reach TC members, but I would like to hear feedback from TC members and other interested parties before calling that decision made. Please let me know what you think. +1

[openstack-dev] [ironic] status of the zuulv3 job migration

Just quick summary of the status and looking for some input about the experimental jobs 15 jobs are now done, with another 2 ready for reviewing. This leaves 6 jobs 1 x multinode job I've yet to finished porting this one 2 x grenade jobs Last time I looked grenade jobs couldn't yet be

Re: [openstack-dev] [release][collectd-openstack-plugins] Schedule new release?

On Fri, Sep 21, 2018 at 09:43:52AM +0200, Matthias Runge wrote: > Hello, > > it has been some time, since collectd-ceilometer-plugin[1] > has been renamed to collectd-openstack-plugins[2] and since there has been a > release. > > What is required to trigger a new release here? > > Thank you, >

Re: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the lists!

In my mind, there is value to having a mailing list for things like important meetings, but it seems more reasonable to just address such items as needed. At the same time, I agree with ttx, the separate list is no longer useful. +1 On Fri, Sep 21, 2018 at 5:24 AM Thierry Carrez wrote: > > Doug

Re: [openstack-dev] [release-schedule] about release Series

Jaze Lee wrote: Hello, Is the content in https://releases.openstack.org/ is the latest? There are some question here, why Queens cycles is longer then Rocy cycles. The Rocy cycles is too shot of live, even less than six month? May be the "estimated 2019-02-23" is a slip of pen?

Re: [openstack-dev] [ptg][cinder] Stein PTG Summary Page Ready ...

Thanks Jay! Em qua, 19 de set de 2018 às 06:53, Gorka Eguileor escreveu: > On 18/09, Jay S Bryant wrote: > > Team, > > > > I have put together the following page with a summary of all our > discussions > > at the PTG: https://wiki.openstack.org/wiki/CinderSteinPTGSummary > > > > Please review

Re: [openstack-dev] [release][collectd-openstack-plugins] Schedule new release?

On 2018-09-21 05:53:08 -0500 (-0500), Sean McGinnis wrote: [...] > collectd-openstack-plugins does not appear to be an official repo under > governance [1]. For these types of projects to do a release, the team would > need to push a tag to the repo. That will trigger some post jobs to run that >

[openstack-dev] [goals][python3][karbor] Please process the python3-first patches

Hi Karbor team and Karbor PTL, As part of the "Run under Python 3 by default" community goal [1] for OpenStack in the Stein cycle, I proposed the patches related to python3-first goal very long time ago. However, there is no activity for those patches. Please receive those patches and review

Re: [openstack-dev] [neutron][nova] Small bandwidth demo on the PTG

Hi, At the demo it turned out that people were interested in a written version of the demo, so here you can find a blog post about the current state of the guaranteed minimum bandwidth feature: https://rubasov.github.io/2018/09/21/openstack-qos-min-bw-demo.html Cheers, Bence On Thu, Sep 13,

[openstack-dev] [keystone] Keystone Team Update - Week of 17 September 2018

# Keystone Team Update - Week of 17 September 2018 ## News ### PTG recaps The PTG was last week! Lance[1] and I[2] posted recaps of the keystone sessions. [1] https://www.lbragstad.com/blog/openstack-stein-ptg-keystone-summary [2] http://www.gazlene.net/denver-ptg-2.html ### No-op roles and

[openstack-dev] [all][tc] please vote

A few hours ago Emmet reported that we have around 20% participation in the Technical Committee election, so far. I think we can do better. Our community is founded on the idea that the contributors should decide how the project is run. PTL and TC elections are the most explicit example of this

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

On Fri, Sep 21, 2018 at 2:10 AM Ghanshyam Mann wrote: > On Thu, 20 Sep 2018 18:43:00 +0900 John Garbutt < > j...@johngarbutt.com> wrote > > tl;dr+1 consistent names > > I would make the names mirror the API... because the Operator setting > them knows the API, not the codeIgnore the

[openstack-dev] 回复：[goals][python3][karbor] Please process thepython3-first patches

Thanks for pushing these patches, we will review and merge them ASAP. 原始邮件 发件人:Nguyễn Trí Hảinguyentriha...@gmail.com 收件人:OpenStack Development Mailing List (not for usage questions)openstack-dev@lists.openstack.org 抄送:jiaopengjujiaopen...@cmss.chinamobile.com 发送时间:2018年9月21日(周五) 20:36

Re: [openstack-dev] Are we ready to put stable/ocata into extended maintenance mode?

Hi, Here is an etherpad with the teams that have stable:follow-policy tag on their repos: https://etherpad.openstack.org/p/ocata-final-release-before-em On the links you can find reports about the open and unreleased changes, that could be a useful input for the before-EM/final release.

[openstack-dev] [manila] Stein PTG summary

We've summarized the manila PTG sessions in this etherpad [1] and I've included its contents below. Please feel free to supplement/correct as appropriate, or to follow up on this mailing list. -- Tom Barron (tbarron) We'll use this etherpad to distill AIs, focus areas, etc. from the Stein

[openstack-dev] OpenStack Project Navigator

Following up on my (very brief) talk from the PTG, you can now propose changes to the Project Navigator by going to https://git.openstack.org/cgit/openstack/openstack-map repository Once your patch is merged, the page should reflect the changes straight away. Cheers, Jimmy

Re: [openstack-dev] Are we ready to put stable/ocata into extended maintenance mode?

Excerpts from Elõd Illés's message of 2018-09-21 16:08:28 +0200: > Hi, > > Here is an etherpad with the teams that have stable:follow-policy tag on > their repos: > > https://etherpad.openstack.org/p/ocata-final-release-before-em > > On the links you can find reports about the open and

[openstack-dev] [oslo] Storyboard test import done

Hi, The test import of the Oslo projects is done (thanks Kendall!), so everyone from the Oslo team please take a look around and provide feedback on it. If we do the migration this cycle we want to do it earlier rather than later so we aren't dealing with migration fallout while trying to

Re: [openstack-dev] [goals][upgrade-checkers] Week R-29 Update

On 9/21/2018 3:53 PM, Matt Riedemann wrote: * The reference docs I wrote for writing upgrade checks is published now [4]. As I've been answering some questions in storyboard and IRC, it's obvious that I need to add some FAQs into those docs because I've taken some of this for granted on how it

Re: [openstack-dev] [Openstack-sigs] Capturing Feedback/Input

Melvin Hillsman writes: > On Fri, Sep 21, 2018 at 11:16 AM Doug Hellmann > wrote: > >> Maybe we're overthinking the organization on this. What is special about >> the items that would be on this list compared to items opened directly >> against projects? >> > > Yeah unfortunately we do have a

Re: [openstack-dev] OpenStack Project Navigator

Thank you Jimmy for making this available for updates. I was unable to find the code backing the project tags section of the Project Navigator pages. Our page is missing some upgrade tags and is showing duplicate "Stable branch policy" tags.

Re: [openstack-dev] OpenStack Project Navigator

On 9/21/2018 1:11 PM, Michael Johnson wrote: Thank you Jimmy for making this available for updates. I was unable to find the code backing the project tags section of the Project Navigator pages. Our page is missing some upgrade tags and is showing duplicate "Stable branch policy" tags.

[openstack-dev] [goals][upgrade-checkers] Week R-29 Update

Updates for this week: * As bnemec noted in the last update [1], he's making some progress with the oslo.upgradecheck library. He's retrofitting the nova-status upgrade check code to use the library and has a patch up for designate to use it. * The only two projects that I'm aware of with

Re: [openstack-dev] [goals][upgrade-checkers] Week R-29 Update

On 09/21/2018 03:53 PM, Matt Riedemann wrote: Updates for this week: * As bnemec noted in the last update [1], he's making some progress with the oslo.upgradecheck library. He's retrofitting the nova-status upgrade check code to use the library and has a patch up for designate to use it.

Re: [openstack-dev] [Openstack-sigs] Capturing Feedback/Input

On 2018-09-21 12:55:09 -0500 (-0500), Melvin Hillsman wrote: [...] > Yeah unfortunately we do have a tendency to overthink/complicate > things. Not saying Storyboard is the right tool but suggested > rather than having something extra to maintain was what I > understood. There are at least 3

Re: [openstack-dev] OpenStack Project Navigator

Matt, I'm a bit confused by your response. I'm not looking for a definition of the tags, that is very clear. I'm looking for the source code backing the page that is rendering which tags a project has. This code appears to be broken and not rendering the tags correctly and I wanted to see if I

Re: [openstack-dev] OpenStack Project Navigator

The TC tags are indeed in a different repo: https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml Let me know if this makes sense. Jimmy Michael Johnson September 21, 2018 at 4:32 PM Matt, I'm a bit confused by your response. I'm not

Re: [openstack-dev] [Tripleo] Automating role generation

Hi All As per the discussion at PTG, I have filed a BP [1]. I will push a spec sometime around mid-October. [1]. https://blueprints.launchpad.net/tripleo/+spec/automatic-role-generation On Tue, Sep 4, 2018 at 2:56 PM Steven Hardy wrote: > On Tue, Sep 4, 2018 at 9:48 AM, Jiří Stránský wrote:

Re: [openstack-dev] OpenStack Project Navigator

Jimmy, Yes, the tags are correct in https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml but are not correct in Project Navigator. I am asking where is the git repository with the Project Navigator code that creates the "Project Details" section? I am looking for the

Re: [openstack-dev] [neutron] heads up to long time ovs users...

The important point of this notice is that packet drops will happen when switching of_interface option from ovs-ofctl (which was the default value in the old releases) to native (which is the current default ). Once neutron drops the option, if deployers use the legacy value "ovs-ofctl", they

Re: [openstack-dev] [goals][python3][karbor] Please process thepython3-first patches

Hi, Thanks for reviewing them. Only two patches need to review: https://review.openstack.org/#/c/594827/ https://review.openstack.org/#/c/594815/ (Depends-On: https://review.openstack.org/#/c/596289/) On Fri, Sep 21, 2018 at 10:33 PM jiaopengju wrote: > Thanks for pushing these patches, we

[openstack-dev] [cinder] Mid-Cycle Planning ...

Team, As we discussed at the PTG I have started an etherpad to do some planning for a possible Cinder Mid-cycle meeting.  Please check out the etherpad [1] and leave your input. Thanks! Jay [1] https://etherpad.openstack.org/p/cinder-stein-mid-cycle-planning

Re: [openstack-dev] [Openstack-sigs] Capturing Feedback/Input

On Fri, Sep 21, 2018 at 11:16 AM Doug Hellmann wrote: > Excerpts from Melvin Hillsman's message of 2018-09-21 10:18:26 -0500: > > On Fri, Sep 21, 2018 at 9:41 AM Doug Hellmann > wrote: > > > > > Excerpts from Melvin Hillsman's message of 2018-09-20 17:30:32 -0500: > > > > Hey everyone, > > > >

[openstack-dev] [placement] update 18-38

HTML: https://anticdent.org/placement-update-18-38.html Here's a placement update. Last week there wasn't one, because of the PTG. There will be some references to various PTG stuff within but since we haven't fully resolved what the priorities will be, the discussion here will be somewhat

Re: [openstack-dev] [docs][cinder] about cinder volume qos

On Mon, Sep 10, 2018 at 2:22 PM Jay S Bryant wrote: > > > On 9/10/2018 7:17 AM, Rambo wrote: > > Hi,all > > At first,I find it is supported that we can define hard performance > limits for each volume in doc.openstack.org[1].But only can define hard > performance limits for each volume

Re: [openstack-dev] [cinder] Proposed Changes to the Core Team ...

On Wed, Sep 19, 2018 at 08:43:24PM -0500, Jay S Bryant wrote: > All, > > In the last year we have had some changes to Core team participation.  This > was a topic of discussion at the PTG in Denver last week.  Based on that > discussion I have reached out to John Griffith and Winston D (Huang

[openstack-dev] [manila] Team Photos

Manila team photos from the recent Stein PTG in Denver [1]. -- Tom Barron (tbarron) [1] https://www.dropbox.com/sh/2pmvfkstudih2wf/AADI7Yo-wuJ2nmAIuYFEun5Ea/Manila?dl=0_nav_tracking=1 signature.asc Description: PGP signature

Re: [openstack-dev] [cinder] Proposed Changes to the Core Team ...

On Fri, Sep 21, 2018 at 11:00 AM Sean McGinnis wrote: > On Wed, Sep 19, 2018 at 08:43:24PM -0500, Jay S Bryant wrote: > > All, > > > > In the last year we have had some changes to Core team participation. > This > > was a topic of discussion at the PTG in Denver last week. Based on that > >

Re: [openstack-dev] Are we ready to put stable/ocata into extended maintenance mode?

On Fri, Sep 21, 2018 at 08:26:41AM -0600, Doug Hellmann wrote: > Excerpts from Elõd Illés's message of 2018-09-21 16:08:28 +0200: > > Hi, > > > > Here is an etherpad with the teams that have stable:follow-policy tag on > > their repos: > > > >

Re: [openstack-dev] [goals][upgrade-checkers] Week R-30 update

On 09/15/2018 10:30 AM, Matt Riedemann wrote: Just a couple of updates this week. * I have assigned PTLs (for projects that have PTLs [1]) to their respective tasks in StoryBoard [2]. If someone else on your team is planning on working on the pre-upgrade check goal then please just

Re: [openstack-dev] [cinder] Proposed Changes to the Core Team ...

On 9/21/2018 12:06 PM, John Griffith wrote: On Fri, Sep 21, 2018 at 11:00 AM Sean McGinnis > wrote: On Wed, Sep 19, 2018 at 08:43:24PM -0500, Jay S Bryant wrote: > All, > > In the last year we have had some changes to Core team

[openstack-dev] [manila] User Survey Results

More PTG follow up :) The foundation shared results of the User Survey for Manila, where users were asked "Which OpenStack Shared File Systems (Manila) driver(s) are you using?" I've uploaded these in a Google Sheets document here [1]. The first tab has the raw results as passed to me by