cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From romain-dartigues <>
Subject [GitHub] cloudstack pull request #1604: improvement: systemvm slow operations
Date Tue, 05 Jul 2016 13:17:49 GMT
GitHub user romain-dartigues opened a pull request:

    improvement: systemvm slow operations

    On our setup we had issues with vrouters when a large number of VM were created at once.
    The vrouters try to arping the gateway (to refresh the ARP cache I suppose), but in some
case it take too much time and the vrouters got killed for being unresponsive.
    The following patches attempt to solve this by:
    * a96ab18f, 8908371b defensive fix, maybe a bug?
    * fce10c55 do not block on arping command
    This patch has been running for a month on our test environment and seems to solve the
initial problem.

You can merge this pull request into a Git repository by running:

    $ git pull systemvm-none-gateway

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1604
commit a96ab18fbed6f3411c0cd6062a6fbd799e3f4198
Author: Romain Dartigues <>
Date:   2016-05-31T08:21:11Z

    systemvm: ips.json without gateway
    The file "/etc/cloudstack/ips.json" is generated with a gateway at
    "None" even when the gateway is present in the input "cmd_line.json".

commit 8908371b213cb50f628b64637fedfda97201d33f
Author: Romain Dartigues <>
Date:   2016-05-31T08:34:35Z

    systemvm: do not arping None
    If the gateway is None, don't bother arping it.

commit fce10c55a0d482751e4736663d32aae00733b913
Author: Romain Dartigues <>
Date:   2016-05-31T09:02:09Z

    systemvm: arping in background
    Do not wait for :man:`arping(8)` to complete to continue.


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message