josin/cloud_gunther — Issue #6: Instance_launcher rewrite
Author: vondrt4
Created: 2012-01-19 09:50:08+00:00
State: open

1) If we use :addressing_type => "private", CG must be in the same network as the cloud. Then it won't be able to use multiple cloud engines, unless we use tunnels.
2) Why are we waiting for pending->running transition with exponential back-off and for OS boot with a constant time-out?
3) Why are we connecting with SSH 2 times to each instance?

All those would be solved if first connection went from the instance to CG.

There must be a timeout for that to happen. That will be tracked in scheduler's termination method.
It also must catch errors like direct pending->terminated transitions. (in short: system will track all launched instances)
This kind of errors will cause scheduler to re-launch failed instances. (beware of infinite loops, per-task re-launch quota?)

All instances will be launched at once and instance_service will handle initialization. (no need for threads in instance_launcher)
If the alg_runner reports errors launching algorithm, instance will not re-launch, whole task and all instances may be terminated.