Re: [openstack-dev] [mistral] Extend created(updated)_at by started(finished)_at to clarify the duration of the task

On Wed, 26 Sep 2018 at 12:03, Олег Овчарук wrote: > Hi everyone! Please take a look to the blueprint that i've just created > https://blueprints.launchpad.net/mistral/+spec/mistral-add-started-finished-at > > I'd like to implement this feature, also I want to update CloudFlow when > this will be

[openstack-dev] [mistral] [PTL] PTL on Vacation 17th - 28th September

Hey all, I'll be on vacation from 17th to the 28th of September. I don't anticipate anything coming up but Renat Akhmerov is standing in as PTL while I'm out. Cheers, Dougal __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [mistral] [release] [stable] Cherry-pick migration to stable/rocky

On 5 September 2018 at 10:52, Dougal Matthews wrote: > (Note: I added [release] to the email subject, as I think that will make > it visible to the right folks.) > Darn. It should have been [stable]. I have added that now. Sorry for

Re: [openstack-dev] [mistral][release] Cherry-pick migration to stable/rocky

On 5 September 2018 at 10:31, Pierre Gaxatte wrote: > Hello, > > Related change: https://review.openstack.org/#/c/599606 > > I'd like to push this to stable/rocky because this bug affects me in > production and I'd like to be able to upgrade to rocky to fix this. I > understand that new

Re: [openstack-dev] [tripleo] quickstart for humans

On 31 August 2018 at 12:11, Steven Hardy wrote: > On Thu, Aug 30, 2018 at 3:28 PM, Honza Pokorny wrote: > > Hello! > > > > Over the last few months, it seems that tripleo-quickstart has evolved > > into a CI tool. It's primarily used by computers, and not humans. > > tripleo-quickstart is a

[openstack-dev] [mistral] No Denver PTG Sessions

Hi all, Unfortunately due to some personal conflicts and trouble with travel plans, there will be no Mistral cores at the Denver PTG. This means that we have had to cancel the Mistral sessions. I recently asked if anyone was planning to attend and only got one maybe. I am considering trying to

[openstack-dev] [mistral] Denver PTG

Hey all, I wanted to reach out and see who is interested in attending the Mistral sessions at the Denver PTG. Unfortunately I wont be able to make it but Renat Akhmerov may be able to go and run the sessions. Most of the other Mistral cores wont be able to attend unfortunately. Please reply as

Re: [openstack-dev] [tripleo] Proposing Lukas Bezdicka core on TripleO

+1 On 6 August 2018 at 16:28, Alex Schultz wrote: > +1 > > On Mon, Aug 6, 2018 at 7:19 AM, Bogdan Dobrelya > wrote: > > +1 > > > > On 8/1/18 1:31 PM, Giulio Fidente wrote: > >> > >> Hi, > >> > >> I would like to propose Lukas Bezdicka core on TripleO. > >> > >> Lukas did a lot work in our

Re: [openstack-dev] [mistral] Clearing out old gerrit reviews

On 3 August 2018 at 10:45, Dougal Matthews wrote: > On 9 July 2018 at 16:13, Dougal Matthews wrote: > >> Hey folks, >> >> I'd like to propose that we start abandoning old Gerrit reviews. >> >> This report shows how stale and out of date some of the reviews ar

[openstack-dev] [mistral] Removing Inactive Cores

Hey, As we are approaching the end of Rocky I am doing some house keeping. The people below have been removed from the Mistral core team due to reviewing inactivity in the last 180 days[1]. I would like to thank them for their contributions and they are welcome to re-join the Mistral core team

Re: [openstack-dev] [mistral] Clearing out old gerrit reviews

On 9 July 2018 at 16:13, Dougal Matthews wrote: > Hey folks, > > I'd like to propose that we start abandoning old Gerrit reviews. > > This report shows how stale and out of date some of the reviews are: > http://stackalytics.com/report/reviews/mistral-group/open > > I

[openstack-dev] [mistral] Mistral Monthly August 2018

Hey everyone! It is time to wrap-up the last month and have a look and see what has happened. # General News We are now close to the end of the Rocky release cycle! It has been a pleasure serving at the PTL and it looks like you are stuck with me for Stein :) -

[openstack-dev] [mistral] Clearing out old gerrit reviews

Hey folks, I'd like to propose that we start abandoning old Gerrit reviews. This report shows how stale and out of date some of the reviews are: http://stackalytics.com/report/reviews/mistral-group/open I would like to initially abandon anything without any activity for a year, but we might

[openstack-dev] [mistral][ptl] PTL On Vacation 3rd - 6th July

Hey all, I'll be out for the rest of the week after today. I don't anticipate anything coming up but Renat Akhmerov is standing in as PTL while I'm out. See you all on Monday next week. Cheers, Dougal __ OpenStack

[openstack-dev] [mistral] Mistral Monthly July 2018

Hey Mistralites! Here is your monthly recap of whats what in the Mistral community. Arriving to you a day late as the 1st was a Sunday. When that happens I'll just aim to send it as close to the 1st as I can. Either slightly early or slightly late. # General News Vitalii Solodilov joined the

Re: [openstack-dev] [mistral] Promoting Vitalii Solodilov to the Mistral core team

On 19 June 2018 at 10:27, Renat Akhmerov wrote: > Hi, > > I’d like to promote Vitalii Solodilov to the core team of Mistral. In my > opinion, Vitalii is a very talented engineer who has been demonstrating it > by providing very high quality code and reviews in the last 6-7 months. > He’s one of

Re: [openstack-dev] [mistral] Promoting Vitalii Solodilov to the Mistral core team

On 19 June 2018 at 10:27, Renat Akhmerov wrote: > Hi, > > I’d like to promote Vitalii Solodilov to the core team of Mistral. In my > opinion, Vitalii is a very talented engineer who has been demonstrating it > by providing very high quality code and reviews in the last 6-7 months. > He’s one of

[openstack-dev] [mistral] Mistral Monthly June 2018

Hey Mistralites! Welcome to the second edition of Mistral Monthly. # Summit Brad Crochet done a great job giving the Mistral project update talk. Check it out: https://www.youtube.com/watch?v=y9qieruccO4 Also checkout the Congress update, they discuss their recent support for Mistral.

[openstack-dev] [mistral] Skipping Office Hours on Monday

Hey folks, I forgot to say - I wont be around on Monday for office hours. Feel free to carry on without me. It should be less formal than a meeting, so anyone can chat - just send some messages to #openstack-mistral so folks know you are around for it. The ehterpad has a pinglist you can use to

[openstack-dev] [mistral] Mistral Monthly May 2018

Hey Folks! Welcome to the first Mistral Monthly newsletter! # Intro I am going to try sending out a monthly newsletter summarising what is going on in the world of Mistral. This is an experiment, so feedback would be very welcome! If you have something you want me to share for next time, please

Re: [openstack-dev] [mistral] September PTG in Denver

On 23 April 2018 at 20:58, Sean McGinnis wrote: > On Mon, Apr 23, 2018 at 07:32:40PM +, Kendall Nelson wrote: > > Hey Dougal, > > > > I think I had said May 2nd in my initial email asking about attendance. > If > > you can get an answer out of your team by then I would

Re: [openstack-dev] [mistral] [vitrage] Propose adding Vitrage's actions to Mistral Actions

I spoke with Jaewook briefly in #openstack-mistral, for anyone interested in following this work there is now a blueprint to track it. https://blueprints.launchpad.net/mistral/+spec/mistral-vitrage-actions Thanks all On 23 April 2018 at 07:57, Jaewook Oh wrote: > Hello

[openstack-dev] [mistral] September PTG in Denver

Hey all, You may have seen the news already, but yesterday the next PTG location was announced [1]. It will be in Denver again. Can you let me know if you are planning to attend and go to Mistral sessions? I have been asked about numbers and need to reply by May 5th. Thanks, Dougal [1]:

[openstack-dev] [mistral] Rocky-1 Release and Rocky-2 Plans

Hey all, Mistral Rocky-1 [1] has been released and mistral-lib [2] and mistral client [3] are on their way. I have moved all of the open bugs and blueprints assigned to Rocky-1 to the Rocky-2 cycle. Can you please check the following: - All the bugs and blueprints important to you are

Re: [openstack-dev] [Mistral]I think Mistral need K8S action

giving feedback and testing or possibly helping out too. > > > Regards, > > Xian Jun Hong > > > > > > *From:* Dougal Matthews <dou...@redhat.com> > *Sent:* Saturday, April 14, 2018 1:00 AM > *To:* OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [Mistral]I think Mistral need K8S action

On 13 April 2018 at 05:47, Renat Akhmerov wrote: > Hi, > > I completely agree with you that having such an action would be useful. > However, I don’t think this kind of action should be provided by Mistral > out of the box. Actions and triggers are integration pieces

Re: [openstack-dev] [all] [api] Re-Reminder on the state of WSME

On 11 April 2018 at 11:39, Chris Dent wrote: > On Tue, 10 Apr 2018, Michael Johnson wrote: > > I echo Ben's question about what is the recommended replacement. >> > > It's a good question. Unfortunately I don't have a good answer. My > involvement in WSME is simply the

[openstack-dev] Todays Office Hour Time Change

Hey all, I have moved the office hour today from 16:00 UTC to 15:00 UTC. If there is demand we could make it a 2 hour slot or move it back. I wasn't able to make it for 16:00 UTC today and it will often be tricky for me. I think one of the biggest advantages to doing office hours is that we can

[openstack-dev] [mistral] Bug Triage on Friday

Hey all, During the office hour on Friday, and maybe some time after it, I am going to do some Mistral bug triage, planning and general tidying up on launchpad and gerrit. If you are able and want to join, please do! The slot is 8AM UTC - 9AM UTC. I'll be in #openstack-mistral I hope to try and

[openstack-dev] [mistral] [ptl] PTL vacation from March 26 - March 30

I'll be out for the dates in the subject, so all of next week. Renat Akhmerov (rakhmerov on IRC) will be standing in for anything that comes up. Cheers, Dougal __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [mistral][tempest][congress] import or retain mistral tempest service client

On 13 March 2018 at 18:51, Eric K wrote: > Hi Mistral folks and others, > > I'm working on Congress tempest tests [1] for integration with Mistral. In > the tests, we use a Mistral service client to call Mistral APIs and > compare results against those obtained by

Re: [openstack-dev] [mistral] PTG Summary

On 7 March 2018 at 09:28, Dougal Matthews <dou...@redhat.com> wrote: > Hey Mistralites (maybe?), > > I have been through the etherpad from the PTG and attempted to expand on > the topics with details that I remember. If I have missed anything or you > have any questions, p

[openstack-dev] [mistral] PTG Summary

Hey Mistralites (maybe?), I have been through the etherpad from the PTG and attempted to expand on the topics with details that I remember. If I have missed anything or you have any questions, please get in touch. I want to update it while the memory is as fresh as possible. For each main topic

Re: [openstack-dev] [mistral] What's new in latest CloudFlow?

me know). > > > > *From:* Dougal Matthews [mailto:dou...@redhat.com] > *Sent:* Thursday, March 1, 2018 17:43 > *To:* OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > *Subject:* Re: [openstack-dev] [mistral] What'

[openstack-dev] [mistral] Retiring the Mistral Wiki pages

Hey folks, Mistral has several Wiki pages that rank highly in Google searches. However, most of them have not been updated in months (or years in many cases). I am therefore starting to remove these and direct people to the Mistral documentation. Where possible I will link them to the relevant

Re: [openstack-dev] [mistral] What's new in latest CloudFlow?

Hey Guy, Thanks for sharing this update. I need to find time to try it out. The biggest issue for me is the lack of keystone support. I wonder if any of the code in tripleo-ui could be used to help with KeyStone support. It is a front-end JavaScript GUI. https://github.com/openstack/tripleo-ui

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

On 14 February 2018 at 10:03, Renat Akhmerov wrote: > 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:

[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

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

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

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

On 20 November 2017 at 08:56, Renat Akhmerov <renat.akhme...@gmail.com> 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

[openstack-dev] [TripleO] Workflow Squad Meetings

Hey all, Starting next week we are going to have regular weekly meetings for the workflows squad. This will be at 3pm UTC every Wednesday. https://etherpad.openstack.org/p/tripleo-workflows-squad-status We will be using the above etherpad to store the meeting details, location etc and lake

Re: [openstack-dev] [tripleo] Proposing John Fulton core on TripleO

On 8 November 2017 at 22:24, Giulio Fidente wrote: > Hi, > > I would like to propose John Fulton core on TripleO. > > I think John did an awesome work during the Pike cycle around the > integration of ceph-ansible as a replacement for puppet-ceph, for the > deployment of

Re: [openstack-dev] [tripleo] Nominate akrivoka for tripleo-validations core

+1 On 9 November 2017 at 05:57, Marios Andreou wrote: > > > On Mon, Nov 6, 2017 at 4:32 PM, Honza Pokorny wrote: > >> Hello people, >> >> I would like to nominate Ana Krivokapić (akrivoka) for the core team for >> tripleo-validations. She has really

Re: [openstack-dev] Nominate chem and matbu for tripleo-core !

On 9 November 2017 at 08:44, Marios Andreou wrote: > Hello fellow owls, > > I would like to nominate (and imo these are both long overdue already): > > Sofer Athlan Guyot (chem) and > > Mathieu Bultel (matbu) > +1 to both! > > to tripleo-core. They have both made many

Re: [openstack-dev] [stable][mistral] Asking for stable branch policy exception

On 17 October 2017 at 09:19, Renat Akhmerov wrote: > Hi, > > We have two patches in Mistral that we need to back port to stable/pike. > However, they are against of stable branch management policy because they > slightly change the DB schema. The patches are the

Re: [openstack-dev] [tripleo] add mistral to the auto-update package list for TripleO CI

On 25 August 2017 at 13:27, Brad P. Crochet wrote: > On Thu, Aug 24, 2017 at 5:35 PM, Ben Nemec wrote: > > I think I'm +0 on this. On the one hand we do have the gating job on > > Mistral, on the other hand our gate jobs don't exercise all of the > >

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

Re: [openstack-dev] [tripleo] Proposing Saravanan KR core

+1! On 21 July 2017 at 16:01, Emilien Macchi wrote: > Saravanan KR has shown an high level of expertise in some areas of > TripleO, and also increased his involvement over the last months: > - Major contributor in DPDK integration > - Derived parameter works > - and a lot of

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 >

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 23 June 2017 at 12:52, Thierry Carrez <thie...@openstack.org> wrote: > Dougal Matthews wrote: > >> We have been trying to break the requirement on mistral (from > >> tripleo-common) but it is proving to be harder than expected. We are > >> really

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 22 June 2017 at 14:01, Dougal Matthews <dou...@redhat.com> wrote: > > > On 22 June 2017 at 11:01, Thierry Carrez <thie...@openstack.org> wrote: > >> Thierry Carrez wrote: >> > Renat Akhmerov wrote: >> >> We have a weekly meeting next Monday,

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 22 June 2017 at 11:01, Thierry Carrez wrote: > Thierry Carrez wrote: > > Renat Akhmerov wrote: > >> We have a weekly meeting next Monday, will it be too late? > > > > Before Thursday EOD (when the Pike-2 deadline hits) should be OK. > > If there was a decision, I missed

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 31 May 2017 at 09:35, Renat Akhmerov wrote: > > On 31 May 2017, 15:08 +0700, Thierry Carrez , > wrote: > > > This has hit us with the mistral and tripleo projects particularly > (tagged in the title). They disallow pbr-3.0.0 and in the case of

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) >

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

On 14 March 2017 at 10:21, lương hữu tuấn <tuantulu...@gmail.com> wrote: > > > On Tue, Mar 14, 2017 at 10:28 AM, Dougal Matthews <dou...@redhat.com> > wrote: > >> >> >> On 13 March 2017 at 09:49, lương hữu tuấn <tuantulu...@gmail.com> wrote: >

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)

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

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 >

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

On 9 March 2017 at 17:19, Dougal Matthews <dou...@redhat.com> wrote: > On 9 March 2017 at 04:35, Ryan Brady <rbr...@redhat.com> wrote: > >> At the PTG and previous discussions in IRC, I mentioned there were two >> different design ideas I had for the develope

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 >

Re: [openstack-dev] [TripleO][Containers] Creating launchpad bugs and correct tags

On 2 March 2017 at 10:40, Flavio Percoco wrote: > Greetings, > > Just wanted to give a heads up that we're tagging all the containers > related > bugs with the... guess what?... containers tag. If you find an issue with > one of > the containers jobs or running tripleo on

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

On 1 March 2017 at 16:47, 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 Nokia CloudBand and being a CloudBand engineer she knows > Mistral very well > as a user and

Re: [openstack-dev] [tripleo] Deployment plan management efforts sync up

On 2 February 2017 at 11:56, Jiri Tomasek wrote: > Hello all, > > there has been several ongoing efforts in TripleO regarding Deployment > Plans management and Deployment configuration itself. A lot of this work is > done to satisfy certain individual requirements but I

Re: [openstack-dev] [TripleO] Proposing Dmitry Tantsur and Alex Schultz as instack-undercloud cores

+1 On 31 January 2017 at 16:02, Ben Nemec wrote: > In the spirit of all the core team changes, here are a couple more I'd > like to propose. > > Dmitry has been very helpful reviewing in instack-undercloud for a long > time so this is way overdue. I'm also going to

Re: [openstack-dev] [tripleo] Update TripleO core members

+1! On 23 January 2017 at 19:03, Emilien Macchi wrote: > Greeting folks, > > I would like to propose some changes in our core members: > > - Remove Jay Dobies who has not been active in TripleO for a while > (thanks Jay for your hard work!). > - Add Flavio Percoco core on

Re: [openstack-dev] [tripleo] Proposing Honza Pokorny core on tripleo-ui

+1! On 25 January 2017 at 15:28, Steven Hardy wrote: > On Tue, Jan 24, 2017 at 08:52:51AM -0500, Emilien Macchi wrote: > > I have been discussed with TripleO UI core reviewers and it's pretty > > clear Honza's work has been valuable so we can propose him part of > > Tripleo

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

+1! On 26 January 2017 at 18:36, Harry Rybacki wrote: > On Thu, Jan 26, 2017 at 12:25 PM, Martin André wrote: > > On Tue, Jan 24, 2017 at 6:03 PM, Juan Antonio Osorio > > wrote: > >> Sagi (sshnaidm on IRC) has done significant work

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

On 24 January 2017 at 16:16, Mikhail Fedosin wrote: > Hey, Flavio :) Thanks for your questions! > > As you said currently only Nokia's adopting Glare for its own platform, > but if we talk about OpenStack, that I believe Mistral will start to use it > soon. > Has there been

Re: [openstack-dev] [TripleO][Mistral][Ansible] Calling Ansible from Mistral workflows

larger ecosystem of actions that can be installed, they don't all need to be included with Mistral itself. > Thoughts? > > Renat Akhmerov > @Nokia > > On 12 Jan 2017, at 22:27, Dougal Matthews <dou...@redhat.com> wrote: > > Hey all, > > I just wanted to share a

Re: [openstack-dev] [TripleO][CI]

On 15 January 2017 at 20:24, Sagi Shnaidman wrote: > Hi, all > > FYI, the periodic TripleO nonha jobs fail because of introspection > failure, there is opened bug in mistral: > > Ironic introspection fails because unexpected keyword "insecure" >

[openstack-dev] [TripleO][Mistral][Ansible] Calling Ansible from Mistral workflows

Hey all, I just wanted to share a quick experiment that I tried out. I had heard there was some interest in native Ansible actions for Mistral. After much dragging my heels I decided to give it a go, and it turns out to be very easy. This code is very raw and has only been lightly tested - I

Re: [openstack-dev] [TripleO][Upgrade Squad syncup]

On 13 December 2016 at 16:12, Emilien Macchi wrote: > On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou > wrote: > > Hi OOOs o/ as discussed on this week's upstream weekly irc meeting [1] > > lets schedule a syncup on the Ocata composable upgrades work and

[openstack-dev] [mistral] No team meeting today - Dec 12th

Hi all, Todays meeting is cancelled as none of the Mistral team are available to attend. If you have anything you would have liked to discuss please raise it in a reply to this email. As for me, I just have a couple of small patches that need second reviews: https://review.openstack.org/408617

[openstack-dev] [TripleO] Proposing Julie Pichon for tripleo core

Hi all, I would like to propose we add Julie (jpich) to the TripleO core team for python-tripleoclient and tripleo-common. This nomination is based partially on review stats[1] and also my experience with her reviews and contributions. Julie has consistently provided thoughtful and detailed

Re: [openstack-dev] [mistral] Meeting Time

this next week or the week after? I'm not sure how/where we need to update with the new meeting information. I also think we need to reserve the time in IRC. Thanks Dougal > > > Renat Akhmerov > @Nokia > > On 21 Nov 2016, at 21:14, Dougal Matthews <dou...@redhat.com> w

Re: [openstack-dev] [mistral] Meeting Time

ell. > > > > I’m volunteering to participate in this alternate meeting even if > > it’s not too comfortable for me. > > > > > > Renat Akhmerov > > @Nokia > > > > > On 21 Nov 2016, at 21:14, Dougal Matthews <dou...@redhat.com> > > &

Re: [openstack-dev] [mistral] Meeting Time

On 7 November 2016 at 16:20, Dougal Matthews <dou...@redhat.com> wrote: > Hi all, > > We want to make sure that the Mistral meeting time is as good as possible, > so that everyone interested can attend. To do that, please add your > name/nick and the times that suit

Re: [openstack-dev] [mistral] Promoting Dougal Matthews to the core team

;> J >> >> >> >> Michal Gershenzon >> Software Engineer, CloudBand >> Application & Analytics , Nokia >> Contact number: +972 9 793 3163 >> >> >> >> *From:* Deja, Dawid [mailto:dawid.d...@intel.com] >> *Sent:* Tuesday,

[openstack-dev] [mistral] Meeting Time

Hi all, We want to make sure that the Mistral meeting time is as good as possible, so that everyone interested can attend. To do that, please add your name/nick and the times that suit you to this etherpad: https://etherpad.openstack.org/p/mistral-meeting-time If we are really lucky, we will

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

On 6 November 2016 at 19:54, James Slagle wrote: > On Fri, Nov 4, 2016 at 1:40 PM, Emilien Macchi wrote: > > MIchele Baldessari (bandini on IRC) has consistently demonstrated high > > levels of contributions in TripleO projects, specifically in High >

Re: [openstack-dev] [mistral] Cancelling team meeting - 10/17/2016

On 17 October 2016 at 10:26, Renat Akhmerov wrote: > Hi, just one week left before the summit and there’s a lot of preparations > going on so we’re cancelling team meeting today. > I'd like to raise the idea of moving the meeting to a more convenient time again. I

Re: [openstack-dev] [tripleo][ironic] introspection and CI

On 17 October 2016 at 22:10, Wesley Hayutin wrote: > Greetings, > > The RDO CI team is considering adding retries to our calls to > introspection again [1]. > This is very handy for bare metal environments where retries may be needed > due to random chaos in the environment

Re: [openstack-dev] [mistral] Cancelling team meeting - 10/03/2016

On 3 October 2016 at 08:32, Renat Akhmerov wrote: > Hi, > > We decided to cancel today’s team meeting because most people are either > busy with release activities or on holidays. > Hi, Thanks for sending this. I just had a quick idea - maybe when we cancel the

Re: [openstack-dev] [TripleO] TripleO Core nominations

On 15 September 2016 at 10:20, Steven Hardy wrote: > Hi all, > > As we work to finish the last remaining tasks for Newton, it's a good time > to look back over the cycle, and recognize the excellent work done by > several new contributors. > > We've seen a different

Re: [openstack-dev] [release][mistral] mistral Newton RC1 available

On 16 September 2016 at 00:06, Doug Hellmann wrote: > Hello everyone, > > The release candidate for mistral for the end of the Newton cycle > is available! You can find the RC1 source code tarballs at: > > https://tarballs.openstack.org/mistral/mistral-3.0.0.0rc1.tar.gz >

Re: [openstack-dev] [tripleo] CI is currently down: 2 blockers

For those interested we now have a minimal way to reproduce the MessagingTimeout in Mistral. https://bugs.launchpad.net/mistral/+bug/1624284 It seems to be related to this change in Mistral: https://github.com/openstack/mistral/commit/1b0f0cddd620a3785017bb28d432cb0030b627d7 And even more

[openstack-dev] [TripleO] Mistral transition status for RC1

Hey, This is just a quick update on the Mistral API transition. We are now at a point where all the major CLI commands (node registration, introspection and deployment) are being powered by mistral workflows. We have an etherpad that is tracking all the reviews in quite a bit of detail:

Re: [openstack-dev] [TripleO] [UI] Version

On Wednesday, 27 July 2016, Steven Hardy <sha...@redhat.com> wrote: > On Wed, Jul 27, 2016 at 02:08:08PM +0100, Dougal Matthews wrote: > >On 27 July 2016 at 12:41, Honza Pokorny <ho...@redhat.com > <javascript:;>> wrote: > > > > Hello fol

Re: [openstack-dev] [TripleO] [UI] Version

On 27 July 2016 at 12:41, Honza Pokorny wrote: > Hello folks, > > As the tripleo-ui project is quickly maturing, it might be time to start > versioning our code. As of now, the version is set to 0.0.1 and that > hardly reflects the state of the project. > > What do you think?

Re: [openstack-dev] [TripleO] tripleo-common bugs, bug tracking and launchpad tags

On 19 July 2016 at 16:20, Steven Hardy wrote: > On Mon, Jul 18, 2016 at 12:28:10PM +0100, Julie Pichon wrote: > > Hi, > > > > On Friday Dougal mentioned on IRC that he hadn't realised there was a > > separate project for tripleo-common bugs on Launchpad [1] and that he'd > >

Re: [openstack-dev] [mistral] [murano] [yaql] yaqluator bug

ce3-20d0-47b2-84f2-7bd1cb2bf9f7 >> { >> "output_expr": [ >> [ >> 1, >> 3 >> ] >> ] >> } >> >> >> As Matthews pointed out, the yaqluator is indeed OpenSource and >> con

Re: [openstack-dev] [mistal] Mistral logo ideas?

On 28 June 2016 at 06:38, Jason Rist <jr...@redhat.com> wrote: > On 06/27/2016 06:57 AM, Dougal Matthews wrote: > > On 27 June 2016 at 07:45, Renat Akhmerov <renat.akhme...@gmail.com> > wrote: > > > > > > > >> Ideally it would

Re: [openstack-dev] [mistral] [murano] [yaql] yaqluator bug

On 27 June 2016 at 14:30, Alexey Khivin wrote: > Hello, Moshe > > Tomorrow I discovered yaqluator.com for myself! Thanks for the useful > tool! > > But suddenly I was said that the expression > [1,2].join([3], true, [$1, $2]) > evaluated to [[1,3]] on the yaqluator > > A the

Re: [openstack-dev] [mistral] Cancelling team meeting today - 06/27/2016

Last week the topic of timeslot came up, would it be good to start that discussion? Maybe we can have a vote on slots, and since we would need the PTL to attend it would be best to start with a list of times that work for you. Or, if most people are happy with the current time, we can just stick

Re: [openstack-dev] [mistal] Mistral logo ideas?

On 27 June 2016 at 07:45, Renat Akhmerov wrote: > > > Ideally it would be nice to have something that matches the meaning of > the > > name. Maybe we can combine wind with one of the other ideas. > > > > I like the idea of the logo being a stylized wind turbine. Perhaps

Re: [openstack-dev] [mistal] Mistral logo ideas?

On 22 June 2016 at 06:35, Renat Akhmerov wrote: > Hi, > > We’d like to finally come up with a logo for Mistral and it’d be cool to > hear some ideas from the community. > > Some ideas from me: > • A picture of a graph (but the point is that it must be very very

Re: [openstack-dev] [TripleO] Proposed TripleO core changes

On 9 June 2016 at 15:03, Steven Hardy wrote: > Hi all, > > I've been in discussion with Martin André and Tomas Sedovic, who are > involved with the creation of the new tripleo-validations repo[1] > > We've agreed that rather than create another gerrit group, they can be >

Re: [openstack-dev] [mistral] Team meeting reminder - 05/30/2016

On 30 May 2016 at 08:40, Renat Akhmerov wrote: > Hi, > > This is a reminder about the team meeting that we’ll have today at 16.00 > UTC at #openstack-meeting. > > Agenda: > >- Review action items >- Current status (progress, issues, roadblocks, further plans) >

Re: [openstack-dev] [tripleo] Zaqar messages standardization

On 20 May 2016 at 18:39, Dan Prince wrote: > On Fri, 2016-05-20 at 17:52 +0200, Jiri Tomasek wrote: > > Hey all, > > > > I've been recently working on getting the TripleO UI integrated with > > Zaqar, so it can receive a messages from Mistral workflows and act > > upon them

  1   2   >