You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rajani Karuturi (JIRA)" <ji...@apache.org> on 2015/03/25 11:02:56 UTC

[jira] [Updated] (CLOUDSTACK-8332) Add test case to check SSVM and system VM creation after setting "system.vm.default.hypervisor" to xenserver

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajani Karuturi updated CLOUDSTACK-8332:
----------------------------------------
    Fix Version/s:     (was: Future)
                   4.6.0

> Add test case to check SSVM and system VM creation after setting "system.vm.default.hypervisor" to xenserver
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8332
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8332
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: Future
>            Reporter: Gaurav Aradhye
>            Assignee: Gaurav Aradhye
>              Labels: automation
>             Fix For: 4.6.0
>
>
> # Validate the following:
> # 1. Check if the setup has more than 1 zones and one of the zones
>      has xenserver host
> # 2. Deploy VMs using all templates present in the setup of different
>      hypervisors
> # 3. Set the global setting "system.vm.default.hypervisor" to "xenserver"
> # 4. Destroy all the system vms and wait for them to get recreated
> # 5. When all the SSVMs are up and running again, deploy VMs on all presen hypervisors, VMs should get deployed successfully
> # 6. The system Vms in the zone where Xenserver template is present should be running on Xenserver only and not on any other hypervisor present in the setup



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