Great thanks.<div><br></div><div>Hope you (and all on this list) had a great Thanksgiving!</div><div><br></div><div>Dan<br><br><div class="gmail_quote">On Fri, Nov 26, 2010 at 6:27 PM, Justin Riley <span dir="ltr"><<a href="mailto:jtriley@mit.edu">jtriley@mit.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div></div><div class="h5">On 11/26/10 6:19 PM, Dan Yamins wrote:<br>
> Is there any way to access to the cluster object (and in particular<br>
> the cluster object's .ec2 attribute) from within the plugin?<br>
><br>
> What I want to be able to do is modify the cluster permissions (e.g.<br>
> to open a specific port) in the plugin logic ... I could do it via<br>
> boto with the cluster.ec2 object if that object is available ... or<br>
> what is the right way?<br>
<br>
</div></div>Assuming you're using the latest github code, each Node instance now has<br>
an 'ec2' attribute the same as the Cluster class. So you could use<br>
master.ec2.* in a plugin.<br>
<br>
~Justin<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>
</blockquote></div><br></div>