about using the cg1.4xlarge or cc1.4xlarge instances

From: Moussa Taifi <no email>
Date: Mon, 29 Nov 2010 13:29:51 -0500

Hello,

I am kind of new to this.

I was trying to use the starcluster with the new cg1.4xlarge instances but I
found out that the images that are provided as example (ami-a5c42dcc and
ami-d1c42db8) are both paravirtual while the cluster instances require hvm,
hardware virtualization. not that I understand fully all this yet but is
there anyone that had this problem? and is there an ami available to use for
the cluster instances that is at the same time configured like the available
amis?

Thank you,

Moussa

On Sat, Nov 27, 2010 at 12:21 PM, <starcluster-request_at_mit.edu> wrote:

> Send StarCluster mailing list submissions to
> starcluster_at_mit.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.mit.edu/mailman/listinfo/starcluster
> or, via email, send a message with subject or body 'help' to
> starcluster-request_at_mit.edu
>
> You can reach the person managing the list at
> starcluster-owner_at_mit.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of StarCluster digest..."
>
>
> Today's Topics:
>
> 1. access cluster object from plugin (Dan Yamins)
> 2. Re: access cluster object from plugin (Justin Riley)
> 3. Re: access cluster object from plugin (Dan Yamins)
> 4. Re: access cluster object from plugin (Justin Riley)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 26 Nov 2010 18:19:51 -0500
> From: Dan Yamins <dyamins_at_gmail.com>
> Subject: [StarCluster] access cluster object from plugin
> To: starcluster <starcluster_at_mit.edu>
> Message-ID:
> <AANLkTimC6Ox57-Pq+_FgGpaQyOary50MW4H7Fi_TDCSp_at_mail.gmail.com<AANLkTimC6Ox57-Pq%2B_FgGpaQyOary50MW4H7Fi_TDCSp_at_mail.gmail.com>
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Justin:
>
> Is there any way to access to the cluster object (and in particular the
> cluster object's .ec2 attribute) from within the plugin?
>
> What I want to be able to do is modify the cluster permissions (e.g. to
> open
> a specific port) in the plugin logic ... I could do it via boto with the
> cluster.ec2 object if that object is available ... or what is the right
> way?
>
> Dan
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/starcluster/attachments/20101126/c15fd033/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Fri, 26 Nov 2010 18:27:14 -0500
> From: Justin Riley <jtriley_at_MIT.EDU>
> Subject: Re: [StarCluster] access cluster object from plugin
> To: starcluster_at_MIT.EDU
> Message-ID: <4CF04252.9040304_at_mit.edu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 11/26/10 6:19 PM, Dan Yamins wrote:
> > Is there any way to access to the cluster object (and in particular
> > the cluster object's .ec2 attribute) from within the plugin?
> >
> > What I want to be able to do is modify the cluster permissions (e.g.
> > to open a specific port) in the plugin logic ... I could do it via
> > boto with the cluster.ec2 object if that object is available ... or
> > what is the right way?
>
> Assuming you're using the latest github code, each Node instance now has
> an 'ec2' attribute the same as the Cluster class. So you could use
> master.ec2.* in a plugin.
>
> ~Justin
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 26 Nov 2010 18:30:28 -0500
> From: Dan Yamins <dyamins_at_gmail.com>
> Subject: Re: [StarCluster] access cluster object from plugin
> To: starcluster_at_mit.edu
> Message-ID:
> <AANLkTin8698PjstJS7iLi-Zg4=64aT65zAyUPDB1v232_at_mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Great thanks.
>
> Hope you (and all on this list) had a great Thanksgiving!
>
> Dan
>
> On Fri, Nov 26, 2010 at 6:27 PM, Justin Riley <jtriley_at_mit.edu> wrote:
>
> > On 11/26/10 6:19 PM, Dan Yamins wrote:
> > > Is there any way to access to the cluster object (and in particular
> > > the cluster object's .ec2 attribute) from within the plugin?
> > >
> > > What I want to be able to do is modify the cluster permissions (e.g.
> > > to open a specific port) in the plugin logic ... I could do it via
> > > boto with the cluster.ec2 object if that object is available ... or
> > > what is the right way?
> >
> > Assuming you're using the latest github code, each Node instance now has
> > an 'ec2' attribute the same as the Cluster class. So you could use
> > master.ec2.* in a plugin.
> >
> > ~Justin
> > _______________________________________________
> > StarCluster mailing list
> > StarCluster_at_mit.edu
> > http://mailman.mit.edu/mailman/listinfo/starcluster
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/starcluster/attachments/20101126/a30a27fc/attachment-0001.htm
>
> ------------------------------
>
> Message: 4
> Date: Fri, 26 Nov 2010 18:32:02 -0500
> From: Justin Riley <jtriley_at_MIT.EDU>
> Subject: Re: [StarCluster] access cluster object from plugin
> To: starcluster_at_MIT.EDU
> Message-ID: <4CF04372.3040106_at_mit.edu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 11/26/10 6:19 PM, Dan Yamins wrote:
> >
> > What I want to be able to do is modify the cluster permissions (e.g.
> > to open a specific port) in the plugin logic ... I could do it via
> > boto with the cluster.ec2 object if that object is available ... or
> > what is the right way?
> I assume you don't know the permissions you need before runtime and this
> is why you're needing to modify security group permission settings in a
> plugin. Just as a reminder, if you *do* know the permissions you can use
> the new [permission] config settings.
>
> ~Justin
>
>
> ------------------------------
>
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
>
>
> End of StarCluster Digest, Vol 15, Issue 10
> *******************************************
>
Received on Mon Nov 29 2010 - 13:29:52 EST