https://sourceforge.net/p/kluster/wiki/CreatingInstance/Recent changes to CreatingInstanceenFri, 05 Jun 2015 01:32:24 -0000https://sourceforge.net/p/kluster/wiki/CreatingInstance/<div class="markdown_content"><pre>--- v15 +++ v16 @@ -42,7 +42,7 @@ &lt;snip&gt; admin@domU-12-31-39-04-30-B3:~# -In order to get a prompt as root you can now do: +Note that you have to ssh into the machine as admin at first, as root access through ssh is initially disabled. In order to get a prompt as root you can now do: # sudo bash </pre> </div>Carl PupaFri, 05 Jun 2015 01:32:24 -0000https://sourceforge.nete0889e4d75d2692c004eb8871a863e6867c3aadahttps://sourceforge.net/p/kluster/wiki/CreatingInstance/<div class="markdown_content"><pre>--- v14 +++ v15 @@ -2,11 +2,11 @@ We have chosen to base these instructions on Debian Linux. Running on a Red Hat distribution or Amazon's equivalents is probably easy too, but our scripts would not work as written. -The first step is to choose a suitable "image" to customize. At this point you probably should also choose an "availability zone" (read: data center) to run in, since the images are specific to different availability zones. I chose us-east-1c. I chose a Debian image from this [list of Debian images](http://wiki.debian.org/Cloud/AmazonEC2Image); I chose the image `ami-e00df089`. There was nothing very special about this image, but it had a couple of features: +The first step is to choose a suitable "image" to customize. At this point you probably should also choose an "availability zone" (read: data center) to run in, since the images are specific to different availability zones. I chose us-east-1c. I chose a Debian image from this [list of Debian images](http://wiki.debian.org/Cloud/AmazonEC2Image); I chose the image `ami-e0efab88`. There was nothing very special about this image, but it had a couple of features: * It is a 64 bit, not 32 bit, image. * It is "ebs-backed", not "instance-store backed". - * At the time of writing (Oct 6, 2013) it was the latest version of Debian Linux they had. + * At the time of writing (Jun 4, 2015) it was the latest Debian version providing gridengine EBS-backed means that you can stop and start the image and it won't lose the data; this is generally more convenient. Now, if you want to follow these instructions exactly you should choose exactly this image, because this recipe might not work for other images. @@ -17,30 +17,30 @@ To create your instance, do as follows: - ec2-run-instances ami-e00df089 -g mycluster -k mycluster -z us-east-1c -t c3.large + ec2-run-instances ami-e0efab88 -g mycluster -k mycluster -z us-east-1c -t c3.large The option `-g mycluster` puts the new instance in the security group "mycluster". The option "-k mycluster" means that it will use the keypair called "mycluster" (this is a separate type of object to which we assigned the same name). The -z option specifies the "availability zone" (presumably, data-center), and `-t c3.large` specifies the type of machine ("instance type"). The output should look like this: - # ec2-run-instances ami-e00df089 -g mycluster -k mycluster -z us-east-1c -t c3.large + # ec2-run-instances ami-e0efab88 -g mycluster -k mycluster -z us-east-1c -t c3.large RESERVATION r-9aa24ae7 167806836050 mycluster - INSTANCE i-7877a019 ami-e00df089 pending mycluster 0 c3.large 2013-03-21T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled ebs paravirtual xen sg-3decf455 default false + INSTANCE i-7877a019 ami-e0efab88 pending mycluster 0 c3.large 2015-06-04T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled ebs hvm xen sg-3decf455 default false The output tells you various things about the instance you just launched. The format is easily parse-able by a script. The fields can best be extracted by e.g. `cut -f 2` because they are tab-separated. Copy and paste the instance-id; in this case, it is i-7877a019. Then use the command `ec2din i-7877a019` to get the information again: # ec2din i-7877a019 RESERVATION r-9aa24ae7 167806836050 mycluster - INSTANCE i-7877a019 ami-e00df089 ec2-54-235-5-54.compute-1.amazonaws.com domU-12-31-39-04-30-B3.compute-1.internal running mycluster 0 c3.large 2013-03-21T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled 54.235.5.54 10.240.55.65 ebs paravirtual xen sg-3decf455 default false - BLOCKDEVICE /dev/sda vol-51ca3b22 2013-03-21T20:08:03.000Z true + INSTANCE i-7877a019 ami-e0efab88 ec2-54-235-5-54.compute-1.amazonaws.com domU-12-31-39-04-30-B3.compute-1.internal running mycluster 0 c3.large 2015-06-04T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled 54.235.5.54 10.240.55.65 ebs hvm xen sg-3decf455 default false + BLOCKDEVICE /dev/sda vol-51ca3b22 2015-06-04T20:08:03.000Z true Assuming you waited a few seconds for the instance to be assigned an address, the output should look like the above. Copy the address (`ec2-54-235-5-54.compute-1.amazonaws.com` in this case) and ssh to it as follows (you may have to wait a minute before it is ready): - # ssh -i ~/.ssh/mycluster.pem root@ec2-54-235-5-54.compute-1.amazonaws.com + # ssh -i ~/.ssh/mycluster.pem admin@ec2-54-235-5-54.compute-1.amazonaws.com The authenticity of host 'ec2-54-235-5-54.compute-1.amazonaws.com (54.235.5.54)' can't be established. RSA key fingerprint is d5:50:bd:8e:23:eb:14:3f:cf:15:87:42:0b:bf:e2:60. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'ec2-54-235-5-54.compute-1.amazonaws.com,54.235.5.54' (RSA) to the list of known hosts. &lt;snip&gt; - root@domU-12-31-39-04-30-B3:~# + admin@domU-12-31-39-04-30-B3:~# In order to get a prompt as root you can now do: </pre> </div>Carl PupaFri, 05 Jun 2015 01:30:37 -0000https://sourceforge.netf752d866799d3fd8cdccd9f9dbb92bfef82b0d4bhttps://sourceforge.net/p/kluster/wiki/CreatingInstance/<div class="markdown_content"><pre>--- v13 +++ v14 @@ -17,30 +17,30 @@ To create your instance, do as follows: - ec2-run-instances ami-e00df089 -g mycluster -k mycluster -z us-east-1c -t m1.large + ec2-run-instances ami-e00df089 -g mycluster -k mycluster -z us-east-1c -t c3.large -The option `-g mycluster` puts the new instance in the security group "mycluster". The option "-k mycluster" means that it will use the keypair called "mycluster" (this is a separate type of object to which we assigned the same name). The -z option specifies the "availability zone" (presumably, data-center), and `-t m1.large` specifies the type of machine ("instance type"). The output should look like this: +The option `-g mycluster` puts the new instance in the security group "mycluster". The option "-k mycluster" means that it will use the keypair called "mycluster" (this is a separate type of object to which we assigned the same name). The -z option specifies the "availability zone" (presumably, data-center), and `-t c3.large` specifies the type of machine ("instance type"). The output should look like this: - # ec2-run-instances ami-e00df089 -g mycluster -k mycluster -z us-east-1c -t m1.large + # ec2-run-instances ami-e00df089 -g mycluster -k mycluster -z us-east-1c -t c3.large RESERVATION r-9aa24ae7 167806836050 mycluster - INSTANCE i-7877a019 ami-e00df089 pending mycluster 0 m1.large 2013-03-21T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled ebs paravirtual xen sg-3decf455 default false + INSTANCE i-7877a019 ami-e00df089 pending mycluster 0 c3.large 2013-03-21T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled ebs paravirtual xen sg-3decf455 default false The output tells you various things about the instance you just launched. The format is easily parse-able by a script. The fields can best be extracted by e.g. `cut -f 2` because they are tab-separated. Copy and paste the instance-id; in this case, it is i-7877a019. Then use the command `ec2din i-7877a019` to get the information again: # ec2din i-7877a019 RESERVATION r-9aa24ae7 167806836050 mycluster - INSTANCE i-7877a019 ami-e00df089 ec2-54-235-5-54.compute-1.amazonaws.com domU-12-31-39-04-30-B3.compute-1.internal running mycluster 0 m1.large 2013-03-21T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled 54.235.5.54 10.240.55.65 ebs paravirtual xen sg-3decf455 default false + INSTANCE i-7877a019 ami-e00df089 ec2-54-235-5-54.compute-1.amazonaws.com domU-12-31-39-04-30-B3.compute-1.internal running mycluster 0 c3.large 2013-03-21T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled 54.235.5.54 10.240.55.65 ebs paravirtual xen sg-3decf455 default false BLOCKDEVICE /dev/sda vol-51ca3b22 2013-03-21T20:08:03.000Z true Assuming you waited a few seconds for the instance to be assigned an address, the output should look like the above. Copy the address (`ec2-54-235-5-54.compute-1.amazonaws.com` in this case) and ssh to it as follows (you may have to wait a minute before it is ready): - # ssh -i ~/.ssh/mycluster.pem admin@ec2-54-235-5-54.compute-1.amazonaws.com + # ssh -i ~/.ssh/mycluster.pem root@ec2-54-235-5-54.compute-1.amazonaws.com The authenticity of host 'ec2-54-235-5-54.compute-1.amazonaws.com (54.235.5.54)' can't be established. RSA key fingerprint is d5:50:bd:8e:23:eb:14:3f:cf:15:87:42:0b:bf:e2:60. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'ec2-54-235-5-54.compute-1.amazonaws.com,54.235.5.54' (RSA) to the list of known hosts. &lt;snip&gt; - admin@domU-12-31-39-04-30-B3:~# + root@domU-12-31-39-04-30-B3:~# In order to get a prompt as root you can now do: </pre> </div>Tal WeissTue, 23 Sep 2014 13:45:19 -0000https://sourceforge.netfcf37bcdfa1b449e5d3150e92c58103323eb4feahttps://sourceforge.net/p/kluster/wiki/CreatingInstance/<div class="markdown_content"><pre>--- v12 +++ v13 @@ -2,7 +2,7 @@ We have chosen to base these instructions on Debian Linux. Running on a Red Hat distribution or Amazon's equivalents is probably easy too, but our scripts would not work as written. -The first step is to choose a suitable "image" to customize. At this point you probably should also choose an "availability zone" (read: data center) to run in, since the images are specific to different availability zones. I chose us-east-1c. I chose a Debian image from this [list of Debian images](http://wiki.debian.org/Cloud/AmazonEC2Image); I chose the image `ami-9e95e8f7`. There was nothing very special about this image, but it had a couple of features: +The first step is to choose a suitable "image" to customize. At this point you probably should also choose an "availability zone" (read: data center) to run in, since the images are specific to different availability zones. I chose us-east-1c. I chose a Debian image from this [list of Debian images](http://wiki.debian.org/Cloud/AmazonEC2Image); I chose the image `ami-e00df089`. There was nothing very special about this image, but it had a couple of features: * It is a 64 bit, not 32 bit, image. * It is "ebs-backed", not "instance-store backed". @@ -17,7 +17,7 @@ To create your instance, do as follows: - ec2-run-instances ami-9e95e8f7 -g mycluster -k mycluster -z us-east-1c -t m1.large + ec2-run-instances ami-e00df089 -g mycluster -k mycluster -z us-east-1c -t m1.large The option `-g mycluster` puts the new instance in the security group "mycluster". The option "-k mycluster" means that it will use the keypair called "mycluster" (this is a separate type of object to which we assigned the same name). The -z option specifies the "availability zone" (presumably, data-center), and `-t m1.large` specifies the type of machine ("instance type"). The output should look like this: @@ -29,7 +29,7 @@ # ec2din i-7877a019 RESERVATION r-9aa24ae7 167806836050 mycluster - INSTANCE i-7877a019 ami-9e95e8f7 ec2-54-235-5-54.compute-1.amazonaws.com domU-12-31-39-04-30-B3.compute-1.internal running mycluster 0 m1.large 2013-03-21T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled 54.235.5.54 10.240.55.65 ebs paravirtual xen sg-3decf455 default false + INSTANCE i-7877a019 ami-e00df089 ec2-54-235-5-54.compute-1.amazonaws.com domU-12-31-39-04-30-B3.compute-1.internal running mycluster 0 m1.large 2013-03-21T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled 54.235.5.54 10.240.55.65 ebs paravirtual xen sg-3decf455 default false BLOCKDEVICE /dev/sda vol-51ca3b22 2013-03-21T20:08:03.000Z true Assuming you waited a few seconds for the instance to be assigned an address, the output should look like the above. Copy the address (`ec2-54-235-5-54.compute-1.amazonaws.com` in this case) and ssh to it as follows (you may have to wait a minute before it is ready): </pre> </div>Tal WeissTue, 23 Sep 2014 13:42:38 -0000https://sourceforge.neta29ebf016ac5e545f7c2bbd4bed9913c14fd6df9https://sourceforge.net/p/kluster/wiki/CreatingInstance/<div class="markdown_content"><p>Log in as "admin@" was denied. Log in as "root@" was successful. Looking at "/etc/passwd" shows there is no admin on this instance.</p></div>Tal WeissThu, 18 Sep 2014 06:46:59 -0000https://sourceforge.net927896726b48e127f5107671c7f2cab7e9cd7ca9https://sourceforge.net/p/kluster/wiki/CreatingInstance/<div class="markdown_content"><p>"m1.large" is a bad choice. It is old, which means less powerful and more expensive than newer types!</p></div>Tal WeissThu, 18 Sep 2014 06:29:46 -0000https://sourceforge.net359ee7d950a10d839aa63eda2e8029c995696e46https://sourceforge.net/p/kluster/wiki/CreatingInstance/<div class="markdown_content"><p>"ami-9e95e8f7" doesn't exist. In parts of this page you used "ami-e00df089" which works.</p></div>Tal WeissThu, 18 Sep 2014 06:23:06 -0000https://sourceforge.net94ed6c1648ffd40d58d4318cccc9b3286c45c739https://sourceforge.net/p/kluster/wiki/CreatingInstance/<div class="markdown_content"><pre>--- v11 +++ v12 @@ -2,10 +2,11 @@ We have chosen to base these instructions on Debian Linux. Running on a Red Hat distribution or Amazon's equivalents is probably easy too, but our scripts would not work as written. -The first step is to choose a suitable "image" to customize. At this point you probably should also choose an "availability zone" (read: data center) to run in, since the images are specific to different availability zones. I chose us-east-1c. I chose a Debian image from this [list of Debian images](http://wiki.debian.org/Cloud/AmazonEC2Image); I chose the image `ami-e00df089`. There was nothing very special about this image, but it had a couple of features: +The first step is to choose a suitable "image" to customize. At this point you probably should also choose an "availability zone" (read: data center) to run in, since the images are specific to different availability zones. I chose us-east-1c. I chose a Debian image from this [list of Debian images](http://wiki.debian.org/Cloud/AmazonEC2Image); I chose the image `ami-9e95e8f7`. There was nothing very special about this image, but it had a couple of features: * It is a 64 bit, not 32 bit, image. * It is "ebs-backed", not "instance-store backed". + * At the time of writing (Oct 6, 2013) it was the latest version of Debian Linux they had. EBS-backed means that you can stop and start the image and it won't lose the data; this is generally more convenient. Now, if you want to follow these instructions exactly you should choose exactly this image, because this recipe might not work for other images. @@ -16,7 +17,7 @@ To create your instance, do as follows: - ec2-run-instances ami-e00df089 -g mycluster -k mycluster -z us-east-1c -t m1.large + ec2-run-instances ami-9e95e8f7 -g mycluster -k mycluster -z us-east-1c -t m1.large The option `-g mycluster` puts the new instance in the security group "mycluster". The option "-k mycluster" means that it will use the keypair called "mycluster" (this is a separate type of object to which we assigned the same name). The -z option specifies the "availability zone" (presumably, data-center), and `-t m1.large` specifies the type of machine ("instance type"). The output should look like this: @@ -28,7 +29,7 @@ # ec2din i-7877a019 RESERVATION r-9aa24ae7 167806836050 mycluster - INSTANCE i-7877a019 ami-e00df089 ec2-54-235-5-54.compute-1.amazonaws.com domU-12-31-39-04-30-B3.compute-1.internal running mycluster 0 m1.large 2013-03-21T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled 54.235.5.54 10.240.55.65 ebs paravirtual xen sg-3decf455 default false + INSTANCE i-7877a019 ami-9e95e8f7 ec2-54-235-5-54.compute-1.amazonaws.com domU-12-31-39-04-30-B3.compute-1.internal running mycluster 0 m1.large 2013-03-21T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled 54.235.5.54 10.240.55.65 ebs paravirtual xen sg-3decf455 default false BLOCKDEVICE /dev/sda vol-51ca3b22 2013-03-21T20:08:03.000Z true Assuming you waited a few seconds for the instance to be assigned an address, the output should look like the above. Copy the address (`ec2-54-235-5-54.compute-1.amazonaws.com` in this case) and ssh to it as follows (you may have to wait a minute before it is ready): </pre> </div>Daniel PoveyMon, 07 Oct 2013 00:12:11 -0000https://sourceforge.net4d8bd65208cf07c55f778cb57bf271e836226658https://sourceforge.net/p/kluster/wiki/CreatingInstance/<div class="markdown_content"><pre>--- v10 +++ v11 @@ -33,13 +33,17 @@ Assuming you waited a few seconds for the instance to be assigned an address, the output should look like the above. Copy the address (`ec2-54-235-5-54.compute-1.amazonaws.com` in this case) and ssh to it as follows (you may have to wait a minute before it is ready): - # ssh -i ~/.ssh/mycluster.pem root@ec2-54-235-5-54.compute-1.amazonaws.com + # ssh -i ~/.ssh/mycluster.pem admin@ec2-54-235-5-54.compute-1.amazonaws.com The authenticity of host 'ec2-54-235-5-54.compute-1.amazonaws.com (54.235.5.54)' can't be established. RSA key fingerprint is d5:50:bd:8e:23:eb:14:3f:cf:15:87:42:0b:bf:e2:60. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'ec2-54-235-5-54.compute-1.amazonaws.com,54.235.5.54' (RSA) to the list of known hosts. - root@domU-12-31-39-04-30-B3:~# + admin@domU-12-31-39-04-30-B3:~# + +In order to get a prompt as root you can now do: + + # sudo bash If you don't like having to type "yes" at this point, you can set the following at the top of your file ~/.ssh/config on your local machine (create the file if it doesn't exist): </pre> </div>Daniel PoveyMon, 07 Oct 2013 00:10:52 -0000https://sourceforge.netc477e849991af389c4031f5f01bf38196568b6b7https://sourceforge.net/p/kluster/wiki/CreatingInstance/<div class="markdown_content"><pre>--- v9 +++ v10 @@ -31,7 +31,7 @@ INSTANCE i-7877a019 ami-e00df089 ec2-54-235-5-54.compute-1.amazonaws.com domU-12-31-39-04-30-B3.compute-1.internal running mycluster 0 m1.large 2013-03-21T20:07:58+0000 us-east-1c aki-4e7d9527 monitoring-disabled 54.235.5.54 10.240.55.65 ebs paravirtual xen sg-3decf455 default false BLOCKDEVICE /dev/sda vol-51ca3b22 2013-03-21T20:08:03.000Z true -Assuming you waited a few seconds for the instance to be assigned an address, the output should look like the above. Copy the address (`ec2-54-235-5-54.compute-1.amazonaws.com` in this case) and ssh to it as follows: +Assuming you waited a few seconds for the instance to be assigned an address, the output should look like the above. Copy the address (`ec2-54-235-5-54.compute-1.amazonaws.com` in this case) and ssh to it as follows (you may have to wait a minute before it is ready): # ssh -i ~/.ssh/mycluster.pem root@ec2-54-235-5-54.compute-1.amazonaws.com The authenticity of host 'ec2-54-235-5-54.compute-1.amazonaws.com (54.235.5.54)' can't be established. @@ -54,5 +54,6 @@ ec2tag i-7877a019 --tag Name=customize_phase_1 +Previous: [Creating a key-pair](CreatingKeyPair) Next: [Customizing your Image (Phase 1)](CustomizingImage1) Up: [Kluster Wiki](Home) </pre> </div>Daniel PoveyMon, 25 Mar 2013 00:56:52 -0000https://sourceforge.net131890895f04577521ec3c282e683cdba400b253