Please update F19 slaves
Hi, can you please update F19 slaves? looks like some of them are missing sos update: http://jenkins.ovirt.org/job/ovirt-log-collector_master_create-rpms_merged/label=fedora19/126/console sos = 3 is needed by ovirt-log-collector-3.5.0-0.0.master.20140520.git234f49f.fc19.noarch 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
[oVirt Jenkins] ovirt-log-collector_master_create-rpms_merged - Build # 127 - Still Failing!
Project: http://jenkins.ovirt.org/job/ovirt-log-collector_master_create-rpms_merged/ Build: http://jenkins.ovirt.org/job/ovirt-log-collector_master_create-rpms_merged/127/ Build Number: 127 Build Status: Still Failing Triggered By: Retriggered by user sbonazzo for Gerrit: http://gerrit.ovirt.org/27909 - Changes Since Last Success: - Changes for Build #126 [Sandro Bonazzola] sos: require and support sos 3.1.1 Changes for Build #127 [Sandro Bonazzola] sos: require and support sos 3.1.1 - Failed Tests: - No tests ran. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[oVirt Jenkins] ovirt-engine_master_animal-sniffer_merged - Build # 6849 - Fixed!
Project: http://jenkins.ovirt.org/job/ovirt-engine_master_animal-sniffer_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_animal-sniffer_merged/6849/ Build Number: 6849 Build Status: Fixed Triggered By: Triggered by Gerrit: http://gerrit.ovirt.org/27928 - Changes Since Last Success: - Changes for Build #6848 [Vered Volansky] core: Consolidating DiskValidator's RO validations Changes for Build #6849 [Ramesh Nachimuthu] gluster:Hide skipped file count in remove brick status - Failed Tests: - No tests ran. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Fwd: Change in ovirt-log-collector[master]: sos: require and support sos 3.1.1
Hi, there's an error in the gerrit trigger, ovirt-log-collector_master_create-rpms_merged should be started only when the patch is merged. artifacts from ovirt-log-collector_master_create-rpms_merged are published in nightly snapshot so if we want to check that the package build per patch we need a ovirt-log-collector_master_create-rpms_gerrit job as we did for other packages. Can you fix that? Thanks, Sandro Messaggio originale Oggetto: Change in ovirt-log-collector[master]: sos: require and support sos 3.1.1 Data: Thu, 22 May 2014 02:32:13 -0400 Mittente: oVirt Jenkins CI Server gerr...@gerrit.ovirt.org A: Sandro Bonazzola sbona...@redhat.com CC: automat...@ovirt.org, Simone Tiraboschi stira...@redhat.com oVirt Jenkins CI Server has posted comments on this change. Change subject: sos: require and support sos 3.1.1 .. Patch Set 1: Build Failed http://jenkins.ovirt.org/job/ovirt-log-collector_gerrit/152/ : SUCCESS http://jenkins.ovirt.org/job/ovirt-log-collector_master_create-rpms_merged/127/ : FAILURE -- To view, visit http://gerrit.ovirt.org/27909 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I74b1d24cff897d6cc393ee68edfe0d78030877c5 Gerrit-PatchSet: 1 Gerrit-Project: ovirt-log-collector Gerrit-Branch: master Gerrit-Owner: Sandro Bonazzola sbona...@redhat.com Gerrit-Reviewer: Simone Tiraboschi stira...@redhat.com Gerrit-Reviewer: automat...@ovirt.org Gerrit-Reviewer: oVirt Jenkins CI Server Gerrit-HasComments: No ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[oVirt Jenkins] ovirt-log-collector_master_create-rpms_merged » fedora19 - Build # 128 - Still Failing!
Project: http://jenkins.ovirt.org/job/ovirt-log-collector_master_create-rpms_merged/label=fedora19/ Build: http://jenkins.ovirt.org/job/ovirt-log-collector_master_create-rpms_merged/label=fedora19/128/ Build Number: 128 Build Status: Still Failing Triggered By: Started by upstream project ovirt-log-collector_master_create-rpms_merged build number 128 - Changes Since Last Success: - Changes for Build #126 [Sandro Bonazzola] sos: require and support sos 3.1.1 Changes for Build #127 [Sandro Bonazzola] sos: require and support sos 3.1.1 Changes for Build #128 [Sandro Bonazzola] packaging: allow to override sos version - Failed Tests: - No tests ran. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Fwd: Change in ovirt-log-collector[master]: sos: require and support sos 3.1.1
On Thu 22 May 2014 08:38:11 AM CEST, Sandro Bonazzola wrote: Hi, there's an error in the gerrit trigger, ovirt-log-collector_master_create-rpms_merged should be started only when the patch is merged. artifacts from ovirt-log-collector_master_create-rpms_merged are published in nightly snapshot so if we want to check that the package build per patch we need a ovirt-log-collector_master_create-rpms_gerrit job as we did for other packages. Can you fix that? Thanks, Sandro Messaggio originale Oggetto: Change in ovirt-log-collector[master]: sos: require and support sos 3.1.1 Data: Thu, 22 May 2014 02:32:13 -0400 Mittente: oVirt Jenkins CI Server gerr...@gerrit.ovirt.org A: Sandro Bonazzola sbona...@redhat.com CC: automat...@ovirt.org, Simone Tiraboschi stira...@redhat.com oVirt Jenkins CI Server has posted comments on this change. Change subject: sos: require and support sos 3.1.1 .. Patch Set 1: Build Failed http://jenkins.ovirt.org/job/ovirt-log-collector_gerrit/152/ : SUCCESS http://jenkins.ovirt.org/job/ovirt-log-collector_master_create-rpms_merged/127/ : FAILURE Changed, also triggered a run with the latest master merged code for the publisher, it's not the first I see the should trigger for merged patches and is configured to trigger on all of them... I'm starting to suspect that there's a problem with the way I changed the jobs :/ That screams for a migration to yaml!! -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 signature.asc Description: OpenPGP digital signature ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Please update F19 slaves
Il 22/05/2014 10:38, David Caro ha scritto: On Thu 22 May 2014 08:31:03 AM CEST, Sandro Bonazzola wrote: Hi, can you please update F19 slaves? looks like some of them are missing sos update: http://jenkins.ovirt.org/job/ovirt-log-collector_master_create-rpms_merged/label=fedora19/126/console sos = 3 is needed by ovirt-log-collector-3.5.0-0.0.master.20140520.git234f49f.fc19.noarch Thanks, This should be handled by mock requirements, where should it get the sos rpms from? that job is not using mock. sos 3 is available in fedora 19 updates repo. -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 -- 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: Using the free space on rackspace for old releases
Le mercredi 21 mai 2014 à 07:40 -0700, Karsten Wade a écrit : On 05/21/2014 12:54 AM, David Caro wrote: Hi! We are having some issues on linode due to space limitations, and as we are not using the space we have on rackspace, maybe we can move there the old releases. That will require configuring apache on the rackspace node that will host the files and also some configuration on linode, but not complicated as far as I can tell. Any objections or other ideas? Feel free to move everything over. :) Actually, why not move all of resources.ovirt.org, leaving Mailman for a separate migration to a new, different server? I'd like to decommission that VM as soon as we can. So I looked around at the existing ressources. Alterway ovirt cluster still has 4G of memory, so we could create 1 VM there for mailman ( 1g should be enough, even if I suspect spamassassin may be more confortable with more ). The hosts in rackspace have a lot more free memory, so we could also move the VM there. The only blocking point would be to get enough IP address ( ie, 1 would be enough ). -- Michael Scherer Open Source and Standards, Sysadmin signature.asc Description: This is a digitally signed message part ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Using the free space on rackspace for old releases
- Original Message - From: Michael Scherer msche...@redhat.com To: infra@ovirt.org Sent: Thursday, May 22, 2014 1:12:33 PM Subject: Re: Using the free space on rackspace for old releases Le mercredi 21 mai 2014 à 07:40 -0700, Karsten Wade a écrit : On 05/21/2014 12:54 AM, David Caro wrote: Hi! We are having some issues on linode due to space limitations, and as we are not using the space we have on rackspace, maybe we can move there the old releases. That will require configuring apache on the rackspace node that will host the files and also some configuration on linode, but not complicated as far as I can tell. Any objections or other ideas? Feel free to move everything over. :) Actually, why not move all of resources.ovirt.org, leaving Mailman for a separate migration to a new, different server? I'd like to decommission that VM as soon as we can. So I looked around at the existing ressources. Alterway ovirt cluster still has 4G of memory, so we could create 1 VM there for mailman ( 1g should be enough, even if I suspect spamassassin may be more confortable with more ). The hosts in rackspace have a lot more free memory, so we could also move the VM there. +1 for moving to alterway if possible (btw, we can (ab)use an exiting vm there also, and run it virtual host. i wouldn't migrate anything to rackspace other than jenkins stateless slaves, since we're planning to stop using that once the phx2 lab is up and running. The only blocking point would be to get enough IP address ( ie, 1 would be enough ). -- Michael Scherer Open Source and Standards, Sysadmin ___ 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
[oVirt Jenkins] ovirt-engine_master_animal-sniffer_merged - Build # 6859 - Fixed!
Project: http://jenkins.ovirt.org/job/ovirt-engine_master_animal-sniffer_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_animal-sniffer_merged/6859/ Build Number: 6859 Build Status: Fixed Triggered By: Triggered by Gerrit: http://gerrit.ovirt.org/27945 - Changes Since Last Success: - Changes for Build #6857 [Yair Zaslavsky] aaa: Remove dependency at builtin on Common config Changes for Build #6858 [Anmol Babu] engine : Introduce TimeConverter Changes for Build #6859 [Anmol Babu] engine: TimeConversions in GlusterVolumeProfileInfoReturnForXmlRpc - Failed Tests: - No tests ran. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[ACTION NEEDED] ovirt-3.4-snapshot not updated
Hi, looks like http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly_3.4 is not publishing new 3.4 builds since May 20, 2014 12:01:06 AM The cause seems to be ovirt-engine 3.4 build failing: http://jenkins.ovirt.org/job/ovirt-engine_3.4_create-rpms_merged/ and last successful build not available anymore. I think we should change ovirt-engine_3.4_create-rpms_merged for preserving last successful build in any case. That, said, please check http://jenkins.ovirt.org/job/ovirt-engine_3.4_create-rpms_merged/label=fedora20/420/consoleFull It's failing while building permutations so it may be a memory / disk issue, but I'm not sure about it. We've 3.4.2 RC next week and we shouldn't have engine not building the week before. 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
How come same version pep8 does't work the same?
I see a patch failing to build vsdm rpm on a pep8 error. pep8 version is 1.4.6, yet the actual pep8 job works jst fine. Same pep8 version to both. How come? I need to know why this happens in order to fix my job. Patch in question: http://gerrit.ovirt.org/#/c/26759/5 pep8 job: http://jenkins.ovirt.org/job/vdsm_master_pep8_gerrit/9179/console Failing job: http://jenkins.ovirt.org/job/vdsm_master_storage_functional_tests_localfs_gerrit/852/consoleFull Thanks, Vered ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: How come same version pep8 does't work the same?
- Original Message - From: Vered Volansky ve...@redhat.com To: infra infra@ovirt.org Sent: Thursday, May 22, 2014 4:48:37 PM Subject: How come same version pep8 does't work the same? I see a patch failing to build vsdm rpm on a pep8 error. pep8 version is 1.4.6, yet the actual pep8 job works jst fine. Same pep8 version to both. How come? Please upgrade your version of pep8. There were many changes in the latest update and this is probably causing your issue. Yaniv I need to know why this happens in order to fix my job. Patch in question: http://gerrit.ovirt.org/#/c/26759/5 pep8 job: http://jenkins.ovirt.org/job/vdsm_master_pep8_gerrit/9179/console Failing job: http://jenkins.ovirt.org/job/vdsm_master_storage_functional_tests_localfs_gerrit/852/consoleFull Thanks, Vered ___ 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
Re: About merging patches without tests
On 05/21/2014 06:32 PM, David Caro wrote: On Wed 21 May 2014 04:28:10 PM CEST, Itamar Heim wrote: On 05/21/2014 05:25 PM, Eyal Edri wrote: - Original Message - From: Itamar Heim ih...@redhat.com To: Sandro Bonazzola sbona...@redhat.com, David Caro dcaro...@redhat.com Cc: infra infra@ovirt.org Sent: Friday, May 16, 2014 9:48:19 PM Subject: Re: About merging patches without tests On 05/16/2014 05:38 AM, Sandro Bonazzola wrote: Il 16/05/2014 10:37, David Caro ha scritto: On Fri 16 May 2014 09:33:44 AM CEST, Sandro Bonazzola wrote: Il 15/05/2014 18:46, David Caro ha scritto: Hi! From time to time we have some patches that are merged to master branches without having been tested mostly because the developer merges before having any response from the jenkins system. Merging one of those patches makes any following test run on that branch to fail, and creating a lot of noise and trouble around all patches and jobs. So I wanted to stat a little discussion to bring up ideas on how to prevent that. Some random thoughts: * -1 the patch at jenkins job start, and reset to 0 on success or infra failure, and keep -1 if jenkins failure * Only send a message to the patch with 'jenkins jobs started' I think that something like jenkins jobs started, please don't merge until they finish should be enough. * Setup zuul as gateway, and make it block the patches if they do not pass the tests Cheers! ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra Usually the flow is reabase - submit, that is done pretty easily from the ui, and it does not give too much time to check any comments (the rebase and submit buttons are on the top, and the comments show at the end). So doing that will not help on that case, as the developer would not see the comment before submitting. I think we should block, at least for a couple minutes, so he has to read the comments to be able to submit. We had that before also, adding a comment when the jobs start, but we removed it by developers request iirc Also recently you can just press submit and it automatically rebase before merging. So maybe yes, just a message isn't enough its not possible to wait for the job on a simple rebase usually - too many collisions possible. we're mostly talking about jobs that fail to compile, i think in those cases, it worth to wait for jenkins job to finish. if the previous patch failed to compile - i agree. if a rebase of a patch that passed previously, waiting for another round of jobs isn't practical if other merge in the meantime. I'd say: - wait for it if last patch is several days old. - make sure to check the email from automation post the merge and revert/fix if it broke in a short loop. Maybe we can retake the initiative of testing 'on demand', meaning, that the high load jobs only run after a maintainer +1 and a verified +1, that added to the extra flag might help ease the load and keep master stable: lets wait a bit till we have the extra hardware up and running? Devel sends patches/rebase/whatever, verifies +1, then a maintainer reviews +1 - jenkins job starts and adds the 'tested' flag when finished - maintainer can submit But e will need some control over the maintainers of each project (we have more or less that already as gerrit groups and permissions). -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
can someone please restart ovirt gerrit? it's crawling. thanks!
Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gsher...@redhat.com ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
request for merge permission on releng-tools repo
Hi, can you grant me merge permission on releng-tools repo? 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
Re: request for merge permission on releng-tools repo
On Thu 22 May 2014 04:56:49 PM CEST, Sandro Bonazzola wrote: Hi, can you grant me merge permission on releng-tools repo? Thanks, +1 -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 signature.asc Description: OpenPGP digital signature ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: can someone please restart ovirt gerrit? it's crawling. thanks!
On Thu 22 May 2014 04:39:59 PM CEST, Greg Sheremeta wrote: Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gsher...@redhat.com ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra Is this still an issue? I see no load on gerrit and fetching works quite well for me. -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 signature.asc Description: OpenPGP digital signature ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: request for merge permission on releng-tools repo
+1 On May 22, 2014 6:04 PM, David Caro dcaro...@redhat.com wrote: On Thu 22 May 2014 04:56:49 PM CEST, Sandro Bonazzola wroteOn Thu 22 May 2014 04:56:49 PM CEST, Sandro Bonazzola wrote: Hi, can you grant me merge permission on releng-tools repo? Thanks, +1 -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: How come same version pep8 does't work the same?
On Thu 22 May 2014 03:50:23 PM CEST, Yaniv Dary wrote: - Original Message - From: Vered Volansky ve...@redhat.com To: infra infra@ovirt.org Sent: Thursday, May 22, 2014 4:48:37 PM Subject: How come same version pep8 does't work the same? I see a patch failing to build vsdm rpm on a pep8 error. pep8 version is 1.4.6, yet the actual pep8 job works jst fine. Same pep8 version to both. How come? Please upgrade your version of pep8. There were many changes in the latest update and this is probably causing your issue. Yaniv I need to know why this happens in order to fix my job. Patch in question: http://gerrit.ovirt.org/#/c/26759/5 pep8 job: http://jenkins.ovirt.org/job/vdsm_master_pep8_gerrit/9179/console Failing job: http://jenkins.ovirt.org/job/vdsm_master_storage_functional_tests_localfs_gerrit/852/consoleFull Thanks, Vered ___ 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 Couple of things to have in mind here: The jobs that you sent are for different patches, I'll focus on the patch you sent only. Why pep8 job did pass: - Because the pep8 job only checks the changes made in that patch, and in that patch, there were no issues (git diff HEAD~) Why vdsm_master_storage_functional_tests_localfs_gerrit did not pass: - Because when compiling it will check all the files, not only the ones your patch changes, and your patch was based on an already failing patchset (http://gerrit.ovirt.org/#/c/27977/5/vdsm/BindingXMLRPC.py,cm). You can see in the gerrit comments for that patchset that it did actually fail: Patch Set 5: Code-Review-1 Verified-1 Build Unstable http://jenkins.ovirt.org/job/vdsm_master_pep8_gerrit/9162/ : UNSTABLE http://jenkins.ovirt.org/job/vdsm_master_unit_tests_gerrit/9305/ : SUCCESS http://jenkins.ovirt.org/job/vdsm_master_unit_tests_gerrit_el/8374/ : SUCCESS Mybe it's a good point to run pep8 on all the files and not only on the latest commit diff, to block any patchset based on a previously failing patch. Ideas? -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 signature.asc Description: OpenPGP digital signature ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: request for merge permission on releng-tools repo
On Thu 22 May 2014 05:36:00 PM CEST, Eyal Edri wrote: +1 On May 22, 2014 6:04 PM, David Caro dcaro...@redhat.com wrote: On Thu 22 May 2014 04:56:49 PM CEST, Sandro Bonazzola wrote On Thu 22 May 2014 04:56:49 PM CEST, Sandro Bonazzola wrote: Hi, can you grant me merge permission on releng-tools repo? Thanks, +1 -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 Adde :) -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 signature.asc Description: OpenPGP digital signature ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Using the free space on rackspace for old releases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/22/2014 03:24 AM, Eyal Edri wrote: - Original Message - From: Michael Scherer msche...@redhat.com To: infra@ovirt.org Sent: Thursday, May 22, 2014 1:12:33 PM Subject: Re: Using the free space on rackspace for old releases Le mercredi 21 mai 2014 à 07:40 -0700, Karsten Wade a écrit : On 05/21/2014 12:54 AM, David Caro wrote: Hi! We are having some issues on linode due to space limitations, and as we are not using the space we have on rackspace, maybe we can move there the old releases. That will require configuring apache on the rackspace node that will host the files and also some configuration on linode, but not complicated as far as I can tell. Any objections or other ideas? Feel free to move everything over. :) Actually, why not move all of resources.ovirt.org, leaving Mailman for a separate migration to a new, different server? I'd like to decommission that VM as soon as we can. So I looked around at the existing ressources. Alterway ovirt cluster still has 4G of memory, so we could create 1 VM there for mailman ( 1g should be enough, even if I suspect spamassassin may be more confortable with more ). The hosts in rackspace have a lot more free memory, so we could also move the VM there. +1 for moving to alterway if possible (btw, we can (ab)use an exiting vm there also, and run it virtual host. i wouldn't migrate anything to rackspace other than jenkins stateless slaves, since we're planning to stop using that once the phx2 lab is up and running. +1 - -- Karsten 'quaid' Wade.^\ CentOS Doer of Stuff http://TheOpenSourceWay.org\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlN+V34ACgkQ2ZIOBq0ODEGzzwCeJIR8ekl2FnKO1LqkyFQBb1jK I+AAoM4vEqbUKrEfUYXvtK77Bbv5zCOi =/Dgs -END PGP SIGNATURE- ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [ovirt] #105: Jenkins server for oVirt Kimchi incubator project
#105: Jenkins server for oVirt Kimchi incubator project -+ Reporter: alinefm | Owner: infra@… Type: task | Status: new Priority: major| Milestone: oVirt 3.4 Component: Jenkins | Version: Test Severity: Normal | Resolution: Keywords: | Blocked By: Blocking: | -+ Comment (by eedri): @aline - any update on getting PPC vms for jenkins? -- Ticket URL: https://fedorahosted.org/ovirt/ticket/105#comment:4 ovirt http://www.ovirt.org/ oVirt - virtualization made easy. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [ovirt] #135: Create ovirt-releases and ovirt-snapshots repositories in artifactory.ovirt.org
#135: Create ovirt-releases and ovirt-snapshots repositories in artifactory.ovirt.org ---+- Reporter: jhernand | Owner: infra@… Type: task | Status: closed Priority: major | Milestone: oVirt 3.4 Component: Repositories Mgmt | Version: Production Severity: Normal | Resolution: fixed Keywords: artifactory| Blocked By: Blocking: | ---+- Changes (by dcaro): * status: new = closed * resolution: = fixed Comment: Sent both the credentials, let me know when you don't need them no more. Reopen if you have any issues. -- Ticket URL: https://fedorahosted.org/ovirt/ticket/135#comment:3 ovirt http://www.ovirt.org/ oVirt - virtualization made easy. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[ovirt] #138: Add SSL support to artifactory.ovirt.org
#138: Add SSL support to artifactory.ovirt.org + Reporter: jhernand | Owner: infra@… Type: enhancement| Status: new Priority: major | Milestone: oVirt 4.0 Component: Repositories Mgmt |Version: Production Severity: Normal | Keywords: Blocked By: | Blocking: + Currently the access to artifactory.ovirt.org ins't protected with SSL. This means that login in poses the risk of passwords being stolen. Can we set up an Apache with SSL support? -- Ticket URL: https://fedorahosted.org/ovirt/ticket/138 ovirt http://www.ovirt.org/ oVirt - virtualization made easy. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
