Migrate to softlayer_api 2.2.0+ in order to expose SL api timeout for end user #23
Conversation
ju2wheels
commented
Aug 6, 2014
ju2wheels
commented
- Should resolve all issues/feature requests in Enable parallel provisioning #16
- sl_warden may need some review in terms of Exception handling (api migrated to stock Ruby exceptions)
|
+1 to approve. Related to this, @ju2wheels what is the average time you see for SL to complete provisioning of an instance once the post_install script concludes? I am hitting the 20 minute timeout in the SL provider code but I see at the SL dashboard that SL is moving the instance through power down, power on, network setup and reboot. Typically, the timeout fires during the reboot phase. Optimistically to this biased script hacker, it looks like my post_install stuff is ok and it is just SL that is taking a very long time to bring up the provisioned instance. Do you agree or is it more likely that my shutdown request is getting hung up? |
|
|
Hi guys, I can't wait for this pull request to be merged :) I am still hitting timeout errors from time to time and hope that they will be resolved in this new version. |
ju2wheels
force-pushed
the
develop
branch
2 times, most recently
from
2891225
to
d8094b8
Compare
…r API timeout, bump softlayer_api required version to 2.2.0 or newer
…en as its no longer used in softlayer_api 2.x branch
…ted on and add transaction status to debug logging
ju2wheels
force-pushed
the
sl_api_2x_migrate
branch
from
5e4111c
to
1c15a28
Compare
Migrate to softlayer_api 2.2.0+ in order to expose SL api timeout for end user
