Hi, I'm wondering if something like nested virtualization is possible/available/recommended in centos ci.
My use case is that we would like to have a test for mariadb galera and this test is hard to be written on one machine + ideally we'd like to test real machine to machine workflow.
Is it something we can do in the jenkins?
Honza
On 17/02/16 13:29, Honza Horak wrote:
Hi, I'm wondering if something like nested virtualization is possible/available/recommended in centos ci.
My use case is that we would like to have a test for mariadb galera and this test is hard to be written on one machine + ideally we'd like to test real machine to machine workflow.
Is it something we can do in the jenkins?
I don't think you'd even need nested virt, since the tests run on bare metal (via Duffy). If you do virtualise, then the hosts that the tests run on are virt-capable.
You may not even need virtualisation as you can launch multiple hosts and could configure them to run tests between each other. The sclo-ci-tests are rather hardcoded for a single host, but this could be extended either as a one-off or build it into the data in the repo some more, e.g. a separate run.sh script per host.
On 02/17/2016 02:36 PM, Dominic Cleal wrote:
On 17/02/16 13:29, Honza Horak wrote:
Hi, I'm wondering if something like nested virtualization is possible/available/recommended in centos ci.
My use case is that we would like to have a test for mariadb galera and this test is hard to be written on one machine + ideally we'd like to test real machine to machine workflow.
Is it something we can do in the jenkins?
I don't think you'd even need nested virt, since the tests run on bare metal (via Duffy). If you do virtualise, then the hosts that the tests run on are virt-capable.
You may not even need virtualisation as you can launch multiple hosts and could configure them to run tests between each other. The sclo-ci-tests are rather hardcoded for a single host, but this could be extended either as a one-off or build it into the data in the repo some more, e.g. a separate run.sh script per host.
Thank you all, I haven't realized we are on bare metal, then it should be quite easy. As for now, I'd probably keep the sclo-ci-tests as single host tests, since changing it doesn't seem to be worth for one test.. we can change it later though, in case we have more multi-host tests..
Honza
On 02/17/2016 08:29 AM, Honza Horak wrote:
Hi, I'm wondering if something like nested virtualization is possible/available/recommended in centos ci.
My use case is that we would like to have a test for mariadb galera and this test is hard to be written on one machine + ideally we'd like to test real machine to machine workflow.
Is it something we can do in the jenkins?
I dont think anything needs to happen in jenkins. The baremetal servers provided by centos ci work for nested virt. The tripleo-quickstart jobs for RDO actually provision a whole openstack setup in virtual machines, and then run tests which launch virtual machines on that virtual compute node. So I think it works out of the box.
Honza _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 17/02/16 14:29, Honza Horak wrote:
Hi, I'm wondering if something like nested virtualization is possible/available/recommended in centos ci.
My use case is that we would like to have a test for mariadb galera and this test is hard to be written on one machine + ideally we'd like to test real machine to machine workflow.
Is it something we can do in the jenkins?
Honza
Hi Honza,
As other people already mention it, all the tests are running on bare-metal nodes, so you're free to then deploy whatever VM you want on top for your tests, then tear those down when calling the Duffy API with Done. But I'd say that you can even bypass the need for VMs and just ask multiple bare-metal nodes during your tests, as it would be in "real life" scenario.
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab