You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Gaurav Aradhye (JIRA)" <ji...@apache.org> on 2014/07/31 16:48:38 UTC

[jira] [Created] (CLOUDSTACK-7215) [Automation] Make expunge=True as default parameter value for destroyVirtualMachine api call through base library

Gaurav Aradhye created CLOUDSTACK-7215:
------------------------------------------

             Summary: [Automation] Make expunge=True as default parameter value for destroyVirtualMachine api call through base library
                 Key: CLOUDSTACK-7215
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7215
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Automation
    Affects Versions: 4.5.0
            Reporter: Gaurav Aradhye
            Assignee: Gaurav Aradhye
             Fix For: 4.5.0


In almost 90% of the scenarios where VMs are created through test case, VMs are added to cleanup list and the delete method is called for them through cleanup_resources method in utils.py file.

These VMs remain in destroyed state for long time and keep blocking the resources (IP Address etc) and hence the load on the setup on which regression build is fired increases.

Making expunge=True as default parameter in destroyVirtualMachine api call through base library will make all these VMs expunge quickly making resources available for next test cases.

Also, it can be passed as False whenever we don't want VM to expunge immediately, and in case when we recover the VM through test case after destroying it. Pass expunge=False for all such scenarios.

This will hugely boost the test cases execution speed too.



--
This message was sent by Atlassian JIRA
(v6.2#6252)