cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nvazquez <>
Subject [GitHub] cloudstack pull request #1594: CLOUDSTACK-9407: vm_network_map table doesnt ...
Date Thu, 16 Jun 2016 17:40:24 GMT
GitHub user nvazquez opened a pull request:

    CLOUDSTACK-9407: vm_network_map table doesnt get cleaned up properly

    ### Introduction
    It was found out that in production environments `vm_network_map` table entries were slowly
growing. It was investigated how this entries were cleaned up.
    ### Behaviour
    On vm creation, vm mappings are inserted on `vm_network_map`.
    On vm stop, mappings are deleted from `vm_network_map` for vm, as a result of the release
of its nics.
    ### Problem
    If created vm is stopped from hypervisor side (at least on vSphere in which we tested
it), when CloudStack realizes vm is stopped it doesn't clean up `vm_network_table,` and, as
cleanup is made during vm stop, when vm is eventually destroyed and expunged it won't clean
up their entries in that table.
    ### Proposed solution
    We propose to move `vm_network_map` table cleanup to expunge command instead of stop command.

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

    $ git pull vmnetworkmapissue

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 #1594
commit d3f3fb0590f14c540493d5f27c18cea13fa092af
Author: nvazquez <>
Date:   2016-06-06T14:47:45Z

    CLOUDSTACK-9407: Release network resources on expunge command


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