> I think the ultimate answer is to stop using removal policies and mark resources as unhealthy instead.
Long term you may be right, but short term that doesn't help us as we're doing index based personalization of servers, which means we want index->server relationships to be unique (e.g rebuilding index "0" and getting a completely different node in the rack built will not be acceptable for some operators).
Another possibility is we stop using heat to build the servers altogether and instead build them via a mistral workflow, but again that is a long term idea. For now I'll hack around it with some ugly yaql logic :\
> I think the ultimate answer is to stop using removal policies and mark resources as unhealthy instead.
Long term you may be right, but short term that doesn't help us as we're doing index based personalization of servers, which means we want index->server relationships to be unique (e.g rebuilding index "0" and getting a completely different node in the rack built will not be acceptable for some operators).
Another possibility is we stop using heat to build the servers altogether and instead build them via a mistral workflow, but again that is a long term idea. For now I'll hack around it with some ugly yaql logic :\