Question: Cloudman instance type support
0
gravatar for johnbot1
3.7 years ago by
johnbot10
United States
johnbot10 wrote:

Hi,

I've just started digging into cloudman but noticed it doesn't appear to support any of the modern AWS instance types. Perhaps I missed something. Are there plans to introduce C3,M3 and R3 instances in the near future?

Thanks,

John

 

aws cloudman ec2 • 649 views
ADD COMMENTlink modified 3.7 years ago by Dannon Baker3.7k • written 3.7 years ago by johnbot10
1
gravatar for Dannon Baker
3.7 years ago by
Dannon Baker3.7k
United States
Dannon Baker3.7k wrote:

Hey John,

Sure, those should work fine right out of the box as far as I know -- the types listed in the cloudlaunch dropdown are just what we found to work well for most use-cases in an attempt to avoid overwhelming users with options there.  That list was put together a long time ago, though, and definitely needs to be updated.  I'll add it to my list.

You can still launch an instance the manual way through the AWS console and select whatever instance type you'd like, or, I just used cloudlaunch and edited the form's html prior to submitting (just add a new option to the select for c3.large, for instance) and I have a C3 instance that came up fine.

-Dannon

ADD COMMENTlink written 3.7 years ago by Dannon Baker3.7k

Thanks Dannon,

I'll try running with some of the new C and R instances now that I know how. I also wanted to ask how one would go about launching cloudman in regions other than us-east and if there's a way to launch cloudman without handing over IAM credentials to the ?  I *think* the AMI is only available in us-east so I'd imagine I'd have to launch in us-east-1 then make an AMI to migrate to us-west-2. Thoughts? 

 

Thanks,

John

ADD REPLYlink written 3.7 years ago by johnbot10

That's correct, you'd have to migrate the AMI and associated volumes, and configure a separate bucket to indicate the correct ids in us-west-2.  We don't currently do this because of the additional cost of mirroring (and somewhat limited benefit).

I'd love to be able to get away with not actually passing AWS creds to the application.  Basically, the remote application needs to be able to act on your behalf to spin up other instances and provision volumes and the like, and without creds that sort of direct action on a user's behalf is not possible (unless something has changed recently that I'm not aware of).

 

That said, there *are* ways around this (I think, with a redesign of the main architecture) that we hope to address in future work using new AWS features that didn't exist when Cloudman was designed, but currently, we're more or less stuck with it.

ADD REPLYlink modified 3.7 years ago • written 3.7 years ago by Dannon Baker3.7k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 102 users visited in the last hour