cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ProjectMoon <>
Subject [GitHub] cloudstack pull request: Enable/disable static NAT associates only...
Date Mon, 21 Mar 2016 16:56:44 GMT
GitHub user ProjectMoon opened a pull request:

    Enable/disable static NAT associates only relevant IPs.

    This pull request fixes a concurrency issue when disabling static NAT on a bunch of IPs
simultaneously. Under the old behavior, executing multiple disable requests would result in
invalid IP associations being sent to the virtual router. This commit changes the behavior
to apply an IP association for only the IP being added/released, which means that it is impossible
for the virtual router to receive invalid data.
    This was tested against a virtual router running on KVM and VMware. It would be nice to
have some input how this change could affect redundant routers and other static NAT providers.

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

    $ git pull pr-static-nat-concurrency-fix

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 #1450
commit fb5c8951b8d76018eb3ae235c3dbb11f0acae579
Author: jeff <>
Date:   2016-03-21T15:20:27Z

    Enable/disable static NAT associates only relevant IPs.


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