Virtual machine - made cloud computing possible
Harvard class: http://cm.dce.harvard.edu/2010/01/13450/L07/seg1/index_FlashSingleHighBandwidth.html

VM types:

• Xen -free
• VMware - commercial, used by industry, full virtualization
• Parallels - tailored for Mac users

Amazon uses Xen, will be used by this class

Hyperviser - VM 0-layer

'Amazon web services'
single Front: multiple back ends machines doing the work

Jargon:

• AMI - Amazon Machine Image , it is a file on a disk
• Instance - IMA executed to become a machine
• EBS Volume- elastic block store volume, secondary storage allocated elsewhere

Various types of AMI, we will use Fedora - a version of Red Hat Linux

On-Demand Instances:

• c1. small, $0.10 per hour
• c1.medium , 2 virtual cores
• c1.xLarge, 8 virtual cores, $0.80 per hours

All resources are described at http://cs50.net/wiki/CS_264

Private cloud computing: http://aws.amazon.com/

And this is my 1st VM on the claud

Steps to fire VM & ssh to it (after you set up all credentials)

1. login to AWS page
2. select: Amazon Elastic Compute Cloud
3. TOP-UP: 'Your Account' , select 'AWS Management Console'
4. TOP-UP-Yellow: 'Sign in to AWS console'
5. 'Lunch Instances'
6. select type of VM (e.g. Fedora for regular linux), press select
7. in lunch wizard 'Skip this'
8. select # of machines & CPU power (star with 1, small)
9. in 'Key Pair Name' select ssh Keys you have created earlier
10. if you want output to survive after VM is shut down in options select: Availability Zone & remember it
11. press 'Lunch' at the bottom
    Now find it , it is beta-version, pressing 'Refresh' screen in the browser may help
12. to ssh to this machine you need to know:
    • Public DNS, sth like: ec2-75-101-246-229.compute-1.amazonaws.com
    • absolute path to your ssh keys, e.g. janAmazonKey.pem
13. from the local prompt execute:
    ssh -i janAmazonKey.pem root@ec2-75-101-246-229.compute-1.amazonaws.com

If ssh hangs forever, you need to open fire wall.

1. On the left, go to 'Security Groups'
2. select 'default' fire wall (unless you have sth else already)
3. add & save : SSH tcp 22 22 0.0.0.0
4. now try ssh again