cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Boris Stoyanov <>
Subject Re: Automated testing of our environment
Date Tue, 20 Mar 2018 10:31:42 GMT
Hi Daniel,

Marvin is the framework that carries out the integration tests of CloudStack. We use it extensively
in the community when testing new changes. I can recommend you to use the all the tests in
‘smoke' directory since they cover most of the functionality.

Since 4.10 we’ve invested a big effort into fixing most of the issues in the smoke tests
and now they are mostly passing, with some small exceptions.

On your question, it’s not recommended to run marvin tests agains your prod environment
since it’ll be creating new vms, networks and etc. This can cause downtime and unavailability
of some of your resources. Marvin DOES NOT write anything in the data base, with some ignorable
exceptions (changing global settings and then reverting them), so you should not be worried
about marvin interactions with the DB. I would recommend you to run tests only against a test

Boris Stoyanov
53 Chandos Place, Covent Garden, London  WC2N 4HSUK

On 20 Mar 2018, at 11:38,<>

Hi all,

We’d like to automatically run some tests again our live environment on regular basis. Something

“Deploy a VM with a specific template, assign an IP address, enable static NAT, and check
if the SSH password and keys work”

While researching, I came across the Marvin tests described here:
. I guess this would allow us to greatly reduce the amount of required work to setup test
cases. What makes me curious however:

The Framework does require access to the CS database. Is it actually writing to the DB, or
is it only using the DB to verify the API operations, such that a read-only user account would
be enough?


Daniel Herrmann
Network Engineer – Fraunhofer Private Cloud
CCIE #55056 (Routing and Switching)

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message