From mburns at redhat.com Tue Apr 9 13:50:28 2013 From: mburns at redhat.com (Mike Burns) Date: Tue, 09 Apr 2013 09:50:28 -0400 Subject: [node-devel] oVirt Node Weekly Meeting minutes -- 2013-04-09 Message-ID: <51641CA4.8090009@redhat.com> Minutes: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-04-09-13.00.html Minutes (text): http://ovirt.org/meetings/ovirt/2013/ovirt.2013-04-09-13.00.txt Log: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-04-09-13.00.log.html ================================= #ovirt: oVirt Node weekly meeting ================================= Meeting started by mburns at 13:00:40 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2013/ovirt.2013-04-09-13.00.log.html . Meeting summary --------------- * next release (mburns, 13:01:07) * LINK: http://www.ovirt.org/Node_2.7_release-management (fabiand, 13:02:08) * additional features added to the release planning page (mburns, 13:03:10) * in discussing the release yesterday, fabiand and i thought that it might make sense to re-number the release as 3.0 (mburns, 13:05:06) * since we're removing vdsm and making the image generic, changing the TUI, etc. (mburns, 13:05:30) * ACTION: fabiand to update the release management page to reflect 3.0.0 release number (mburns, 13:06:42) * ACTION: mburns to post patches to move version numbers in spec files to 3.0.0 instead of 2.7.0 (mburns, 13:07:08) * AGREED: next version will be 3.0.0 (mburns, 13:07:34) * ACTION: mburns to re-target bugs for 3.0.0 instead of 2.7.0 (mburns, 13:08:21) * IDEA: Feature freeze and beta preparation -- 01-May (mburns, 13:08:57) * IDEA: RC Build -- 15-May (mburns, 13:09:30) * IDEA: GA -- 31-May (mburns, 13:09:48) * the reasoning behind these dates: Need to be ready prior to oVirt 3.3 builds are being posted live (mburns, 13:10:23) * also need them out prior to F19 (mburns, 13:10:33) * AGREED: on the proposed dates (mburns, 13:12:52) * Universal Image (mburns, 13:13:15) * owner: mburns (mburns, 13:13:19) * status: code complete and merged (mburns, 13:13:32) * no objections to inclusion in 3.0.0 (mburns, 13:14:19) * ACTION: mburns to add feature page -- due 10-Apr (mburns, 13:14:56) * this feature is making the node generic so it can be used by multiple projects (oVirt, OpenStack, Gluster, etc) (mburns, 13:15:28) * ACTION: mburns to link new feature page to release management page (mburns, 13:15:59) * new upgrade tool (mburns, 13:19:20) * owner: jboggs (mburns, 13:19:25) * status: patches posted, in review (mburns, 13:19:36) * no objections for inclusion in 3.0.0 (mburns, 13:19:54) * ACTION: jboggs to create feature page and link to release management page -- due 12-April (mburns, 13:20:15) * this feature is to improve support for upgrades to minimize the various upgrade issues we've found in the past (mburns, 13:21:08) * jboggs will be posting updated patches later today (mburns, 13:21:55) * Software iSCSI support (mburns, 13:22:29) * owner: jboggs (mburns, 13:22:36) * status: code complete and merged, needs testing (mburns, 13:22:47) * this feature adds the ability to install to and boot from a software iscsi target (mburns, 13:23:12) * no objections to inclusion in 3.0.0 (mburns, 13:23:34) * ACTION: jboggs to put up feature page and link to release management page -- due 12-April (mburns, 13:24:20) * puppet configuration (mburns, 13:25:38) * owner: rbarry (mburns, 13:25:45) * status: in development (mburns, 13:25:51) * this feature will allow ovirt-node to be configured from a puppet instance (mburns, 13:26:05) * there are 2 parts to this feature, the puppet provider and the parts in ovirt-node to allow the configuration (mburns, 13:26:26) * ACTION: rbarry to add a feature page and link to the release management page -- due 12-April (mburns, 13:27:43) * at risk until we see the code and feature page (mburns, 13:28:08) * puppet provider code is located here: https://github.com/evol262/puppet-ovirt-node-plugin?ref=commandbarr (mburns, 13:29:48) * swap enhancements (mburns, 13:30:26) * owner: mburns (mburns, 13:30:30) * status: not started (mburns, 13:30:37) * this feature is to improve allocation of swap with a couple of related sub-features (mburns, 13:31:30) * details will be included in the feature page (mburns, 13:31:57) * ACTION: mburns to post feature page and link to release management page -- due 12-April (mburns, 13:32:13) * no objection to inclusion in 3.0.0, but at risk until patches are posted (mburns, 13:32:43) * TUI -- installer (mburns, 13:34:06) * owner: fabiand (mburns, 13:34:12) * status: complete and merged (mburns, 13:34:19) * ACTION: fabiand to create feature page and link to release page -- due 12-April (mburns, 13:34:44) * this feature is a re-write of the TUI installer using the urwid backend (mburns, 13:35:09) * already merged, so no objections to 3.0.0 (mburns, 13:36:42) * TUI -- ipv6 support (mburns, 13:36:52) * owner: jboggs (mburns, 13:36:59) * status: in development (mburns, 13:37:10) * risk for 3.0.0 until patches are posted (mburns, 13:37:21) * in the past, we had IPv6 code in the TUI, but it was disabled, this will port that code to the new TUI infrastructure and enable it by default (mburns, 13:38:00) * ACTION: jboggs to create and link feature page -- due 12-April (mburns, 13:38:23) * TUI -- diagnostics (mburns, 13:39:51) * owner: rbarry (mburns, 13:39:57) * status: patches posted and in review (mburns, 13:40:08) * no objections to 3.0.0 (mburns, 13:40:17) * this page enables some additional diagnostic information in the TUI and adds a scrollable table widget for future use (mburns, 13:40:46) * ACTION: rbarry to create a feature page and link to release status page --due April 12 (mburns, 13:41:15) * Compatibility (mburns, 13:43:12) * this feature is to ensure that all work is compatible on F18, F19 (pending late F19 changes), and EL6 (RHEL/CentOS) (mburns, 13:43:57) * owner: fabiand (mburns, 13:44:31) * status: current master should be compatible on F18, no testing yet on F19/EL6 (mburns, 13:44:59) * ACTION: fabiand to work out plan for this feature (mburns, 13:45:53) * other topics (mburns, 13:47:29) Meeting ended at 13:49:27 UTC. Action Items ------------ * fabiand to update the release management page to reflect 3.0.0 release number * mburns to post patches to move version numbers in spec files to 3.0.0 instead of 2.7.0 * mburns to re-target bugs for 3.0.0 instead of 2.7.0 * mburns to add feature page -- due 10-Apr * mburns to link new feature page to release management page * jboggs to create feature page and link to release management page -- due 12-April * jboggs to put up feature page and link to release management page -- due 12-April * rbarry to add a feature page and link to the release management page -- due 12-April * mburns to post feature page and link to release management page -- due 12-April * fabiand to create feature page and link to release page -- due 12-April * jboggs to create and link feature page -- due 12-April * rbarry to create a feature page and link to release status page --due April 12 * fabiand to work out plan for this feature Action Items, by person ----------------------- * fabiand * fabiand to update the release management page to reflect 3.0.0 release number * fabiand to create feature page and link to release page -- due 12-April * fabiand to work out plan for this feature * jboggs * jboggs to create feature page and link to release management page -- due 12-April * jboggs to put up feature page and link to release management page -- due 12-April * jboggs to create and link feature page -- due 12-April * mburns * mburns to post patches to move version numbers in spec files to 3.0.0 instead of 2.7.0 * mburns to re-target bugs for 3.0.0 instead of 2.7.0 * mburns to add feature page -- due 10-Apr * mburns to link new feature page to release management page * mburns to post feature page and link to release management page -- due 12-April * rbarry * rbarry to add a feature page and link to the release management page -- due 12-April * rbarry to create a feature page and link to release status page --due April 12 * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mburns (119) * fabiand (32) * ovirtbot (5) * jboggs (4) * MACscr (2) * Rydekull (2) * rbarry (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From fabiand at redhat.com Thu Apr 11 14:58:10 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Thu, 11 Apr 2013 16:58:10 +0200 Subject: [node-devel] Testing oVirt Node with EFI in libvirt Message-ID: <1365692290.2419.1.camel@fdeutsch-laptop.local> Hey, it might be of interest to someone of how to test Node with EFI if you don't have an EFI machine around. In short: It's possible to boot a VM with EFI (instead of BIOS), the steps are described here [1]. Greetings fabian --- [1] http://dummdida.blogspot.de/2013/04/getting-efi-ovmf-into-libvirt.html From fabiand at redhat.com Thu Apr 18 11:45:09 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Thu, 18 Apr 2013 13:45:09 +0200 Subject: [node-devel] Disabled ovirt-node-iso job temproraily Message-ID: <1366285509.2462.0.camel@fdeutsch-laptop.local> Hey, I've disabled the ovirt-node-iso job temprorarily because of our current build problems. As soon as these are resolved I'll enable the job again. fabian From mburns at redhat.com Tue Apr 23 12:51:29 2013 From: mburns at redhat.com (Mike Burns) Date: Tue, 23 Apr 2013 08:51:29 -0400 (EDT) Subject: [node-devel] Cancelled: oVirt Node weekly meeting Message-ID: <508407968.1164626.1366721489919.JavaMail.root@redhat.com> A single instance of the following meeting has been cancelled: Subject: oVirt Node weekly meeting Organizer: "Mike Burns" Location: #ovirt on irc.oftc.net Time: Tuesday, April 23, 2013, 9:00:00 AM - 9:30:00 AM GMT -05:00 US/Canada Eastern Invitees: aliguori at linux.vnet.ibm.com; anthony at codemonkey.ws; node-devel at ovirt.org; whenry at redhat.com *~*~*~*~*~*~*~*~*~* Weekly call to go over features, bugs, tasks, etc -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 2836 bytes Desc: not available URL: From jonas at israelsson.com Thu Apr 25 15:28:36 2013 From: jonas at israelsson.com (Jonas Israelsson) Date: Thu, 25 Apr 2013 17:28:36 +0200 Subject: [node-devel] Logrotate seem broken Message-ID: <51794BA4.20308@israelsson.com> Hi, Ovirt-node: 2.6.1-20120228.fc18 I have noticed the my /var/log volume run out of space very fast. The reason is the /var/log/libvirtd.log file that grows rapidly. This file is included in the /etc/cron.d/vdsm-libvirt-logrotate $ cat /etc/cron.d/vdsm-libvirt-logrotate 10,25,40,55 * * * * root /usr/sbin/logrotate /etc/logrotate.d/libvirtd Running logrotate-command above manually and the log is indeed rotated, so nothing seem wrong there. Just to test I therefore added : 10,25,40,55 * * * * root /usr/sbin/logrotate /etc/logrotate.d/libvirtd 10,25,40,55 * * * * root echo "HEJ" > /tmp/apa.file And I do get the "/tmp/apa.file" , so crontab seem to be working as well. Permission looks ok.... [root at fat-tony log]# ll /etc/cron.d/ total 20 -rw-r--r--. 1 root root 128 Nov 27 10:01 0hourly -rw-r--r--. 1 root root 169 Feb 28 15:24 ovirt-logrotate -rw-r--r--. 1 root root 108 Feb 5 15:30 raid-check -rw-r--r--. 1 root root 235 Dec 3 17:05 sysstat -rw-r--r--. 1 root root 124 Apr 25 14:53 vdsm-libvirt-logrotate [root at fat-tony log]# ll /etc/logrotate.d/ total 54 -rw-r--r--. 1 root root 92 Feb 5 10:35 dracut_log -rw-r--r--. 1 root root 167 Jan 30 14:10 glusterd -rw-r--r--. 1 root root 138 Jan 30 14:10 glusterfs-fuse -rw-r--r--. 1 root root 173 Jul 20 2012 iscsiuiolog -rw-r--r--. 1 root root 359 Apr 2 06:56 libvirtd -rw-r--r--. 1 root root 162 Jan 28 20:35 libvirtd.lxc -rw-r--r--. 1 root root 163 Jan 28 20:35 libvirtd.qemu -rw-r--r--. 1 root root 162 Jan 28 20:35 libvirtd.uml -rw-r--r--. 1 root root 86 Feb 28 15:24 ovirt-node -rw-r--r--. 1 root root 175 Nov 13 17:39 sanlock -rw-r--r--. 1 root root 210 Jan 25 16:12 syslog -rw-r--r--. 1 root root 331 Feb 28 10:10 vdsm -rw-r--r--. 1 root root 251 Feb 28 10:10 vdsm-reg -rw-r--r--. 1 root root 100 Feb 6 10:06 yum So I must be missing the obvious... /J From mburns at redhat.com Thu Apr 25 15:52:11 2013 From: mburns at redhat.com (Mike Burns) Date: Thu, 25 Apr 2013 11:52:11 -0400 Subject: [node-devel] Logrotate seem broken In-Reply-To: <51794BA4.20308@israelsson.com> References: <51794BA4.20308@israelsson.com> Message-ID: <5179512B.10405@redhat.com> Can you provide the output of the following: du -sh /var/log df -h /var/log On 04/25/2013 11:28 AM, Jonas Israelsson wrote: > Hi, > > Ovirt-node: 2.6.1-20120228.fc18 > > I have noticed the my /var/log volume run out of space very fast. > > The reason is the /var/log/libvirtd.log file that grows rapidly. > > This file is included in the /etc/cron.d/vdsm-libvirt-logrotate > > $ cat /etc/cron.d/vdsm-libvirt-logrotate > 10,25,40,55 * * * * root /usr/sbin/logrotate /etc/logrotate.d/libvirtd > > Running logrotate-command above manually and the log is indeed rotated, > so nothing seem wrong there. > > Just to test I therefore added : > > 10,25,40,55 * * * * root /usr/sbin/logrotate /etc/logrotate.d/libvirtd > 10,25,40,55 * * * * root echo "HEJ" > /tmp/apa.file > > And I do get the "/tmp/apa.file" , so crontab seem to be working as well. > > Permission looks ok.... > > [root at fat-tony log]# ll /etc/cron.d/ > total 20 > -rw-r--r--. 1 root root 128 Nov 27 10:01 0hourly > -rw-r--r--. 1 root root 169 Feb 28 15:24 ovirt-logrotate > -rw-r--r--. 1 root root 108 Feb 5 15:30 raid-check > -rw-r--r--. 1 root root 235 Dec 3 17:05 sysstat > -rw-r--r--. 1 root root 124 Apr 25 14:53 vdsm-libvirt-logrotate > > [root at fat-tony log]# ll /etc/logrotate.d/ > total 54 > -rw-r--r--. 1 root root 92 Feb 5 10:35 dracut_log > -rw-r--r--. 1 root root 167 Jan 30 14:10 glusterd > -rw-r--r--. 1 root root 138 Jan 30 14:10 glusterfs-fuse > -rw-r--r--. 1 root root 173 Jul 20 2012 iscsiuiolog > -rw-r--r--. 1 root root 359 Apr 2 06:56 libvirtd > -rw-r--r--. 1 root root 162 Jan 28 20:35 libvirtd.lxc > -rw-r--r--. 1 root root 163 Jan 28 20:35 libvirtd.qemu > -rw-r--r--. 1 root root 162 Jan 28 20:35 libvirtd.uml > -rw-r--r--. 1 root root 86 Feb 28 15:24 ovirt-node > -rw-r--r--. 1 root root 175 Nov 13 17:39 sanlock > -rw-r--r--. 1 root root 210 Jan 25 16:12 syslog > -rw-r--r--. 1 root root 331 Feb 28 10:10 vdsm > -rw-r--r--. 1 root root 251 Feb 28 10:10 vdsm-reg > -rw-r--r--. 1 root root 100 Feb 6 10:06 yum > > So I must be missing the obvious... > > /J > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From fabiand at redhat.com Thu Apr 25 16:27:27 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Thu, 25 Apr 2013 18:27:27 +0200 Subject: [node-devel] Test Automation Update Message-ID: <1366907247.7021.5.camel@fdeutsch-laptop.local> Hey, it seems that testing oVirt Node and writing testcases for oVirt Node is still (too) hard. To lower the entrance barrier I worked a bit on improving igor (daemon+client) and node. The goal of this work is to have (it the not to far future) a check-local Makefile target, which builds a testable iso for the current git tree and tests it against a given testsuite. This became much easier during this week (and the random preparations in the last couple of weeks). There is a small video [0] which shows the workflow and look of the current work and some additional notes. Some remaining steps are: - Merge igor-slave into ovirt-node codebase (wip) - Create a wrapper around edit-node to build a testable iso (wip) - Add makefile target - Improve igorc to ease usage of custom testsuites - fabian -- [0] http://dummdida.blogspot.de/2013/04/testing-ovirt-node-in-4min.html From mburns at redhat.com Thu Apr 25 17:47:56 2013 From: mburns at redhat.com (Mike Burns) Date: Thu, 25 Apr 2013 13:47:56 -0400 Subject: [node-devel] Logrotate seem broken In-Reply-To: <51796959.9020502@elementary.se> References: <51794BA4.20308@israelsson.com> <5179512B.10405@redhat.com> <51796959.9020502@elementary.se> Message-ID: <51796C4C.6040303@redhat.com> On 04/25/2013 01:35 PM, Jonas Israelsson wrote: > On 25/04/13 17:52, Mike Burns wrote: >> Can you provide the output of the following: >> >> du -sh /var/log >> df -h /var/log >> > I sure can, I'll even give you two.. > > Bellow you find the output with about an hour between, during this the > the log should have been rotated four times, right ? > The /var/log/libvirtd.log grows about a MB/min > > > # First -- Thu Apr 25 16:33:36 UTC 2013 > > [root at fat-tony admin]# df -h /var/log/ > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/HostVG-Logging 2.0G 374M 1.6G 20% /var/log > > [root at fat-tony admin]# du -sh /var/log/ > 168M /var/log/ > [root at fat-tony admin]# > > > # Second -- Thu Apr 25 17:25:45 UTC 2013 > > [root at fat-tony admin]# df -h /var/log/ > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/HostVG-Logging 2.0G 443M 1.5G 24% /var/log > > [root at fat-tony admin]# du -sh /var/log/ > 231M /var/log/ > > > > All rotated logs below are when running logrotate manually. > > [root at fat-tony admin]# ll /var/log > -rw-------. 1 root root 144427492 Apr 25 17:30 libvirtd.log > -rw-------. 1 root root 1177724 Apr 25 15:30 libvirtd.log.1.xz > -rw-------. 1 root root 845740 Apr 25 15:02 libvirtd.log.2.xz > -rw-------. 1 root root 81856 Apr 25 14:42 libvirtd.log.3.xz > -rw-------. 1 root root 66488 Apr 25 14:40 libvirtd.log.4.xz That's what I expected. There is an issue with vdsm that the logs aren't being cleaned up after log rotate. If you run lsof /var/log, you'll see something like: python 20829 root 4r REG 253,10 25471139 280 /var/log/vdsm/vdsm.log.1 (deleted) This can be resolved by doing the following: Put the host in maintenance mode (recommended, but possible to skip) edit /etc/logrotate.d/vdsm to add copytrucate to first entry[1]. restart vdsmd (systemctl restart vdsmd) Now, the logs shouldn't fill up. Mike From jonas.israelsson at elementary.se Thu Apr 25 15:27:54 2013 From: jonas.israelsson at elementary.se (Jonas Israelsson) Date: Thu, 25 Apr 2013 17:27:54 +0200 Subject: [node-devel] Logrotate seem broken Message-ID: <51794B7A.8060209@elementary.se> Hi, Ovirt-node: 2.6.1-20120228.fc18 I have noticed the my /var/log volume run out of space very fast. The reason is the /var/log/libvirtd.log file that grows rapidly. This file is included in the /etc/cron.d/vdsm-libvirt-logrotate $ cat /etc/cron.d/vdsm-libvirt-logrotate 10,25,40,55 * * * * root /usr/sbin/logrotate /etc/logrotate.d/libvirtd Running logrotate-command above manually and the log is indeed rotated, so nothing seem wrong there. Just to test I therefore added : 10,25,40,55 * * * * root /usr/sbin/logrotate /etc/logrotate.d/libvirtd 10,25,40,55 * * * * root echo "HEJ" > /tmp/apa.file And I do get the "/tmp/apa.file" , so crontab seem to be working as well. Permission looks ok.... [root at fat-tony log]# ll /etc/cron.d/ total 20 -rw-r--r--. 1 root root 128 Nov 27 10:01 0hourly -rw-r--r--. 1 root root 169 Feb 28 15:24 ovirt-logrotate -rw-r--r--. 1 root root 108 Feb 5 15:30 raid-check -rw-r--r--. 1 root root 235 Dec 3 17:05 sysstat -rw-r--r--. 1 root root 124 Apr 25 14:53 vdsm-libvirt-logrotate [root at fat-tony log]# ll /etc/logrotate.d/ total 54 -rw-r--r--. 1 root root 92 Feb 5 10:35 dracut_log -rw-r--r--. 1 root root 167 Jan 30 14:10 glusterd -rw-r--r--. 1 root root 138 Jan 30 14:10 glusterfs-fuse -rw-r--r--. 1 root root 173 Jul 20 2012 iscsiuiolog -rw-r--r--. 1 root root 359 Apr 2 06:56 libvirtd -rw-r--r--. 1 root root 162 Jan 28 20:35 libvirtd.lxc -rw-r--r--. 1 root root 163 Jan 28 20:35 libvirtd.qemu -rw-r--r--. 1 root root 162 Jan 28 20:35 libvirtd.uml -rw-r--r--. 1 root root 86 Feb 28 15:24 ovirt-node -rw-r--r--. 1 root root 175 Nov 13 17:39 sanlock -rw-r--r--. 1 root root 210 Jan 25 16:12 syslog -rw-r--r--. 1 root root 331 Feb 28 10:10 vdsm -rw-r--r--. 1 root root 251 Feb 28 10:10 vdsm-reg -rw-r--r--. 1 root root 100 Feb 6 10:06 yum So I must be missing the obvious... /J From jonas.israelsson at elementary.se Thu Apr 25 17:35:21 2013 From: jonas.israelsson at elementary.se (Jonas Israelsson) Date: Thu, 25 Apr 2013 19:35:21 +0200 Subject: [node-devel] Logrotate seem broken In-Reply-To: <5179512B.10405@redhat.com> References: <51794BA4.20308@israelsson.com> <5179512B.10405@redhat.com> Message-ID: <51796959.9020502@elementary.se> On 25/04/13 17:52, Mike Burns wrote: > Can you provide the output of the following: > > du -sh /var/log > df -h /var/log > I sure can, I'll even give you two.. Bellow you find the output with about an hour between, during this the the log should have been rotated four times, right ? The /var/log/libvirtd.log grows about a MB/min # First -- Thu Apr 25 16:33:36 UTC 2013 [root at fat-tony admin]# df -h /var/log/ Filesystem Size Used Avail Use% Mounted on /dev/mapper/HostVG-Logging 2.0G 374M 1.6G 20% /var/log [root at fat-tony admin]# du -sh /var/log/ 168M /var/log/ [root at fat-tony admin]# # Second -- Thu Apr 25 17:25:45 UTC 2013 [root at fat-tony admin]# df -h /var/log/ Filesystem Size Used Avail Use% Mounted on /dev/mapper/HostVG-Logging 2.0G 443M 1.5G 24% /var/log [root at fat-tony admin]# du -sh /var/log/ 231M /var/log/ All rotated logs below are when running logrotate manually. [root at fat-tony admin]# ll /var/log -rw-------. 1 root root 144427492 Apr 25 17:30 libvirtd.log -rw-------. 1 root root 1177724 Apr 25 15:30 libvirtd.log.1.xz -rw-------. 1 root root 845740 Apr 25 15:02 libvirtd.log.2.xz -rw-------. 1 root root 81856 Apr 25 14:42 libvirtd.log.3.xz -rw-------. 1 root root 66488 Apr 25 14:40 libvirtd.log.4.xz -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabiand at redhat.com Tue Apr 30 11:57:21 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Tue, 30 Apr 2013 13:57:21 +0200 Subject: [node-devel] [Beta] Cleaning gerrit Message-ID: <1367323041.2619.10.camel@fdeutsch-laptop.local> Hey, according to our release planning [0] we will be releasing our beta of ovirt-node-3.0 on Thursday, April 2nd 2013 (in two days). Please take care of your pending patches in gerrit and take action if necessary. Greetings - fabian -- [0] http://www.ovirt.org/Node_3.0_release-management