Open Stack

Oleg,

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.


References:

1. http://lists.openstack.org/pipermail/openstack-dev/2015-May/064670.html <http://lists.openstack.org/pipermail/openstack-dev/2015-May/064670.html>
2. https://etherpad.openstack.org/p/fuel-cluster-complex-status <https://etherpad.openstack.org/p/fuel-cluster-complex-status>


- romcheg

> 22 трав. 2015 о 22:32 Oleg Gelbukh <ogelbukh at mirantis.com> написав(ла):
> 
> Roman,
> 
> 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).
> 
> --
> Best regards,
> Oleg Gelbukh
> 
> On Fri, May 22, 2015 at 5:33 PM, Roman Prykhodchenko <me at romcheg.me <mailto:me at romcheg.me>> wrote:
> Hi folks!
> 
> 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.
> 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.
> 
> 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?
> 
> 1. https://bugs.launchpad.net/fuel/7.0.x/+bug/1449086 <https://bugs.launchpad.net/fuel/7.0.x/+bug/1449086>
> 
> 
> - romcheg
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150526/ed1a1026/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150526/ed1a1026/attachment.pgp>