Amazon EC2: GPU Cluster: Difference between revisions
imported>Ubervert m →Installing CUDA: 'sudo' is redundant when logged in as root (only default login for SUSE) |
No edit summary |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
An '''Amazon EC2: GPU cluster''' is a remote GPU cluster | An '''Amazon EC2: GPU cluster''' is a remote GPU cluster service. | ||
=Creating a new image= | =Creating a new image= | ||
| Line 5: | Line 5: | ||
From this point on, we will deal with a SUSE instance, but the general steps will be the same. '''Only select an instance that can work with CUDA!''' | From this point on, we will deal with a SUSE instance, but the general steps will be the same. '''Only select an instance that can work with CUDA!''' | ||
* With the Classic Wizard, select SUSE Linux Enterprise | * With the Classic Wizard, select Cluster Instances HVM SUSE Linux Enterprise 11 | ||
* Change the Instance Type from | * Change the Instance Type from M3 Extra Large to CG1 Cluster GPU (cg1.4xlarge). | ||
* Enable Termination protection. | * Enable Termination protection. | ||
* Make sure you specify that your Elastic Block Storage volume NOT be destroyed when the instance is terminated (or your data will be lost when the instance is terminated, which may happen without your consent if you are using a spot instance and the variable price exceeds your maximum bid). | * Make sure you specify that your Elastic Block Storage volume NOT be destroyed when the instance is terminated (or your data will be lost when the instance is terminated, which may happen without your consent if you are using a spot instance and the variable price exceeds your maximum bid). | ||