Re: [openstack-dev] [Senlin] Proposing Liyi as core reviewer

Congrats Liyi. +2 from me :) 2017-08-16 12:50 GMT+08:00 Qiming Teng : > Dear Senlin cores, > > As you might have witnessed, Liyi has been a solid contributor to Senlin > during Pike cycle. His patches are of high quality, showing that he has > a good grasp of the

[openstack-dev] [Senlin] Proposing Liyi as core reviewer

Dear Senlin cores, As you might have witnessed, Liyi has been a solid contributor to Senlin during Pike cycle. His patches are of high quality, showing that he has a good grasp of the design and the code. Based on the contribution record and his agreement to work with the team more closely, I'm

[openstack-dev] [acceleration] a basic workflow of Cyborg

Hi Team, I have proposed a patch https://review.openstack.org/#/c/492134/, which pulls together the api,conductor,db processes to implement a basic workflow please help review the patch :) Hi jkilpatr, I think you can start your automated deployment work above it best.

Re: [openstack-dev] [tripleo] critical situation with CI / upgrade jobs

On Tue, Aug 15, 2017 at 9:33 PM, Emilien Macchi wrote: > So far, we're having 3 critical issues, that we all need to address as > soon as we can. > > Problem #1: Upgrade jobs timeout from Newton to Ocata > https://bugs.launchpad.net/tripleo/+bug/1702955 > Today I spent an

[openstack-dev] [Octavia]Questions about octavia flavors spec

Hi, I'm trying to figure out how the flavor will be implemented and have few questions about the flavor spec[1] 1. What does "*RO*" mean in API* /flavors*? Is it short for ReadOnly? In my understanding, user need create flavor by himself, so the flavor API should not be readonly.

[openstack-dev] [keystone] office hours report 2017-08-15

Hey all, Office hours was pretty focused today. We spent the majority of the time discussing and merging fixes we need for RC2. In addition to that we discussed plans for the PTG as well as the schedule. Full details can be found in the logs [0]. Thanks, Lance [0]

[openstack-dev] [tripleo] critical situation with CI / upgrade jobs

So far, we're having 3 critical issues, that we all need to address as soon as we can. Problem #1: Upgrade jobs timeout from Newton to Ocata https://bugs.launchpad.net/tripleo/+bug/1702955 Today I spent an hour to look at it and here's what I've found so far: depending on which public cloud we're

Re: [openstack-dev] [tripleo] Proposal to require bugs for tech debt

On Tue, Aug 15, 2017 at 5:46 PM, Alex Schultz wrote: > Hey folks, > > I'm proposing that in order to track tech debt that we're adding in as > part of development that we create a way to track these items and not > approve them without a bug (and a reference to said bug)[0].

[openstack-dev] [tripleo] Proposal to require bugs for tech debt

Hey folks, I'm proposing that in order to track tech debt that we're adding in as part of development that we create a way to track these items and not approve them without a bug (and a reference to said bug)[0]. Please take a moment to review the proposed policy and comment. I would like to

Re: [openstack-dev] [tc] Declaring explicit minimum database versions

On 2017-08-15 11:59 AM, Monty Taylor wrote: stabbing himself in the eyes yesterday I find it interesting that I was just about to read this article: https://www.thestar.com/opinion/commentary/2017/08/15/boys-and-men-must-do-the-right-thing-it-will-save-female-lives.html when I noticed Monty

Re: [openstack-dev] [trove][tc][all] Trove restart - next steps

Tim, This is an idea that was discussed at a trove midcycle a long time back (Juno midcycle, 2014). It came up briefly in the Kilo midcycle as well but was quickly rejected again. I've added it to the list of topics for discussion at the PTG. If others want to add topics to that list, the

Re: [openstack-dev] [keystone] Adding Kristi Nikolla to keystone-core

Congrats Kristi! Well deserved. On Tue, Aug 15, 2017 at 4:54 PM, Davanum Srinivas wrote: > Go Kristi! > > On Tue, Aug 15, 2017 at 3:00 PM, Lance Bragstad > wrote: > > I made the announcement in today's keystone meeting [0] that the current > > reviewers

[openstack-dev] [tacker] vim fernet keys HA deployment

Hi, While deploying master multinode realized vim fernet keys are created locally only in one node unless barbican is used. This causes only be able to run one tacker-server service simultaneously. Question: Is there a method in tacker to make HA multinode without barbican and without shared

Re: [openstack-dev] [keystone] Adding Kristi Nikolla to keystone-core

Go Kristi! On Tue, Aug 15, 2017 at 3:00 PM, Lance Bragstad wrote: > I made the announcement in today's keystone meeting [0] that the current > reviewers have decided to add Kristi Nikolla (knikolla) to the team. > > Kristi has been an extremely valuable asset to the team

Re: [openstack-dev] [kolla-kubernetes] Proposing Rich Wellum to core team

+1 from me as well. Great job Rich :D On Fri, Aug 11, 2017 at 11:01 AM, Michał Jastrzębski wrote: > Hello, > > It's my pleasure to start another core team vote. This time for our > colleague rwellum. I propose that he joins kolla-kubernetes team. > > This is my +1 vote. Every

Re: [openstack-dev] [kolla-kubernetes] Proposing Rich Wellum to core team

Would be great to have Rich, an enthusiastic +1 from me :) On Sat, Aug 12, 2017 at 11:38 AM, Serguei Bezverkhi (sbezverk) < sbezv...@cisco.com> wrote: > +1 > > well deserved > > Serguei > > *From: *"Vikram Hosakote (vhosakot)" > *Reply-To: *"OpenStack Development Mailing

Re: [openstack-dev] [keystone] Adding Kristi Nikolla to keystone-core

Congrats Kristi! Well deserved indeed! On Tue, Aug 15, 2017 at 3:00 PM, Lance Bragstad wrote: > I made the announcement in today's keystone meeting [0] that the current > reviewers have decided to add Kristi Nikolla (knikolla) to the team. > > Kristi has been an extremely

[openstack-dev] [keystone] Adding Kristi Nikolla to keystone-core

I made the announcement in today's keystone meeting [0] that the current reviewers have decided to add Kristi Nikolla (knikolla) to the team. Kristi has been an extremely valuable asset to the team over the last couple of releases. He especially stepped up to the plate during Pike. He provides

[openstack-dev] [tc] [all] TC Report 33

(If you prefer HTML: https://anticdent.org/tc-report-33.html ) Some are still in peak release cycle time and others have left for their summer holidays, so once again: a bit of a slow week. No major spectacles or controversies, so the best I can do is give some summaries of the conversations in

Re: [openstack-dev] [watcher] Stepping down as Watcher spec core

Antoine, It’s been a pleasure getting to work alongside you in the open source community. Your leadership was paramount to the project and I wish you all the best in your next chapter! Best, Joe (jwcroppe) > On Aug 15, 2017, at 1:26 PM, Susanne Balle wrote: > >

Re: [openstack-dev] [watcher] Stepping down as Watcher spec core

Thanks for all the hard work. best of luck, Susanne On Fri, Jul 21, 2017 at 3:48 AM, Чадин Александр (Alexander Chadin) < a.cha...@servionica.ru> wrote: > Antoine, > > Congratulations to the new step of your life! > You’ve set high level of project management and this is big honour to me > to

Re: [openstack-dev] [watcher] nominate Aditi Sharma to Watcher Core group

+1 On Thu, Aug 3, 2017 at 7:40 PM, Hidekazu Nakamura < hid-nakam...@vf.jp.nec.com> wrote: > +1 > > > -Original Message- > > From: Чадин Александр (Alexander Chadin) > > [mailto:a.cha...@servionica.ru] > > Sent: Wednesday, August 02, 2017 9:48 PM > > To: OpenStack Development Mailing List

[openstack-dev] [all][elections] Last days to elect your PTL for Ironic and Documentation

Hello Ironic and Documentation contributors, Just a quick reminder that elections are closing soon, if you haven't already you should use your right to vote and pick your favorite candidate! You have until August 16th, 2017 at 23:45 UTC. Thanks for your time! -Kendall Nelson(diablo_rojo)

Re: [openstack-dev] [oslo][oslo.messaging] Proposing Andy Smith as an oslo.messaging core reviewers

+1 On Tue, Aug 15, 2017 at 12:21 PM, Ben Nemec wrote: > +1 > > > On 08/14/2017 05:59 AM, ChangBo Guo wrote: >> >> I propose that we add Andy Smith to the oslo.messaging team. >> >> Andy Smith has been actively contributing to oslo.messaging for a while >> now, both >> in

Re: [openstack-dev] [trove][tc][all] Trove restart - next steps

One idea I found interesting from the past discussion was the approach that the user need is a database with a connection string. How feasible is the approach where we are provisioning access to a multi-tenant database infrastructure rather than deploying a VM with storage and installing a

Re: [openstack-dev] [oslo][oslo.messaging] Proposing Andy Smith as an oslo.messaging core reviewers

+1 On 08/14/2017 05:59 AM, ChangBo Guo wrote: I propose that we add Andy Smith to the oslo.messaging team. Andy Smith has been actively contributing to oslo.messaging for a while now, both in helping make oslo.messaging better via code contribution(s) and by helping with the review load when

Re: [openstack-dev] [keystone] using only sql for resource backends

On Tue, Aug 15, 2017 at 7:36 AM, Lance Bragstad wrote: > During RC, Morgan's made quite a bit of progress on a bug found by the > gate [0]. Part of the solution led to another patch that removes the > ability to configure anything but sql for keystone's resource backend >

[openstack-dev] [tc] Declaring explicit minimum database versions

Hey all, Morgan was stabbing himself in the eyes yesterday dealing with a database issue in keystone related to datetimes and subsecond precision. As usually happens when people want to stab MySQL I got roped in and my first thought was "dude, we landed the subsecond precision patches in

Re: [openstack-dev] [snaps] proposing Pete Vander Giessen for snaps-core and snaps-release group membership

On Mon, Aug 14, 2017 at 4:27 PM, Ryan Beisner wrote: > Hi Snappers > > I'm writing to propose Pete Vander Giessen to the *snaps-core* and > *snaps-release* groups. Pete has done a good bit of work in OpenStack > Snaps, particularly snap testing and CI tooling. I

[openstack-dev] [trove][tc][all] Trove restart - next steps

Now that we have successfully navigated the Pike release and branched the tree, I would like to restart the conversation about how to revive and restart the Trove project. Feedback from the last go around on this subject[1] resulted in a lively discussion which I summarized in [2]. The very quick

Re: [openstack-dev] [snaps] proposing David Ames for snaps-core and snaps-release group membership

On Mon, Aug 14, 2017 at 4:22 PM, Ryan Beisner wrote: > Hi Snappers > > I'm writing to propose David Ames to the *snaps-core* and *snaps-release* > groups. David has done a good bit of work in OpenStack Snaps. I feel he > would add a lot of value to the general

[openstack-dev] [nova] notification subteam meeting is canceled

Hi, The notification subteam meeting is canceled this week. Cheers, gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [keystone] using only sql for resource backends

During RC, Morgan's made quite a bit of progress on a bug found by the gate [0]. Part of the solution led to another patch that removes the ability to configure anything but sql for keystone's resource backend (`keystone.conf [resource] driver`). The reasoning behind this is that there were FK

Re: [openstack-dev] [release][ptl] tools for creating new releases

On 08/08/2017 03:30 PM, Doug Hellmann wrote: We realized recently that we haven't publicized some of the tools in the releases repository very well. One tool that will be useful this week as you prepare your release candidates is the 'new-release' command, which edits a deliverable file to add a

Re: [openstack-dev] [masakari]I withdraw my remark of today's IRC meerting.

Hi Rikimaru, Thank you for verification. --- Regards, Sampath On Tue, Aug 15, 2017 at 7:37 PM, Rikimaru Honjo wrote: > Hello, > > In today's Masakari IRC meeting, I said that executing masakari notification > API was failed in the latest devstack

[openstack-dev] [masakari]I withdraw my remark of today's IRC meerting.

Hello, In today's Masakari IRC meeting, I said that executing masakari notification API was failed in the latest devstack environment[1]. I rebuilt my environment after that. As a result, I couldn't reproduce the issue. So I don't report it to launchpad. Sorry. [1]

Re: [openstack-dev] [Oslo] PTG Planning with online meeting

Hi ALL, Oslo team will try to set up online meeting( maybe zoom) during the PTG, then others who can't travel to Denver can join the discussion. will send out the meeting link before the PTG. So please add topics in https://etherpad.openstack.org/p/oslo-ptg-queens even you can't attend the

Re: [openstack-dev] [l2gw] How to handle correctly unknown-dst traffic

> The ucast-mac-remote table is filled with information that don't match > your comments. In my environment, I have created only one neutron > network, one l2gw instance and one l2gw connection. However, the mac > reflected in that table corresponds to the dhcp port of the Neutron > network (I've

Re: [openstack-dev] [distributions][devstack][requirements] Upper constraints broken in stable/ocata on CentOS 7/RHEL 7

On Mon, Aug 14, 2017 at 05:58:50PM -0700, Arun SAG wrote: > Hi, > > RHEL/CentOS 7 released new libvirt packages (upgraded from 2.x to 3.x) > which broke bootstrapping devstack on stable/ocata branch. I have a review > up here to fix this in upper-requirements.txt >

[openstack-dev] [ironic][nova][grenade] Ironic CI grenade job degradation

Hello Community! Recently with CI performance degradation ironic team meet with the following problem. Quick automated cleaning is enabled on grenade jobs which is started exactly after nova instance is deleted. We do not wait for cleaning is finished in nova virt driver before mark instance as