<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Ok, the main problem is that we won’t be able to use Kilo releases of Murano and Mistral in the same environment which doesn’t make me happy. Hm… Ok. So looks like we’ll have to switch back to old YAQL till Liberty (which is very soon). <div class=""><div class=""><br class=""></div><div class=""><br class=""><div class="">
<div class="">Renat Akhmerov</div><div class="">@ Mirantis Inc.</div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 14 Apr 2015, at 01:09, Stan Lagun <<a href="mailto:slagun@mirantis.com" class="">slagun@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">1) yaql 1.0 is not a drop-in replacement for yaql 0.2 but only one version can be installed on any given system. Unless we use virtualenv, Docker or anything else to isolate applications. So if Murano and Mistral uses different yaql versions they will unable to live together on the same host<div class=""><br class=""></div><div class="">2) Currently we observe such impact on devstack tests but in general that will mean Murano and Mistral cannot be installed on the same DevStack or be together in some OpenStack distribution like Mirantis OpenStack at least the way they are deployed currently</div><div class=""><br class=""></div><div class="">3) yaql 1.0 is in beta status and is ready exactly to that degree. We don't expect any breaking changes anymore but it may still contain some bugs</div><div class=""><br class=""></div><div class="">4) Murano will move to yaql 1.0. We just didn't managed to do that in time before FF and it is too late to do that in Kilo</div><div class=""><br class=""></div><div class="">5) Generally we should have documentation for both versions. But the fact is that at the moment we don't even have documentation for 1.0 which is of a higher priority for us. So once again I suggest to contribute rather than wait for somebody else</div></div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature"><div dir="ltr" class=""><span style="border-collapse: separate; font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; font-size: inherit;" class=""><span style="font-family:arial;font-size:small" class="">Sincerely yours,<br class="">Stan Lagun<br class="">Principal Software Engineer @ Mirantis</span></span><br class=""><span style="border-collapse: separate; font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; font-size: inherit;" class=""><span style="font-family:arial;font-size:small" class=""><br class=""><a href="mailto:slagun@mirantis.com" target="_blank" class=""></a></span></span></div></div></div>
<br class=""><div class="gmail_quote">On Mon, Apr 13, 2015 at 9:19 PM, Dmitri Zimine <span dir="ltr" class=""><<a href="mailto:dzimine@stackstorm.com" target="_blank" class="">dzimine@stackstorm.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">My 2c:<br class="">
<br class="">
Yes Mistral moved to YAQL 1.0 based on Murano team recommendations :)<br class="">
<br class="">
some questions/comments before we decide how to proceed:<br class="">
<br class="">
1) Let’s clarify the impact: this problem doesn’t affect Murano directly; but it impacts Murano-Congress-Mistral initiative, correct?<br class="">
Is this a voting gate? What exactly is impacted? Are there any simpler workarounds?<br class="">
<br class="">
2) on YAQL readiness:<br class="">
Mistral moved to YAQL it because 1) power 2) upcoming docs and 3) compatibility.<br class="">
<br class="">
We target to claim Mistral DSL “complete” in Kilo. YAQL is a big part of DSL from the user standpoint.<br class="">
Changing YAQL makes users migrate their workflows.<br class="">
Thus we want to stick to a version of YAQL which will be documented and used long term.<br class="">
<br class="">
If YAQL 1.0 is not ready in Kilo we should revert no questions.<br class="">
If it is ready, and comes with documentation - would it be good for Murano users if Murano moves to it?<br class="">
<br class="">
3) given that YAQL 0.2 is supported for another cycle (.5 year) and users of both Mistral and Murano are using it,<br class="">
are there any plans to add documentation to it? It is the lack of docs on 0.2 is the biggest reason to push forward.<br class="">
(Does this sound like an invitation to cheat and offer no docs for 1.0 in kilo to convince Mistral to stay on 0.2?)<br class="">
<span class="HOEnZb"><font color="#888888" class=""><br class="">
DZ><br class="">
</font></span><div class="HOEnZb"><div class="h5"><br class="">
On Apr 13, 2015, at 6:13 AM, Serg Melikyan <<a href="mailto:smelikyan@mirantis.com" class="">smelikyan@mirantis.com</a>> wrote:<br class="">
<br class="">
> Hi Nikolay & Filip,<br class="">
><br class="">
> indeed, root cause of the issue is that Murano & Mistral use different<br class="">
> version of yaql library. Murano installs yaql 0.2.4 and overrides<br class="">
> 1.0.0b2 already installed and expected by Mistral.<br class="">
><br class="">
> We decided that we are not going to switch to the yaql 1.0.0 in Kilo<br class="">
> since we already finished Kilo development and working on bug-fixes<br class="">
> and releasing RC. This gate may be fixed if only Mistral will revert<br class="">
> 1.0.0 support in Kilo :'(<br class="">
><br class="">
> Nikolay, what do you think about migrating to YAQL 1.0.0 in the next<br class="">
> release? I know that it was me who proposed Mistral team to adopt yaql<br class="">
> 1.0.0, and I am sorry, I didn't realize all consequences of moving<br class="">
> Mistral to yaql 1.0.0 and Murano team living with yaql 0.2.4.<br class="">
><br class="">
> We need to work on packaging and supporting yaql in Ubuntu/CentOS in<br class="">
> order to add this library to the global-requirements and to avoid this<br class="">
> kind of issues in the future.<br class="">
><br class="">
> On Mon, Apr 13, 2015 at 3:58 PM, Nikolay Makhotkin<br class="">
> <<a href="mailto:nmakhotkin@mirantis.com" class="">nmakhotkin@mirantis.com</a>> wrote:<br class="">
>>><br class="">
>>> We are facing an issue with Mistral devstack installation in our gate job testing murano-congress-mistral integration (policy enforcement) [1] . Mistral devstack scripts are failing with following import error [2]<br class="">
>><br class="">
>><br class="">
>> Hi, Filip!<br class="">
>><br class="">
>> Recently Mistral has moved to new YAQL, and it seems this dependency is missed (yaql 1.0, currently yaql 1.0.0b2)<br class="">
>><br class="">
>> I think the root of problem is that Murano and Mistral have different yaql versions installed.<br class="">
>><br class="">
>> --<br class="">
>> Best Regards,<br class="">
>> Nikolay<br class="">
>><br class="">
>> __________________________________________________________________________<br class="">
>> OpenStack Development Mailing List (not for usage questions)<br class="">
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>><br class="">
><br class="">
><br class="">
><br class="">
> --<br class="">
> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.<br class="">
> <a href="http://mirantis.com/" target="_blank" class="">http://mirantis.com</a> | <a href="mailto:smelikyan@mirantis.com" class="">smelikyan@mirantis.com</a><br class="">
><br class="">
> __________________________________________________________________________<br class="">
> OpenStack Development Mailing List (not for usage questions)<br class="">
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class="">
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div></div></blockquote></div><br class=""></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></div></body></html>