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