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).
Renat Akhmerov
@ Mirantis Inc.
> On 14 Apr 2015, at 0
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
2) Cu
My 2c:
Yes Mistral moved to YAQL 1.0 based on Murano team recommendations :)
some questions/comments before we decide how to proceed:
1) Let’s clarify the impact: this problem doesn’t affect Murano directly; but
it impacts Murano-Congress-Mistral initiative, correct?
Is this a voting gate? W
Hi Nikolay & Filip,
indeed, root cause of the issue is that Murano & Mistral use different
version of yaql library. Murano installs yaql 0.2.4 and overrides
1.0.0b2 already installed and expected by Mistral.
We decided that we are not going to switch to the yaql 1.0.0 in Kilo
since we already fin
>
> 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]
Hi, Filip!
Recently Mistral has moved to new YAQL, and it seems this depen
Hello
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]
2015-04-12 14:06:25.236 | Traceback (most recent call last):
2015-04-12 1
