<div dir="ltr">Dmitry,<div><br></div><div>We are really close to have the consensus, but we need one more meeting with Fuel-Python Component Lead Igor Kalnitsky to make the final decision.</div><div>All patches [0] are on review. The meeting is scheduled for tomorrow (03/11 1:30pm CET). </div><div>Could you please grant us one more day for it?</div><div><br></div><div>[0] - <a href="https://review.openstack.org/#/q/topic:bp/store-deployment-tasks-history">https://review.openstack.org/#/q/topic:bp/store-deployment-tasks-history</a><br></div><div><br></div><div>--</div><div>WBR, Alexey Shtokolov</div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-03-04 3:13 GMT+03:00 Dmitry Borodaenko <span dir="ltr"><<a href="mailto:dborodaenko@mirantis.com" target="_blank">dborodaenko@mirantis.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Granted, merge deadline March 24, task history part of the feature is to<br>
be excluded from this exception grant unless a consensus is reached by<br>
March 10.<br>
<br>
Relevant part of the meeting log starts at:<br>
<a href="http://eavesdrop.openstack.org/meetings/fuel/2016/fuel.2016-03-03-16.00.log.html#l-198" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/meetings/fuel/2016/fuel.2016-03-03-16.00.log.html#l-198</a><br>
<br>
--<br>
Dmitry Borodaenko<br>
<div><div><br>
<br>
On Wed, Mar 02, 2016 at 06:00:40PM +0700, Vitaly Kramskikh wrote:<br>
> Oh, so there is a spec. I was worried that this patch has<br>
> "WIP-no-bprint-assigned-yet" string in the commit message, so I thought<br>
> there is no spec for it. So the commit message should be updated to avoid<br>
> such confusion.<br>
><br>
> It's really good I've seen this spec. There are plans to overhaul UI data<br>
> format description which we use for cluster and node settings to solve some<br>
> issues and implement long-awaited features like nested structures, so we<br>
> might also want to deprecate our expression language and also switch to<br>
> YAQL (and thus port YAQL to JS).<br>
><br>
> 2016-03-02 17:17 GMT+07:00 Vladimir Kuklin <<a href="mailto:vkuklin@mirantis.com" target="_blank">vkuklin@mirantis.com</a>>:<br>
><br>
> > Vitaly<br>
> ><br>
> > Thanks for bringing this up. Actually the spec has been on review for<br>
> > almost 2 weeks: <a href="https://review.openstack.org/#/c/282695/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/282695/</a>. Essentially,<br>
> > this is not introducing new DSL but replacing the existing one with more<br>
> > powerful extendable language which is being actively developed within<br>
> > OpenStack and is already a part of other projects (Murano, Mistral), which<br>
> > has much more contributors, can return not only boolean but any arbitrary<br>
> > collections. So it means that we want to deprecate current Expression<br>
> > language that you wrote and replace it with YAQL due to those reasons. You<br>
> > are not going to extend this Expression-based language in 3 weeks up to<br>
> > level of support of extensions, method overloading, return of arbitrary<br>
> > collections (e.g. we also want to calculate cross-depends and requires<br>
> > fields on the fly which require for it to return list of dicts) and support<br>
> > of this stuff on your own, are you?<br>
> ><br>
> > On Wed, Mar 2, 2016 at 10:09 AM, Vitaly Kramskikh <<a href="mailto:vkramskikh@mirantis.com" target="_blank">vkramskikh@mirantis.com</a><br>
> > > wrote:<br>
> ><br>
> >> I think it's not a part of best practices to introduce changes like<br>
> >> <a href="https://review.openstack.org/#/c/279714/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/279714/</a> (adding yet another DSL to the<br>
> >> project) without a blueprint and review and discussion of the spec.<br>
> >><br>
> >> 2016-03-02 2:19 GMT+07:00 Alexey Shtokolov <<a href="mailto:ashtokolov@mirantis.com" target="_blank">ashtokolov@mirantis.com</a>>:<br>
> >><br>
> >>> Fuelers,<br>
> >>><br>
> >>> I would like to request a feature freeze exception for "Unlock settings<br>
> >>> tab" feature [0]<br>
> >>><br>
> >>> This feature being combined with Task-based deployment [1] and<br>
> >>> LCM-readiness for Fuel deployment tasks [2] unlocks Basic LCM in Fuel. We<br>
> >>> conducted a thorough redesign of this feature and splitted it into several<br>
> >>> granular changes [3]-[6] to allow users to change settings on deployed,<br>
> >>> partially deployed, stopped or erred clusters and further run redeployment<br>
> >>> using a particular graph (custom or calculated based on expected changes<br>
> >>> stored in DB) and with new parameters.<br>
> >>><br>
> >>> We need 3 weeks after FF to finish this feature.<br>
> >>> Risk of not delivering it after 3 weeks is low.<br>
> >>><br>
> >>> Patches on review or in progress:<br>
> >>> <<a href="https://review.openstack.org/#/c/284139/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/284139/</a>><br>
> >>> <a href="https://review.openstack.org/#/c/284139/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/284139/</a><br>
> >>> <a href="https://review.openstack.org/#/c/279714/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/279714/</a><br>
> >>> <a href="https://review.openstack.org/#/c/286754/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/286754/</a><br>
> >>> <a href="https://review.openstack.org/#/c/286783/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/286783/</a><br>
> >>><br>
> >>> Specs:<br>
> >>> <a href="https://review.openstack.org/#/c/286713/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/286713/</a><br>
> >>> <a href="https://review.openstack.org/#/c/284797/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/284797/</a><br>
> >>> <a href="https://review.openstack.org/#/c/282695/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/282695/</a><br>
> >>> <a href="https://review.openstack.org/#/c/284250/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/284250/</a><br>
> >>><br>
> >>><br>
> >>> [0] <a href="https://blueprints.launchpad.net/fuel/+spec/unlock-settings-tab" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/fuel/+spec/unlock-settings-tab</a><br>
> >>> <<a href="https://blueprints.launchpad.net/fuel/+spec/unlock-settings-tab" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/fuel/+spec/unlock-settings-tab</a>>[1]<br>
> >>> <a href="https://blueprints.launchpad.net/fuel/+spec/enable-task-based-deployment" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/fuel/+spec/enable-task-based-deployment</a><br>
> >>> [2]<br>
> >>> <a href="https://blueprints.launchpad.net/fuel/+spec/granular-task-lcm-readiness" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/fuel/+spec/granular-task-lcm-readiness</a><br>
> >>> [3]<br>
> >>> <a href="https://blueprints.launchpad.net/fuel/+spec/computable-task-fields-yaql" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/fuel/+spec/computable-task-fields-yaql</a><br>
> >>> [4]<br>
> >>> <a href="https://blueprints.launchpad.net/fuel/+spec/store-deployment-tasks-history" rel="noreferrer" 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" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/fuel/+spec/custom-graph-execution</a><br>
> >>> [6]<br>
> >>> <a href="https://blueprints.launchpad.net/fuel/+spec/save-deployment-info-in-database" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/fuel/+spec/save-deployment-info-in-database</a><br>
> >>><br>
> >>> --<br>
> >>> ---<br>
> >>> WBR, Alexey Shtokolov<br>
> >>><br>
> >>><br>
> >>> __________________________________________________________________________<br>
> >>> OpenStack Development Mailing List (not for usage questions)<br>
> >>> Unsubscribe:<br>
> >>> <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>
> >>><br>
> >><br>
> >><br>
> >> --<br>
> >> Vitaly Kramskikh,<br>
> >> Fuel UI Tech Lead,<br>
> >> Mirantis, Inc.<br>
> >><br>
> >> __________________________________________________________________________<br>
> >> OpenStack Development Mailing List (not for usage questions)<br>
> >> Unsubscribe:<br>
> >> <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>
> >><br>
> ><br>
> ><br>
> > --<br>
> > Yours Faithfully,<br>
> > Vladimir Kuklin,<br>
> > Fuel Library Tech Lead,<br>
> > Mirantis, Inc.<br>
> > +7 (495) 640-49-04<br>
> > +7 (926) 702-39-68<br>
> > Skype kuklinvv<br>
> > 35bk3, Vorontsovskaya Str.<br>
> > Moscow, Russia,<br>
</div></div>> > <a href="http://www.mirantis.com" rel="noreferrer" target="_blank">www.mirantis.com</a> <<a href="http://www.mirantis.ru/" rel="noreferrer" target="_blank">http://www.mirantis.ru/</a>><br>
<span>> > <a href="http://www.mirantis.ru" rel="noreferrer" target="_blank">www.mirantis.ru</a><br>
> > <a href="mailto:vkuklin@mirantis.com" target="_blank">vkuklin@mirantis.com</a><br>
> ><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>
> ><br>
><br>
><br>
> --<br>
> Vitaly Kramskikh,<br>
> Fuel UI Tech Lead,<br>
> Mirantis, Inc.<br>
<br>
</span><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>
<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr">---<div>WBR, Alexey Shtokolov</div></div></div>
</div></div></div>