You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rohit Yadav (JIRA)" <ji...@apache.org> on 2017/12/17 20:14:00 UTC

[jira] [Closed] (CLOUDSTACK-8208) Improve CloudStack Integration Testing and Write tool for automating it

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

Rohit Yadav closed CLOUDSTACK-8208.
-----------------------------------
    Resolution: Fixed

We've trillian, blueorangutan etc now

> Improve CloudStack Integration Testing and Write tool for automating it
> -----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8208
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8208
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>              Labels: cloud, golang, gsoc2015, java, python
>
> The integration tests that CloudStack has are hard to run on real hardware due to strict/hardcoded configuration. The task of this project are:
> - Figure about minimal system resources needed to run all integration tests (RAM, CPU, no. of VMs).
> - Fix integration tests for they can run on a developer's laptop or mini PCs such as NUC with real hypervisors (and not just simulator) - Xen or KVM. All hypervisors run in nested virtualized environment - for example Xen on VirtualBox, KVM on VMWare workstation or Fusion, or KVM/Xen on KVM etc.
> - Create Jenkins job for the same
> - Write an tool necessary to automate this
> - Create ansible based (ideal/template) CloudStack deployment based on Xen or KVM (checkout as an example, github.com/bhaisaab/peppercorn)
> This will be most important GSoC project and contribution to CloudStack if it delivers the above because right now even if we've the integration tests, they are hard to run by developers.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)