Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 1 Mar 2017 06:57:45 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12996253.1470831618000.27332.1488351465433@Atlassian.JIRA>
In-Reply-To: <JIRA.12996253.1470831618000@Atlassian.JIRA>
References: <JIRA.12996253.1470831618000@Atlassian.JIRA> <JIRA.12996253.1470831618444@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9453) Optimizing Marvin
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 01 Mar 2017 06:57:50 -0000


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

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

Github user abhinandanprateek commented on the issue:

    https://github.com/apache/cloudstack/pull/1675
  
    @rhtyd closing this PR as relevant portion of this are already in codebase via other VRs.


> Optimizing Marvin
> -----------------
>
>                 Key: CLOUDSTACK-9453
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9453
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: marvin
>            Reporter: Abhinandan Prateek
>            Assignee: Abhinandan Prateek
>             Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
>
> Currently running all Marvin tests can take upto 4 days. The tests are not optimized for nested cloud setup where most of the test automation runs. There are some simple things that can be done to optimize the runs:
> 1. Have smaller default template: If we install macchinina template by default and use it where there is no specific dependency on OS, then it will result in speeding up many of Marvin tests.
> 2. Most of the tests have template names hard-coded. It will be a good idea to allow some form of configuration so that test writers can use templates that better suit their test scenario.
> 3. Some test timeouts are unnecessary long and a failure can be deducted much early on instead of undergoing several long timeouts.
> 4. Ability to tune service offerings to better suit marvin environments.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)