Re: Jenkins job for ovirt-iso-uploader and ovirt-image-uploader
Hi oVirt community, following the previous discussion with infra team, I need to get power user rights for jenkins in order to create a jenkins job for basic sanity testing of ovirt-iso-uploader and ovirt-image-uploader. That said, I formally request a power user for jenkins (for those tools I'm already the maintainer) in order to create new jobs for them as well and ask the community for acks. Thanks, Sandro Bonazzola Il 11/09/2013 09:56, Eyal Edri ha scritto: Hi Sandro, I assume we can create a new vm on rackspace to act as NFS server for the job, or even convert one of the existing jenkins slave vms to be one. any other thoughts from the infra team? Also, you will need to get a power user for jenkins (for tools) in order to create new jobs for them as well. The process for that is sending email to this list engine-devel to request it formally and get acks from the community. Eyal. - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: infra infra@ovirt.org Sent: Wednesday, September 11, 2013 9:31:36 AM Subject: Jenkins job for ovirt-iso-uploader and ovirt-image-uploader Hi, I would like to introduce a jenkins job for basic sanity testing of ovirt-iso-uploader and ovirt-image-uploader. For covering NFS upload it will be needed an NFS share where to upload the images, writable by an user having UID and GID of 36. For covering SSH uploads it would be needed also SSH access with a user having UID and GID of 36. For covering upload using the domain id it would be needed a running ovirt-engine instance. The space needed for the images may be little: sample ovf provided by ovirt-image-uploader is ~2kb and for the iso image any non empty file should be enough. The uploaded images will be deleted by the job after running. Is it possible for infra to provide the needed services? Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Jenkins job for ovirt-iso-uploader and ovirt-image-uploader
Il 15/09/2013 10:39, Kiril Nesenko ha scritto: Hello, Is suggest to go with the following: 1. The job will run on a specific slave(will create one for this or change the current one) 2. For NFS we can configure NFS share for localhost only on that specific slave. For ISO,IMAGE uploader that should do the trick. For SSH - will configure localhost access as well. Ok, looks good to me 3. Job should install/cleanup all pkgs after it finishes. It doesn't meter if it succeed or failed. For this, need to add cleanup code into the job itself and in the POST TASK in jenkins. Also it should clean images it uploaded at the end of the job. At the end of the job slave should be clean. Ok, I agree. 4. There is no need to create two jobs for testing these tools. Will have one job that will test ISO/IMAGE tools. I think I'll need some help for having a single job working for both packages but I'm fine with having just 1 job. - Kiril - Original Message - From: Mike Burns mbu...@redhat.com To: Eyal Edri ee...@redhat.com Cc: infra infra@ovirt.org Sent: Wednesday, September 11, 2013 3:16:21 PM Subject: Re: Jenkins job for ovirt-iso-uploader and ovirt-image-uploader On 09/11/2013 03:56 AM, Eyal Edri wrote: Hi Sandro, I assume we can create a new vm on rackspace to act as NFS server for the job, or even convert one of the existing jenkins slave vms to be one. any other thoughts from the infra team? Space -- we should either enforce that the job clean up after itself, or have some sort of cron job to clean up. One approach: jenkins job creates some sort of lockfile, removes it on finish cron job checks for lockfile if found, see how long it's been there, clean up if it's been too long if not, clean up nfs share Mike Also, you will need to get a power user for jenkins (for tools) in order to create new jobs for them as well. The process for that is sending email to this list engine-devel to request it formally and get acks from the community. Eyal. - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: infra infra@ovirt.org Sent: Wednesday, September 11, 2013 9:31:36 AM Subject: Jenkins job for ovirt-iso-uploader and ovirt-image-uploader Hi, I would like to introduce a jenkins job for basic sanity testing of ovirt-iso-uploader and ovirt-image-uploader. For covering NFS upload it will be needed an NFS share where to upload the images, writable by an user having UID and GID of 36. For covering SSH uploads it would be needed also SSH access with a user having UID and GID of 36. For covering upload using the domain id it would be needed a running ovirt-engine instance. The space needed for the images may be little: sample ovf provided by ovirt-image-uploader is ~2kb and for the iso image any non empty file should be enough. The uploaded images will be deleted by the job after running. Is it possible for infra to provide the needed services? Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Jenkins job for ovirt-iso-uploader and ovirt-image-uploader
Il 11/09/2013 09:56, Eyal Edri ha scritto: Hi Sandro, I assume we can create a new vm on rackspace to act as NFS server for the job, or even convert one of the existing jenkins slave vms to be one. any other thoughts from the infra team? Also, you will need to get a power user for jenkins (for tools) in order to create new jobs for them as well. The process for that is sending email to this list engine-devel to request it formally and get acks from the community. Eyal. - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: infra infra@ovirt.org Sent: Wednesday, September 11, 2013 9:31:36 AM Subject: Jenkins job for ovirt-iso-uploader and ovirt-image-uploader Hi, I would like to introduce a jenkins job for basic sanity testing of ovirt-iso-uploader and ovirt-image-uploader. For covering NFS upload it will be needed an NFS share where to upload the images, writable by an user having UID and GID of 36. For covering SSH uploads it would be needed also SSH access with a user having UID and GID of 36. For covering upload using the domain id it would be needed a running ovirt-engine instance. The space needed for the images may be little: sample ovf provided by ovirt-image-uploader is ~2kb and for the iso image any non empty file should be enough. The uploaded images will be deleted by the job after running. About the space needed during the job execution: I can confirm that the ovf file contained in ovirt-image-uploader package for testing, sample.ovf is 1826 byte. iso-uploader should use an iso file: I've just created one: $ echo iso uploader test README $ genisoimage -o isouploader.iso README $ ll isouploader.iso -rw-rw-r--. 1 sbonazzo sbonazzo 358400 24 set 08.41 isouploader.iso That space will be needed both in $TMPDIR and in the NFS destination. non iso file are not listed inside the engine but if 360k is too much, just for testing iso uploader a non empty file is enough: $ echo iso uploader test isouploader.iso $ ll isouploader.iso -rw-rw-r--. 1 sbonazzo sbonazzo 18 24 set 08.50 isouploader.iso Is it possible for infra to provide the needed services? Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Infra Weekly Meeting :: Minutes :: 2013-09-23
Minutes: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-09-23-14.02.html Minutes (text): http://ovirt.org/meetings/ovirt/2013/ovirt.2013-09-23-14.02.txt Log: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-09-23-14.02.log.html == #ovirt Meeting == Meeting started by ewoud at 14:02:31 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2013/ovirt.2013-09-23-14.02.log.html . Meeting summary --- * LINK: http://lists.ovirt.org/pipermail/infra/2013-September/003969.html (ewoud, 14:05:08) * network functional tests (ewoud, 14:05:50) * AGREED: enable per patch network tests for 3.3, maybe for master as well (ewoud, 14:14:54) * AGREED: look at zuul after RH tried it (ewoud, 14:15:20) * plan migration from local storage dc to new gluster based storage with new server (ewoud, 14:16:41) * ACTION: dcaro to open a ticket to install f19 on ovirt03.redhat.com (dcaro, 14:22:22) * AGREED: we look at the migration after the third host at rackspace has been installed (ewoud, 14:29:44) * ACTION: dcaro ensure rackspace03.ovirt.org points to the new host (ewoud, 14:30:15) * ACTION: ewoud ensure we can kickstart using dhcp at rackspace (ewoud, 14:34:20) * ovirt tools (iso uploader/image uploader) jobs (ewoud, 14:35:58) * ACTION: eedri verify with sbonazzo if a localhost nfs server with uid 36.36 is sufficient (ewoud, 14:44:01) * new jenkins LTS version available (ewoud, 14:44:34) * LINK: http://jenkins-ci.org/changelog-stable (eedri, 14:45:09) * jenkins LTS has update pending, change log- http://jenkins-ci.org/changelog-stable (eedri, 14:45:26) * LINK: http://jenkins.ovirt.org/job/backup_jenkins_org/ (eedri, 14:49:01) * ACTION: ewoud update jenkins to latests LTS on thursday (ewoud, 14:52:07) * jenkins per patch jobs only for 3.3 stable branch (ewoud, 14:57:17) * AGREED: change all ovirt-engine jobs to monitor '**' instead of a single branch (ewoud, 15:04:14) * artifactory server (ewoud, 15:05:31) * installed a basic centos 6 on artifactory.ovirt.org, but having network issues (ewoud, 15:06:00) * ACTION: ewoud forward mail about network to our alterway contact (ewoud, 15:07:52) Meeting ended at 15:11:49 UTC. Action Items * dcaro to open a ticket to install f19 on ovirt03.redhat.com * dcaro ensure rackspace03.ovirt.org points to the new host * ewoud ensure we can kickstart using dhcp at rackspace * eedri verify with sbonazzo if a localhost nfs server with uid 36.36 is sufficient * ewoud update jenkins to latests LTS on thursday * ewoud forward mail about network to our alterway contact Action Items, by person --- * dcaro * dcaro to open a ticket to install f19 on ovirt03.redhat.com * dcaro ensure rackspace03.ovirt.org points to the new host * eedri * eedri verify with sbonazzo if a localhost nfs server with uid 36.36 is sufficient * ewoud * ewoud ensure we can kickstart using dhcp at rackspace * ewoud update jenkins to latests LTS on thursday * ewoud forward mail about network to our alterway contact * sbonazzo * eedri verify with sbonazzo if a localhost nfs server with uid 36.36 is sufficient * **UNASSIGNED** * (none) People Present (lines said) --- * eedri (123) * ewoud (113) * dcaro (25) * mburns (8) * ovirtbot (7) * eedri_ (3) * orc_orc (3) * obasan (1) * bjuanico (1) * sbonazzo (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Build failed in Jenkins: publish_ovirt_rpms_nightly #514
See http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly/514/ -- Started by timer Building remotely on fedora19-vm01 in workspace http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly/ws/ [publish_ovirt_rpms_nightly] $ /bin/sh -xe /home/jenkins/workspace/tmp/hudson5696938982116182947.sh + rm -rf http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly/ws/artifacts + mkdir http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly/ws/artifacts Build step 'Copy artifacts from another project' marked build as failure ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Build failed in Jenkins: publish_ovirt_rpms_nightly #515
See http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly/515/ -- Started by timer Building remotely on fedora19-vm01 in workspace http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly/ws/ [publish_ovirt_rpms_nightly] $ /bin/sh -xe /home/jenkins/workspace/tmp/hudson2871967844618070083.sh + rm -rf http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly/ws/artifacts + mkdir http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly/ws/artifacts Build step 'Copy artifacts from another project' marked build as failure ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
