<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Oleg,<div class=""><br class=""></div><div class="">Thanks for the feedback. I have the following as a response:</div><div class=""><br class=""></div><div class="">1. This spec is just an excerpt for scoping in the proposed improvement to the 7.0 release plan. If it get’s scope the full specification will go through a standard review process so it will be possible to discuss names along with the rest of details then.</div><div class=""><br class=""></div><div class="">2. It’s already noticed in the spec the status is is generated using an aggregate query like you described so I don’t propose to store it. Storing that data will require sophisticated algorithms to work with it and also will lead to more locks or race conditions in the database. So yes, it’s going to be a method.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">- romcheg</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">27 трав. 2015 о 08:19 Oleg Gelbukh <<a href="mailto:ogelbukh@mirantis.com" class="">ogelbukh@mirantis.com</a>> написав(ла):</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Roman,<div class=""><br class=""></div><div class="">This looks like a great solution to me, and I like your proposal very much. The status of cluster derived directly from statuses of nodes is exactly what I was thinking about.</div><div class=""><br class=""></div><div class="">I have to notes to the proposal, and I can copy them to etherpad if you think they deserve it:</div><div class=""><br class=""></div><div class="">1) status name 'operational' seem a bit unclear to me, as it sounds more like something Monitoring should report: it implies that the actual OpenStack environment is operational, which might or might not be a case, and Fuel has no way to tell. I would really prefer if that status name was 'Deployed' or something along those lines.</div><div class=""><br class=""></div><div class="">2) I'm not sure if we need to keep the complex status of the cluster explicitly in 'cluster' table in the format you suggest. This information can be taken directly from 'nodes' table in Nailgun DB. For example, getting it in the second form you propose is as simple as: </div><div class=""><br class=""></div><div class="">nailgun=> SELECT status,count(status) FROM nodes GROUP BY status;</div><div class="">discover|1</div><div class="">ready|5<br class=""></div><div class=""><br class=""></div><div class="">What do you think about making it a method rather then an element of data model? Or that's exactly the complexity you want to get rid of?</div><div class=""><br class=""></div><div class="">--</div><div class="">Best regards,</div><div class="">Oleg Gelbukh</div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, May 26, 2015 at 4:16 PM, Roman Prykhodchenko <span dir="ltr" class=""><<a href="mailto:me@romcheg.me" target="_blank" class="">me@romcheg.me</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Oleg,<div class=""><br class=""></div><div class="">Aleksander also proposed a nice proposed a nice solution [1] which is to have a complex status for cluster. That, however, looks like a BP so I’ve created an excerpt [2] for it and we will try to discuss it scope it for 7.0, if there is a consensus.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">References:</div><div class=""><br class=""></div><div class="">1. <a href="http://lists.openstack.org/pipermail/openstack-dev/2015-May/064670.html" target="_blank" class="">http://lists.openstack.org/pipermail/openstack-dev/2015-May/064670.html</a></div><div class="">2. <a href="https://etherpad.openstack.org/p/fuel-cluster-complex-status" target="_blank" class="">https://etherpad.openstack.org/p/fuel-cluster-complex-status</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">- romcheg</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">22 трав. 2015 о 22:32 Oleg Gelbukh <<a href="mailto:ogelbukh@mirantis.com" target="_blank" class="">ogelbukh@mirantis.com</a>> написав(ла):</div><div class=""><div class="h5"><br class=""><div class=""><div dir="ltr" class="">Roman,<div class=""><br class=""></div><div class="">I'm totally for fixing Nailgun. However, the status of environment is not simply function of statuses of nodes in it. Ideally, it should depend on whether appropriate number of nodes of certain roles are in 'ready' status. For the meantime, it would be enough if environment was set to 'operational' when all nodes in it become 'ready', no matter how they were deployed (i.e. via Web UI or CLI).</div><div class=""><br class=""></div><div class="">--</div><div class="">Best regards,</div><div class="">Oleg Gelbukh</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, May 22, 2015 at 5:33 PM, Roman Prykhodchenko <span dir="ltr" class=""><<a href="mailto:me@romcheg.me" target="_blank" class="">me@romcheg.me</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi folks!<br class="">
<br class="">
Recently I encountered an issue [1] that the Deploy Changes button in the web ui is still active when a provisioning of single node is started using the command line client.<br class="">
The background for that issue is that the provisioning task does not seem to update the cluster status correctly and Nailgun’s API returns it as NEW even while some of the node are been provisioned.<br class="">
<br class="">
The reason for raising this thread in the mailing list is that provisioning a node is a feature for developers and basically end-users should not do that. What is the best solution for that: fix Nailgun to set the correct status, or make this provisioning feature available only for developers?<br class="">
<br class="">
1. <a href="https://bugs.launchpad.net/fuel/7.0.x/+bug/1449086" target="_blank" class="">https://bugs.launchpad.net/fuel/7.0.x/+bug/1449086</a><br class="">
<br class="">
<br class="">
- romcheg<br class="">
<br class="">
<br class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></div></div></blockquote></div><br class=""></div></div><br class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>