[openstack-dev] [glare] Few questions regarding OpenStack Glare

[Elisha, Moshe (Nokia - IL)]

Hi,

My name is Moshe Elisha and I work at CloudBand, Nokia.
I watched "Glare - A Unified Binary Repository for OpenStack[1]" and it looks 
very nice and useful.

We are considering using Glare as a standalone artifacts repository.
We have two main use cases:

A. Create a custom artifact_type which basically has one archive file 
(BLOB).

B. Use "images" artifact type to store images.

I have a few questions that I couldn't find the answer for and I would 
appreciate it if you could please reply:


1.  What dependencies does Glare have on other OpenStack services? Is it 
only a dependency in Keystone?

2.  I saw that there is a way to implement a "validate_upload" hook. Is 
there a support for an async validation process (in case validation process is 
long)?

3.  Is there a way to define the "backend" used per artifact_type? For 
example, "heat_templates" will be stored on "File system" and "images" will be 
stored on "Ceph"?

4.  Were there talks about a "Database" backend? Probably only relevant for 
some artifact types.

5.  Disregarding the "backend" used - is there anything that prevents Glare 
from running in HA active/active mode?

6.  With regards to "backend" - which of the currently supported backends 
is preferable in order to achieve HA active/active mode?

7.  I noticed that there is a puppet-glare[2] project. Can you please share 
the status of that project?

8.  Is there any work being done for creating RPMs for glare?

[1] https://www.youtube.com/watch?v=uBtqdXciF4A
[2] https://github.com/openstack/puppet-glare
[3] https://github.com/openstack-packages


Thanks!


Moshe Elisha,
R Director,
CloudBand Network Director, Nokia.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [mistral] Promoting Dawid Deja to core reviewers

[Elisha, Moshe (Nokia - IL)]

Hi,

I am not a core reviewer but having met Dawid in person and working closely 
with him on some important bug fixes – I fully support the idea.

From: Anastasia Kuznetsova 
>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Friday, 29 July 2016 at 15:53
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: Re: [openstack-dev] [mistral] Promoting Dawid Deja to core reviewers

Renat,

I fully support Dawid's promotion! Here is my +1 for Dawid.

Dawid,

I will be glad to see you in the Mistral core team.

On Fri, Jul 29, 2016 at 2:39 PM, Renat Akhmerov 
> wrote:
Hi,

I’d like to promote Dawid Deja working at Intel (ddeja in IRC) to Mistral core 
reviewers.

The reasons why I want to see Dawid in the core team is that he provides 
amazing, very thorough reviews.
Just by looking at a few of them I was able to make a conclusion that he knows 
the system architecture very well
although he started contributing actively not so long ago. He always sees 
things deeply, can examine a problem
from different angles, demonstrates solid technical background in general. He 
is in top 5 reviewers now by a number
of reviews and the only one who still doesn’t have core status. He also 
implemented several very important changes
during Newton cycle. Some of them were in progress for more than a year 
(flexible RPC) but Dawid helped to knock
them down elegantly.

Besides purely professional skills that I just mentioned I also want to say 
that it’s a great pleasure to work with
Dawid. He’s a bright cheerful guy and a good team player.

Dawid’s statistics is here: 
http://stackalytics.com/?module=mistral-group=commits_id=dawid-deja-0


I’m hoping for your support in making this promotion.

Thanks

Renat Akhmerov
@Nokia


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
Best regards,
Anastasia Kuznetsova
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Elisha, Moshe (Nokia - IL)]

Octopus sounds good to me.
For me it somehow relates to Mistral as well – like concurrent tasks…

From: Renat Akhmerov >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Tuesday, 19 July 2016 at 07:36
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: Re: [openstack-dev] [mistal] Mistral logo ideas?



On 18 Jul 2016, at 19:54, Ryan Brady 
> wrote:

On Mon, Jul 18, 2016 at 12:44 AM, Renat Akhmerov 
> wrote:
On choosing a mascot for Mistral. Let’s choose one till next Monday.

To start this discussion I’d like to propose a couple of ideas:


  *   Octopus (kind of symbolic to me). How do you like this beauty? 
http://nashaplaneta.su/_bl/158/78285238.jpg

 +1.  Intelligence, dexterity, tool-use - many good qualitites to associate 
with.


Yep :)


Renat Akhmerov
@Nokia

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [heat] [yaql] Evaluate YAQL expressions in the yaqluator

[Elisha, Moshe (Nokia - IL)]

Hi,

I saw that starting the Newton release - Heat supports yaql function[1].
I think this will prove to be very powerful and very handy.

I wanted to make sure you are familiar with the yaqluator[2] as it might be 
useful for you.

yaqluator – is a free online YAQL evaluator.
* Enter a YAML / JSON and a YAQL expression and evaluate to see the result.
* There is a catalog of commonly used OpenStack API responses to run YAQL 
expressions against.
* It is open-source[3] and any contribution is welcome.

I hope you will find it useful.


[1] http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#yaql
[2] http://yaqluator.com
[3] https://github.com/ALU-CloudBand/yaqluator


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Elisha, Moshe (Nokia - IL)]

Thank you all for assisting.

When I tested Mistral I used an older version of Mistral (meaning an older 
version of yaql).

I have verified that latest Mistral is working as expected.
I have upgraded the yaql library in yaqluator to 1.1.0 and it is now working as 
expected.

Thanks!

From: Dougal Matthews <dou...@redhat.com<mailto:dou...@redhat.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, 5 July 2016 at 17:53
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [mistral] [murano] [yaql] yaqluator bug



On 5 July 2016 at 08:32, Renat Akhmerov 
<renat.akhme...@gmail.com<mailto:renat.akhme...@gmail.com>> wrote:
Stan, thanks for clarification. What’s the latest stable version that we’re 
supposed to use? global-requirements.txt has yaql>=1.1.0, I wonder if it’s 
correct.

It is also worth looking at the upper-constraints.txt. It has 1.1.1 which is 
the latest release. So it all seems up to date.

https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L376

I think the problem is that this external project isn't being updated. Assuming 
they have not deployed anything that isn't committed, then they are running 
YAQL 1.0.2 which is almost a year old.

https://github.com/ALU-CloudBand/yaqluator/blob/master/requirements.txt#L3


Renat Akhmerov
@Nokia

On 05 Jul 2016, at 12:12, Stan Lagun 
<sla...@mirantis.com<mailto:sla...@mirantis.com>> wrote:

Hi!

The issue with join is just a yaql bug that is already fixed. The problem with 
yaqluator is that it doesn't use the latest yaql library.

Another problem is that it does't sets options correctly. As a result it is 
possible to bring the site down with a query that produces endless collection

Sincerely yours,
Stan Lagun
Principal Software Engineer @ Mirantis

<mailto:sla...@mirantis.com>

On Tue, Jun 28, 2016 at 9:46 AM, Elisha, Moshe (Nokia - IL) 
<moshe.eli...@nokia.com<mailto:moshe.eli...@nokia.com>> wrote:
Hi,

Thank you for the kind words, Alexey.

I was able to reproduce your bug and I have also found the issue.

The problem is that we did not create the parser with the engine_options used 
in the yaql library by default when using the CLI.
Specifically, the "yaql.limitIterators" was missing… I am not sure that this 
settings should have this affect but maybe the Yaql guys can comment on that.

If we will change yaqluator to use this setting it will mean that yaqluator 
will not be consistent with Mistral because Mistral is using YAQL without this 
engine option (If I use your example in a workflow, Mistral returns exactly 
like the yaqluator returns)


Workflow:


---
version: '2.0'

test_yaql:
  tasks:
test_yaql:
  action: std.noop
  publish:
output_expr: <% [1,2].join([3], true, [$1, $2]) %>

Workflow result:


[root@s53-19 ~(keystone_admin)]# mistral task-get-published 
01d2bce3-20d0-47b2-84f2-7bd1cb2bf9f7
{
"output_expr": [
[
1,
3
]
]
}


As Matthews pointed out, the yaqluator is indeed OpenSource and contributions 
are welcomed.

[1] 
https://github.com/ALU-CloudBand/yaqluator/commit/e523dacdde716d200b5ed1015543d4c4680c98c2



From: Dougal Matthews <dou...@redhat.com<mailto:dou...@redhat.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Monday, 27 June 2016 at 16:44
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [mistral] [murano] [yaql] yaqluator bug

On 27 June 2016 at 14:30, Alexey Khivin 
<akhi...@gmail.com<mailto:akhi...@gmail.com>> wrote:
Hello, Moshe

Tomorrow I discovered yaqluator.com<http://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 same time this expression evaluated right when I using raw yaql 
interpreter.

Could we fix this issue?

By the way, don't you want to make yaqluator opensource? If you would transfer 
yaqluator to Openstack Foundation, then  community will be able to fix such 
kind of bugs

It looks like it is open source, there is a link in the footer: 
https://github.com/ALU-CloudBand/yaqluator


Thank you!
Best regards, Alexey Khivin



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe

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

[Elisha, Moshe (Nokia - IL)]

Hi,

Thank you for the kind words, Alexey.

I was able to reproduce your bug and I have also found the issue.

The problem is that we did not create the parser with the engine_options used 
in the yaql library by default when using the CLI.
Specifically, the "yaql.limitIterators" was missing… I am not sure that this 
settings should have this affect but maybe the Yaql guys can comment on that.

If we will change yaqluator to use this setting it will mean that yaqluator 
will not be consistent with Mistral because Mistral is using YAQL without this 
engine option (If I use your example in a workflow, Mistral returns exactly 
like the yaqluator returns)


Workflow:


---
version: '2.0'

test_yaql:
  tasks:
test_yaql:
  action: std.noop
  publish:
output_expr: <% [1,2].join([3], true, [$1, $2]) %>

Workflow result:


[root@s53-19 ~(keystone_admin)]# mistral task-get-published 
01d2bce3-20d0-47b2-84f2-7bd1cb2bf9f7
{
"output_expr": [
[
1,
3
]
]
}


As Matthews pointed out, the yaqluator is indeed OpenSource and contributions 
are welcomed.

[1] 
https://github.com/ALU-CloudBand/yaqluator/commit/e523dacdde716d200b5ed1015543d4c4680c98c2



From: Dougal Matthews >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Monday, 27 June 2016 at 16:44
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: 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 same time this expression evaluated right when I using raw yaql 
interpreter.

Could we fix this issue?

By the way, don't you want to make yaqluator opensource? If you would transfer 
yaqluator to Openstack Foundation, then  community will be able to fix such 
kind of bugs

It looks like it is open source, there is a link in the footer: 
https://github.com/ALU-CloudBand/yaqluator


Thank you!
Best regards, Alexey Khivin



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Elisha, Moshe (Nokia - IL)]

Hi,

Attached another draft based on Michal's idea (it probably should be more 
colourful)

Maybe we can upload them to some online survey and vote…


From: Ryan Brady >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Tuesday, 28 June 2016 at 17:08
To: Jason Rist >, "OpenStack 
Development Mailing List (not for usage questions)" 
>
Subject: Re: [openstack-dev] [mistal] Mistral logo ideas?



On Tue, Jun 28, 2016 at 1:38 AM, Jason Rist 
> wrote:
On 06/27/2016 06:57 AM, Dougal Matthews wrote:
> 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 it
> > could be
> >> a turbine with a gust of wind. Then we can show that Mistral harnesses
> > the
> >> power of the wind :-)
> >
> > Yeah, I’m just wondering how it would look like :)
> >
> >
> Yeah, for this idea we probably need somebody with artistic skills far
> superior
> to anything I could manage. We are getting quite a few good ideas now
> anyway!
>
>
> Renat Akhmerov
> > @Nokia
> >
> >
>

Ever since I saw the blueprint for a mistral logo, I've been working on some 
ideas.  I've presented a few to Dougal and Ryan, but I'm sharing widely here.  
I also did the one Michal came up with in Illustrator as well.  Please give me 
some feedback!  Both of the ones I thought of are "wind" related.  I thought 
about doing the ship before as well, but perhaps a little too war related, and 
also obscure.

+1 to the mistral-tornado.png logo.  I think it would be easily distinguishable 
at any size or distance.


Thanks,
Jason

P.S. you may recognize my name from the DLRN logo [1] and the TripleO Logo [2].

[1] 
https://github.com/openstack-packages/DLRN/blob/master/doc/source/_images/DLRN.png
[2] 
https://github.com/dprince/tripleosphinx/blob/master/tripleosphinx/theme/tripleo/static/tripleo_owl.svg

--
Jason E. Rist
Senior Software Engineer
OpenStack User Interfaces
Red Hat, Inc.
openuc: +1.972.707.6408
mobile: +1.720.256.3933
Freenode: jrist
github/twitter: knowncitizen

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
Ryan Brady
Cloud Engineering
rbr...@redhat.com
919.890.8925
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [mistral] More attention to PostgreSQL

[Elisha, Moshe (Nokia - IL)]

Hi,

We have more and more customers that want to run Mistral on top of PostgreSQL 
database (instead of MySQL).
I also know that PostgreSQL is important for some of our active contributors.

Can we add more attention to PostgreSQL? For example, add more gates (like 
gate-rally-dsvm-mistral-task and gate-mistral-devstack-dsvm) that will run on 
top of PostgreSQL as well.

What do you think?

Thanks.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [mistral] Promoting Anastasia Kuznetsova to core reviewers

[Elisha, Moshe (Nokia - IL)]

A very big +1

From: Renat Akhmerov [rakhme...@mirantis.com]
Sent: Friday, January 29, 2016 8:13 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [mistral] Promoting Anastasia Kuznetsova to core   
reviewers

Team,

I’d like to promote Anastasia Kuznetsova to the core team. What she’s been 
doing for 2 years is hard to overestimate. She’s done a huge amount of work 
reviewing code, bugfixing and participating in public discussions including our 
IRC channel #openstack-mistral. She is very reliable, diligent and consistent 
about her work.

Please vote.

Renat Akhmerov
@ Mirantis Inc.




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev