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

ASF subversion and git services commented on CLOUDSTACK-5674:
-------------------------------------------------------------

Commit aa2831231cb82773dcf4460a9b29985782d90ebe in branch refs/heads/marvin 
from [~gpshilamkar]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=aa28312 ]

CLOUDSTACK-5674: apiclient was used before it was created. Fixed it.


> [Automation]: Enhancements to accommodate multiple regression runs on a 
> single CS server
> ----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5674
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5674
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Automation, marvin
>            Reporter: Santhosh Kumar Edukulla
>            Assignee: Santhosh Kumar Edukulla
>
> 1. Currently, we will not be able to run multiple regression runs on a given 
> CS server either sequentially\parallelly reason being few hard codings done 
> at various places. 
> 2. So, the idea is to run complete regression\automation test suites at one 
> stretch on a given setup post deployDC. We deploy multiple zones with 
> different hypervisor type in each zone.
> 3. Tests should cut down time and run across multiple zones with different 
> hypervisor type in each zone, post deployment
> 3. The fixes and new changes should incorporate to take care to run suites 
> parallelly if we wanted or sequentially for various test suites like 
> vmware,xen,kvm etc on single CS machine without disturbing\redeploying and 
> installing the new CS instance. 
> Phase1: We will make framework\marvin changes.
> Phase2: Incorporate test module changes for these.
> Adding this ticket to track these changes.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to