[openstack-dev] [mistral][release][ffe] Requesting FFE for supporting source execution id in the Mistral client

Hi, We were asked to do a FFE request to be able to release a new version of Mistral client out of stable/queens branch. The backport patch: https://review.openstack.org/#/c/543393/ The release patch: https://review.openstack.org/#/c/543402 The reason to do that after the feature freeze is that

[openstack-dev] [mistral][release] Release of openstack/mistral-extra failed

Hey Mistral team, We had a release job failure for mistral-extra. The issue was caused by something that has already been fixed in master (and stable/queens). The root cause of the problem is the way that tox is using constraints. This caused an issue during an attempt to create a source distribu

Re: [openstack-dev] [mistral] Proposing time slots for Mistral office hours

I'm good for helping with the Monday and Friday time slots Cheers, Adriano On Mon, Feb 5, 2018 at 3:23 PM, Dougal Matthews wrote: > > > On 5 February 2018 at 07:48, Renat Akhmerov > wrote: > >> Hi, >> >> Not so long ago we decided to stop holding weekly meetings in one of the >> general IR

[openstack-dev] [mistral] PTG planning on Friday “office hours” session

Hi, This Friday at 8.00 UTC we’ll have our first “Office hours” session according to the time slots earlier proposed in this email thread. It will be devoted to the Dublin PTG planning so please join us at #openstack-mistral if you want to participate (bring your items, get to know things going

[openstack-dev] [mistral] mistral-extra 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for mistral-extra for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral-extra/ Unless release-critical issues are found that warrant a release candidate respin, this candidate wi

[openstack-dev] [mistral] mistral-dashboard 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for mistral-dashboard for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this cand

[openstack-dev] [mistral] mistral 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for mistral for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formal

[openstack-dev] [Mistral][PTL] PTL candidacy for Rocky

I am announcing my candidacy for Mistral PTL for the Rocky release cycle. If you don't know me, I am d0ugal on Freenode. I have been working full time on OpenStack since the Icehouse release cycle in 2014. I started to contribute to Mistral in 2016 and joined the core team later that year. Since t

Re: [openstack-dev] [mistral] Proposing time slots for Mistral office hours

On 5 February 2018 at 07:48, Renat Akhmerov wrote: > Hi, > > Not so long ago we decided to stop holding weekly meetings in one of the > general IRC channel (it was #openstack-meeting-3 for the last several > months). The main reason was that we usually didn’t have a good > representation of the t

[openstack-dev] [mistral] Proposing time slots for Mistral office hours

Hi, Not so long ago we decided to stop holding weekly meetings in one of the general IRC channel (it was #openstack-meeting-3 for the last several months). The main reason was that we usually didn’t have a good representation of the team there because the team is distributed across the world. W

[openstack-dev] [mistral][ptl] PTL candidacy

Hi, I'm Renat Akhmerov. I'm running for PTL of Mistral in Rocky. Mistral is a workflow service developed within the OpenStack community from the ground up. In queens we mainly focused on bugfixing, improving performance and documentation. Performance was again significantly improved (~100%) by o

Re: [openstack-dev] [mistral] Adding Adriano Petrich to the core team

Thank you! On Tue, Jan 16, 2018 at 4:03 AM, Renat Akhmerov wrote: > Adriano, you now have +2 vote and can approve patches :) Welcome! > > Thanks > > Renat Akhmerov > @Nokia > > On 16 Jan 2018, 05:03 +0700, Lingxian Kong , wrote: > > welcome to the team, Adriano! > > > Cheers, > Lingxian Kong (La

Re: [openstack-dev] [mistral] Adding Adriano Petrich to the core team

Adriano, you now have +2 vote and can approve patches :) Welcome! Thanks Renat Akhmerov @Nokia On 16 Jan 2018, 05:03 +0700, Lingxian Kong , wrote: > welcome to the team, Adriano! > > > Cheers, > Lingxian Kong (Larry) > > > On Mon, Jan 15, 2018 at 10:11 PM, Renat Akhmerov > > wrote: > > > Hi, >

Re: [openstack-dev] [mistral] Adding Adriano Petrich to the core team

welcome to the team, Adriano! Cheers, Lingxian Kong (Larry) On Mon, Jan 15, 2018 at 10:11 PM, Renat Akhmerov wrote: > Hi, > > I’d like to promote Adriano Petrich to the Mistral core team. Adriano has > shown the good review rate and quality at least over the last two cycles > and implemented s

Re: [openstack-dev] [mistral] Adding Adriano Petrich to the core team

+1! On Mon, 15 Jan 2018 at 09:12, Renat Akhmerov wrote: > Hi, > > I’d like to promote Adriano Petrich to the Mistral core team. Adriano has > shown the good review rate and quality at least over the last two cycles > and implemented several important features (including new useful YAQL/JINJA >

[openstack-dev] [mistral] Adding Adriano Petrich to the core team

Hi, I’d like to promote Adriano Petrich to the Mistral core team. Adriano has shown the good review rate and quality at least over the last two cycles and implemented several important features (including new useful YAQL/JINJA functions). Please vote whether you agree to add Adriano to the cor

[openstack-dev] [mistral][irc] Switching to office hours from weekly meetings

our IRC channel #openstack-mistral or write to this mailing list with tags "[openstack-dev][mistral]” in the subject. Thanks Renat Akhmerov @Nokia __ OpenStack Development Mailing List (not for usage questions) Unsubs

Re: [openstack-dev] [mistral][ptl] PTL is on vacation from Nov 23 till Dec 4

Ooh, my apologies for the typo! Thanks Dougal ) Renat Akhmerov @Nokia On 20 Nov 2017, 18:42 +0700, Dougal Matthews , wrote: > > > > On 20 November 2017 at 08:56, Renat Akhmerov > > wrote: > > > Hi, > > > > > > I’ll be on vacation from Nov 23 till Dec 4, inclusive. Dougal Matthews > > > (d0gal

Re: [openstack-dev] [mistral][ptl] PTL is on vacation from Nov 23 till Dec 4

On 20 November 2017 at 08:56, Renat Akhmerov wrote: > Hi, > > I’ll be on vacation from Nov 23 till Dec 4, inclusive. Dougal Matthews > (d0gal) will be replacing me during this period. > It doesn't matter too much, but it is d0ugal if anyone is looking for me on IRC :-) > > Thanks > > Renat Akh

[openstack-dev] [mistral][ptl] PTL is on vacation from Nov 23 till Dec 4

Hi, I’ll be on vacation from Nov 23 till Dec 4, inclusive. Dougal Matthews (d0gal) will be replacing me during this period. Thanks Renat Akhmerov @Nokia __ OpenStack Development Mailing List (not for usage questions) Unsubs

[openstack-dev] [mistral] No team meeting today - 11/13/2017

Hi, we’re cancelling the team meeting today because a number of key members won’t attend. Thanks Renat Akhmerov @Nokia __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.

[openstack-dev] [mistral] Pike limit of 100 results makes debugging much harder

The Pike release of python-mistralclient added a default limit of 100 results returned to ease the burden on the database, which makes sense because it's rare that anyone actually needs all of the results that are returned. Unfortunately with the default sort order of "asc" this means that onl

[openstack-dev] [mistral] Cancelling team meeting - 09/18/2017

Hi, There won’t be a team today. Let’s meet next week and discuss the PTG summary and the current activities. Thanks Renat Akhmerov @Nokia __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: opensta

[openstack-dev] [mistral][ptg] Mistral PTG etherpad and schedule

Welcome to the Queens PTG! Just reminding that the Mistral PTG is at [1] and it includes the approximate schedule. I’m saying “approximate” because, if needed, we can change it a little bit if some important topics will be raised unexpectedly.  So I’d suggest we quickly review the entire schedu

[openstack-dev] [mistral] No team meeting today

Hi, We’re cancelling the team meeting today in IRC since our US team members have Labor Day. Renat Akhmerov @Nokia __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.open

[openstack-dev] [mistral] mistral-dashboard 5.0.0.0rc1 (pike)

Hello everyone, A new release candidate for mistral-dashboard for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candid

[openstack-dev] [mistral] mistral-extra 5.0.0.0rc1 (pike)

Hello everyone, A new release candidate for mistral-extra for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral-extra/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will

[openstack-dev] [mistral] mistral 5.0.0.0rc1 (pike)

Hello everyone, A new release candidate for mistral for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

[openstack-dev] [mistral][ptl] PTL is on vacation on Aug 14-28

Hi, I’ll be on vacation between Aug 14th and 28th. Dougal Matthews (d0ugal in IRC) kindly agreed to replace me while I’m off. Please contact him, if needed. Thanks Renat Akhmerov @Nokia __ OpenStack Development Mailing Lis

Re: [openstack-dev] [mistral][core] Proposing Andras Kovi to the Mistral core team

+1 from me. Andras will be a great addition to the core team. Original Message From: Lingxian Kong Sent: Thursday, August 10, 2017 02:59 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [mistral][core] Proposing A

Re: [openstack-dev] [mistral][core] Proposing Andras Kovi to the Mistral core team

+1, It will be great to have him! Cheers, Lingxian Kong (Larry) On Thu, Aug 10, 2017 at 5:34 PM, Renat Akhmerov wrote: > Hi, > > I’d like to propose Andras Kovi to the Mistral core team. > > The current statistics of Andras can be seen at [1]. > Andras has been contributing for about 1.5 years

Re: [openstack-dev] [mistral][core] Proposing Andras Kovi to the Mistral core team

Hi, +1 (from an other Nokia guy, who knows Andras personally and agrees, that he is a good guy ☺) Br, Gerg0 From: Dougal Matthews [mailto:dou...@redhat.com] Sent: Thursday, August 10, 2017 9:54 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev

Re: [openstack-dev] [mistral][core] Proposing Andras Kovi to the Mistral core team

On 10 August 2017 at 06:34, Renat Akhmerov wrote: > Hi, > > I’d like to propose Andras Kovi to the Mistral core team. > > The current statistics of Andras can be seen at [1]. > Andras has been contributing for about 1.5 years and in Pike he increased > his activity significantly, primarily review

[openstack-dev] [mistral][core] Proposing Andras Kovi to the Mistral core team

Hi, I’d like to propose Andras Kovi to the Mistral core team. The current statistics of Andras can be seen at [1]. Andras has been contributing for about 1.5 years and in Pike he increased his activity significantly, primarily reviewing. His reviews are always thorough and insightful. He cares

Re: [openstack-dev] [mistral][heat][tripleo][trove][murano][solum][tacker] Releasing python-mistralclient 3.1.2

On 8 Aug 2017, 17:45 +0700, Thierry Carrez , wrote: > Renat Akhmerov wrote: > > [...] > > So long story short, this change will affect your project only if you > > use “mistral action-execution-list” CLI command because now this command > > will be returning by default only 100 entries (to return

Re: [openstack-dev] [mistral][heat][tripleo][trove][murano][solum][tacker] Releasing python-mistralclient 3.1.2

Renat Akhmerov wrote: > [...] > So long story short, this change will affect your project only if you > use “mistral action-execution-list” CLI command because now this command > will be returning by default only 100 entries (to return all > “--limit=-1” needs to be passed). A number of projects d

[openstack-dev] [mistral][heat][tripleo][trove][murano][solum][tacker] Releasing python-mistralclient 3.1.2

Hi, We recently sent a patch [1] to release the version 3.1.2 of python-mistralclient out of Pike branch. It was done after the date of final client library releases so we’d like to discuss if we can allow such an exception. All the projects mentioned in the subject may be affected so please s

[openstack-dev] [mistral] No meeting today - 08/7/2017

Hi, We decided to cancel today’s Mistral meeting. Thanks Renat Akhmerov @Nokia __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http:/

[openstack-dev] [mistral][summit] Mistral sessions submitted for the Sydney summit

Hi, Here’s the list of talks related to Mistral that we submitted for the summit in Sydney: • What makes Mistral an OpenStack super-star? Right, CloudFlow! -  https://www.openstack.org/summit/sydney-2017/vote-for-speakers#/19109 • Test your Mistral workflows -  https://www.openstack.org/summit/s

Re: [openstack-dev] [mistral] CloudFlow demo available online

Thanks Guy! Great work ) Renat Akhmerov @Nokia On 11 Jul 2017, 16:53 +0700, Dougal Matthews , wrote: > Thanks for this - it is really useful to be able to click around and play > with the UI - gives me a much better feel for it. > > > > On 11 July 2017 at 08:26, Shaanan, Guy (Nokia - IL/Kfar Sav

Re: [openstack-dev] [mistral] CloudFlow demo available online

Thanks for this - it is really useful to be able to click around and play with the UI - gives me a much better feel for it. On 11 July 2017 at 08:26, Shaanan, Guy (Nokia - IL/Kfar Sava) < guy.shaa...@nokia.com> wrote: > CloudFlow (the Mistral Workflow Visualization Tool) demo is now available >

[openstack-dev] [mistral] CloudFlow demo available online

CloudFlow (the Mistral Workflow Visualization Tool) demo is now available online[1] using a real Mistral Pike instance. You can evaluate the tool by selecting one of the pre-existing executions, and: * See it's YAML definition, * Watch the execution information, * Select a task and w

Re: [openstack-dev] [mistral] External GUI for Mistral is now at github

Lingxian, good idea. Most likely, we’ll record it and share publicly. Thanks Renat Akhmerov @Nokia On 4 Jul 2017, 19:21 +0700, Lingxian Kong , wrote: > That's awesome! It'd be better if there is a demo for introduction :-) > > > Cheers, > Lingxian Kong (Larry) > > > On Tue, Jul 4, 2017 at 9:48 P

Re: [openstack-dev] [mistral] External GUI for Mistral is now at github

That's awesome! It'd be better if there is a demo for introduction :-) Cheers, Lingxian Kong (Larry) On Tue, Jul 4, 2017 at 9:48 PM, Shaanan, Guy (Nokia - IL/Kfar Sava) < guy.shaa...@nokia.com> wrote: > Hi all, > > > > We are happy to announce “CloudFlow”- a Mistral Workflow Execution > Visuali

[openstack-dev] [mistral] External GUI for Mistral is now at github

Hi all, We are happy to announce "CloudFlow"- a Mistral Workflow Execution Visualization tool, to help you debug and monitor in real time the progress of executions. CloudFlow offers web based GUI and relies on Mistral REST API. CloudFlow source code is publicly available on github[1]. With t

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

Ok, thanks Tuan. Renat Akhmerov @Nokia On 29 May 2017, 17:38 +0700, lương hữu tuấn , wrote: > Hi Renat, > > Kong is going to move on with this patch and then i will continue with the > main problem of trust token in Mistral. > > Br, > > Tuan/Nokia > > > On Mon, May 29, 2017 at 9:20 AM, Renat Akh

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

Hi Renat, Kong is going to move on with this patch and then i will continue with the main problem of trust token in Mistral. Br, Tuan/Nokia On Mon, May 29, 2017 at 9:20 AM, Renat Akhmerov wrote: > Tuan, > > It’s ok, not always people have cycles to finish something upstream. No > need to expl

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

Tuan, It’s ok, not always people have cycles to finish something upstream. No need to explain that. All I’m worried about is getting this thing done. So if you don’t have capacity please help transfer this work to someone else. Thanks Renat On 29 May 2017, 13:36 +0700, lương hữu tuấn , wrote:

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

Hi Doug and Renat, I totally agree with what Doug mentioned in the previous mail. In fact, my patch is only the used for the purpose of "implementing trust token", not for full refactoring mistral context. Since i do not have my capacity for contributing to Mistral, my commit now is for the need o

[openstack-dev] [mistral] No team meeting today - 05/29/2017

Hi, We’re cancelling today’s meeting since most of the key members can’t attend due to holidays in UK and US. Team, please keep in mind that next week we will release Pike-2. Try to wrap up your most important work this week. Thanks Renat Akhmerov @Nokia ___

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

Hi Doug, Anyway, thank for the notification. We are really appreciated. Regards, Vitaliy > 26 мая 2017 г., в 20:54, Doug Hellmann написал(а): > > Excerpts from Saad Zaher's message of 2017-05-26 12:03:24 +0100: >> Hi Doug, >> >> Thanks for your review. Actually freezer has a separate repo for

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

Excerpts from Saad Zaher's message of 2017-05-26 12:03:24 +0100: > Hi Doug, > > Thanks for your review. Actually freezer has a separate repo for the api, > it can be found here [1]. Freezer is using oslo.context since newton. If > you have the time you can take a look at it and let us know if you

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

Hi Doug, Thanks for your review. Actually freezer has a separate repo for the api, it can be found here [1]. Freezer is using oslo.context since newton. If you have the time you can take a look at it and let us know if you have any comments. Thanks for your help [1] https://github.com/openstack/

Re: [openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

Thanks Doug. We’ll look into this. @Tuan, is there any roadblocks with the patch you’re working on? [1] [1] https://review.openstack.org/#/c/455407/ Renat On 26 May 2017, 01:54 +0700, Doug Hellmann , wrote: > The new work to add the exception information and request ID tracing > depends on usi

[openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

The new work to add the exception information and request ID tracing depends on using both oslo.context and oslo.log to have all of the relevant pieces of information available as log messages are emitted. In the course of reviewing the "done" status for those initiatives, I noticed that although

[openstack-dev] [mistral] Project Update Slides

Here is a link to the slides used during the project update session from this morning. https://goo.gl/I3ufIi - Ryan -- RYAN BRADY SENIOR SOFTWARE ENGINEER Red Hat Inc rbr...@redhat.comT: (919)-890-8925 IM: rbrady @redhatway

Re: [openstack-dev] [mistral][tripleo] mistralclient release needed

Hi, it was released as 3.1.0 recently. Renat On 24 Apr 2017, 20:14 +0700, Juan Antonio Osorio , wrote: > Hey, > > We're trying to migrate the undercloud to use keystone v3. But we're > currently blocked by having an older version of mistralclient available. We > would really use a release to mo

[openstack-dev] [mistral][tripleo] mistralclient release needed

Hey, We're trying to migrate the undercloud to use keystone v3. But we're currently blocked by having an older version of mistralclient available. We would really use a release to move forward. For reference, this is the commit we need to use in mistralclient https://github.com/openstack/python-m

Re: [openstack-dev] [mistral] New CI Job definitions

On 19 Apr 2017, 21:37 +0700, Brad P. Crochet , wrote: > > On Tue, Apr 18, 2017 at 2:10 AM Ренат Ахмеров > > wrote: > > > Thanks Brad! > > > > > > So kombu gate is now non-apache, right? > > > > > > > No. It would be running under mod_wsgi. We can make it non-apache if you > > like. Would be pre

Re: [openstack-dev] [mistral] New CI Job definitions

On Tue, Apr 18, 2017 at 2:10 AM Ренат Ахмеров wrote: > Thanks Brad! > > So kombu gate is now non-apache, right? > > No. It would be running under mod_wsgi. We can make it non-apache if you like. Would be pretty easy to do so. > Thanks > > Renat Akhmerov > @Nokia > > On 17 Apr 2017, 22:17 +0700,

Re: [openstack-dev] [mistral] New CI Job definitions

Thanks Brad! So kombu gate is now non-apache, right? Thanks Renat Akhmerov @Nokia On 17 Apr 2017, 22:17 +0700, Brad P. Crochet , wrote: > Hi y'all... > > In the midst of trying to track down some errors being seen with tempest > tests whilst running under mod_wsgi/apache, I've made it so that

[openstack-dev] [mistral] New CI Job definitions

Hi y'all... In the midst of trying to track down some errors being seen with tempest tests whilst running under mod_wsgi/apache, I've made it so that the devstack plugin is capable of also running with mod_wsgi/apache.[1] In doing so, It's become the default devstack job. I've also now created so

[openstack-dev] [mistral] Team meeting - 04/10/2017

Hi, I’d like to invite Mistral team members to our weekly team meeting today at #openstack-meeting-3 at 15.00 UTC. Agenda: • Review action items • Current status (progress, issues, roadblocks, further plans) • Sync on Pike 1 progress • Setting up project goals for 2017 • Open discussion Gener

Re: [openstack-dev] [mistral] Using mistral to start a not-to-die task

Renat: Perfect. A combination of 1 and 2a would fit our needs. One reason we are venturing toward an async workflow is to address the scale limitation in tacker. Now, do you've some pointers how well mistral scales (so that we don't just move our scale problem down to the mistral dependency). Loo

Re: [openstack-dev] [mistral] Using mistral to start a not-to-die task

Another option: 1. Run a workflow with a loop (i.e. task calls itself), in order to have a delay between task executions you can use either wait-before/wait-after task policies 2.a The workflow can be stopped via Mistral API by a 3rd party, if needed. 2.b The workflow can have a special task tha

Re: [openstack-dev] [mistral] Using mistral to start a not-to-die task

Yeah, as Bob said, cron-trigger is what you are looking for. As our discussion on IRC, currently, Mistral doesn't support to execute shell command directly, my suggestion is, you could consider using http action (which is supproted by Mistral out of the box) or providing a host (physical or virtua

Re: [openstack-dev] [mistral] Using mistral to start a not-to-die task

Hi Gongysh: You are looking for mistral cron-triggers. See https://docs.openstack.org/developer/mistral/terminology/cron_triggers.html Bob On 3/22/2017 7:16 PM, gongys2017 wrote: Hi mistral stackers, Tacker is using the mistral as its part of system. Now we have a requirement: tacker se

[openstack-dev] [mistral] Using mistral to start a not-to-die task

Hi mistral stackers, Tacker is using the mistral as its part of system. Now we have a requirement: tacker server registers an openstack as its NFVI, and needs to ping__ OpenStack Development Mailing List (not for usage question

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

> On 15 Mar 2017, at 15:32, Adriano Petrich wrote: > >I was talking to some friends that have more (and more recent) experience > with standalone zope.interfaces inside other projects (last time I used it > was inside zope and 10 years ago) and I think it might be just overcomplexity > fo

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

Renat, I was talking to some friends that have more (and more recent) experience with standalone zope.interfaces inside other projects (last time I used it was inside zope and 10 years ago) and I think it might be just overcomplexity for our task at hand. Cheers, Adriano On Wed, Mar 15,

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

Well, zope is a cool thing I believe. We can consider to use it. I just don’t see what real advantage it’ll give us now. Essentially, what we’re trying to do now is pretty simple. We’re just defining one base class for all actions w/o talking about various modifications of this class yet. So if

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

Sorry if I'm missing the point here, and for being late on the discussion. But what about zope interfaces? Would not that be clearer? On Tue, Mar 14, 2017 at 11:39 AM, Dougal Matthews wrote: > > > On 14 March 2017 at 11:14, Renat Akhmerov > wrote: > >> Yeah, I finally understood too what Tho

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On 14 March 2017 at 11:14, Renat Akhmerov wrote: > Yeah, I finally understood too what Thomas meant. > > Just to clarify, I think mixed two different discussions here: > >1. Base framework for all actions residing in mistral-lib (what I was >trying to discuss) >2. The new design for O

[openstack-dev] [mistral][irc] Mistral team meeting time/channel change

Hi all,The Mistral meeting is now going to be 1 hour earlier at 15:00 UTC on Monday.It will move to #openstack-meeting-3 due to a conflict in the current channel. This move has been made to make it easier for people after daylight savings kicks in.You can also find a calendar invite in the attachm

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

Oh, Thanks Dougal, i am now clear since it is your TripleO use case. So yes, in this case, IMHO, we should keep the _get_client() as before but change it to the classmethod. May be other methods too like _create_client(), etc. We can think this change to be an alternative to the solution of creati

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

Yeah, I finally understood too what Thomas meant. Just to clarify, I think mixed two different discussions here: Base framework for all actions residing in mistral-lib (what I was trying to discuss) The new design for OpenStack actions On #2 I agree with you that NovaAction.get_client(context) s

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On 14 March 2017 at 10:21, lương hữu tuấn wrote: > > > On Tue, Mar 14, 2017 at 10:28 AM, Dougal Matthews > wrote: > >> >> >> On 13 March 2017 at 09:49, lương hữu tuấn wrote: >> >>> >>> >>> On Mon, Mar 13, 2017 at 9:34 AM, Thomas Herve wrote: >>> On Fri, Mar 10, 2017 at 9:52 PM, Ryan Brady

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On Tue, Mar 14, 2017 at 10:28 AM, Dougal Matthews wrote: > > > On 13 March 2017 at 09:49, lương hữu tuấn wrote: > >> >> >> On Mon, Mar 13, 2017 at 9:34 AM, Thomas Herve wrote: >> >>> On Fri, Mar 10, 2017 at 9:52 PM, Ryan Brady wrote: >>> > >>> > One of the pain points for me as an action devel

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On 14 March 2017 at 05:25, Renat Akhmerov wrote: > So again, I’m for simplicity but that kind of simplicity that also allows > flexibility in the future. > > There’s one principle that I usually follow in programming that says: > > “*Space around code (absence of code) has more potential than the

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On 13 March 2017 at 09:49, lương hữu tuấn wrote: > > > On Mon, Mar 13, 2017 at 9:34 AM, Thomas Herve wrote: > >> On Fri, Mar 10, 2017 at 9:52 PM, Ryan Brady wrote: >> > >> > One of the pain points for me as an action developer is the OpenStack >> > actions[1]. Since they all use the same metho

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

Hi, Agree with the simplicity that Renat has shown. I would not want to change the base class as well as the way of mistral created up to now. Br, Tuan/Nokia On Mar 14, 2017 6:29 AM, "Renat Akhmerov" wrote: > So again, I’m for simplicity but that kind of simplicity that also allows > flexibil

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

So again, I’m for simplicity but that kind of simplicity that also allows flexibility in the future. There’s one principle that I usually follow in programming that says: “Space around code (absence of code) has more potential than the code itself.” That means that it’s better to get rid of any

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On Mon, Mar 13, 2017 at 9:34 AM, Thomas Herve wrote: > On Fri, Mar 10, 2017 at 9:52 PM, Ryan Brady wrote: > > > > One of the pain points for me as an action developer is the OpenStack > > actions[1]. Since they all use the same method name to retrieve the > > underlying client, you cannot simpl

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On Fri, Mar 10, 2017 at 9:52 PM, Ryan Brady wrote: > > One of the pain points for me as an action developer is the OpenStack > actions[1]. Since they all use the same method name to retrieve the > underlying client, you cannot simply inherit from more than one so you are > forced to rewrite the c

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

> One of the pain points for me as an action developer is the OpenStack > actions[1]. Since they all use the same method name to retrieve the > underlying client, you cannot simply inherit from more than one so you are > forced to rewrite the client access methods. We saw this in creating act

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On Fri, Mar 10, 2017 at 5:16 AM, Renat Akhmerov wrote: > > On 10 Mar 2017, at 15:09, Dougal Matthews wrote: > > On 10 March 2017 at 04:22, Renat Akhmerov > wrote: > >> Hi, >> >> I probably like the base class approach better too. >> >> However, I’m trying to understand if we need this variety o

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

Hi, I did not know about this change before but after reading the whole story, IMHO i myself love the way of keeping it as simple at this moment as you guys i think agreed on. For MixinAction or PolicyMixin, etc. we can develop them later when we have concrete case studies. Br, Tuan/Nokia On Fr

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

> On 10 Mar 2017, at 15:09, Dougal Matthews wrote: > > On 10 March 2017 at 04:22, Renat Akhmerov > wrote: > Hi, > > I probably like the base class approach better too. > > However, I’m trying to understand if we need this variety of classes. > Do we need a sep

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On 10 March 2017 at 04:22, Renat Akhmerov wrote: > Hi, > > I probably like the base class approach better too. > > However, I’m trying to understand if we need this variety of classes. > >- Do we need a separate class for asynchronous actions? IMO, since >is_sync() is just an instance met

[openstack-dev] [mistral][ptg] Following up on Pike PTG sessions

Hi, Below is the list of blueprints and bugs updated after the PTG discussions. The etherpad containing all sessions’ info and notes is at [1]. Scalability, Fault Tolerance and HA https://blueprints.launchpad.net/mistral/+spec/mistral-ha-gate

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

Hi, I probably like the base class approach better too. However, I’m trying to understand if we need this variety of classes. Do we need a separate class for asynchronous actions? IMO, since is_sync() is just an instance method that can potentially return both True and False based on the instan

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On 9 March 2017 at 17:19, Dougal Matthews wrote: > On 9 March 2017 at 04:35, Ryan Brady wrote: > >> At the PTG and previous discussions in IRC, I mentioned there were two >> different design ideas I had for the developer experience for custom action >> development in mistral-lib. The purpose an

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

On 9 March 2017 at 04:35, Ryan Brady wrote: > At the PTG and previous discussions in IRC, I mentioned there were two > different design ideas I had for the developer experience for custom action > development in mistral-lib. The purpose and intent behind the patch[1] was > discussed in person at

[openstack-dev] [mistral] Mistral Custom Actions API Design

At the PTG and previous discussions in IRC, I mentioned there were two different design ideas I had for the developer experience for custom action development in mistral-lib. The purpose and intent behind the patch[1] was discussed in person at the PTG and that was helpful for me wrt to scope. I

[openstack-dev] [mistral][cinder][keystone] Fixing Mistral & Cinder service type in the catalog

Hi, There was a patch recently merged ([1]) that works around a bad decision that Cinder and Mistral team (possible someone else too) to include api version in the name of service type in the catalog. For example, for Mistral it was initially “workflow” when we were working on a POC of the proj

Re: [openstack-dev] [mistral] Proposing Michal Gershenzon to the core team

Sent: Thursday, March 02, 2017 9:01 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [mistral] Proposing Michal Gershenzon to the core team Thank you guys! Michal, you’re now included to the core team. Renat Akhmerov @Nokia On 2 Mar 2017, at 0

Re: [openstack-dev] [mistral] Proposing Michal Gershenzon to the core team

Thank you guys! Michal, you’re now included to the core team. Renat Akhmerov @Nokia > On 2 Mar 2017, at 03:50, Lingxian Kong wrote: > > +1, she indeed has been doing great contribution to Mistral, welcome, Michal > :-) > > > Cheers, > Lingxian Kong (Larry) > > On Thu, Mar 2, 2017 at 5:47 A

Re: [openstack-dev] [mistral] Proposing Michal Gershenzon to the core team

+1, she indeed has been doing great contribution to Mistral, welcome, Michal :-) Cheers, Lingxian Kong (Larry) On Thu, Mar 2, 2017 at 5:47 AM, Renat Akhmerov wrote: > Hi, > > Based on the stats of Michal Gershenzon in Ocata cycle I’d like to promote > her to the core team. > Michal works at No

Re: [openstack-dev] [mistral] Proposing Michal Gershenzon to the core team

for usage questions) Subject: Re: [openstack-dev] [mistral] Proposing Michal Gershenzon to the core team +1 for me. Sorry Michal if you read this thread, I thought that you are a man by calling you Mike :d. Tuan/Nokia On Mar 1, 2017 6:04 PM, "Dougal Matthews" mailto:dou...@redhat.c

Re: [openstack-dev] [mistral] Proposing Michal Gershenzon to the core team

+1 for me. Sorry Michal if you read this thread, I thought that you are a man by calling you Mike :d. Tuan/Nokia On Mar 1, 2017 6:04 PM, "Dougal Matthews" wrote: > > > On 1 March 2017 at 16:47, Renat Akhmerov wrote: > >> Hi, >> >> Based on the stats of Michal Gershenzon in Ocata cycle I’d like

<    1   2   3   4   5   6   7   8   9   10   >