cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3797) Create a default appliance to be used as a sample test template
Date Fri, 26 Jul 2013 12:11:59 GMT


ASF subversion and git services commented on CLOUDSTACK-3797:

Commit 26a0fd5af99ed4ade87f6b8e5ba6ab02bd9d6a31 in branch refs/heads/master from [~tsp]
[;h=26a0fd5 ]

CLOUDSTACK-3797: Builtin appliance definition using veewee

This appliance will be used for testing purposes only. The appliance
will replace the built-in in a test environment before deployment.

Some of the integration tests require specific services running within
guests to test for cloudstack features. Eg: VPC LB needs an httpd server
running. When we need to customize the template this appliance can be
used instead of having custom templates for each test.

Signed-off-by: Prasanna Santhanam <>

> Create a default appliance to be used as a sample test template
> ---------------------------------------------------------------
>                 Key: CLOUDSTACK-3797
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation, Test
>    Affects Versions: 4.2.0
>            Reporter: Rayees Namathponnan
>            Assignee: Prasanna Santhanam
>            Priority: Critical
>             Fix For: 4.2.0
> The default built-in used during testing is insufficient to perform certain specific
operations in tests. For eg: in many VPC related tests LB services are verified using a httpd
server running within the guest. We need a default appliance built from the CentOS built-in
that can be used in place of the built-in where such services can be verified.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message