<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><blockquote type="cite" class="clean_bq"><div dir="ltr">(and thus port YAQL to JS)</div></blockquote></div> <div><br></div><div>FYI, you’re not the first one to have that idea. =)</div><div><br></div><div>We have <a href="https://review.openstack.org/#/c/159905/3">https://review.openstack.org/#/c/159905/3</a> an initial draft of how YAQL may look on JS. It’s outdated, but most certainly can be revived and finished if you have interest in helping us make it happen. =)</div><div><br></div> <div id="bloop_sign_1457052929000452096" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Kirill Zaitsev<br>Murano team</div><div style="font-family:helvetica,arial;font-size:13px">Software Engineer</div><div style="font-family:helvetica,arial;font-size:13px">Mirantis, Inc</div></div> <br><p class="airmail_on">On 2 March 2016 at 14:01:57, Vitaly Kramskikh (<a href="mailto:vkramskikh@mirantis.com">vkramskikh@mirantis.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>
<title></title>
<div dir="ltr">
<div>Oh, so there is a spec. I was worried that this patch has
"WIP-no-bprint-assigned-yet" string in the commit message, so I
thought there is no spec for it. So the commit message should be
updated to avoid such confusion.<br>
<br></div>
It's really good I've seen this spec. There are plans to overhaul
UI data format description which we use for cluster and node
settings to solve some issues and implement long-awaited features
like nested structures, so we might also want to deprecate our
expression language and also switch to YAQL (and thus port YAQL to
JS).<br></div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-03-02 17:17 GMT+07:00 Vladimir Kuklin
<span dir="ltr"><<a href="mailto:vkuklin@mirantis.com" target="_blank">vkuklin@mirantis.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Vitaly
<div><br></div>
<div>Thanks for bringing this up. Actually the spec has been on
review for almost 2 weeks: <a href="https://review.openstack.org/#/c/282695/" target="_blank">https://review.openstack.org/#/c/282695/</a>. Essentially,
this is not introducing new DSL but replacing the existing one with
more powerful extendable language which is being actively developed
within OpenStack and is already a part of other projects (Murano,
Mistral), which has much more contributors, can return not only
boolean but any arbitrary collections. So it means that we want to
deprecate current Expression language that you wrote and replace it
with YAQL due to those reasons. You are not going to extend this
Expression-based language in 3 weeks up to level of support of
extensions, method overloading, return of arbitrary collections
(e.g. we also want to calculate cross-depends and requires fields
on the fly which require for it to return list of dicts) and
support of this stuff on your own, are you?</div>
</div>
<div class="gmail_extra">
<div>
<div class="h5"><br>
<div class="gmail_quote">On Wed, Mar 2, 2016 at 10:09 AM, Vitaly
Kramskikh <span dir="ltr"><<a href="mailto:vkramskikh@mirantis.com" target="_blank">vkramskikh@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I think it's not a part of best practices to
introduce changes like <a href="https://review.openstack.org/#/c/279714/" target="_blank">https://review.openstack.org/#/c/279714/</a> (adding yet
another DSL to the project) without a blueprint and review and
discussion of the spec.<br></div>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div>2016-03-02 2:19 GMT+07:00 Alexey Shtokolov <span dir="ltr"><<a href="mailto:ashtokolov@mirantis.com" target="_blank">ashtokolov@mirantis.com</a>></span>:<br></div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>
<div dir="ltr">
<div>
<div>
<div>Fuelers,<br>
<br></div>
I would like to request a feature freeze exception for "Unlock
settings tab" feature [0]<br>
<br></div>
This feature <span lang="en"><span>being combined with Task-based
deployment [1] and LCM-readiness for Fuel deployment tasks [2]
unlocks Basic LCM in Fuel.</span></span> <span lang="en"><span>We
conducted a thorough redesign of this feature and splitted it into
several granular changes [3]-[6] to allow</span></span> <span lang="en"><span>users to change settings on deployed, partially
deployed, stopped or erred clusters and further run redeployment
using a particular graph (custom or calculated based on expected
changes stored in DB) and with new parameters.</span></span></div>
<span><br>
We need 3 weeks after FF to finish this
<span>feature</span>.</span> <span><br>
Risk of not delivering it after 3 weeks is low.</span>
<div><span lang="en"><span><br></span></span></div>
<div><span lang="en"><span>Patches on review or in progress:<br>
<a href="https://review.openstack.org/#/c/284139/" target="_blank"></a></span></span><span lang="en"><span><a href="https://review.openstack.org/#/c/284139/" target="_blank">https://review.openstack.org/#/c/284139/</a><br>
<a href="https://review.openstack.org/#/c/279714/" target="_blank">https://review.openstack.org/#/c/279714/</a><br>
<a href="https://review.openstack.org/#/c/286754/" target="_blank">https://review.openstack.org/#/c/286754/</a><br>
<a href="https://review.openstack.org/#/c/286783/" target="_blank">https://review.openstack.org/#/c/286783/</a><br></span></span><br>
S<span lang="en"><span><span lang="en"><span>pecs:<br></span></span><a href="https://review.openstack.org/#/c/286713/" target="_blank">https://review.openstack.org/#/c/286713/</a><br>
<a href="https://review.openstack.org/#/c/284797/" target="_blank">https://review.openstack.org/#/c/284797/</a><br>
<a href="https://review.openstack.org/#/c/282695/" target="_blank">https://review.openstack.org/#/c/282695/</a><br>
<a href="https://review.openstack.org/#/c/284250/" target="_blank">https://review.openstack.org/#/c/284250/</a><br></span></span></div>
<div><span lang="en"><span><br>
<br>
[0] <a href="https://blueprints.launchpad.net/fuel/+spec/unlock-settings-tab" target="_blank">https://blueprints.launchpad.net/fuel/+spec/unlock-settings-tab</a><br>
<a href="https://blueprints.launchpad.net/fuel/+spec/unlock-settings-tab" target="_blank"></a>[1] <a href="https://blueprints.launchpad.net/fuel/+spec/enable-task-based-deployment" target="_blank">https://blueprints.launchpad.net/fuel/+spec/enable-task-based-deployment<br>
</a>[2] <a href="https://blueprints.launchpad.net/fuel/+spec/granular-task-lcm-readiness" target="_blank">https://blueprints.launchpad.net/fuel/+spec/granular-task-lcm-readiness</a><br>
[3] <a href="https://blueprints.launchpad.net/fuel/+spec/computable-task-fields-yaql" target="_blank">https://blueprints.launchpad.net/fuel/+spec/computable-task-fields-yaql</a><br>
[4] <a href="https://blueprints.launchpad.net/fuel/+spec/store-deployment-tasks-history" target="_blank">https://blueprints.launchpad.net/fuel/+spec/store-deployment-tasks-history</a><br>
[5] <a href="https://blueprints.launchpad.net/fuel/+spec/custom-graph-execution" target="_blank">https://blueprints.launchpad.net/fuel/+spec/custom-graph-execution</a><br>
[6] <a href="https://blueprints.launchpad.net/fuel/+spec/save-deployment-info-in-database" target="_blank">https://blueprints.launchpad.net/fuel/+spec/save-deployment-info-in-database<span><font color="#888888"><br>
</font></span></a><span><font color="#888888"><br></font></span></span></span>
<div>
<div>
<div><span><font color="#888888">--<br></font></span>
<div>
<div dir="ltr"><span><font color="#888888">---</font></span>
<div><span><font color="#888888">WBR, Alexey
Shtokolov</font></span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br></div>
</div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote>
</div>
<span><font color="#888888"><br>
<br clear="all">
<br>
--<br></font></span>
<div>
<div dir="ltr">
<div>
<div dir="ltr"><span><font color="#888888">Vitaly Kramskikh,<br>
Fuel UI Tech Lead,<br>
Mirantis, Inc.</font></span></div>
</div>
</div>
</div>
</div>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote>
</div>
<br>
<br clear="all">
<div><br></div>
--<br></div>
</div>
<div>
<div dir="ltr">
<div>
<div dir="ltr">Yours Faithfully,<br>
Vladimir Kuklin,<br>
Fuel Library Tech Lead,<br>
Mirantis, Inc.<br>
<a href="tel:%2B7%20%28495%29%20640-49-04" value="+74956404904" target="_blank">+7 (495) 640-49-04</a><br>
<a href="tel:%2B7%20%28926%29%20702-39-68" value="+79267023968" target="_blank">+7 (926) 702-39-68</a><br>
Skype kuklinvv<br>
35bk3, Vorontsovskaya Str.<br>
Moscow, Russia,<br>
<a href="http://www.mirantis.ru/" target="_blank">www.mirantis.com</a><br>
<a href="http://www.mirantis.ru/" target="_blank">www.mirantis.ru</a><br>
<a href="mailto:vkuklin@mirantis.com" target="_blank">vkuklin@mirantis.com</a></div>
</div>
</div>
</div>
</div>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote>
</div>
<br>
<br clear="all">
<br>
--<br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">Vitaly Kramskikh,<br>
Fuel UI Tech Lead,<br>
Mirantis, Inc.</div>
</div>
</div>
</div>
</div>
__________________________________________________________________________
<br>OpenStack Development Mailing List (not for usage questions)
<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<br></div></div></span></blockquote></body></html>