<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/">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">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><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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><span lang="en"><span> </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><span></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 class="HOEnZb"><font color="#888888"><br></font></span></a><span class="HOEnZb"><font color="#888888"><br></font></span></span></span><span class="HOEnZb"><font color="#888888"><div><div><div>-- <br><div><div dir="ltr">---<div>WBR, Alexey Shtokolov</div></div></div>
</div></div></div></font></span></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>