Re: [openstack-dev] [oslo] proposing Ken Giusti for oslo-core

On 26/03/18 11:52 -0400, Doug Hellmann wrote: Ken has been managing oslo.messaging for ages now but his participation in the team has gone far beyond that single library. He regularly attends meetings, including the PTG, and has provided input into several of our team decisions recently. I

Re: [openstack-dev] [octavia] Proposing Jacky Hu (dayou) as an Octavia core reviewer

+1, definitely a good contributor! Thanks especially for your work on the dashboard! On Tue, Mar 27, 2018 at 2:09 PM German Eichberger < german.eichber...@rackspace.com> wrote: > +1 > > Really excited to work with Jacky -- > > German > > On 3/26/18, 8:33 PM, "Michael Johnson"

Re: [openstack-dev] [octavia] Proposing Jacky Hu (dayou) as an Octavia core reviewer

+1 Really excited to work with Jacky -- German On 3/26/18, 8:33 PM, "Michael Johnson" wrote: Hello Octavia community, I would like to propose Jacky Hu (dayou) as a core reviewer on the Octavia project. Jacky has done amazing work on Octavia

Re: [openstack-dev] [nova] Proposing Eric Fried for nova-core

+1 On 03/26/2018 10:00 PM, melanie witt wrote: Howdy everyone, I'd like to propose that we add Eric Fried to the nova-core team. Eric has been instrumental to the placement effort with his work on nested resource providers and has been actively contributing to many other areas of openstack

[openstack-dev] [octavia] Proposing Jacky Hu (dayou) as an Octavia core reviewer

Hello Octavia community, I would like to propose Jacky Hu (dayou) as a core reviewer on the Octavia project. Jacky has done amazing work on Octavia dashboard, specifically updating the look and feel of our details pages to be more user friendly. Recently he has contributed support for L7

Re: [openstack-dev] [nova] Proposing Eric Fried for nova-core

+1, Eric is very active and thorough reviewer ~ Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82451493 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193,

Re: [openstack-dev] [oslo] proposing Ken Giusti for oslo-core

+1 2018-03-27 0:58 GMT+08:00 Joshua Harlow : > +1 > > > Ben Nemec wrote: > >> +1! >> >> On 03/26/2018 10:52 AM, Doug Hellmann wrote: >> >>> Ken has been managing oslo.messaging for ages now but his participation >>> in the team has gone far beyond that single library. He

Re: [openstack-dev] [nova] Proposing Eric Fried for nova-core

+1 2018-03-27 10:00 GMT+08:00 melanie witt : > Howdy everyone, > > I'd like to propose that we add Eric Fried to the nova-core team. > > Eric has been instrumental to the placement effort with his work on nested > resource providers and has been actively contributing to many

[openstack-dev] [nova] Proposing Eric Fried for nova-core

Howdy everyone, I'd like to propose that we add Eric Fried to the nova-core team. Eric has been instrumental to the placement effort with his work on nested resource providers and has been actively contributing to many other areas of openstack [0] like project-config, gerritbot,

[openstack-dev] Thank you TryStack!!

Hi everyone, We recently made the tough decision, in conjunction with the dedicated volunteers that run TryStack, to end the service as of March 29, 2018. For those of you that used it, thank you for being part of the TryStack community. The good news is that you can find more resources to

[openstack-dev] [nova] Rocky community goal: remove the use of mox/mox3 for testing

Hey everyone, This cycle there is a community goal to remove the use of mox/mox3 for testing [0]. In nova, we're tracking our work at this blueprint: https://blueprints.launchpad.net/nova/+spec/mox-removal If you propose patches contributing to this goal, please be sure to add something

[openstack-dev] [ironic] Bug Day April 6th poll

Hey everyone, I set up a doodle to vote on when we should hold the bug day on April 6th https://doodle.com/poll/xa999rx653pb58t6 I'm not sure how long we want the session to be so I provided 24 1 hour windows. Please vote with what blocks of time would work best for you. Thanks! Mike Turek

Re: [openstack-dev] [Release-job-failures] Tag of openstack/instack-undercloud failed

On Mon, Mar 26, 2018 at 2:33 PM, Doug Hellmann wrote: > Excerpts from zuul's message of 2018-03-26 18:11:49 +: >> Build failed. >> >> - publish-openstack-releasenotes >>

[openstack-dev] Fwd: [nova][placement] Upgrade placement first!

FYI Forwarded Message Subject: [openstack-dev] [nova][placement] Upgrade placement first! Date: Mon, 26 Mar 2018 15:02:23 -0500 From: Eric Fried Reply-To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Release-job-failures] Tag of openstack/instack-undercloud failed

Excerpts from zuul's message of 2018-03-26 18:11:49 +: > Build failed. > > - publish-openstack-releasenotes > http://logs.openstack.org/94/94bb28ae46bd263314c9d846069ca913d225e625/tag/publish-openstack-releasenotes/9440894/ > : POST_FAILURE in 3m 29s > This release notes build failure is

Re: [openstack-dev] [oslo] Any reason why not have 'choices' parameter for ListOpt()?

Excerpts from melanie witt's message of 2018-03-26 12:28:02 -0700: > On Mon, 26 Mar 2018 14:12:52 -0500, Matt Riedemann wrote: > > On 3/26/2018 6:24 AM, ChangBo Guo wrote: > >> What's your use case for ListOpt, just make sure the value(a list) is > >> part of  'choices' ?   Maybe we need another

Re: [openstack-dev] [oslo] Any reason why not have 'choices' parameter for ListOpt()?

Excerpts from Matt Riedemann's message of 2018-03-26 14:12:52 -0500: > On 3/26/2018 6:24 AM, ChangBo Guo wrote: > > What's your use case for ListOpt, just make sure the value(a list) is > > part of  'choices' ?   Maybe we need another parameter to distinguish > > It came up because of this

[openstack-dev] [nova][placement] Upgrade placement first!

Since forever [0], nova has gently recommended [1] that the placement service be upgraded first. However, we've not made any serious effort to test scenarios where this isn't done. For example, we don't have grenade tests running placement at earlier levels. After a(nother) discussion [2] which

Re: [openstack-dev] [oslo] Any reason why not have 'choices' parameter for ListOpt()?

On Mon, 26 Mar 2018 14:12:52 -0500, Matt Riedemann wrote: On 3/26/2018 6:24 AM, ChangBo Guo wrote: What's your use case for ListOpt, just make sure the value(a list) is part of  'choices' ?   Maybe we need another parameter to distinguish It came up because of this change in nova:

Re: [openstack-dev] [oslo] Any reason why not have 'choices' parameter for ListOpt()?

On 3/26/2018 6:24 AM, ChangBo Guo wrote: What's your use case for ListOpt, just make sure the value(a list) is part of  'choices' ?   Maybe we need another parameter to distinguish It came up because of this change in nova: https://review.openstack.org/#/c/534384/ We want to backport that as

[openstack-dev] [tripleo][oslo] messaging services update

Hi, I wanted to provide an update on the work that has been ongoing to enhance the deployment of messaging system backends for RPC and Notify communications. https://blueprints.launchpad.net/tripleo/+spec/tripleo-messaging The basis of the change is to introduce oslo messaging RPC and Notify

Re: [openstack-dev] [nova] EC2 cleanup ?

> That is easier said than done. There have been a couple of related attempts > in the past: > > https://review.openstack.org/#/c/266425/ > > https://review.openstack.org/#/c/282872/ > > I don't remember exactly where those fell down, but it's worth looking at > this first before trying to do this

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are glad to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) Weekly priorities

[openstack-dev] [Blazar] skip weekly meeting

Hi Blazar folks, As we talked in last meeting, this weekly meeting is skipped because most of the team members are out of office. best regards, Masahito __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [oslo] proposing Ken Giusti for oslo-core

+1 Ben Nemec wrote: +1! On 03/26/2018 10:52 AM, Doug Hellmann wrote: Ken has been managing oslo.messaging for ages now but his participation in the team has gone far beyond that single library. He regularly attends meetings, including the PTG, and has provided input into several of our team

[openstack-dev] [All] New PBR release coming soon

Hi, Since this will potentially affect the majority of OpenStack projects, I wanted to give everyone some advance notice. PBR[1] hasn't been released since last summer, and as a result none of the bug fixes or new features that have gone in since then are available to users. Because of

Re: [openstack-dev] [oslo] proposing Ken Giusti for oslo-core

+1! On 03/26/2018 10:52 AM, Doug Hellmann wrote: Ken has been managing oslo.messaging for ages now but his participation in the team has gone far beyond that single library. He regularly attends meetings, including the PTG, and has provided input into several of our team decisions recently. I

[openstack-dev] [glance] Priorities for WC 26th of March

Hi all, Time for the priority update: The python-glanceclient release was postponed til this week due to some bugs Brian found and is in process of fixing. Lets review these and see what we need for the release, so we can get it out this week. The R-1 Milestone is approaching quickly so I would

Re: [openstack-dev] [oslo] proposing Ken Giusti for oslo-core

w00t! yes please +1 On Mon, Mar 26, 2018 at 11:53 AM, Jay Pipes wrote: > Big +1. > > > On 03/26/2018 11:52 AM, Doug Hellmann wrote: >> >> Ken has been managing oslo.messaging for ages now but his participation >> in the team has gone far beyond that single library. He

[openstack-dev] [oslo] proposing Ken Giusti for oslo-core

Ken has been managing oslo.messaging for ages now but his participation in the team has gone far beyond that single library. He regularly attends meetings, including the PTG, and has provided input into several of our team decisions recently. I think it's time we make him a full member of the

Re: [openstack-dev] [oslo] proposing Ken Giusti for oslo-core

Big +1. On 03/26/2018 11:52 AM, Doug Hellmann wrote: Ken has been managing oslo.messaging for ages now but his participation in the team has gone far beyond that single library. He regularly attends meetings, including the PTG, and has provided input into several of our team decisions recently.

[openstack-dev] [all][oslo] Notice to users of the ZeroMQ transport in oslo.messaging

Folks, It's been over a year since the last commit was made to the ZeroMQ driver in oslo.messaging. It is at the point where some of the related unit tests are beginning to fail due to bit rot. None of the current oslo.messaging contributors have a good enough understanding of the codebase to

Re: [openstack-dev] [kolla] Kolla-Ansible pip packages vulnerable to CVE-2018-1000115

Hi Mathieu, Thanks for raising this issue. The patch is merged on all branches but not released[0].We will release the next release ASAP. But on the other hand, if you build an OpenStack cloud through kolla and be accessible through the internet, you'd better use an external network(interface)

[openstack-dev] [kolla] Kolla-Ansible pip packages vulnerable to CVE-2018-1000115

Hi folks, I initially sent this mail privately, resending it to the list on request : Kolla-Ansible https://docs.openstack.org/kolla-ansible/ pip packages (recommended in the doc) are vulnerable to CVE-2018-1000115. The patch have been commit, merged in stable/queens, stable/pike, stable/ocata

[openstack-dev] [all] Vancouver Forum - Topic submission tool is now open!

Hi everyone, The Forum in Vancouver is getting closer! As a reminder, the Forum is where we take advantage of having a large community presence at the Summit to discuss and get wide feedback on a variety of topics around the future of OpenStack and adjacent projects. Starting today, our

[openstack-dev] [stable][release] Remove complex ACL changes around releases

Hi! TL;DR: We used to do complex things with ACLs for stable/* branches around releases. Let's stop doing that as it's not really useful anyway, and just trust the $project-stable-maint teams to do the right thing. Current situation: As we get close to the end of a release cycle, we start

[openstack-dev] [openstack-ansible] Stepping down from OpenStack-Ansible core

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey there, As promised, I am stepping down from being an OpenStack-Ansible core reviewer since I am unable to meet the obligations of the role with my new job. :( Thanks to everyone who has mentored me along the way and put up with my gate job

Re: [openstack-dev] [ALL][PTLs] [Community goal] Toggle the debug option at runtime

Hi, > Wiadomość napisana przez ChangBo Guo w dniu 26.03.2018, > o godz. 14:15: > > > 2018-03-22 16:12 GMT+08:00 Sławomir Kapłoński : > Hi, > > I took care of implementation of [1] in Neutron and I have couple questions > to about this goal. > > 1.

Re: [openstack-dev] [ALL][PTLs] [Community goal] Toggle the debug option at runtime

2018-03-22 16:12 GMT+08:00 Sławomir Kapłoński : > Hi, > > I took care of implementation of [1] in Neutron and I have couple > questions to about this goal. > > 1. Should we only change "restart_method" to mutate as is described in [2] > ? I did already something like that in

Re: [openstack-dev] [oslo] Any reason why not have 'choices' parameter for ListOpt()?

There is no special reasons that ListOpt doesn't allow parameter, PortOpt also uses parameter 'choices'. PortOpt and StrOpt only accept one value and use this parameter to double check value is valid which is in the 'choices'. What's your use case for ListOpt, just make sure the value(a

[openstack-dev] [oslo] Any reason why not have 'choices' parameter for ListOpt()?

Hi there, I was looking at oslo_config/cfg.py[*], and the StrOpt() class has 'choices' parameter, to allow a sequence of valid values / tuples of valid values for descriptions. However, I don't see the same 'choices' parameter for the ListOpt() class. Out of curiosity, is there a reason to not

[openstack-dev] [nova][ThirdParty-CI] Nova s390x CI back online

Hi, with the latest release of pyroute2 I could bring the s390x CI is back online again. I now start rechecking all the missed patches… There introduction of pyroute2 in Neutron broke Neutron DHCP and L3 agent on s390x. pyroute2 was simply missing s390x enablement. It got added with patch [1].

[openstack-dev] [OpenStack-Ansible] Vancouver forum etherpad

Dear OpenStack-Ansiblers, We've got an etherpad here [1], to track all the things we want to discuss at the forum. if you're an OpenStack-Ansible user, don't hesitate to add your session ideas, list what you liked or disliked in the last release, and share your experience! Thank you in advance.

Re: [openstack-dev] [telemetry][aodh][panko][oslo][performance] OSprofiler in Aodh & Panko

Hello folks, Just a reminder. I have some patches related to OSProfiler that ready to review in Panko and Aodh. Hope that you guys can leave a comment. These patches are: 1. Aodh: https://review.openstack.org/#/c/483268/ 2. Aodh client: https://review.openstack.org/#/c/484295/ 3.