[openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Walls, Jeffrey Joel (Cloud OS R&D) jeff.walls at hp.com
Mon Jan 13 14:54:11 UTC 2014

> From: Jaromir Coufal [mailto:jcoufal at redhat.com]
>> On 2014/10/01 19:02, Dougal Matthews wrote:

> > - If I remove some instances, do I as the administrator need to care
> > which are removed? Do we need to choose or be informed at the end?
> This is great question on which we have long debates. I am convinced that I as
> administrator, do care which nodes I want to free up.
> But current TripleO approach is using heat template and there we can just
> specify number of nodes of that specific role. So it means that I decrease from
> 10 to 9 instances and app will take care for us for some node to be removed
> (AFAIK heat removes the last added node).
> So what we can do at the moment (until there is some way to specify which
> node to remove) is to inform user, which nodes were removed in the end... at
> least.
> In the future, I'd like to enable user to have both ways available - just decrease
> number and let system to decide which nodes are going to be removed for him
> (but at least inform in advance which nodes are the chosen ones). Or, let user to
> choose by himself.

Should a defect be filed against Heat then?  If I have a system that is currently running
my app server and heat comes along and deprovisions it (simply because it happened
to be running on the system that was spun up last), I'm going to be quite upset.


More information about the OpenStack-dev mailing list