Terminating a cluster on AWS

[Greg]

Is there a way to simply stop the instances as opposed to terminating?

Since it's not currently configured for static IP, i'm afraid if I terminate, the following will be lost:

1: The IP address it's currently sitting on
2: The drop-zone data? Or are these retained in the volume, even after terminated?

Basically, I don't want to have the nodes running unless they're being used (otherwise we're paying for nothing).

Any suggestions?

[bforeman]

Since it's not currently configured for static IP, i'm afraid if I terminate, the following will be lost:

1: The IP address it's currently sitting on
2: The drop-zone data? Or are these retained in the volume, even after terminated?
Any suggestions?

In order to stop paying you have to terminate the cluster, and yes, you lose the IP address and all data on the cluster and drop zone.

What we do in training is to create a snapshot using the EB2 protocol, and then store all of the data to spray on that volume. After we start up the cluster, we attach that EB2 storage snapshot at the initialization phase, and then after the cluster is started we use the Spray library functions to automatically spray any data needed to the newly created cluster.

Regards,

Bob

[Greg]

Thanks Bob.

Is there documentation this by any chance?

Also, do you see any other alternatives to AWS?

[bforeman]

Latest Docs:
http://cdn.hpccsystems.com/releases/CE-Candidate-4.2.0/docs/InstantCloud_for_AWS-4.2.0-1.pdf

The AWS page also has good docs on EC2 and Elastic Block Storage.


Finally, there is our own Cloud service:
http://hpccsystems.com/products-and-services/services/cloud

Regards,

Bob