Re: [openstack-dev] ​ [mistral] timeout and retry

> No matter at what stage the task is, but if it’s still in RUNNING state or FAILED but we know that retry policy still didn’t use all attempts then the ‘timeout’ policy should force the task to fail.Ok, then we have a bug because timeout policy doesn't force the task to fail. It retries task. And

Re: [openstack-dev] [mistral] A mechanism to close stuck running executions

Hi Vitalii, thanks for reminding. I've almost forgotten about it. I've updated with the stuff we have tested locally for months. Looking forward to your comments! Thanks, Andras Vitalii Solodilov ezt írta (időpont: 2018. ápr. 27., P, 3:31): > Hi, Jozsef and Andras. > Do you

Re: [openstack-dev] ​[openstack-dev] [mistral] timeout and retry

Hi, I don’t clearly understand the problem you’re trying to point to. IMO, when using these two policies at the same time ‘timeout’ policy should have higher priority. No matter at what stage the task is, but if it’s still in RUNNING state or FAILED but we know that retry policy still didn’t

Re: [openstack-dev] Fwd: [tripleo] PTG session about All-In-One installer: recap & roadmap

We created a new board where we'll track the efforts for the all-in-one installer: https://trello.com/b/iAHhAgjV/tripleo-all-in-one-installer Note: please do not use the containerized undercloud dashboard for these tasks, it is a separated effort. Feel free to join the board and feed the backlog!

Re: [openstack-dev] [osc][swift] Setting storage policy for a container possible via the client?

On 20/04/18 04:54, Dean Troyer wrote: On Thu, Apr 19, 2018 at 7:51 AM, Doug Hellmann wrote: Excerpts from Mark Kirkwood's message of 2018-04-19 16:47:58 +1200: Swift has had storage policies for a while now. These are enabled by setting the 'X-Storage-Policy' header

[openstack-dev] [mistral] A mechanism to close stuck running executions

Hi, Jozsef and Andras. Do you plan to finish this patch? https://review.openstack.org/#/c/527085 I think the stuck RUNNING executions is very a sensitive subject for Mistral. --  Best regards, Vitalii Solodilov __

Re: [openstack-dev] [kolla][vote]Core nomination for Mark Goddard (mgoddard) as kolla core member

+1 Good Contribution !! Mark On Thu, Apr 26, 2018 at 9:01 PM, Jeffrey Zhang wrote: > Kolla core reviewer team, > > It is my pleasure to nominate > mgoddard for kolla core team. > Mark has been working both upstream and downstream with kolla and > kolla-ansible for over

Re: [openstack-dev] Summit Forum Schedule

No problem at all: https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21780/manila-ops-feedback-running-at-scale-overcoming-barriers-to-deployment Tom Barron wrote: running at scale, barriers to deployment

Re: [openstack-dev] Summit Forum Schedule

Jimmy, Also can we 's/barriers/overcoming barriers/' in the title of the manila session? Thanks! -- Tom On 26/04/18 15:27 -0500, Jimmy McArthur wrote: No problem. Done :) Colleen Murphy April 26, 2018 at 1:23 PM Hi Jimmy, I have a conflict on Thursday

Re: [openstack-dev] Changes to keystone-stable-maint members

On Tue, Apr 24, 2018 at 10:58:06AM -0700, Morgan Fainberg wrote: > Hi, > > I am proposing making some changes to the Keystone Stable Maint team. > A lot of this is cleanup for contributors that have moved on from > OpenStack. For the most part, I've been the only one responsible for > Keystone

[openstack-dev] new tool for quickly fixing nits on gerrit reviews

For a while now I've been encouraging folks to propose follow-up patches to fix nits on proposed changes, rather than waiting ages for someone to respond to a -1 for a little typo. Today I've release git-nit, a tool to make doing that easier. The idea is that you would run a command like: $

Re: [openstack-dev] Summit Forum Schedule

No problem. Done :) Colleen Murphy April 26, 2018 at 1:23 PM Hi Jimmy, I have a conflict on Thursday afternoon. Could I propose swapping these two sessions: Monday 11:35-12:15 Manila Ops feedback: running at scale, barriers to deployment Thursday 1:50-2:30

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

Doug Hellmann wrote: Excerpts from Adam Spiers's message of 2018-04-25 18:15:42 +0100: [BTW I hope it's not considered off-bounds for those of us who aren't TC election candidates to reply within these campaign question threads to responses from the candidates - but if

Re: [openstack-dev] Summit Forum Schedule

Hi Jimmy, On Wed, Apr 25, 2018, at 11:07 PM, Jimmy McArthur wrote: > Hi everyone - > > Please have a look at the Vancouver Forum schedule: > https://docs.google.com/spreadsheets/d/15hkU0FLJ7yqougCiCQgprwTy867CGnmUvAvKaBjlDAo/edit?usp=sharing > > (also attached as a CSV) The proposed schedule

Re: [openstack-dev] [all][tc] final stages of python 3 transition

On Thu, Apr 26, 2018, at 7:27 AM, Sean McGinnis wrote: > On Wed, Apr 25, 2018 at 04:54:46PM -0400, Doug Hellmann wrote: > > It's time to talk about the next steps in our migration from python > > 2 to python 3. > > > > [...] > > > > 2. Change (or duplicate) all functional test jobs to run under

Re: [openstack-dev] [all][tc] final stages of python 3 transition

On 2018-04-26 13:17:33 -0400 (-0400), Paul Belanger wrote: [...] > This maybe okay, will allow others to comment, but the main reason > I am not a fan, is we can no longer infer the nodeset by looking > at the job name. tox-py3 could be xenial or bionic. This brings back a question we've

Re: [openstack-dev] [all][tc] final stages of python 3 transition

On Thu, Apr 26, 2018 at 09:27:31AM -0500, Sean McGinnis wrote: > On Wed, Apr 25, 2018 at 04:54:46PM -0400, Doug Hellmann wrote: > > It's time to talk about the next steps in our migration from python > > 2 to python 3. > > > > [...] > > > > 2. Change (or duplicate) all functional test jobs to

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

My worry with changing the default is that it would be like adding the following in /etc/environment, alias ls=' rm -rf / --no-preserve-root' i.e. an operation which was previously read-only now becomes irreversible. We also have current use cases with Ironic where we are moving machines

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, Today's meeting was quite short and saw a review of everyone's status and the merging of one guideline. We began by sharing our current work and plans for the near future. Although everyone is on tight schedules currently, we discussed the next steps for the work

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

+1. It would be good to also identify the use cases. Surprised that node should be cleaned up automatically. I would expect that we want it to be a deliberate request from administrator to do. Maybe user when they "return" a node to free pool after baremetal usage. Thanks, Arkady -Original

Re: [openstack-dev] [infra][qa][requirements] Pip 10 is on the way

Clark Boylan writes: ... > I've since worked out a change that passes tempest using a global > virtualenv installed devstack at > https://review.openstack.org/#/c/558930/. This needs to be cleaned up > so that we only check for and install the virtualenv(s) once and we >

Re: [openstack-dev] [kolla][neutron][requirements][pbr]Use git+https line in requirements.txt break the pip install

W dniu 18.04.2018 o 04:48, Jeffrey Zhang pisze: > Is this expected? and how could we fix this? I posted a workaround: https://review.openstack.org/#/c/564552/ But this should be fixed in networking-odl (imho). __ OpenStack

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

How about asking the operators at the summit Forum or asking on openstack-operators to see what the users think? Tim -Original Message- From: Ben Nemec Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [openstack-ansible] Proposing Mohammed Naser as core reviewer

+2! On Thu, Apr 26, 2018 at 10:20 AM, Carter, Kevin wrote: > +2 from me! > > > -- > > Kevin Carter > IRC: Cloudnull > > On Wed, Apr 25, 2018 at 4:06 AM, Markos Chandras wrote: >> >> On 24/04/18 16:05, Jean-Philippe Evrard wrote: >> > Hi everyone, >> > >>

Re: [openstack-dev] [Designate] Plan for OSM

On 04/25/2018 11:31 PM, da...@vn.fujitsu.com wrote: Hi forks, We tested and completed our process with OVO migration in Queens cycle. Now, we can continue with OSM implementation for Designate. Actually, we have pushed some patches related to OSM[1] and it's ready to review. Out of

Re: [openstack-dev] [kolla][vote]Core nomination for Mark Goddard (mgoddard) as kolla core member

W dniu 26.04.2018 o 17:31, Jeffrey Zhang pisze: > Kolla core reviewer team, > > It is my pleasure to nominate > ​ > mgoddard for kolla core team. +1 __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [kolla][vote]Core nomination for Mark Goddard (mgoddard) as kolla core member

+1 > On 26. Apr 2018, at 17:31, Jeffrey Zhang wrote: > > Kolla core reviewer team, > > It is my pleasure to nominate ​mgoddard for kolla core team. > ​ > Mark has been working both upstream and downstream with kolla and > kolla-ansible for over two years, building bare

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

On 04/26/2018 09:24 AM, Dmitry Tantsur wrote: Answering to both James and Ben inline. On 04/25/2018 05:47 PM, Ben Nemec wrote: On 04/25/2018 10:28 AM, James Slagle wrote: On Wed, Apr 25, 2018 at 10:55 AM, Dmitry Tantsur wrote: On 04/25/2018 04:26 PM, James Slagle

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

On Thu, Apr 26, 2018 at 11:24 AM, Dmitry Tantsur wrote: > Sure, but how do people know if they want it? Okay, if they use Ceph, they > have to. Then.. mm.. "if you have multiple disks and you're not sure what's > on them, please clean"? It may work, I wonder how many people

[openstack-dev] [kolla][vote]Core nomination for Mark Goddard (mgoddard) as kolla core member

Kolla core reviewer team, It is my pleasure to nominate ​ mgoddard for kolla core team. ​ Mark has been working both upstream and downstream with kolla and kolla-ansible for over two years, building bare metal compute clouds with ironic for HPC. He's been involved with OpenStack since 2014. He

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

On 04/26/2018 05:12 PM, James Slagle wrote: On Thu, Apr 26, 2018 at 10:24 AM, Dmitry Tantsur wrote: Answering to both James and Ben inline. On 04/25/2018 05:47 PM, Ben Nemec wrote: On 04/25/2018 10:28 AM, James Slagle wrote: On Wed, Apr 25, 2018 at 10:55 AM, Dmitry

Re: [openstack-dev] Summit Forum Schedule

Matt Riedemann wrote: > On 4/25/2018 4:07 PM, Jimmy McArthur wrote: >> Please have a look at the Vancouver Forum schedule: >> https://docs.google.com/spreadsheets/d/15hkU0FLJ7yqougCiCQgprwTy867CGnmUvAvKaBjlDAo/edit?usp=sharing >> (also attached as a CSV) The proposed schedule was put together by

Re: [openstack-dev] [openstack-ansible] Proposing Mohammed Naser as core reviewer

+2 from me! -- Kevin Carter IRC: Cloudnull On Wed, Apr 25, 2018 at 4:06 AM, Markos Chandras wrote: > On 24/04/18 16:05, Jean-Philippe Evrard wrote: > > Hi everyone, > > > > I’d like to propose Mohammed Naser [1] as a core reviewer for > OpenStack-Ansible. > > > > +2 > > --

Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

On 4/25/18 10:13 PM, Shu M. wrote: > Hi folks, > >> unwinding things >> >> >> There are a few different options, but it's important to keep in mind >> that we ultimately want all of the following: >> >> * The code works >> * Tests can run properly in CI >> * "Depends-On" works in

Re: [openstack-dev] [E] [tripleo] ironic automated cleaning by default?

This change would need to be very clearly mentioned in Documentation/Release Notes. It could be a really nasty surprise for an operator expecting the current behavior. On Wed, Apr 25, 2018 at 8:14 AM, Dmitry Tantsur wrote: > Hi all, > > I'd like to restart conversation on

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

On Thu, Apr 26, 2018 at 10:24 AM, Dmitry Tantsur wrote: > Answering to both James and Ben inline. > > > On 04/25/2018 05:47 PM, Ben Nemec wrote: >> >> >> >> On 04/25/2018 10:28 AM, James Slagle wrote: >>> >>> On Wed, Apr 25, 2018 at 10:55 AM, Dmitry Tantsur

[openstack-dev] [Neutron] [Upgrades] Cancel next IRC meeting (May 3rd)

Hi, We are canceling our next Neutron Upgrades subteam meeting on May 3rd. We will resume on May 10th. Thanks, Lujin __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] Following the new PTI for document build, broken local builds

On Wed, 2018-04-25 at 12:06 -0500, Sean McGinnis wrote: > > > > > > > > [1] https://review.openstack.org/#/c/564232/ > > > > > > > > > > The only concern I have is that it may slow the transition to the > > > python 3 version of the jobs, since someone would have to actually > > > fix the

Re: [openstack-dev] [all][tc] final stages of python 3 transition

On Wed, Apr 25, 2018 at 04:54:46PM -0400, Doug Hellmann wrote: > It's time to talk about the next steps in our migration from python > 2 to python 3. > > [...] > > 2. Change (or duplicate) all functional test jobs to run under >python 3. As a test I ran Cinder functional and unit test jobs

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

Answering to both James and Ben inline. On 04/25/2018 05:47 PM, Ben Nemec wrote: On 04/25/2018 10:28 AM, James Slagle wrote: On Wed, Apr 25, 2018 at 10:55 AM, Dmitry Tantsur wrote: On 04/25/2018 04:26 PM, James Slagle wrote: On Wed, Apr 25, 2018 at 9:14 AM, Dmitry

Re: [openstack-dev] [all][tc] final stages of python 3 transition

On 04/25/2018 11:40 PM, Jeremy Stanley wrote: > It may be worth considering how this interacts with the switch of > our default test platform from Ubuntu 16.04 (which provides Python > 3.5) to 18.04 (which provides Python 3.6). If we switch from 3.5 to > 3.6 before we change most remaining jobs

Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

Monty Taylor wrote on 04/25/2018 09:40:47 AM: ... > Introduce a whitelist of git repo urls, starting with: > >* https://git.openstack.org/openstack/neutron >* https://git.openstack.org/openstack/horizon > We would also need to include at least nova (e.g. [1]) and

[openstack-dev] [release] Release countdown for week R-17, April 30 - May 4

Time again for our regular release countdown email. Development Focus - Teams should now be focused on feature development and completion of release goals [0]. [0] https://governance.openstack.org/tc/goals/rocky/index.html General Information --- If you have

Re: [openstack-dev] Summit Forum Schedule

On 4/25/2018 4:07 PM, Jimmy McArthur wrote: Please have a look at the Vancouver Forum schedule: https://docs.google.com/spreadsheets/d/15hkU0FLJ7yqougCiCQgprwTy867CGnmUvAvKaBjlDAo/edit?usp=sharing (also attached as a CSV) The proposed schedule was put together by two members from UC, TC and

[openstack-dev] [tripleo] [heat-templates] Deprecated environment files

Hi guys, I'm wondering, what is the plan of having these environments/*.yaml and enviroments/services-baremetal/*.yaml. It seems that it's deprecated files, Please advice here. Regards Waleed Mousa SW Engineer at Mellanox

[openstack-dev] [publiccloud-wg] Meeting this afternoon for Public Cloud WG

Hi folks, Time for a new meeting for the Public Cloud WG. Vancouver is coming closer, very open agenda this week so please join and bring your topic to discuss. The open agenda (please add topics) can be found at https://etherpad.openstack.org/p/publiccloud-wg See you all at 1400 UTC in

Re: [openstack-dev] [openstack-infra] How to take over a project?

Thank you, Thierry I will follow that link. Sangho > On 26 Apr 2018, at 5:09 PM, Thierry Carrez wrote: > > Sangho Shin wrote: >> Ihar, >> >> I tried to add netwokring-onos-core group to "Create Reference” permission >> using the gerrit UI, and it is registered as a

Re: [openstack-dev] [openstack-infra] How to take over a project?

Sangho Shin wrote: > Ihar, > > I tried to add netwokring-onos-core group to "Create Reference” permission > using the gerrit UI, and it is registered as a new gerrit review. > But, it seems that it is not a right process, according to the gerrit history > of the similar issues. > Can you please

Re: [openstack-dev] [openstack-infra] How to take over a project?

Ihar, I tried to add netwokring-onos-core group to "Create Reference” permission using the gerrit UI, and it is registered as a new gerrit review. But, it seems that it is not a right process, according to the gerrit history of the similar issues. Can you please let me know how to change the