4:04 a.m.
On Tue, Jul 18, 2017 at 11:47 AM Petr Kotas <pkotas(a)redhat.com> wrote:
Hi Marc,
I have been working on a development environment for the oVirt. The
environment is basically two VMs running beside together. One runs the
engine, second is a host that runs the vdsm with nested virtualization.
I am now working on the vagrant file with orchestration to make the
environment setup easier. So if You would wait for a few more days, You
will be able to start from my setup.
Interesting, can you share a link?
As for the containers. For you to have a full test setup, you would
need
to place a VM inside the container and run a nested virtualization inside.
This is what the two projects you mentioned are doing. Therefore they are
not that lightweight as you would like.
I would recommend using the VM environment, which is the simplest solution.
I will send a reply again once my environment is up.
Petr
On Thu, Jul 13, 2017 at 4:52 PM, Greg Sheremeta <gshereme(a)redhat.com>
wrote:
> Does ovirt-system-tests meet your needs? It can leave the VMs standing
> when it's done.
>
> On Thu, Jul 13, 2017 at 10:39 AM, Marc Young <3vilpenguin(a)gmail.com>
> wrote:
>
>> I've been trying for weeks to come up with a better (most specifically
>> lighter) testing environment for external API requests (specifically
>> vagrant).
>>
>>
Right now It basically hooks into a real running oVirt to spin up and
test
>> VMs. It works but it's not portable or lightweight.
>>
>> I've been looking into the docker containers:
>> https://github.com/oVirt/ovirt-container-engine (doesnt look like
>> this is going to stay maintained? )
>> https://github.com/oVirt/ovirt-containers (this requires openshift
>> making it a giant yak to shave)
>>
>> Are there any thoughts on where to head from here? Im looking to purely
>> launch oVirt of specific versions and run some tests against it (launching
>> real VMs).
>>
>> I got the first docker one working, but it turned into a turtles problem
>> because there was no host, and adding a host requires ssh to be running
>> (which isnt), etc etc.
>>
>>
I too thing ovirt-system-tests may be a good fit. It has already suites for
master branch (coming 4.2) and 4.1 and writing a test is very easy, it uses
the python SDK which is exactly what you want.
Basically you can write your own suite, by copy-paste an already existing
suite and just modify it to your needs.
You said you wanted real VMs, but in case you want to test API calls and
interaction you can consider vdsmfake[1] which will simulate multi hosts
and multi vms all in one
[1] https://github.com/oVirt/ovirt-vdsmfake
_______________________________________________
>> Devel mailing list
>> Devel(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
>
> --
> Greg Sheremeta, MBA
> Sr. Software Engineer
> Red Hat, Inc.
> gshereme(a)redhat.com
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel