Merge pull request #1471 from remibergsma/47_lower_interface_wait

Lower the time we wait for interfaces to appearWaiting for interfaces is 
tricky. They might never appear.. for example when we have entries in 
`/etc/cloudstack/ips.json` that haven't been plugged yet. Waiting this long 
makes everything horribly slow (every vm, interface, static route, etc, etc, 
will hit this wait, for every device). We've seen CloudStack send an 
`ip_assoc.json` command for `eth1` public nic only and then the router goes 
crazy waiting for all other interfaces that were there before reboot and aren't 
there. If only the router would return to the mgt server a success of `eth1`, 
it would get the command for `eth2` etc etc. Obviously, a destroy works much 
faster because no state services, so no knowledge of previous devices so no 
waits :-)

After a stop/start the router has state in `/etc/cloudstack/ips.json` and every 
commands waits. Eventually hitting the hardcoded 120 sec timeout.

* pr/1471:
  lower the time we wait for interfaces to appear

Signed-off-by: Will Stevens <[email protected]>


Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/d9429f6a
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/d9429f6a
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/d9429f6a

Branch: refs/heads/4.7
Commit: d9429f6add4e463b7502577d79212af959c0795f
Parents: 5ccebf0 3636ad1
Author: Will Stevens <[email protected]>
Authored: Thu May 26 15:49:49 2016 -0400
Committer: Will Stevens <[email protected]>
Committed: Thu May 26 15:49:50 2016 -0400

----------------------------------------------------------------------
 systemvm/patches/debian/config/opt/cloud/bin/cs/CsAddress.py | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d9429f6a/systemvm/patches/debian/config/opt/cloud/bin/cs/CsAddress.py
----------------------------------------------------------------------

Reply via email to