[openstack-dev] [Murano][Heat][Mistral] Use and adoption of YAQL
slagun at mirantis.com
Tue Mar 10 18:49:36 UTC 2015
I would suggest to do the migration but not to merge it till official yaql
1.0 release which is going to happen soon.
As for the docs it is still very hard to write them since yaql 1.0 has got
tons on new features and hundreds of functions. Any help is appreciated.
But 99% of yaql 1.0 features and functions are covered by unit tests and
there are ~250 of them so this is the best source of information at the
Principal Software Engineer @ Mirantis
<slagun at mirantis.com>
On Sat, Feb 7, 2015 at 12:46 AM, Dmitri Zimine <dzimine at stackstorm.com>
> Stan, Alex, Renat:
> Should we migrate to YAQL 1.0 now? and stop using the initial one? What’s
> the delta?
> Still short on the docs :) but I understand they’re coming up.
> Cheers, Dmitri.
> On Jan 16, 2015, at 6:46 AM, Stan Lagun <slagun at mirantis.com> wrote:
> we are working hard towards stable YAQL 1.0 which is expected to be
> released during Kilo cycle. It is going to have proper documentation and
> high unit test coverage which can also serve as a documentation source.
> YAQL has already migrated to StackForge and adopted OpenStack development
> process and tools but the work is still in progress. Any help from Mistral
> team and/or other YAQL adopters is appreciated.
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
> <slagun at mirantis.com>
> On Thu, Jan 15, 2015 at 10:54 PM, Dmitri Zimine <dzimine at stackstorm.com>
>> We use YAQL in Mistral for referencing variables, expressing conditions,
>> etc. Murano is using it extensively, I saw Heat folks thought of using it,
>> at least once :) May be others...
>> We are learning that YAQL incredibly powerful comparing to alternatives
>> like Jinja2 templates used in salt / ansible.
>> But with lack of documentation, it becomes one of adoption blockers to
>> Mistral (we got very vocal user feedback on this).
>> This is pretty much all the docs I can offer our users on YAQL so far.
>> Not much.
>> Are there any plans to fix it?
>> Are there interest from other projects to use YAQL?
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev