Hi Guys, since mom is now required by vdsm, we'd like to have Jenkins running a few tests of vdsm+mom to make sure we have no regressions, etc. The thing with mom is, that we need a real host to see memory sharing (KSM) kicks in correctly, and if the host starts swapping mom tunes the VMs memory balloon to fix it. So basically the question is, if we have a real jenkins slave, which we can use as a hypervisor for mom tests. Obviously as a slave it may run other tests while vdsm+mom tests are not running. I thought about nested kvm, but IIUC advanced features such as memory balloon may have issues there. Appreciate your feedback on this. Doron
On Tue, Nov 27, 2012 at 06:55:03AM -0500, Doron Fediuck wrote:
since mom is now required by vdsm, we'd like to have Jenkins running a few tests of vdsm+mom to make sure we have no regressions, etc.
The thing with mom is, that we need a real host to see memory sharing (KSM) kicks in correctly, and if the host starts swapping mom tunes the VMs memory balloon to fix it.
So basically the question is, if we have a real jenkins slave, which we can use as a hypervisor for mom tests. Obviously as a slave it may run other tests while vdsm+mom tests are not running.
Right now we only have virtual servers. Physical servers are expected soon, both from Alter Ways and Red Hat IT. Once we have those servers we can provide a better service to our developers. Don't pin me down on this, but I think before the end of this year we should be able to offer something.
I thought about nested kvm, but IIUC advanced features such as memory balloon may have issues there.
Nested KVM would be nice, but even that is currently not possible because our too little control over our current VMs.
Another thing we want to do is expand the unit tests. A lot of functionality can be independently verified through these types of tests and it won't even require virtualization. I am working to expand the test cases and we'll make sure that the existing Jenkins job runs those automatically. On Tue, Nov 27, 2012 at 06:55:03AM -0500, Doron Fediuck wrote:
Hi Guys, since mom is now required by vdsm, we'd like to have Jenkins running a few tests of vdsm+mom to make sure we have no regressions, etc.
The thing with mom is, that we need a real host to see memory sharing (KSM) kicks in correctly, and if the host starts swapping mom tunes the VMs memory balloon to fix it.
So basically the question is, if we have a real jenkins slave, which we can use as a hypervisor for mom tests. Obviously as a slave it may run other tests while vdsm+mom tests are not running.
I thought about nested kvm, but IIUC advanced features such as memory balloon may have issues there.
Appreciate your feedback on this. Doron
-- Adam Litke <agl@us.ibm.com> IBM Linux Technology Center
----- Original Message -----
From: "Adam Litke" <agl@us.ibm.com> To: "Doron Fediuck" <dfediuck@redhat.com> Cc: "infra" <infra@ovirt.org> Sent: Tuesday, November 27, 2012 4:07:19 PM Subject: Re: Testing MoM
Another thing we want to do is expand the unit tests. A lot of functionality can be independently verified through these types of tests and it won't even require virtualization. I am working to expand the test cases and we'll make sure that the existing Jenkins job runs those automatically.
I'm sure the above is much simpler than getting a server :) So regardless of unitests, we still need the ability to test ballooning and memory sharing which requires real iron.
On Tue, Nov 27, 2012 at 06:55:03AM -0500, Doron Fediuck wrote:
Hi Guys, since mom is now required by vdsm, we'd like to have Jenkins running a few tests of vdsm+mom to make sure we have no regressions, etc.
The thing with mom is, that we need a real host to see memory sharing (KSM) kicks in correctly, and if the host starts swapping mom tunes the VMs memory balloon to fix it.
So basically the question is, if we have a real jenkins slave, which we can use as a hypervisor for mom tests. Obviously as a slave it may run other tests while vdsm+mom tests are not running.
I thought about nested kvm, but IIUC advanced features such as memory balloon may have issues there.
Appreciate your feedback on this. Doron
-- Adam Litke <agl@us.ibm.com> IBM Linux Technology Center
participants (3)
-
Adam Litke -
Doron Fediuck -
Ewoud Kohl van Wijngaarden