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? What exactly is impacted? Are there any simpler workarounds? 2) on YAQL readiness: Mistral moved to YAQL it because 1) power 2) upcoming docs and 3) compatibility. We target to claim Mistral DSL “complete” in Kilo. YAQL is a big part of DSL from the user standpoint. Changing YAQL makes users migrate their workflows. Thus we want to stick to a version of YAQL which will be documented and used long term. If YAQL 1.0 is not ready in Kilo we should revert no questions. If it is ready, and comes with documentation - would it be good for Murano users if Murano moves to it? 3) given that YAQL 0.2 is supported for another cycle (.5 year) and users of both Mistral and Murano are using it, 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. (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?) DZ> On Apr 13, 2015, at 6:13 AM, Serg Melikyan <[email protected]> wrote: > 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 finished Kilo development and working on bug-fixes > and releasing RC. This gate may be fixed if only Mistral will revert > 1.0.0 support in Kilo :'( > > Nikolay, what do you think about migrating to YAQL 1.0.0 in the next > release? I know that it was me who proposed Mistral team to adopt yaql > 1.0.0, and I am sorry, I didn't realize all consequences of moving > Mistral to yaql 1.0.0 and Murano team living with yaql 0.2.4. > > We need to work on packaging and supporting yaql in Ubuntu/CentOS in > order to add this library to the global-requirements and to avoid this > kind of issues in the future. > > On Mon, Apr 13, 2015 at 3:58 PM, Nikolay Makhotkin > <[email protected]> wrote: >>> >>> 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 dependency is >> missed (yaql 1.0, currently yaql 1.0.0b2) >> >> I think the root of problem is that Murano and Mistral have different yaql >> versions installed. >> >> -- >> Best Regards, >> Nikolay >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > > -- > Serg Melikyan, Senior Software Engineer at Mirantis, Inc. > http://mirantis.com | [email protected] > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
