Unfortunately not. When removing nodes, CloudMan chooses from the nodes that are currently not being used but among those the choice is random. <div>You can manually terminate a particular worker instance from the AWS console and thus remove it from your cluster by force. CloudMan will then reconfigure the cluster. Although this has been implemented and tested, it is not really the recommended behavior, especially not repeatedly. </div>

<div><br></div><div>I&#39;ll look into how to implement this option. </div><div>Enis</div><div><br><div class="gmail_quote">On Thu, Dec 1, 2011 at 6:20 AM, Clare Sloggett <span dir="ltr">&lt;<a href="mailto:sloc@unimelb.edu.au">sloc@unimelb.edu.au</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi galaxy-devs,<br>
<br>
Quick question: when using the cloud console on CloudMan, it&#39;s<br>
possible to add different types of nodes (large, micro, etc) to the<br>
virtual cluster using the &#39;Add Nodes&#39; option at the top. I can also<br>
remove a given number of nodes using the &#39;Remove Nodes&#39; option at the<br>
top. However, is there any way to control exactly which node (or more<br>
importantly just which type of node) gets removed?<br>
<br>
Thanks for any help!<br>
<br>
Clare<br>
<font color="#888888"><br>
--<br>
E: <a href="mailto:sloc@unimelb.edu.au">sloc@unimelb.edu.au</a><br>
P: 03 903 53357<br>
M: 0414 854 759<br>
___________________________________________________________<br>
Please keep all replies on the list by using &quot;reply all&quot;<br>
in your mail client.  To manage your subscriptions to this<br>
and other Galaxy lists, please use the interface at:<br>
<br>
  <a href="http://lists.bx.psu.edu/" target="_blank">http://lists.bx.psu.edu/</a><br>
</font></blockquote></div><br></div>