Invito aggiornato: oVirt 3.6.0 Alpha Release Test Day - mer 2015-05-27 (oVirt schedule)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART;VALUE=DATE:20150527 DTEND;VALUE=DATE:20150528 DTSTAMP:20150518T125529Z ORGANIZER;CN=oVirt schedule:mailto:ppqtk46u9cglj7l987ruo2l0f8@group.calenda r.google.com UID:ai2aa31e02qaj02fbi1tusl...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=infra@ovirt.org;X-NUM-GUESTS=0:mailto:infra@ovirt.org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=de...@ovirt.org;X-NUM-GUESTS=0:mailto:de...@ovirt.org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=us...@ovirt.org;X-NUM-GUESTS=0:mailto:us...@ovirt.org CREATED:20150219T141714Z DESCRIPTION:Visualizza il tuo evento in https://www.google.com/calendar/eve nt?action=VIEWeid=YWkyYWEzMWUwMnFhajAyZmJpMXR1c2xtaG8gaW5mcmFAb3ZpcnQub3Jn tok=NTIjcHBxdGs0NnU5Y2dsajdsOTg3cnVvMmwwZjhAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLm NvbTBiY2YyMWU5NjVmZDFkZjUzMTQwODRhNTM0YmVhNGRlYjIyNDViNTcctz=Europe/Romeh l=it. LAST-MODIFIED:20150518T125529Z LOCATION: SEQUENCE:3 STATUS:CONFIRMED SUMMARY:oVirt 3.6.0 Alpha Release Test Day TRANSP:TRANSPARENT END:VEVENT END:VCALENDAR invite.ics Description: application/ics ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [ovirt-devel] Fedora 20 is not supported any more on master
Il 18/05/2015 13:49, Dan Kenigsberg ha scritto: On Mon, May 18, 2015 at 01:32:27AM -0400, Yedidyah Bar David wrote: - Original Message - From: Nir Soffer nsof...@redhat.com To: Yedidyah Bar David d...@redhat.com Cc: Sandro Bonazzola sbona...@redhat.com, David Caro dcaro...@redhat.com, de...@ovirt.org, infra infra@ovirt.org Sent: Sunday, May 17, 2015 8:50:26 PM Subject: Re: [ovirt-devel] Fedora 20 is not supported any more on master - Original Message - From: Yedidyah Bar David d...@redhat.com To: Sandro Bonazzola sbona...@redhat.com Cc: David Caro dcaro...@redhat.com, Nir Soffer nsof...@redhat.com, de...@ovirt.org, infra infra@ovirt.org Sent: Sunday, May 17, 2015 8:41:42 AM Subject: Re: [ovirt-devel] Fedora 20 is not supported any more on master - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: David Caro dcaro...@redhat.com, Nir Soffer nsof...@redhat.com Cc: de...@ovirt.org, infra infra@ovirt.org Sent: Friday, May 15, 2015 3:26:02 PM Subject: Re: [ovirt-devel] Fedora 20 is not supported any more on master Il 15/05/2015 10:23, David Caro ha scritto: This job is on yaml, it's fairly simple to add/remove distros, you can do it yourself, ping me when you are around and I can guide you. The fix should remove the fc20 section under distro from the file: https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/yaml/jobs/vdsm/vdsm_create-rpms.yaml;hb=refs/heads/master from the project that has the master version Please also disable ovirt-hoste-deploy-offline for fedora 20 as well. I'll have to disable all-in-one too. Maybe we should consider to drop fedora 20 at all in master at this point. Opening the vote: +1 for me; adding de...@ovirt.org. I'd like to understand the support/build matrix with this change. Fedora 22 is to be released 2015-05-26. We currently do not build the engine for it, and I understand we do not intend to, until the port to wildfly/java8 is done. Right? Any ETA for that? We do build everything for fedora 21, but [1] says it will not be supported. Is this still true? We do not build vdsm, at least, for el6, and it's not intended to be supported anymore. We also build everything for el7. So it turns out that the only distro fully supported is el7, and no version of fedora will be supported until the port to f22/wildfly/java8 is finished. Indeed? Not sure how long we can/want to be in this state. The subject was confusing - I'm talking about vdsm support in Fedora 20, not about engine support, which as far as I know, works fine on Fedora 20. Sorry for the confusion. np at all, but my question still applies (not directed to you specifically) ... The question applies mostly to Sandro. Personally, I think we can safely skip Engine support for f21. Vdsm support for f21 is important (it's actually the ONLY supported Fedora version for the master branch, as much that master is supported.) In 3.6 engine and its dependencies will be built on el6, el7 and f22 (as soon as it will be able to use wildfly, hopefully next week). VDSM is already built on el7, f21 and f22, missing support for el6. Engine will be built on Fedora 20 until F22 support will be in, granting to be able to run engine at least on one Fedora release. We (as integration and releng but probably also infra) have not enough resources for handling support for F21 too. And a related one: Do we (want to) support engine on el6/7 with hosts on fedora (21/22)? As far as I recall, we support this combination for a long long time (as long as f* and e* hosts are kept on separate clusters), and I don't see the benefit of dropping this support. It can come up useful for conservative users, running el6, but wanting to test new stuff on el7/f29 hypervisors. -- 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
[URGENT][ACTION REQUIRED] going out of space on release server
Hi, please take urgent action to provide more space on release server. We'll not be able to release next RC / alpha with just 2 gb of space there. 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: [URGENT][ACTION REQUIRED] going out of space on release server
Depends on what you want to migrate, if only the repos hosting, I'd say 2-3 days dedicated to it to make sure all the processes that depend on them are also adapted and such, (crons, stats, mirrors, etc). That would be the easy part imo, and also the one that is requiring most of the space. On 05/18, Eyal Edri wrote: David, how much time do we need to migrate it now to phx lab dedicated vm? e. - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: infra infra@ovirt.org Sent: Monday, May 18, 2015 9:37:59 AM Subject: [URGENT][ACTION REQUIRED] going out of space on release server Hi, please take urgent action to provide more space on release server. We'll not be able to release next RC / alpha with just 2 gb of space there. 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 -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 pgpI8LByinlRH.pgp Description: PGP signature ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Logwatch for linode01.ovirt.org (Linux)
### Logwatch 7.3.6 (05/19/07) Processing Initiated: Mon May 18 03:42:06 2015 Date Range Processed: yesterday ( 2015-May-17 ) Period is day. Detail Level of Output: 0 Type of Output: unformatted Logfiles for Host: linode01.ovirt.org ## - httpd Begin Requests with error response codes 400 Bad Request /: 1 Time(s) /cgi-bin/test-cgi: 2 Time(s) /robots.txt/a.php: 2 Time(s) /w00tw00t.at.ISC.SANS.DFind:): 1 Time(s) 404 Not Found //app/etc/local.xml: 1 Time(s) //components/com_alphauserpoints/assets/ph ... mb/phpThumb.php: 1 Time(s) //dompdf.php?input_file=http://identerpris ... css/byroe.jpg??: 12 Time(s) //dompdf.php?input_file=http://identerpris ... r/css/kht.jpg??: 12 Time(s) //dompdf.php?input_file=test??: 12 Time(s) //images/stories/barner.gif: 1 Time(s) /_h5ai/client/icons/96/folder-page.png: 1 Time(s) /_h5ai/client/icons/96/zip.png: 1 Time(s) /_h5ai/client/images/app-16x16.ico: 16 Time(s) /_h5ai/client/images/crumb.svg: 2 Time(s) /_h5ai/client/images/home.svg: 2 Time(s) /admin.php: 8 Time(s) /admin/: 8 Time(s) /admin/board: 1 Time(s) /admin/login.php: 9 Time(s) /administrator/index.php: 8 Time(s) /apple-touch-icon-precomposed.png: 1 Time(s) /apple-touch-icon.png: 1 Time(s) /bitrix/admin/index.php?lang=en: 8 Time(s) /blog/wp-admin/: 19 Time(s) /board: 2 Time(s) /category/news/feed: 1 Time(s) /category/news/feed/: 1 Time(s) /data/admin/ver.txt: 1 Time(s) /favicon.ico: 343 Time(s) /index.php?gf_page=upload: 1 Time(s) /index.php?option=com_jcetask=pluginplug ... 86d0dd595c8e20b: 2 Time(s) /index.php?q=user: 1 Time(s) /listinfo/board: 1 Time(s) /meetings/ovirt/2012/ovirt.2012-08-01-14.0 ... F0%E0%E2%EA%E8;: 1 Time(s) /old/wp-admin/: 19 Time(s) /p: 1 Time(s) /pipermail/arch/2012-February/000264.html/trackback/: 1 Time(s) /pipermail/board/201: 1 Time(s) /pipermail/board/2013-July/000911.html ... F0%E0%E2%EA%E8;: 1 Time(s) /pipermail/devel/2013-April/004273.html/trackback/: 2 Time(s) /pipermail/engine-devel/2013-April/004135.html/trackback/: 2 Time(s) /pipermail/engine-patches/2012-April/014738.html: 1 Time(s) /pipermail/engine-patches/2012-April/015035.html: 1 Time(s) /pipermail/engine-patches/2012-August/029579.html: 1 Time(s) /pipermail/engine-patches/2012-February/007741.html: 1 Time(s) /pipermail/engine-patches/2012-July/026633.html: 1 Time(s) /pipermail/engine-patches/2012-July/028883.html: 1 Time(s) /pipermail/engine-patches/2012-June/021386.html: 1 Time(s) /pipermail/engine-patches/2012-June/024327.html: 1 Time(s) /pipermail/engine-patches/2012-November/042017.html: 1 Time(s) /pipermail/engine-patches/2012-November/subject.html: 1 Time(s) /pipermail/engine-patches/2012-October/thread.html: 1 Time(s) /pipermail/engine-patches/2012-September/034069.html: 1 Time(s) /pipermail/engine-patches/2013-April/065282.html: 1 Time(s) /pipermail/engine-patches/2013-April/066117.html: 1 Time(s) /pipermail/engine-patches/2013-April/thread.html: 1 Time(s) /pipermail/engine-patches/2013-August/092789.html: 1 Time(s) /pipermail/engine-patches/2013-August/092904.html: 1 Time(s) /pipermail/engine-patches/2013-August/093111.html: 1 Time(s) /pipermail/engine-patches/2013-August/093380.html: 1 Time(s) /pipermail/engine-patches/2013-August/093612.html: 1 Time(s) /pipermail/engine-patches/2013-August/093943.html: 1 Time(s) /pipermail/engine-patches/2013-August/095065.html: 1 Time(s) /pipermail/engine-patches/2013-August/095323.html: 1 Time(s) /pipermail/engine-patches/2013-August/100156.html: 1 Time(s) /pipermail/engine-patches/2013-August/101235.html: 1 Time(s) /pipermail/engine-patches/2013-August/102649.html: 1 Time(s) /pipermail/engine-patches/2013-August/102996.html: 1 Time(s) /pipermail/engine-patches/2013-August/thread.html: 1 Time(s) /pipermail/engine-patches/2013-December/130271.html: 1 Time(s) /pipermail/engine-patches/2013-December/130483.html: 1 Time(s) /pipermail/engine-patches/2013-December/130747.html: 1 Time(s) /pipermail/engine-patches/2013-December/130872.html: 1 Time(s) /pipermail/engine-patches/2013-December/132001.html: 1 Time(s) /pipermail/engine-patches/2013-December/132627.html: 1 Time(s) /pipermail/engine-patches/2013-December/132798.html: 1 Time(s) /pipermail/engine-patches/2013-December/134705.html: 1
Re: [URGENT][ACTION REQUIRED] going out of space on release server
Il 18/05/2015 09:40, David Caro ha scritto: Depends on what you want to migrate, if only the repos hosting, I'd say 2-3 days dedicated to it to make sure all the processes that depend on them are also adapted and such, (crons, stats, mirrors, etc). That would be the easy part imo, and also the one that is requiring most of the space. +1 On 05/18, Eyal Edri wrote: David, how much time do we need to migrate it now to phx lab dedicated vm? e. - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: infra infra@ovirt.org Sent: Monday, May 18, 2015 9:37:59 AM Subject: [URGENT][ACTION REQUIRED] going out of space on release server Hi, please take urgent action to provide more space on release server. We'll not be able to release next RC / alpha with just 2 gb of space there. 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 ISSUE: [oVirt Jenkins] ovirt-engine_3.5_upgrade-from-3.4_merged - Build # 1484 - Still Failing!
Project: http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged/1484/ Build Number: 1484 Build Status: Still Failing Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/40818 - Changes Since Last Success: - Changes for Build #1472 [Alon Bar-Lev] packaging: setup: pki: renew about to expire certificates [Sandro Bonazzola] fix centos 7 base repo Changes for Build #1473 [Tal Nisan] core: Check attached VMs snapshot preview only status when moving a disk Changes for Build #1474 [Alexander Wels] userportal,webadmin: multiple login messages Changes for Build #1475 [Eli Mesika] core: change other OS to 64bit [David Caro] Fixed only one rpmbuild option being used [Sandro Bonazzola] add hooks to vdsm_install-rpm-sanity [Sandro Bonazzola] uses yum-deprecated where available [Sandro Bonazzola] add python-six dep to vdsm build jobs [David Caro] Added fix for BZ1118988 Changes for Build #1476 [Amit Aviram] core: Extracting virtIO-scsi disabling check in CDA [David Caro] Added vdsm 3.5 non-merged jobs [Eyal Edri] yaml: remove obselete use of m2crypto due to BZ#601 fixed [Eyal Edri] yaml: add default values for throttle concurrent builds Changes for Build #1477 [Amit Aviram] core: NPE fix in clone image from snapshot Changes for Build #1478 [Maor Lipchuk] restapi: Use description for discover FCP Storage in rsdl [Eyal Edri] The workers option is not supported on test [Eyal Edri] yaml: enable throttle builds for rpm install template Changes for Build #1479 [Dudi Maroshi] engine: Fix ambigous error message Changes for Build #1480 [Dudi Maroshi] engine: validate (vm NUMA nodes) = (vm CPU cores) Changes for Build #1481 [Tomer Saban] webadmin: Fixed capitalization on New Cluster. Changes for Build #1482 [Tomer Saban] webadmin: Fixed text wrapping in New Cluster. Changes for Build #1483 [Amit Aviram] restapi: Extending disk editing when adding a new template. [David Caro] refactor host-deploy hack [David Caro] On EL6 master don't build ovirt-host-deploy-offline [Sandro Bonazzola] ovirt-engine-wildfly-overlay: new job [David Caro] Allowing empty .req files on standard build [David Caro] jobs: add ovirt-engine-sdk jobs Changes for Build #1484 [Yedidyah Bar David] packaging: Do not dump/restore owner/privileges - Failed Tests: - No tests ran. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [URGENT][ACTION REQUIRED] going out of space on release server
- Original Message - From: David Caro dcaro...@redhat.com To: Eyal Edri ee...@redhat.com Cc: infra infra@ovirt.org Sent: Monday, May 18, 2015 10:40:05 AM Subject: Re: [URGENT][ACTION REQUIRED] going out of space on release server Depends on what you want to migrate, if only the repos hosting, I'd say 2-3 days dedicated to it to make sure all the processes that depend on them are also adapted and such, (crons, stats, mirrors, etc). what about puppetizing the server, so the new vm on phx will be fully configured and reproducable via puppet? That would be the easy part imo, and also the one that is requiring most of the space. On 05/18, Eyal Edri wrote: David, how much time do we need to migrate it now to phx lab dedicated vm? e. - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: infra infra@ovirt.org Sent: Monday, May 18, 2015 9:37:59 AM Subject: [URGENT][ACTION REQUIRED] going out of space on release server Hi, please take urgent action to provide more space on release server. We'll not be able to release next RC / alpha with just 2 gb of space there. 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 -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 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 ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [URGENT][ACTION REQUIRED] going out of space on release server
On 05/18, Eyal Edri wrote: - Original Message - From: David Caro dcaro...@redhat.com To: Eyal Edri ee...@redhat.com Cc: infra infra@ovirt.org Sent: Monday, May 18, 2015 10:40:05 AM Subject: Re: [URGENT][ACTION REQUIRED] going out of space on release server Depends on what you want to migrate, if only the repos hosting, I'd say 2-3 days dedicated to it to make sure all the processes that depend on them are also adapted and such, (crons, stats, mirrors, etc). what about puppetizing the server, so the new vm on phx will be fully configured and reproducable via puppet? I was including the puppetizing, though the puppetizing of the related processes is another issue (that spans throug multiple machines, that might not be puppetized) That would be the easy part imo, and also the one that is requiring most of the space. On 05/18, Eyal Edri wrote: David, how much time do we need to migrate it now to phx lab dedicated vm? e. - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: infra infra@ovirt.org Sent: Monday, May 18, 2015 9:37:59 AM Subject: [URGENT][ACTION REQUIRED] going out of space on release server Hi, please take urgent action to provide more space on release server. We'll not be able to release next RC / alpha with just 2 gb of space there. 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 -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 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 -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 pgpNYo80C0k7X.pgp Description: PGP signature ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [ovirt-devel] Fedora 20 is not supported any more on master
On Mon, May 18, 2015 at 01:32:27AM -0400, Yedidyah Bar David wrote: - Original Message - From: Nir Soffer nsof...@redhat.com To: Yedidyah Bar David d...@redhat.com Cc: Sandro Bonazzola sbona...@redhat.com, David Caro dcaro...@redhat.com, de...@ovirt.org, infra infra@ovirt.org Sent: Sunday, May 17, 2015 8:50:26 PM Subject: Re: [ovirt-devel] Fedora 20 is not supported any more on master - Original Message - From: Yedidyah Bar David d...@redhat.com To: Sandro Bonazzola sbona...@redhat.com Cc: David Caro dcaro...@redhat.com, Nir Soffer nsof...@redhat.com, de...@ovirt.org, infra infra@ovirt.org Sent: Sunday, May 17, 2015 8:41:42 AM Subject: Re: [ovirt-devel] Fedora 20 is not supported any more on master - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: David Caro dcaro...@redhat.com, Nir Soffer nsof...@redhat.com Cc: de...@ovirt.org, infra infra@ovirt.org Sent: Friday, May 15, 2015 3:26:02 PM Subject: Re: [ovirt-devel] Fedora 20 is not supported any more on master Il 15/05/2015 10:23, David Caro ha scritto: This job is on yaml, it's fairly simple to add/remove distros, you can do it yourself, ping me when you are around and I can guide you. The fix should remove the fc20 section under distro from the file: https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/yaml/jobs/vdsm/vdsm_create-rpms.yaml;hb=refs/heads/master from the project that has the master version Please also disable ovirt-hoste-deploy-offline for fedora 20 as well. I'll have to disable all-in-one too. Maybe we should consider to drop fedora 20 at all in master at this point. Opening the vote: +1 for me; adding de...@ovirt.org. I'd like to understand the support/build matrix with this change. Fedora 22 is to be released 2015-05-26. We currently do not build the engine for it, and I understand we do not intend to, until the port to wildfly/java8 is done. Right? Any ETA for that? We do build everything for fedora 21, but [1] says it will not be supported. Is this still true? We do not build vdsm, at least, for el6, and it's not intended to be supported anymore. We also build everything for el7. So it turns out that the only distro fully supported is el7, and no version of fedora will be supported until the port to f22/wildfly/java8 is finished. Indeed? Not sure how long we can/want to be in this state. The subject was confusing - I'm talking about vdsm support in Fedora 20, not about engine support, which as far as I know, works fine on Fedora 20. Sorry for the confusion. np at all, but my question still applies (not directed to you specifically) ... The question applies mostly to Sandro. Personally, I think we can safely skip Engine support for f21. Vdsm support for f21 is important (it's actually the ONLY supported Fedora version for the master branch, as much that master is supported.) And a related one: Do we (want to) support engine on el6/7 with hosts on fedora (21/22)? As far as I recall, we support this combination for a long long time (as long as f* and e* hosts are kept on separate clusters), and I don't see the benefit of dropping this support. It can come up useful for conservative users, running el6, but wanting to test new stuff on el7/f29 hypervisors. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
