#51: jenkins job for running vdsm functional tests -------------------------------------------+------------------------ Reporter: apuimedo | Owner: infra@… Type: enhancement | Status: new Priority: major | Milestone: oVirt 3.3 Component: Jenkins | Version: Test Severity: Normal | Resolution: Keywords: functional tests jenkins jobs | Blocked By: Blocking: | -------------------------------------------+------------------------ Comment (by zhshzhou): I sent mail to infra list to get an power user account to configure a job for functional tests. I got the account. Functional tests requires installing vdsm packages, starting/stopping vdsm service, and the code in the functional tests will add new NFS exports and iSCSI target to the system. All these need the root privilege for process running the functional tests, and the tests may mess up with the Jenkins slave (we are adding networking tests), so a conclusion is that we need a VM to run those tests. I just get a Jenkins account and need help on allocating a new VM. Some suggestions are discussed in the mailing list on how to use VM to run the tests. The current solution in my lab is that boot a VM in snapshot mode when there is tests to run, if it's idle, shutdown it automatically. There is a Jenkins plugin (libvirt-slave) which can start/stop VM on demand. Another suggestion is that in the job specification, start a VM and ssh to it, execute scripts to run functional tests then scp the results, at last shutdown the VM. I think this is a bit complicated, not as easy as using libvirt-slave plugin, because that plugin does exactly what we do in this solution to help managing VM and tests. All the suggestions need ability to generate VM, now the infrastructure is on EC2 and linode (I guess), and we do not have this ability. I'd wait till we can generate VM and re-raise the discussion. -- Ticket URL: <https://fedorahosted.org/ovirt/ticket/51#comment:2> ovirt <http://www.ovirt.org/> oVirt - virtualization made easy.