cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9453) Optimizing Marvin
Date Mon, 22 Aug 2016 02:14:20 GMT


ASF GitHub Bot commented on CLOUDSTACK-9453:

Github user jburwell commented on a diff in the pull request:
    --- Diff: setup/db/db/schema-490to491.sql ---
    @@ -0,0 +1,4 @@
    +LOCK TABLES `vm_template` WRITE;
    +INSERT INTO `vm_template` VALUES (13,'macchinina-x86_64-xen','Macchinina (64-bit) no
GUI (XenServer)','9511a500-620b-11e6-843c-00505635944c',1,1,'BUILTIN',0,64,'','VHD','2016-08-14
16:11:00',NULL,1,'30985504bc31bf0cd3b9d2c6ca7944d3','Macchinina(64-bit) no GUI (XenServer)',0,0,99,1,0,1,1,'XenServer',NULL,NULL,0,NULL,'Active',0,NULL,0),(14,'macchinina-x86_64','Macchinina
(64-bit) no GUI (KVM)','9512a500-620b-11e6-843c-00505635944c',1,1,'BUILTIN',0,64,'','QCOW2','2016-08-14
16:11:02',NULL,1,'f50acb3a4387019b473d0f25a42bf06e','Macchinina (64-bit) no GUI (KVM)',0,0,99,1,0,1,1,'KVM',NULL,NULL,0,NULL,'Active',0,NULL,0),(15,'macchinina-x64','Macchinina
(64-bit) no GUI (vSphere)','9513a500-620b-11e6-843c-00505635944c',1,1,'BUILTIN',0,64,'','OVA','2016-08-14
16:11:05',NULL,1,'f6f881b7f2292948d8494db837fe0f47','Macchinina (64-bit) no GUI (vSphere)',0,0,99,1,0,1,1,'VMware',NULL,NULL,0,NULL,'Active',0,NULL,0);
    --- End diff --
    Why is a database change required for a Marvin optimization?

> Optimizing Marvin
> -----------------
>                 Key: CLOUDSTACK-9453
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: marvin
>    Affects Versions: Future
>            Reporter: Abhinandan Prateek
>            Assignee: Abhinandan Prateek
>             Fix For: Future
> 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
> 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

View raw message