Guy Tel-Zur's Blog

I tested globus-provision which is an easy way to have a globus+condor cluster ready for number crunching on Amazon’s EC2 cloud. My front end was my laptop which runs Windows. Python on Windows does not behave exactly as on Linux when it comes to SIGINT and therefore os.fork() generated an error message. Thanks to the support of  Borja Sotomayor the SIGINT issues has resolved and the solution was to by-pass the SIGINT so I could proceed with the test. You can read more about this issue from here: http://jira.globus.org/browse/GP-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel I tried the example from: http://globus.org/provision/guide_compute_go.html#guide-compute-go I decided not to use globusonline for the eBooks transfer and I used wget instead. Below are a few screen captures that show the test. My configuration file:  Preparing the instance: after a minute or two: checking the instance: Watching my cluster at the AWS management ...

    When introducing Cloud Computing (CC) people usually like to emphasize the similarities between Electric Power Grids (EPG) and CC.     These analogies include: On demand service, Pay-Per-Use (PPU) model, the Elasticity of the resources, load balancing and even water cooling,     After the Amazon EC2 service disruption on April 21 st , 2011, we can identify more similarities between EPG and CC in disasters related issues. These similarities include: 1. A global damage (with immediate and delayed components). 2. Uncontrolled behavior of the resources (neutron population vs. loss of connectivity or fuel rods meltdown vs. failing servers). 3. During the crisis, similar announcements to the public which minimize the catastrophe. 4. After the crisis, publication of the event investigation in length. 5. Loss of confidence in the technology by the users.