Re-enable cloud 'bursting'

[GoogleCodeExporter]

This is becoming fairly urgent as several of our users are struggling with lack 
of resources (Radu, Joel, Vanessa, the FGCZ guys)

source of the issue is that the LRMSError raised by ec2 backend is not 
intercepted by the engine/core

while checking this, Antonio and Sergio realized that there is no coherence on 
the LRMSError raised by the various LRMS backends.

So, first thing first:
1. Check all the LRMSError raised by LRMS and find an agreement on each case
2. Intercept the LRMSError properly in engine/core 

S.

Original issue reported on code.google.com by sergio.m...@gmail.com on 3 Oct 2013 at 10:08

[GoogleCodeExporter]

Original comment by riccardo.murri@gmail.com on 9 Oct 2013 at 12:05

[GoogleCodeExporter]

I think that SVN r3739 might have fixed this, restoring the behavior that we 
had before the new scheduler  was introduced.

Can you please check this?

Original comment by riccardo.murri@gmail.com on 22 Oct 2013 at 8:52

[GoogleCodeExporter]

Can you please check again with SVN r3742 ?

Original comment by riccardo.murri@gmail.com on 22 Oct 2013 at 10:51

[GoogleCodeExporter]

Fixed in SVN r3745.

Original comment by riccardo.murri@gmail.com on 22 Oct 2013 at 12:17

[GoogleCodeExporter]

Original comment by riccardo.murri@gmail.com on 22 Oct 2013 at 12:17

• Changed state: Fixed