Re: [openstack-dev] [horizon] Adding Ivan Kolodyazhny to the Horizon Core team

Ivan, Congratulations! Jay On 12/15/2017 10:52 AM, Ying Zuo (yinzuo) wrote: Hi everyone, After some discussion with the Horizon Core team, I am pleased to announce that we are adding Ivan Kolodyazhny to the team. Ivan has been actively contributing to Horizon since the beginning of the

Re: [openstack-dev] Race in FixedIP.associate_pool

Hi Jay, On Fri, Dec 15, 2017 at 1:56 PM, Jay Pipes wrote: > Can you point us to the code that is generating the above? It seems that > get_instance_nw_info() in the Yahoo! manager.py contrib module line 965 is > trying to build network information for an empty list of

Re: [openstack-dev] [ceilometer] about add transformer into libvirt

2017-12-15 23:17 GMT+08:00 gordon chung : > > > On 2017-12-14 10:38 PM, Jaze Lee wrote: >> It sounds like great. When the gnocchi can be ready to do transformer's work? >> If it takes long time, we have to move to compute temporarily. > > it already exists in gnocchi 4.1+. we just

Re: [OpenStack-Infra] Xenial Upgrade Sprint Recap

Clark Boylan writes: > Hello everyone, > > Just wanted to quickly recap what we got done this week during our > control plane upgrade to Xenial sprint. Thanks! Now that this is over, I wonder if we should start a 'marathon' (as opposed to a sprint) to finish the rest of

Re: [openstack-dev] [neutron] Stepping down from core

Armando, You’ve been great for Neutron. It’s sad to see you have to cut back, but it’s great to hear you aren’t totally leaving. Thank you for all of your hard work. You’ve brought Neutron along quite nicely. I’d also like to thank you for all of your help with the stadium projects. Your

Re: [openstack-dev] [all] Switching to longer development cycles

On 12/15/2017 05:52 PM, Matt Riedemann wrote: > On 12/15/2017 9:15 AM, Thomas Goirand wrote: >> Not only that. Everyone is lagging a few release behind, and currently, >> upstream OpenStack don't care backporting to older releases. > > Can you clarify this please? The nova team is definitely

Re: [openstack-dev] [First Contact] [SIG] Presence at the PTG

Thinking more around a half a day to a full day, but if you can't make it the whole time I will likely type up a summary to send to the dev list at the end and take notes all throughout our discussions. -Kendall (diablo_rojo) On Thu, Dec 14, 2017 at 5:10 PM Ghanshyam Mann

[OpenStack-Infra] Xenial Upgrade Sprint Recap

Hello everyone, Just wanted to quickly recap what we got done this week during our control plane upgrade to Xenial sprint. Prior to the sprint we had a few systems running on Xenial: * Everything zuulv3 * All of the new nodepool launchers and image builders * The translate servers * The

Re: [openstack-dev] Race in FixedIP.associate_pool

On 12/12/2017 03:22 PM, Arun SAG wrote: This kind of how the logs look like 2017-12-08 22:33:37,124 DEBUG [yahoo.contrib.ocata_openstack_yahoo_plugins.nova.network.manager]

Re: [openstack-dev] [all] Switching to longer development cycles

On Thu, Dec 14, 2017 at 7:07 AM, Dan Smith wrote: > > > Agreed. The first reaction I had to this proposal was pretty much what > you state here: that now the 20% person has a 365-day window in which > they have to keep their head in the game, instead of a 180-day one. > >

Re: [Openstack] [Openstack-operators] Certifying SDKs

+1 to editing the sheet as well and because you are spot on with your assessment of what I meant; scenarios we can “guarantee” an SDK allows/affords a tool to deliver on. -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: +1 (832) 264-2646 irc: mrhillsman On 12/15/17, 1:53 PM,

Re: [Openstack-operators] [Openstack] Certifying SDKs

+1 to editing the sheet as well and because you are spot on with your assessment of what I meant; scenarios we can “guarantee” an SDK allows/affords a tool to deliver on. -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: +1 (832) 264-2646 irc: mrhillsman On 12/15/17, 1:53 PM,

[openstack-dev] [keystone] Keystone weekly update - Week of 11 December 2017

Hey all, Things were pretty light this week since people are preparing for the holidays. Colleen is out this week, so I'm going to take a stab at the weekly report. # Keystone Team Update - Week of 11 December 2017 ## News ### Specification Freeze December 8th was specification freeze for

Re: [Openstack] [Openstack-operators] Certifying SDKs

Joe, +1 to edit the sheet directly. Thanks, Dims On Fri, Dec 15, 2017 at 2:45 PM, Joe Topjian wrote: > Hi all, > > I've been meaning to reply to this thread. Volodymyr, your reply reminded me > :) > > I agree with what you said that the SDK should support everything that the

Re: [Openstack-operators] [Openstack] Certifying SDKs

Joe, +1 to edit the sheet directly. Thanks, Dims On Fri, Dec 15, 2017 at 2:45 PM, Joe Topjian wrote: > Hi all, > > I've been meaning to reply to this thread. Volodymyr, your reply reminded me > :) > > I agree with what you said that the SDK should support everything that the

Re: [Openstack] [Openstack-operators] Certifying SDKs

Hi all, I've been meaning to reply to this thread. Volodymyr, your reply reminded me :) I agree with what you said that the SDK should support everything that the API supports. In that way, one could simply review the API reference docs and create a checklist for each possible action. I've often

Re: [Openstack-operators] [Openstack] Certifying SDKs

Hi all, I've been meaning to reply to this thread. Volodymyr, your reply reminded me :) I agree with what you said that the SDK should support everything that the API supports. In that way, one could simply review the API reference docs and create a checklist for each possible action. I've often

Re: [openstack-dev] [tripleo] TripleO CI end of sprint status

On Fri, Dec 15, 2017 at 1:15 PM, Ben Nemec wrote: > > > On 12/15/2017 10:26 AM, Emilien Macchi wrote: > >> On Fri, Dec 15, 2017 at 5:04 AM, Arx Cruz wrote: >> [...] >> >>> The goal on this sprint was to enable into quickstart a way to reproduce >>>

[openstack-dev] [neutron] Stepping down from core

Hi neutrinos, To some of you this email may not come as a surprise. During the past few months my upstream community engagements have been more and more sporadic. While I tried hard to stay committed and fulfill my core responsibilities I feel like I failed to retain the level of quality and

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

On Thu, Dec 14, 2017 at 5:01 PM, Tony Breeds wrote: > On Wed, Dec 13, 2017 at 03:01:41PM -0700, Alex Schultz wrote: >> I assume since some of this work was sort of done earlier outside of >> tripleo and does not affect the default installation path that most >> folks will

Re: [openstack-dev] [tripleo] TripleO CI end of sprint status

On 12/15/2017 10:26 AM, Emilien Macchi wrote: On Fri, Dec 15, 2017 at 5:04 AM, Arx Cruz wrote: [...] The goal on this sprint was to enable into quickstart a way to reproduce upstream jobs, in your personal RDO cloud tenant, making easy to developers to debug and reproduce

Re: [openstack-dev] [tripleo] TripleO CI end of sprint status

On Fri, Dec 15, 2017 at 11:26 AM, Emilien Macchi wrote: > On Fri, Dec 15, 2017 at 5:04 AM, Arx Cruz wrote: > [...] > > The goal on this sprint was to enable into quickstart a way to reproduce > > upstream jobs, in your personal RDO cloud tenant, making

Re: [openstack-dev] [all] [tc] Community Goals for Rocky

On Tue, Nov 28, 2017 at 2:22 PM, Emilien Macchi wrote: [...] > Suggestions are welcome: > - on the mailing-list, in a new thread per goal [all] [tc] Proposing > goal XYZ for Rocky > - on Gerrit in openstack/governance like Kendall did. Just a fresh reminder about Rocky goals.

[openstack-dev] [horizon] Adding Ivan Kolodyazhny to the Horizon Core team

Hi everyone, After some discussion with the Horizon Core team, I am pleased to announce that we are adding Ivan Kolodyazhny to the team. Ivan has been actively contributing to Horizon since the beginning of the Pike release. He has worked on many bug fixes, blueprints, and performed thorough

Re: [openstack-dev] [all] Switching to longer development cycles

On 12/15/2017 9:15 AM, Thomas Goirand wrote: Not only that. Everyone is lagging a few release behind, and currently, upstream OpenStack don't care backporting to older releases. Can you clarify this please? The nova team is definitely backporting fixes to pike, ocata and newton. Newton isn't

[openstack-dev] No networking-sfc meetings until Jan 11

There will no networking-sfc meetings until Jan 11. Seasons greetings. https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting - Louis __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [tripleo] TripleO CI end of sprint status

On Fri, Dec 15, 2017 at 5:04 AM, Arx Cruz wrote: [...] > The goal on this sprint was to enable into quickstart a way to reproduce > upstream jobs, in your personal RDO cloud tenant, making easy to developers > to debug and reproduce their code. This phrase confused some

[openstack-dev] [nova] [placement] resource providers update 45

Here's resource provider and placement update 45. I think we'll call this one the last one of 2017 and I'll start things up again in 2018 on the 5th. Probably with some kind of new numbering scheme so the subjects don't overlap with this year. Thanks to everyone who has helped to move placement

[openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

I wanted to send out a note to any 3rd Party CI or other users of the tempest plugin code inside either openstack/ironic or openstack/ironic-inspector. That code has been migrated to the openstack/ironic-inspector-plugin repository. We have been busily (

Re: [openstack-dev] [ceilometer] about add transformer into libvirt

On 2017-12-14 10:38 PM, Jaze Lee wrote: > It sounds like great. When the gnocchi can be ready to do transformer's work? > If it takes long time, we have to move to compute temporarily. it already exists in gnocchi 4.1+. we just need to change the workflow in ceilometer so it integrates with

Re: [openstack-dev] [all] Switching to longer development cycles

On 12/14/2017 12:44 AM, Clint Byrum wrote: > We can take stock of the intermediate releases over the last year, and make > sure they all work together once a year. Chris Jones mentioned that we should > give users time between milestones and release. I suggest we release an > intermediary and

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

I have https://blueprints.launchpad.net/mistral/+spec/mistral-workflow-executions-yaql-function almost all implemented and I would like submit an FFE for it Cheers, Adriano On Fri, Dec 15, 2017 at 12:01 AM, Tony Breeds wrote: > On Wed, Dec 13, 2017 at 03:01:41PM

Re: [openstack-dev] [tripleo] Removing old baremetal commands from python-tripleoclient

On 12/15/2017 01:04 PM, Dmitry Tantsur wrote: On 12/15/2017 04:49 AM, Tony Breeds wrote: Hi All, In review I01837a9daf6f119292b5a2ffc361506925423f11 I updated ValidateInstackEnv to handle the case when then instackenv.json file needs to represent a node that deosn't require a pm_user for

[openstack-dev] [ironic] reminder about deadlines

Hi all! Half of the Queens cycle is behind us. I'd like to remind about a few deadlines and how they affect us: 1. Jan 18th is the non-client library release deadline. It affects ironic-lib and sushy. The latter has a few outstanding changes - please try to find some time to get them a bit

[openstack-dev] [tripleo] TripleO CI end of sprint status

Hello, On December 13 we came the end of sprint using our new team structure, and here’s the highlights. Sprint Review: The goal on this sprint was to enable into quickstart a way to reproduce upstream jobs, in your personal RDO cloud tenant, making easy to developers to debug and reproduce

Re: [openstack-dev] [tripleo] Removing old baremetal commands from python-tripleoclient

On 12/15/2017 04:49 AM, Tony Breeds wrote: Hi All, In review I01837a9daf6f119292b5a2ffc361506925423f11 I updated ValidateInstackEnv to handle the case when then instackenv.json file needs to represent a node that deosn't require a pm_user for IMPI to work. It turns out that I foudn that

Re: [openstack-dev] [all] Switching to longer development cycles

On 12/15/2017 11:00 AM, Luigi Toscano wrote: - Original Message - On 12/14/2017 9:38 AM, Luigi Toscano wrote: And the QE in me says that there are enough moving parts around for the integration testing (because CD yes, but the resources are limited) that a longer cycle with a longer

Re: [Openstack] Neutron/OpenVswitch problem

Hi again I've discovered that this error in raised only when the environment has neutron-fwaas extension enabled. Without it, everything is ok. Any ideas on the relation between fwaas and /Port not present in bridge br-int /? On 14/12/17 18:54, magicb...@gmail.com wrote: Hi everyone,

Re: [openstack-dev] [oslo][requirements][vitrage] oslo.service 1.28.1 breaks Vitrage gate

Thanks for raising this, Oslo team will revert the change in https://review.openstack.org/#/c/528202/ 2017-12-14 23:58 GMT+08:00 Afek, Ifat (Nokia - IL/Kfar Sava) < ifat.a...@nokia.com>: > Hi, > > > > The latest release of oslo.service 1.28.1 breaks the Vitrage gate. We are > creating several

Re: [openstack-dev] [nova][stable] What nova needs to get to newton end of life

On 14-12-17 09:15:18, Matt Riedemann wrote: > I'm not sure how many other projects still have an active stable/newton > branch, but I know nova is one of them. > > At this point, these are I think the things that need to get done to end of > life the newton branch for nova: > > 1. We have a set

Re: [Openstack-operators] Newton LBaaS v2 settings

Hi, That is fantastic, just what I am looking for! Thanks for the help. Kind Regards, On 15/12/17 10:43, Volodymyr Litovka wrote: Hi Grant, in case of Octavia, when you create healthmonitor with parameters of monitoring: $ openstack loadbalancer healthmonitor create usage: openstack

Re: [Openstack-operators] Newton LBaaS v2 settings

Hi Grant, in case of Octavia, when you create healthmonitor with parameters of monitoring: $ openstack loadbalancer healthmonitor create usage: openstack loadbalancer healthmonitor create [-h]    [-f {json,shell,table,value,yaml}]  

[openstack-dev] [tc] Technical Committee Status update, December 15th

Hi! This is the weekly summary of Technical Committee initiatives. You can find the full list of all open topics (updated twice a week) at: https://wiki.openstack.org/wiki/Technical_Committee_Tracker If you are working on something (or plan to work on something) that is not on the tracker, feel

Re: [Openstack-operators] thierry's longer dev cycle proposal

The thread on the dev list is already too long for my liking. I hope there will be a TL;DR in the dev mailing list digest. Tomas -Original Message- From: arkady.kanev...@dell.com [mailto:arkady.kanev...@dell.com] Sent: Thursday, December 14, 2017 3:40 AM To: mrhills...@gmail.com;

[Openstack-operators] Newton LBaaS v2 settings

Hi All, I wonder if anyone would be able to help with some settings I might be obviously missing for LBaaS. We have a client that uses the service but they are coming across issues with their app randomly not working.  Basically if their app takes longer than 20 seconds to process a request

Re: [openstack-dev] [all] Switching to longer development cycles

Adrian Turjak wrote: > I worry that moving to a yearly release is actually going to make things > worse for deployers and there will be less encouragement for them to be > on more up to date and bug fixed code. Not to mention, no one will trust > or use the intermediary releases unless they are

Re: [openstack-dev] [all] Switching to longer development cycles

- Original Message - > On 12/14/2017 9:38 AM, Luigi Toscano wrote: > > And the QE in me says that there are enough moving parts around for the > > integration testing (because CD yes, but the resources are limited) that a > > longer cycle with a longer time between freeze and release is