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
signature.asc
Description: Message signed with OpenPGP using GPGMail
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
