Great. And, will the ClusterSetup class be extended to have a method "run_incremental_add" (or something with a better name) that's run upon add_node after the default setup ops are called? (Like plugins are now.)<br>
<br>Also: have you guys thought about having a "shutdown" method in the ClusterSetup class, an inverse to the "run" method -- to be run upon call to starcluster stop? E.g. to handle any user-defined shutdown procedures? Presumably it would be run <i>prior</i> to calling the default shutdown process (inverse to the "run" method). And by analogy one could have a "shutdown_incremental_remove" to be run prior to shutdown of an individual node when remove_node is called. <br>
<br>Da<br><br><br><div class="gmail_quote">On Wed, Jul 28, 2010 at 10:51 PM, Rajat Banerjee <span dir="ltr"><<a href="mailto:rqbanerjee@gmail.com">rqbanerjee@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
They will definitely be exposed in the shell (you can use them<br>
already), but we can probably expose them on the command line too.<br>
Justin's choice.<br>
<br>
Raj<br>
<div><div></div><div class="h5"><br>
<br>
On Wed, Jul 28, 2010 at 10:49 PM, Dan Yamins <<a href="mailto:dyamins@gmail.com">dyamins@gmail.com</a>> wrote:<br>
> When the loadbalancer is released, will the underlying "add_node" and<br>
> "remove_node" (whatever they are actually called) be exposed as part of the<br>
> user-facing api? That is, in addition to the loadbalancer function built on<br>
> top of these functions?<br>
><br>
> Dan<br>
><br>
> On Wed, Jul 28, 2010 at 10:46 PM, Rajat Banerjee <<a href="mailto:rbanerj@fas.harvard.edu">rbanerj@fas.harvard.edu</a>><br>
> wrote:<br>
>><br>
>> Hi All,<br>
>> The load balancer has been much improved and several of the bugs I<br>
>> described last time have been fixed. I've just run an elaborate system<br>
>> test on it and haven't seen any issues. I encourage you to try it.<br>
>><br>
>> It will be formally released in a few weeks after Justin releases the<br>
>> main / stable branch. Until then, it is available through GitHub per<br>
>> the instructions in my last email.<br>
>><br>
>> The attatched JPG explains the decision making process of the load<br>
>> balancer.<br>
>><br>
>> <img src="<a href="http://www.hindoogle.com/img/starcluster-decision-diagram.jpg" target="_blank">http://www.hindoogle.com/img/starcluster-decision-diagram.jpg</a>"><br>
>><br>
>> <a href="http://www.hindoogle.com/img/starcluster-decision-diagram.jpg" target="_blank">http://www.hindoogle.com/img/starcluster-decision-diagram.jpg</a><br>
>><br>
>> Thanks,<br>
>> Rajat<br>
>> _______________________________________________<br>
>> Starcluster mailing list<br>
>> <a href="mailto:Starcluster@mit.edu">Starcluster@mit.edu</a><br>
>> <a href="http://mailman.mit.edu/mailman/listinfo/starcluster" target="_blank">http://mailman.mit.edu/mailman/listinfo/starcluster</a><br>
><br>
><br>
> _______________________________________________<br>
> Starcluster mailing list<br>
> <a href="mailto:Starcluster@mit.edu">Starcluster@mit.edu</a><br>
> <a href="http://mailman.mit.edu/mailman/listinfo/starcluster" target="_blank">http://mailman.mit.edu/mailman/listinfo/starcluster</a><br>
><br>
><br>
<br>
</div></div></blockquote></div><br>