Hi,
I’ll be on vacation till Dec 17th. I’ll be replying emails but with delays.
Thanks
Renat Akhmerov
@Nokia
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.
Greetings, Mistral team!
As you may be aware, I've been working with other folks in the community
on documenting a vision for OpenStack clouds (formerly known as the
'Technical Vision') - essentially to interpret the mission statement in
long-form, in a way that we can use to actually help guid
Hi Ken,
Awesome! IMO it works for us.
Thanks
Renat Akhmerov
@Nokia
On 20 Oct 2018, 01:19 +0700, Ken Giusti , wrote:
> Hi Renat,
> After discussing this a bit with Ben on IRC we're going to push the removal
> off to T milestone 1.
>
> I really like Ben's idea re: adding a blocking entry to your
Hi Renat,
After discussing this a bit with Ben on IRC we're going to push the removal
off to T milestone 1.
I really like Ben's idea re: adding a blocking entry to your project's
setup.cfg file. We can remove the explicit check for blocking in
oslo.messaging so you won't get an annoying warning i
Hi,
@Ken, I understand your considerations. I get that. I’m only asking not to
remove it *for now*. And yes, if you think it should be discouraged from using
it’s totally fine. But practically, it’s been the only reliable option for
Mistral so far that may be our fault, I have to admit, becaus
On 10/18/18 9:59 AM, Ken Giusti wrote:
Hi Renat,
The biggest issue with the blocking executor (IMHO) is that it blocks
the protocol I/O while RPC processing is in progress. This increases
the likelihood that protocol processing will not get done in a timely
manner and things start to fail
Hi Renat,
The biggest issue with the blocking executor (IMHO) is that it blocks the
protocol I/O while RPC processing is in progress. This increases the
likelihood that protocol processing will not get done in a timely manner
and things start to fail in weird ways. These failures are timing rel
Hi Oslo Team,
Can we retain “blocking” executor for now in Oslo Messaging?
Some background..
For a while we had to use Oslo Messaging with “blocking” executor in Mistral
because of incompatibility of MySQL driver with green threads when choosing
“eventlet” executor. Under certain conditions w
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
Hi Oleg,
I looked at the blueprint. Looks good to me, I understand the motivation
behind. The fact that we use created_at and updated_at now to see the duration
of the task is often confusing, I agree. So this would be a good addition and
it is backward compatible. The only subtle thing is that
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 done. Please let me know in the blueprint if I can start
impl
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 usag
> Backporting a migration like that is OK as long as you don't skip
> migrations, that is to say revision '030' of the database should be the
> same on all branches. Given we've only just released rocky I expect
> that will be the case here.
>
> You absolutely must have a release note and call it
On Wed, Sep 05, 2018 at 10:54:25AM +0100, Dougal Matthews wrote:
> 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
I’m also in favour of backporting it because it solves a real production
problem.
Thanks
Renat Akhmerov
@Nokia
On 5 Sep 2018, 16:55 +0700, Dougal Matthews , wrote:
> > On 5 September 2018 at 10:52, Dougal Matthews wrote:
> > > > (Note: I added [release] to the email subject, as I think that wil
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 the
noise.
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 migration
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 migrations should not be added to a stable branch
and Renat Akhmerov advise
It’s disappointing that we can’t make it this time. Really bad coincidence of
different issues..
I’d love to have a virtual PTG and Dmitry’s notes look very helpful to me.
Thanks
Renat Akhmerov
@Nokia
On 21 Aug 2018, 17:15 +0700, Dmitry Tantsur , wrote:
> On 08/21/2018 10:22 AM, Dougal Matthews
On 08/21/2018 10:22 AM, Dougal Matthews wrote:
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
an
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 ar
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 so
Hello everyone,
A new release candidate for mistral-dashboard for the end of the Rocky
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 candi
Hello everyone,
A new release candidate for mistral-extra for the end of the Rocky
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 wil
Hello everyone,
A new release candidate for mistral for the end of the Rocky
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 formall
Awesome! We need to do it periodically :) It’ll be easier to sort out patches.
Thanks
Renat Akhmerov
@Nokia
On 6 Aug 2018, 16:24 +0700, Dougal Matthews , wrote:
>
>
> > On 3 August 2018 at 10:45, Dougal Matthews wrote:
> > > > On 9 July 2018 at 16:13, Dougal Matthews wrote:
> > > > > Hey folks,
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 are:
>> http://stackalytics.com/report/
Same.
On 3 August 2018 at 13:15, Renat Akhmerov wrote:
> Dougal, the policy looks good for me. I gave it the second +2 but didn’t
> approve yet so that others could also review (e.g. Adriano and Vitalii).
>
> Thanks
>
> Renat Akhmerov
> @Nokia
> On 3 Aug 2018, 16:46 +0700, Dougal Matthews , wrot
Dougal, the policy looks good for me. I gave it the second +2 but didn’t
approve yet so that others could also review (e.g. Adriano and Vitalii).
Thanks
Renat Akhmerov
@Nokia
On 3 Aug 2018, 16:46 +0700, Dougal Matthews , wrote:
> > On 9 July 2018 at 16:13, Dougal Matthews wrote:
> > > Hey folks
Lingxian, and any time welcome back as an active contributor if you wish! :) I
want to thank you for all contribution and achievements you made for our
project!
Renat Akhmerov
@Nokia
On 3 Aug 2018, 17:14 +0700, Lingxian Kong , wrote:
> +1 for me, i am still watching mistral :-)
>
> Cheers,
> Lin
+1 for me, i am still watching mistral :-)
Cheers,
Lingxian Kong
On Fri, Aug 3, 2018 at 9:58 PM Dougal Matthews wrote:
> 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 inactivit
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 if
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 would like to initially aban
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 :)
- https://governance.openstack.org
Agreed.
On 10 July 2018 at 05:42, Renat Akhmerov wrote:
> Dougal, I’m totally OK with this idea.
>
> Thanks
>
> Renat Akhmerov
> @Nokia
> On 9 Jul 2018, 22:14 +0700, Dougal Matthews , wrote:
>
> Hey folks,
>
> I'd like to propose that we start abandoning old Gerrit reviews.
>
> This report shows
Dougal, I’m totally OK with this idea.
Thanks
Renat Akhmerov
@Nokia
On 9 Jul 2018, 22:14 +0700, 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
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 want
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 Developmen
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 Mi
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
+1
On 19 June 2018 at 10:47, Dougal Matthews wrote:
>
>
> 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 h
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
+1 well deserved!
Renat Akhmerov ezt írta (időpont: 2018. jún.
19., K, 11:28):
> 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
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 the people who doesn’t hesitate taking responsibility for
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. https://w
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 r
_
From: Clark Boylan
Sent: Tuesday, May 1, 2018 6:12 PM
Subject: Re: [openstack-dev] [mistral] Help with test run
To:
On Fri, Apr 27, 2018, at 2:22 AM, András Kövi wrote:
> Hi,
>
> Can someone please help me with why this build ended with TIMED_OUT?
> http://logs.open
Thanks Brad for the check. Yes it’s quite consistent.
_
From: Brad P. Crochet
Sent: Tuesday, May 1, 2018 5:13 PM
Subject: Re: [openstack-dev] [mistral] Help with test run
To: OpenStack Development Mailing List (not for usage questions)
On Fri, Apr 27, 2018 at 5
On Fri, Apr 27, 2018, at 2:22 AM, András Kövi wrote:
> Hi,
>
> Can someone please help me with why this build ended with TIMED_OUT?
> http://logs.openstack.org/85/527085/8/check/mistral-tox-unit-mysql/3ffae9f/
Reading the job log the job setup only took a few minutes. Then the unittests
start an
On Fri, Apr 27, 2018 at 5:23 AM András Kövi wrote:
> Hi,
>
> Can someone please help me with why this build ended with TIMED_OUT?
> http://logs.openstack.org/85/527085/8/check/mistral-tox-unit-mysql/3ffae9f/
>
>
I'm not seeing any particular reason for it. Is it happening consistently?
> Thanks
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
Thanks for confirmation.Ticket https://bugs.launchpad.net/mistral/+bug/1767352I will try to fix it. 27.04.2018, 12:02, "Renat Akhmerov" :Yep, agree that this is a bug. We need to fix that. Would you please create a ticket at LP?ThanksRenat Akhmerov@NokiaOn 27 Apr 2018, 12:53 +0700, Vitalii Solodilo
Hi,
Can someone please help me with why this build ended with TIMED_OUT?
http://logs.openstack.org/85/527085/8/check/mistral-tox-unit-mysql/3ffae9f/
Thanks,
Andras
__
OpenStack Development Mailing List (not for usage questio
Yep, agree that this is a bug. We need to fix that. Would you please create a
ticket at LP?
Thanks
Renat Akhmerov
@Nokia
On 27 Apr 2018, 12:53 +0700, Vitalii Solodilov , wrote:
> > No matter at what stage the task is, but if it’s still in RUNNING state or
> > FAILED but we know that retry poli
> 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
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 plan to finish this p
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 us
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
__
OpenStac
Hey Sean :)
The reason why we picked the May 2nd date was so that people would know if
they needed to register before the early bird pricing closes. If groups
feel like they need more time to decide that's fine. It would still be
helpful if those needing more time could fill the survey with the 'M
Hi Dougal,
Very likely, I will join over the phone.
Thanks,
Andras
From: Renat Akhmerov
Sent: Tuesday, April 24, 2018 2:46:36 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [mistral] September PTG in Denver
Dougal,
Most likely, I’ll go.
Thanks
Renat Akhmerov
@Nokia
24 апр. 2018 г., 17:05 +0700, Dougal Matthews , писал:
>
>
> > 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
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 greatly appreciate
> >
Hi Renat, Can you explain me and Dougal how timeout policy should work with
retry policy?
I guess there is bug right now.
The behaviour is something like this https://ibb.co/hhm0eH
Example: https://review.openstack.org/#/c/563759/
Logs:
http://logs.openstack.org/59/563759/1/check/openstack-tox-
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 greatly appreciate
> it! If you need more time please let me know by then (May 2nd)
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 greatly appreciate
it! If you need more time please let me know by then (May 2nd) instead.
-Kendall (diablo_rojo)
On Fri, Apr 20, 2018 at 8:17 AM Dougal M
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 Renat,
>
> I'll join the
From: Renat Akhmerov
Date: Monday, 23 April 2018 at 9:45
On 23 Apr 2018, 13:38 +0700, Jaewook Oh , wrote:
Hello Mistral and Vitrage team,
I've been testing vitrage with mistral workflow,
but it seems that there are no Vitrage actions in Mistral yet.
I think Vitrage actions should be added t
Hello Renat,
I'll join the IRC channel :)
Thanks,
Jaewook.
2018-04-23 15:45 GMT+09:00 Renat Akhmerov :
> On 23 Apr 2018, 13:38 +0700, Jaewook Oh , wrote:
>
> Hello Mistral and Vitrage team,
>
> I've been testing vitrage with mistral workflow,
> but it seems that there are no Vitrage actions in
On 23 Apr 2018, 13:38 +0700, Jaewook Oh , wrote:
> Hello Mistral and Vitrage team,
>
> I've been testing vitrage with mistral workflow,
> but it seems that there are no Vitrage actions in Mistral yet.
>
> I think Vitrage actions should be added to Mistral.
> We can use the actions in mistral workf
Hello Mistral and Vitrage team,
I've been testing vitrage with mistral workflow,
but it seems that there are no Vitrage actions in Mistral yet.
I think Vitrage actions should be added to Mistral.
We can use the actions in mistral workflow to automate lots of repeated
tasks as it was originally in
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]:
http:/
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 correctly
ubject: Re: [openstack-dev] [Mistral]I think Mistral need K8S action
On 16 April 2018 at 05:08, mailto:xianjun...@dcn.ssu.ac.kr> > wrote:
Thanks for your reply.
I will refer to this Ansible action and developing actions for K8S somewhere
externally.
Great. Do let us kno
sibly helping out too.
>
>
> Regards,
>
> Xian Jun Hong
>
>
>
>
>
> *From:* Dougal Matthews
> *Sent:* Saturday, April 14, 2018 1:00 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
>
: [openstack-dev] [Mistral]I think Mistral need K8S action
On 13 April 2018 at 05:47, Renat Akhmerov mailto:renat.akhme...@gmail.com> > 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 provi
On 13 Apr 2018, 23:01 +0700, Dougal Matthews , wrote:
> > I would recommend developing actions for K8s somewhere externally, then
> > when mistral-extra is ready we can move them over. This is the approach
> > that I took for the Ansible actions[1] and they will likely be one of the
> > first a
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 for Mistral and
> are nativel
Thanks for your reply.
I will continue to pay attention.
Regards,
Xian Jun Hong
From: Renat Akhmerov
Sent: Friday, April 13, 2018 1:48 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Mistral]I think Mistral need K8S action
Hi
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 for Mistral and are
natively external to Mistral code base. In other words, this actio
Hello Mistral team.
I'm doing some work on the K8S but I observed that there is only Docker's
action in Mistral.
I would like to ask Mistral Team, why there is no K8S action in the mistral.
I think it would be useful in Mistral.
If you feel it's necessary, could I add K8S action to mistral?
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
Thank you, Dougal and Ghanshyam for the responses!
What I can gather is: service client registration > import service client
> retaining copy.
So the best thing for Congress to do now is to import the service client.
On 3/17/18, 9:00 PM, "Ghanshyam Mann" wrote:
>Hi All,
>
>Sorry for late respon
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)
U
Can we push a Mistral image to some registry?I think it is more convenient than zip for user. And we can add image to cache-from section. https://docs.docker.com/compose/compose-file/#cache_from About mysql, sorry, i don't have experience. I added the latest version of mysql. As I know that It's R
Hi All,
Sorry for late response, i kept this mail unread but forgot to
respond. reply inline.
On Fri, Mar 16, 2018 at 8:08 PM, Dougal Matthews wrote:
>
>
> 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
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 Mistral driver for Congress.
>
>
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 Mistral driver for Congress.
Regarding the service client, Congress can either impo
On 7 Mar 2018, 16:29 +0700, Dougal Matthews , 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, please get in touch. I want to update it
On 7 March 2018 at 09:28, Dougal Matthews 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, please get in touch. I want to update it whil
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 I
IMO, these sections should be moved to the official docs in some form:
• FAQ - https://wiki.openstack.org/w/index.php?title=Mistral&oldid=99745#FAQ
• Actions design -
https://wiki.openstack.org/wiki/Mistral/Blueprints/ActionsDesign
• Description of use cases:
• https://wiki.openstack.org/wik
Thanks Dougal, I’ll also look at it to see what’s still relevant.
Renat Akhmerov
@Nokia
On 6 Mar 2018, 21:24 +0700, Dougal Matthews , wrote:
> 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
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'
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
doc
: 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
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
C
CloudFlow [1] is an open-source web-based GUI tool that helps visualize and
debug Mistral workflows.
With the latest release [2] of CloudFlow (v0.5.0) you can:
* Visualize the flow of workflow executions
* Identify the execution path of a single task in huge workflows
* Search Mistral by any enti
Thanks!
Renat Akhmerov
@Nokia
On 14 Feb 2018, 22:55 +0700, Matthew Thode , wrote:
> On 18-02-14 17:03:10, 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: ht
On 18-02-14 17:03:10, 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: https://review.openstack.org/#/c/5434
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: https://review.openstack.org/#
1 - 100 of 1163 matches
Mail list logo