Open Stack

Folks,

Recently we were investigating an issue [1] when a user configured a cluster to cause deployment to fail and then expected a discard button will allow to reset changes made after that failure. As Julia mentioned in her comment on the bug, basically what we’ve got is that users actually perceive the meaning of a cluster.deployed attribute as a snapshot to a latest deployment configuration while it was designed to keep the latest configuration of a successful deployment. Should we re-consider the meaning of that attribute and therefore features and the action of the Discard button?


References:

1. https://bugs.launchpad.net/fuel/+bug/1584681

-------------- 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/20160525/321ede19/attachment.pgp>