<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><blockquote cite="mid:CAJ3HoZ2VZQHpw-Xax-nuM1tQy1oHTeC127+Hia+ZNR96gHTN6Q@mail.gmail.com"><pre>- As an infrastructure administrator, Anna wants to be able to unallocate a node from a deployment.
</pre><pre>Why? Whats her motivation. One plausible one for me is 'a machine
needs to be serviced so Anna wants to remove it from the deployment to
avoid causing user visible downtime.' So lets say that: Anna needs to
be able to take machines out of service so they can be maintained or
disposed of.</pre></blockquote>Node being serviced is a different user story for me.<br><div><br></div> I believe we are still 'fighting' here with two approaches and I believe we need both. We can't only provide a way 'give us resources we will do a magic'. Yes this is preferred way - especially for large deployments, but we also need a fallback so that user can say - no, this node doesn't belong to the class, I don't want it there - unassign. Or I need to have this node there - assign.</blockquote><div>Just for clarification - the wireframes don't cover individual nodes being manually assigned, do they? I thought the concession to manual control was entirely through resource classes and node profiles, which are still parameters to be passed through to the nova-scheduler filter. To me, that's very different from manual assignment.<br></div><div><br></div><div>Mainn<br></div><div><br></div></div></body></html>