cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9407) vm_network_map table doesnt get cleaned up properly
Date Thu, 16 Jun 2016 17:41:05 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334260#comment-15334260
] 

ASF GitHub Bot commented on CLOUDSTACK-9407:
--------------------------------------------

GitHub user nvazquez opened a pull request:

    https://github.com/apache/cloudstack/pull/1594

    CLOUDSTACK-9407: vm_network_map table doesnt get cleaned up properly

    JIRA TICKET: https://issues.apache.org/jira/browse/CLOUDSTACK-9407
    
    ### 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 https://github.com/nvazquez/cloudstack vmnetworkmapissue

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

    https://github.com/apache/cloudstack/pull/1594.patch

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 <nicolas.m.vazquez@gmail.com>
Date:   2016-06-06T14:47:45Z

    CLOUDSTACK-9407: Release network resources on expunge command

----


> vm_network_map table doesnt get cleaned up properly
> ---------------------------------------------------
>
>                 Key: CLOUDSTACK-9407
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9407
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.9.0
>            Reporter: Nicolas Vazquez
>            Assignee: Nicolas Vazquez
>             Fix For: 4.9.0
>
>
> h3. 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.
> h3. 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.
> h3. 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.
> h3. Proposed solution
> We propose to move {{vm_network_map}} table cleanup to expunge command instead of stop
command.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message