From jonas.israelsson at elementary.se Sat May 4 19:10:52 2013 From: jonas.israelsson at elementary.se (Jonas Israelsson) Date: Sat, 04 May 2013 21:10:52 +0200 Subject: [node-devel] Firmware missing Message-ID: <51855D3C.8090004@elementary.se> Greetings, I have a few Brocade 815 Fibre Channel HBA's that I was planning to use on my oVirt nodes. While the kernel module for these HBA's (bfa) is included the firmware also needed is not. I added them to one node by just remounting the root-filesystem as read-write and copied the files to /lib/firmware. These files does however not survive a reboot. Anyone knows where to place them in order to make them stay permanently ? Furthermore, would it be possible to consider adding these as standard ? There seem to be already existing fedora packages, I used this package to extract the files before adding them to the node. http://rpmfind.net/linux/RPM/fedora/devel/rawhide/x86_64/b/bfa-firmware-3.1.2.1-2.fc19.noarch.html With kind regards, Jonas From jboggs at redhat.com Mon May 6 02:10:42 2013 From: jboggs at redhat.com (Joey Boggs) Date: Sun, 05 May 2013 22:10:42 -0400 Subject: [node-devel] Firmware missing In-Reply-To: <51855D3C.8090004@elementary.se> References: <51855D3C.8090004@elementary.se> Message-ID: <51871122.7030907@redhat.com> On 05/04/2013 03:10 PM, Jonas Israelsson wrote: > Greetings, > > I have a few Brocade 815 Fibre Channel HBA's that I was planning to use > on my oVirt nodes. > While the kernel module for these HBA's (bfa) is included the firmware > also needed is not. > > I added them to one node by just remounting the root-filesystem as > read-write and copied the files to /lib/firmware. > These files does however not survive a reboot. Anyone knows where to > place them in order to make them stay permanently ? > > Furthermore, would it be possible to consider adding these as standard ? > > There seem to be already existing fedora packages, I used this package > to extract the files before adding them to the node. > > http://rpmfind.net/linux/RPM/fedora/devel/rawhide/x86_64/b/bfa-firmware-3.1.2.1-2.fc19.noarch.html > > With kind regards, > Jonas > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel Looks like its just a blacklisting problem. We install bfa-firmware but only keep some of the actual files. As a workaround you can edit common-minimizer.ks and add these lines and build the iso yourself. I'll be submitting a patch shortly and hopefully should make the 3.0 beta/release here soon. keep /lib/firmware/cbfw.bin keep /lib/firmware/ct2fw.bin keep /lib/firmware/ctfw.bin From wenyi at linux.vnet.ibm.com Tue May 7 07:19:07 2013 From: wenyi at linux.vnet.ibm.com (Wenyi Gao) Date: Tue, 07 May 2013 15:19:07 +0800 Subject: [node-devel] ovirt-node iso based on Fedora18 install issue via CD-ROM Message-ID: <5188AAEB.5000903@linux.vnet.ibm.com> Hey, I built a ovirt-node iso based on Fedora18 repository, but I ran into some problems on installing it to host via CD-ROM dracut-initqueue[698]: Warning: Could not boot. dracut-initqueue[698]: Warning: /dev/disk/by-label/ovirt-node-image does not exist dracut-initqueue[698]: Warning: /dev/mapper/live-rw does not exist dracut:/# I google the issue, it seems that Fedora don't support installation via CD-ROM. I change the boot parameter: root=live:LABEL=ovirt-node-image to root=live:/dev/sr0, the issue disappears, but got another issue: INFO Starging '' application with '' UI INFO Creating UI for application '' INFO Creating UI for application '' WARNING Device in names but not in dict: /dev/sr0 ERROR An error appeared in the UI: IOError(2, 'No such file or directory') WARNING Device in names but not in dect: /dev/sr0 Does anyone experience this issues? Thanks. By the way, I can install the iso on a VM using qemu successfully. Best regards Wenyi Gao From fabiand at redhat.com Tue May 7 10:07:35 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Tue, 07 May 2013 12:07:35 +0200 Subject: [node-devel] ovirt-node iso based on Fedora18 install issue via CD-ROM In-Reply-To: <5188AAEB.5000903@linux.vnet.ibm.com> References: <5188AAEB.5000903@linux.vnet.ibm.com> Message-ID: <1367921255.2604.3.camel@fdeutsch-laptop.local> Am Dienstag, den 07.05.2013, 15:19 +0800 schrieb Wenyi Gao: > Hey, > > I built a ovirt-node iso based on Fedora18 repository, but I ran into > some problems on installing it to host via CD-ROM > > dracut-initqueue[698]: Warning: Could not boot. > dracut-initqueue[698]: Warning: /dev/disk/by-label/ovirt-node-image does > not exist > dracut-initqueue[698]: Warning: /dev/mapper/live-rw does not exist > > dracut:/# Did this happen on a real machine? If so, what kind of CD-Drive did this appear on? I'm regularly installing Node in a VM using the ISO image and I didn't run into this problem recently, although I saw this a couple of months back. > I google the issue, it seems that Fedora don't support installation via > CD-ROM. Where did you find this? This would be new to me that Fedora can not be installed using a CD. > I change the boot parameter: root=live:LABEL=ovirt-node-image to > root=live:/dev/sr0, the issue disappears, but got another issue: > > INFO Starging ' '/usr/lib/python2.7/site-packages/ovirt/node/installer/__init__.pyc'>' > application with '' UI > INFO Creating UI for application ' 0x7f55ea7bd1d0>' > INFO Creating UI for application ' 0x7f55ea7bd1d0>' > WARNING Device in names but not in dict: /dev/sr0 > ERROR An error appeared in the UI: IOError(2, 'No such file or directory') > WARNING Device in names but not in dect: /dev/sr0 Mh - this is a bug in the UI or base libs I'd say, please open a bug to track this issue. > > Does anyone experience this issues? Thanks. > By the way, I can install the iso on a VM using qemu successfully. What bus emulation did you use for the CD Drive in qemu? Greetings - fabian From fabiand at redhat.com Tue May 7 12:06:42 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Tue, 07 May 2013 14:06:42 +0200 Subject: [node-devel] Beta for oVirt Node 3.0.0 Message-ID: <1367928402.2604.15.camel@fdeutsch-laptop.local> Hey, with a delay of five days according to our release plan for 3.0.0 [0] we are releasing the first beta of oVirt Node 3.0.0 - the ISO [1] and packages [2]. Please go ahead and give this ISO a try. What changed? The features of this release can be found here [0]. Note that vdsm was dropped from Node to make the image more generic. That means this image is not able to register with oVirt Engine. Plugins like the vdsm, cim or snmp plugin can be addded to the beta ISO using the edit-node tool (part of the ovirt-node-tools package). What can I test? You can focus on hardware support, package integration, the installation (all paths) and the TUI. What can I do if I find/miss something? Just reaches us on this mailinglist, on irc [3] or open a bug [4]. Sincerely yours The oVirt Node Team -- [0] http://www.ovirt.org/Node_3.0_release-management [1] http://resources.ovirt.org/releases/node-base/beta/iso/ovirt-node-iso-3.0.0-1.0.20130506beta1.fc18.iso [2] http://resources.ovirt.org/releases/node-base/beta/rpm/Fedora/18/ [3] irc://irc.oftc.net/#ovirt [4] https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt&component=ovirt-node From fabiand at redhat.com Tue May 7 13:24:31 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Tue, 07 May 2013 15:24:31 +0200 Subject: [node-devel] oVirt Node Weekly Meeting minutes -- 2013-05-07 Message-ID: <1367933071.2604.17.camel@fdeutsch-laptop.local> Minutes: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-07-13.01.html Minutes (text): http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-07-13.01.txt Log: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-07-13.01.log.html ================================= #ovirt: oVirt Node Weekly Meeting ================================= Meeting started by fabiand at 13:01:30 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-07-13.01.log.html . Meeting summary --------------- * Agenda (fabiand, 13:01:46) * beta status for 3.0 (fabiand, 13:02:00) * pending patches (fabiand, 13:02:14) * Beta Status (fabiand, 13:04:39) * Beta released today (fabiand, 13:05:19) * RC to be build on 2013-05-15 (fabiand, 13:06:29) * Pending Patches (fabiand, 13:07:21) * Currently 6 pending patches (fabiand, 13:07:49) * ACTION: jboggs to push updates for patches (fabiand, 13:09:00) * Other Topics (fabiand, 13:09:50) * puppet plugin code is done (fabiand, 13:11:56) * needs packaging (eta Thur/Fri) (fabiand, 13:12:12) * ACTION: rbarry to create repo for ovirt-node puppet provider (fabiand, 13:20:19) * ACTION: rbarry to push ovirt-node specific puppet patches to gerrit (fabiand, 13:20:37) Meeting ended at 13:22:53 UTC. Action Items ------------ * jboggs to push updates for patches * rbarry to create repo for ovirt-node puppet provider * rbarry to push ovirt-node specific puppet patches to gerrit Action Items, by person ----------------------- * jboggs * jboggs to push updates for patches * rbarry * rbarry to create repo for ovirt-node puppet provider * rbarry to push ovirt-node specific puppet patches to gerrit * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * fabiand (54) * mburns (15) * rbarry (11) * ovirtbot (4) * jboggs (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From mburns at redhat.com Tue May 7 13:33:25 2013 From: mburns at redhat.com (Mike Burns) Date: Tue, 07 May 2013 09:33:25 -0400 Subject: [node-devel] Beta for oVirt Node 3.0.0 In-Reply-To: <1367928402.2604.15.camel@fdeutsch-laptop.local> References: <1367928402.2604.15.camel@fdeutsch-laptop.local> Message-ID: <518902A5.5040908@redhat.com> On 05/07/2013 08:06 AM, Fabian Deutsch wrote: > Hey, > > with a delay of five days according to our release plan for 3.0.0 > [0] we are releasing the first beta of oVirt Node 3.0.0 - the ISO > [1] and packages [2]. > > Please go ahead and give this ISO a try. > > What changed? > The features of this release can be found here [0]. > Note that vdsm was dropped from Node to make the image more generic. > That means this image is not able to register with oVirt Engine. > Plugins like the vdsm, cim or snmp plugin can be addded to the beta > ISO using the edit-node tool (part of the ovirt-node-tools package). > The vdsm plugin to make this image work with ovirt-engine is currently not quite ready. I will reply as soon as we have that available. Thanks Mike > What can I test? > You can focus on hardware support, package integration, the > installation (all paths) and the TUI. > > What can I do if I find/miss something? > Just reaches us on this mailinglist, on irc [3] or open a bug [4]. > > > Sincerely yours > The oVirt Node Team > > -- > [0] http://www.ovirt.org/Node_3.0_release-management > [1] http://resources.ovirt.org/releases/node-base/beta/iso/ovirt-node-iso-3.0.0-1.0.20130506beta1.fc18.iso > [2] http://resources.ovirt.org/releases/node-base/beta/rpm/Fedora/18/ > [3] irc://irc.oftc.net/#ovirt > [4] > https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt&component=ovirt-node > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel > From wenyi at linux.vnet.ibm.com Wed May 8 03:16:32 2013 From: wenyi at linux.vnet.ibm.com (Wenyi Gao) Date: Wed, 08 May 2013 11:16:32 +0800 Subject: [node-devel] ovirt-node iso based on Fedora18 install issue via CD-ROM In-Reply-To: <1367921255.2604.3.camel@fdeutsch-laptop.local> References: <5188AAEB.5000903@linux.vnet.ibm.com> <1367921255.2604.3.camel@fdeutsch-laptop.local> Message-ID: <5189C390.5040304@linux.vnet.ibm.com> On 2013-05-07 18:07, Fabian Deutsch wrote: > Am Dienstag, den 07.05.2013, 15:19 +0800 schrieb Wenyi Gao: >> Hey, >> >> I built a ovirt-node iso based on Fedora18 repository, but I ran into >> some problems on installing it to host via CD-ROM >> >> dracut-initqueue[698]: Warning: Could not boot. >> dracut-initqueue[698]: Warning: /dev/disk/by-label/ovirt-node-image does >> not exist >> dracut-initqueue[698]: Warning: /dev/mapper/live-rw does not exist >> >> dracut:/# > Did this happen on a real machine? If so, what kind of CD-Drive did this > appear on? Yes, this happen on a physical machine. But I don't run into this problem on a VM. I am using ibm x3650 server and using Virtual CD via IMM. > I'm regularly installing Node in a VM using the ISO image and I didn't > run into this problem recently, although I saw this a couple of months > back. > >> I google the issue, it seems that Fedora don't support installation via >> CD-ROM. > Where did you find this? This would be new to me that Fedora can not be > installed using a CD. I got a similar problem with me on https://bugzilla.redhat.com/show_bug.cgi?id=824617 > >> I change the boot parameter: root=live:LABEL=ovirt-node-image to >> root=live:/dev/sr0, the issue disappears, but got another issue: >> >> INFO Starging '> '/usr/lib/python2.7/site-packages/ovirt/node/installer/__init__.pyc'>' >> application with '' UI >> INFO Creating UI for application '> 0x7f55ea7bd1d0>' >> INFO Creating UI for application '> 0x7f55ea7bd1d0>' >> WARNING Device in names but not in dict: /dev/sr0 >> ERROR An error appeared in the UI: IOError(2, 'No such file or directory') >> WARNING Device in names but not in dect: /dev/sr0 > Mh - this is a bug in the UI or base libs I'd say, please open a bug to > track this issue. Ok, I will open a bug to track this issue. >> Does anyone experience this issues? Thanks. >> By the way, I can install the iso on a VM using qemu successfully. > What bus emulation did you use for the CD Drive in qemu? I just install the iso via qemu on Fedora17 environment using the following command: qemu-kvm -M pc --enable-kvm -m 536 -smp 1 -boot d -cdrom $ISO -hda $IMG > > Greetings > - fabian > From wenyi at linux.vnet.ibm.com Tue May 7 06:24:52 2013 From: wenyi at linux.vnet.ibm.com (Wenyi Gao) Date: Tue, 07 May 2013 14:24:52 +0800 Subject: [node-devel] ovirt-node iso install issue via CD-ROM In-Reply-To: <51889B76.5020303@linux.vnet.ibm.com> References: <51889B76.5020303@linux.vnet.ibm.com> Message-ID: <51889E34.4050807@linux.vnet.ibm.com> Hey, I built a ovirt-node iso based on Fedora18 repository, but I ran into some problems on installing it to physical host via CD-ROM screen shot about the install issue I google the issue, it seems that Fedora don't support installation via CD-ROM. I change the boot parameter: root=live:LABEL=ovirt-node-image to root=live:/dev/sr0, the issue disappears, but got another issue: IOError Does anyone experience this issues? Thanks. By the way, I can install the iso on a VM using qemu successfully. Best regards Wenyi Gao -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 42650 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 20255 bytes Desc: not available URL: From wenyi at linux.vnet.ibm.com Tue May 7 07:03:24 2013 From: wenyi at linux.vnet.ibm.com (Wenyi Gao) Date: Tue, 07 May 2013 15:03:24 +0800 Subject: [node-devel] ovirt-node iso install issue via CD-ROM In-Reply-To: <51889E34.4050807@linux.vnet.ibm.com> References: <51889E34.4050807@linux.vnet.ibm.com> Message-ID: <5188A73C.4020309@linux.vnet.ibm.com> Hey, I built a ovirt-node iso based on Fedora18 repository, but I ran into some problems on installing it to physical host via CD-ROM screen shot about the install issue I google the issue, it seems that Fedora don't support installation via CD-ROM. I change the boot parameter: root=live:LABEL=ovirt-node-image to root=live:/dev/sr0, the issue disappears, but got another issue: IOError Does anyone experience this issues? Thanks. By the way, I can install the iso on a VM using qemu successfully. Best regards Wenyi Gao -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 42650 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 20255 bytes Desc: not available URL: From fabiand at redhat.com Wed May 8 14:42:12 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Wed, 08 May 2013 16:42:12 +0200 Subject: [node-devel] ovirt-node iso install issue via CD-ROM In-Reply-To: <5188A73C.4020309@linux.vnet.ibm.com> References: <51889E34.4050807@linux.vnet.ibm.com> <5188A73C.4020309@linux.vnet.ibm.com> Message-ID: <1368024132.4625.2.camel@fdeutsch-laptop.local> Hi Wenyi, Am Dienstag, den 07.05.2013, 15:03 +0800 schrieb Wenyi Gao: > I built a ovirt-node iso based on Fedora18 repository, but I ran into > some problems on installing it to physical host via CD-ROM > > screen shot about the install issue > > I google the issue, it seems that Fedora don't support installation > via CD-ROM. I change the boot parameter: > root=live:LABEL=ovirt-node-image to > root=live:/dev/sr0, the issue disappears, but got another issue: Nice that you could work around this first problem. > Does anyone experience this issues? Thanks. > By the way, I can install the iso on a VM using qemu successfully. I believe the scond/follow up error yupo see is a bug in the node libs which needs to be fixed. I don't see a workaround for this problem right now. - fabian From mburns at redhat.com Wed May 15 12:56:18 2013 From: mburns at redhat.com (Mike Burns) Date: Wed, 15 May 2013 08:56:18 -0400 Subject: [node-devel] oVirt Node Weekly Meeting Minutes Message-ID: <519385F2.6030107@redhat.com> Minutes: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-14-13.02.html Minutes (text): http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-14-13.02.txt Log: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-14-13.02.log.html ================================= #ovirt: oVirt Node Weekly Meeting ================================= Meeting started by mburns at 13:02:15 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-14-13.02.log.html . Meeting summary --------------- * agenda (mburns, 13:02:30) * feature status for 3.0.0 (mburns, 13:02:44) * other topics (mburns, 13:03:00) * Release Status (mburns, 13:03:37) * scheduled for RC build tomorrow (mburns, 13:03:50) * beta build is posted (mburns, 13:03:58) * LINK: http://www.ovirt.org/Node_3.0_release-management (mburns, 13:04:11) * blocked on systemd update in Fedora 18 (mburns, 13:06:06) * build ovirt-node packages tomorrow (mburns, 13:09:40) * build test iso if systemd will be delayed (mburns, 13:09:54) * and rebuild the iso when systemd lands (mburns, 13:10:24) * if systemd looks like it will land this week, then hold the iso build (mburns, 13:10:43) * bug 952204 -- Post (mburns, 13:11:52) * moving to modified since it's merged (mburns, 13:13:01) * bug 953895 -- status: Post (mburns, 13:13:14) * moving to Modified since it's merged (mburns, 13:13:24) * bug 953963 -- Assigned (mburns, 13:14:23) * patches posted and in final review (mburns, 13:15:52) * mburns working on the vdsm plugin (mburns, 13:19:29) * should be posted in the next couple days (mburns, 13:19:37) * fabiand working on the plugins page and migrating it to the new UI (mburns, 13:20:20) * ipv6 added to the network screen and working with basic testing (mburns, 13:21:29) * puppet patch posted and under review (mburns, 13:21:37) Meeting ended at 13:25:40 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mburns (54) * fabiand (32) * rbarry (7) * jboggs (5) * ovirtbot (5) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From Luc.Simard at tatacommunications.com Wed May 15 18:43:58 2013 From: Luc.Simard at tatacommunications.com (Luc Simard) Date: Wed, 15 May 2013 18:43:58 +0000 Subject: [node-devel] Problem with biosdevname Message-ID: <2D37E7D4AB4EF94EAA007A6E5074110070F5342D@uswv1vdag02.vsnl.co.in> Hi guys, I have a problem with the renaming of the network interfaces (dell poweredge r710). At every boot, one of the interface will be renamed to renameX and it's never the same one. In the output I pasted below bios device p2p2 has been renamed to rename7. Also as you can see the p2p3 is renamed p2p2 instead of p2p3. Anybody knows why this occurs? Here's the version the server currently use: [root at virtual02 ~]# cat /etc/redhat-release oVirt Node Hypervisor release 2.6.1 (20120228.fc18) The output using biosdevname -d: [...] BIOS device: p2p2 Kernel name: rename7 Permanent MAC: x Assigned MAC : x ifIndex: 7 Driver: igb Driver version: 4.0.1-k Firmware version: 1.51, 0x00016169 Bus Info: 0000:06:00.1 PCI name : 0000:06:00.1 PCI Slot : 2 Index in slot: 2 BIOS device: p2p3 Kernel name: p2p2 Permanent MAC: x Assigned MAC : x ifIndex: 8 Driver: igb Driver version: 4.0.1-k Firmware version: 1.51, 0x0001616a Bus Info: 0000:07:00.0 PCI name : 0000:07:00.0 PCI Slot : 2 Index in slot: 3 [...] --Luc -------------- next part -------------- An HTML attachment was scrubbed... URL: From jboggs at redhat.com Wed May 15 18:53:23 2013 From: jboggs at redhat.com (Joey Boggs) Date: Wed, 15 May 2013 14:53:23 -0400 Subject: [node-devel] Problem with biosdevname In-Reply-To: <2D37E7D4AB4EF94EAA007A6E5074110070F5342D@uswv1vdag02.vsnl.co.in> References: <2D37E7D4AB4EF94EAA007A6E5074110070F5342D@uswv1vdag02.vsnl.co.in> Message-ID: <5193D9A3.6020608@redhat.com> On 05/15/2013 02:43 PM, Luc Simard wrote: > > Hi guys, > > I have a problem with the renaming of the network interfaces (dell > poweredge r710). At every boot, one of the interface will be renamed > to renameX and it's never the same one. In the output I pasted below > bios device p2p2 has been renamed to rename7. Also as you can see the > p2p3 is renamed p2p2 instead of p2p3. Anybody knows why this occurs? > > Here's the version the server currently use: > > [root at virtual02 ~]# cat /etc/redhat-release > > oVirt Node Hypervisor release 2.6.1 (20120228.fc18) > > The output using biosdevname --d: > > [...] > > BIOS device: p2p2 > > Kernel name: rename7 > > Permanent MAC: x > > Assigned MAC : x > > ifIndex: 7 > > Driver: igb > > Driver version: 4.0.1-k > > Firmware version: 1.51, 0x00016169 > > Bus Info: 0000:06:00.1 > > PCI name : 0000:06:00.1 > > PCI Slot : 2 > > Index in slot: 2 > > BIOS device: p2p3 > > Kernel name: p2p2 > > Permanent MAC: x > > Assigned MAC : x > > ifIndex: 8 > > Driver: igb > > Driver version: 4.0.1-k > > Firmware version: 1.51, 0x0001616a > > Bus Info: 0000:07:00.0 > > PCI name : 0000:07:00.0 > > PCI Slot : 2 > > Index in slot: 3 > > [...] > > --Luc > > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel Can you get the ifcfg-XXXX files and the output from dmesg? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Luc.Simard at tatacommunications.com Thu May 16 01:43:49 2013 From: Luc.Simard at tatacommunications.com (Luc Simard) Date: Thu, 16 May 2013 01:43:49 +0000 Subject: [node-devel] Problem with biosdevname In-Reply-To: <5193D9A3.6020608@redhat.com> References: <2D37E7D4AB4EF94EAA007A6E5074110070F5342D@uswv1vdag02.vsnl.co.in> <5193D9A3.6020608@redhat.com> Message-ID: <2D37E7D4AB4EF94EAA007A6E5074110070F536E3@uswv1vdag02.vsnl.co.in> > -----Original Message----- > From: Joey Boggs [mailto:jboggs at redhat.com] > Sent: May-15-13 2:53 PM > To: Luc Simard > Cc: node-devel at ovirt.org > Subject: Re: [node-devel] Problem with biosdevname > > On 05/15/2013 02:43 PM, Luc Simard wrote: > > > Hi guys, > > > > I have a problem with the renaming of the network interfaces (dell > poweredge r710). At every boot, one of the interface will be renamed to > renameX and it's never the same one. In the output I pasted below bios > device p2p2 has been renamed to rename7. Also as you can see the p2p3 is > renamed p2p2 instead of p2p3. Anybody knows why this occurs? > > > > Here's the version the server currently use: > > [root at virtual02 ~]# cat /etc/redhat-release > > oVirt Node Hypervisor release 2.6.1 (20120228.fc18) > > > > The output using biosdevname -d: > > [...] > > BIOS device: p2p2 > > Kernel name: rename7 > > Permanent MAC: x > > Assigned MAC : x > > ifIndex: 7 > > Driver: igb > > Driver version: 4.0.1-k > > Firmware version: 1.51, 0x00016169 > > Bus Info: 0000:06:00.1 > > PCI name : 0000:06:00.1 > > PCI Slot : 2 > > Index in slot: 2 > > > > BIOS device: p2p3 > > Kernel name: p2p2 > > Permanent MAC: x > > Assigned MAC : x > > ifIndex: 8 > > Driver: igb > > Driver version: 4.0.1-k > > Firmware version: 1.51, 0x0001616a > > Bus Info: 0000:07:00.0 > > PCI name : 0000:07:00.0 > > PCI Slot : 2 > > Index in slot: 3 > > [...] > > > > --Luc > > > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel > > > Can you get the ifcfg-XXXX files and the output from dmesg? I have only one configuration file for em1 but I doubt it's related to this issue. Here's the udev dmesg output: [ 4.429169] systemd-udevd[302]: renamed network interface eth1 to p2p2 [ 4.441210] systemd-udevd[304]: renamed network interface eth0 to p2p1 [ 4.446207] systemd-udevd[306]: renamed network interface eth6 to p1p3 [ 4.457198] systemd-udevd[305]: renamed network interface eth3 to p2p3 [ 4.467193] systemd-udevd[311]: renamed network interface eth5 to p1p2 [ 4.480199] systemd-udevd[308]: renamed network interface eth4 to p1p1 [ 4.480247] systemd-udevd[309]: Tried to rename network interface eth2, but the target name p2p3 already exists! The names that udev rules assign to network interfaces must be changed. Avoid names that collide with kernel created ones. A workaround will be attempted now, but this WILL BREAK in a future release! See https://bugs.freedesktop.org/show_bug.cgi?id=56929#c3 [ 4.491179] systemd-udevd[313]: renamed network interface eth7 to p1p4 [ 4.502116] systemd-udevd[309]: renamed network interface eth2 to rename8 --Luc From mburns at redhat.com Thu May 16 14:20:28 2013 From: mburns at redhat.com (Mike Burns) Date: Thu, 16 May 2013 10:20:28 -0400 (EDT) Subject: [node-devel] oVirt Node weekly meeting Message-ID: <39817024.2829216.1368714028149.JavaMail.root@redhat.com> The following meeting has been modified: Subject: oVirt Node weekly meeting Organizer: "Mike Burns" Location: #ovirt on irc.oftc.net Time: 10:00:00 AM - 10:30:00 AM GMT -05:00 US/Canada Eastern [MODIFIED] Recurrence : Every Tuesday No end date Effective Nov 22, 2011 Invitees: aliguori at linux.vnet.ibm.com; anthony at codemonkey.ws; node-devel at ovirt.org; whenry at redhat.com *~*~*~*~*~*~*~*~*~* Moving this meeting to 10:00 AM EDT permanently. 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: 1647 bytes Desc: not available URL: From mburns at redhat.com Fri May 17 16:12:48 2013 From: mburns at redhat.com (Mike Burns) Date: Fri, 17 May 2013 12:12:48 -0400 Subject: [node-devel] RC for oVirt Node 3.0.0 is now available Message-ID: <51965700.5040504@redhat.com> Hi all, An update to our beta release from early last week is now available What changed? The features of this release can be found here [0]. Note that vdsm was dropped from Node to make the image more generic. That means this image is not able to register with oVirt Engine. Plugins like the vdsm, cim or snmp plugin can be addded to the beta ISO using the edit-node tool (part of the ovirt-node-tools package). What can I test? You can focus on hardware support, package integration, the installation (all paths) and the TUI. What can I do if I find/miss something? Just reaches us on this mailinglist, on irc [3] or open a bug [4]. Changes since the previous build: * Fix a corruption in NFSv4 configuration * Fix cpu topology reporting for some newer processors * enhancements in the upgrade code * Fix log file visibility * add the keyboard selection page on upgrade * Add IPv6 configuration to the TUI Also available (but still pre-beta, since it's tied to the oVirt release schedule, not the oVirt Node schedule) is the vdsm plugin for ovirt node. This packages can be found here[2]. An iso with this plugin pre-installed is also available[5]. A edit-node.repo file has also been posted for convenience[6] for those of you wishing to make use of the plugins that are not included by default, but available at [2]. These can be installed by using the following command: # sudo edit-node --repo=edit-node.repo --install=

Sincerely yours The oVirt Node Team -- [1] http://resources.ovirt.org/releases/node-base/beta/iso/ovirt-node-iso-3.0.0-1.0.20130517.fc18.iso [2] http://resources.ovirt.org/releases/node-base/beta/rpm/Fedora/18/ [3] irc://irc.oftc.net/#ovirt [4] https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt&component=ovirt-node [5] http://resources.ovirt.org/releases/node-base/beta/iso/ovirt-node-iso-3.0.0-1.0.20130517.ovirt-node-plugin-vdsm.fc18.iso [6] http://resources.ovirt.org/releases/node-base/edit-node.repo From alonbl at redhat.com Mon May 20 08:48:15 2013 From: alonbl at redhat.com (Alon Bar-Lev) Date: Mon, 20 May 2013 04:48:15 -0400 (EDT) Subject: [node-devel] RC for oVirt Node 3.0.0 is now available In-Reply-To: <51965700.5040504@redhat.com> References: <51965700.5040504@redhat.com> Message-ID: <766183827.2397987.1369039695708.JavaMail.root@redhat.com> ----- Original Message ----- > From: "Mike Burns" > To: "node-devel" , announce at ovirt.org > Sent: Friday, May 17, 2013 7:12:48 PM > Subject: [node-devel] RC for oVirt Node 3.0.0 is now available > > What can I test? > You can focus on hardware support, package integration, the > installation (all paths) and the TUI. Hi! 1. ovirt-node-upgrade should be moved to /usr/sbin as it is a tool to be executed by admin, and it is not working properly. ssh host ovirt-node-upgrade --iso=- --reboot=10 < iso 2. when I try to enable ssh and save, I get the following on black text screen: An error appeared in the UI: Press ENTER to logout... or enter 's' to drop to shell 3. I don't understand the difference of gray and non gray fields... I can access both... 4. Registration of HTTP does not work for some reason... do not think it is a new problem. 5. Registration using HTTPS produces a dialog with the following content: @ENGINENAME@ Fingerprint TBD ... 6. Saving does not configure vdsm-reg.conf nor starting it. --- Douglas, Can you please work with ovirt-node team so that we have a working solution? Thanks, Alon From mburns at redhat.com Mon May 20 12:03:53 2013 From: mburns at redhat.com (Mike Burns) Date: Mon, 20 May 2013 08:03:53 -0400 Subject: [node-devel] RC for oVirt Node 3.0.0 is now available In-Reply-To: <766183827.2397987.1369039695708.JavaMail.root@redhat.com> References: <51965700.5040504@redhat.com> <766183827.2397987.1369039695708.JavaMail.root@redhat.com> Message-ID: <519A1129.9070002@redhat.com> On 05/20/2013 04:48 AM, Alon Bar-Lev wrote: > > > ----- Original Message ----- >> From: "Mike Burns" >> To: "node-devel" , announce at ovirt.org >> Sent: Friday, May 17, 2013 7:12:48 PM >> Subject: [node-devel] RC for oVirt Node 3.0.0 is now available >> >> What can I test? >> You can focus on hardware support, package integration, the >> installation (all paths) and the TUI. > > Hi! Thanks for the testing Alon! > > 1. ovirt-node-upgrade should be moved to /usr/sbin as it is a tool to be executed by admin, and it is not working properly. > > ssh host ovirt-node-upgrade --iso=- --reboot=10 < iso Joey, can you post a patch to move it into /usr/sbin? > > 2. when I try to enable ssh and save, I get the following on black text screen: > > An error appeared in the UI: > Press ENTER to logout... > or enter 's' to drop to shell Ryan, can you look into this? > > 3. I don't understand the difference of gray and non gray fields... I can access both... Do you have examples? Fabian, can you investigate? > > 4. Registration of HTTP does not work for some reason... do not think it is a new problem. > > 5. Registration using HTTPS produces a dialog with the following content: > > @ENGINENAME@ Fingerprint > TBD > ... > > 6. Saving does not configure vdsm-reg.conf nor starting it. These 3 -- yes, there are a number of things broken on the page. I filed a bug over the weekend: https://bugzilla.redhat.com/show_bug.cgi?id=964320 > > --- > > Douglas, > > Can you please work with ovirt-node team so that we have a working solution? > > Thanks, > Alon > Thanks, Mike From mburns at redhat.com Mon May 20 14:08:48 2013 From: mburns at redhat.com (Mike Burns) Date: Mon, 20 May 2013 10:08:48 -0400 Subject: [node-devel] RC for oVirt Node 3.0.0 is now available In-Reply-To: <519A3C45.3040808@redhat.com> References: <51965700.5040504@redhat.com> <766183827.2397987.1369039695708.JavaMail.root@redhat.com> <519A1129.9070002@redhat.com> <519A3C45.3040808@redhat.com> Message-ID: <519A2E70.8090407@redhat.com> On 05/20/2013 11:07 AM, Douglas Schilling Landgraf wrote: > On 05/20/2013 08:03 AM, Mike Burns wrote: >> On 05/20/2013 04:48 AM, Alon Bar-Lev wrote: >>> >>> >>> ----- Original Message ----- >>>> From: "Mike Burns" >>>> To: "node-devel" , announce at ovirt.org >>>> Sent: Friday, May 17, 2013 7:12:48 PM >>>> Subject: [node-devel] RC for oVirt Node 3.0.0 is now available >>>> >>>> What can I test? >>>> You can focus on hardware support, package integration, the >>>> installation (all paths) and the TUI. >>> >>> Hi! >> >> Thanks for the testing Alon! >> >>> >>> 1. ovirt-node-upgrade should be moved to /usr/sbin as it is a tool to >>> be executed by admin, and it is not working properly. >>> >>> ssh host ovirt-node-upgrade --iso=- --reboot=10 < iso >> >> Joey, can you post a patch to move it into /usr/sbin? >> >>> >>> 2. when I try to enable ssh and save, I get the following on black >>> text screen: >>> >>> An error appeared in the UI: >>> Press ENTER to logout... >>> or enter 's' to drop to shell >> >> Ryan, can you look into this? >> >>> >>> 3. I don't understand the difference of gray and non gray fields... I >>> can access both... >> >> Do you have examples? >> >> Fabian, can you investigate? >> >>> >>> 4. Registration of HTTP does not work for some reason... do not think >>> it is a new problem. >>> >>> 5. Registration using HTTPS produces a dialog with the following >>> content: >>> >>> @ENGINENAME@ Fingerprint >>> TBD >>> ... >>> >>> 6. Saving does not configure vdsm-reg.conf nor >>> starting it. >> >> These 3 -- yes, there are a number of things broken on the page. I >> filed a bug over the weekend: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=964320 > Mike/Alon Should I start from this point? > > This is were I left it over the weekend. Mike From dougsland at redhat.com Mon May 20 15:07:49 2013 From: dougsland at redhat.com (Douglas Schilling Landgraf) Date: Mon, 20 May 2013 11:07:49 -0400 Subject: [node-devel] RC for oVirt Node 3.0.0 is now available In-Reply-To: <519A1129.9070002@redhat.com> References: <51965700.5040504@redhat.com> <766183827.2397987.1369039695708.JavaMail.root@redhat.com> <519A1129.9070002@redhat.com> Message-ID: <519A3C45.3040808@redhat.com> On 05/20/2013 08:03 AM, Mike Burns wrote: > On 05/20/2013 04:48 AM, Alon Bar-Lev wrote: >> >> >> ----- Original Message ----- >>> From: "Mike Burns" >>> To: "node-devel" , announce at ovirt.org >>> Sent: Friday, May 17, 2013 7:12:48 PM >>> Subject: [node-devel] RC for oVirt Node 3.0.0 is now available >>> >>> What can I test? >>> You can focus on hardware support, package integration, the >>> installation (all paths) and the TUI. >> >> Hi! > > Thanks for the testing Alon! > >> >> 1. ovirt-node-upgrade should be moved to /usr/sbin as it is a tool to >> be executed by admin, and it is not working properly. >> >> ssh host ovirt-node-upgrade --iso=- --reboot=10 < iso > > Joey, can you post a patch to move it into /usr/sbin? > >> >> 2. when I try to enable ssh and save, I get the following on black >> text screen: >> >> An error appeared in the UI: >> Press ENTER to logout... >> or enter 's' to drop to shell > > Ryan, can you look into this? > >> >> 3. I don't understand the difference of gray and non gray fields... I >> can access both... > > Do you have examples? > > Fabian, can you investigate? > >> >> 4. Registration of HTTP does not work for some reason... do not think >> it is a new problem. >> >> 5. Registration using HTTPS produces a dialog with the following content: >> >> @ENGINENAME@ Fingerprint >> TBD >> ... >> >> 6. Saving does not configure vdsm-reg.conf nor >> starting it. > > These 3 -- yes, there are a number of things broken on the page. I > filed a bug over the weekend: > > https://bugzilla.redhat.com/show_bug.cgi?id=964320 Mike/Alon Should I start from this point? -- Cheers Douglas From fabiand at redhat.com Tue May 21 10:34:27 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Tue, 21 May 2013 12:34:27 +0200 Subject: [node-devel] RC for oVirt Node 3.0.0 is now available In-Reply-To: <519A1129.9070002@redhat.com> References: <51965700.5040504@redhat.com> <766183827.2397987.1369039695708.JavaMail.root@redhat.com> <519A1129.9070002@redhat.com> Message-ID: <1369132467.2645.1.camel@fdeutsch-laptop.local> Am Montag, den 20.05.2013, 08:03 -0400 schrieb Mike Burns: > On 05/20/2013 04:48 AM, Alon Bar-Lev wrote: > > > > > > ----- Original Message ----- > >> From: "Mike Burns" > >> To: "node-devel" , announce at ovirt.org > >> Sent: Friday, May 17, 2013 7:12:48 PM > >> Subject: [node-devel] RC for oVirt Node 3.0.0 is now available > >> > >> What can I test? > >> You can focus on hardware support, package integration, the > >> installation (all paths) and the TUI. > > > > Hi! > > Thanks for the testing Alon! Yes! Thanks for testing. > > 3. I don't understand the difference of gray and non gray fields... I can access both... > > Do you have examples? > > Fabian, can you investigate? Sure. Alon, one example I could find were "options", e.g. on the NIC details page (where you set the bootprotocol of a nic etc) the options were also gray (instead of black, to signal that you can change them). It is intended - and it widely is this way - that gray fields can not be edited/changed. Have you got another example of a field which is gray and can be edited/changed? Thanks! fabian From fabiand at redhat.com Tue May 21 11:08:37 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Tue, 21 May 2013 13:08:37 +0200 Subject: [node-devel] RC for oVirt Node 3.0.0 is now available In-Reply-To: <1369132467.2645.1.camel@fdeutsch-laptop.local> References: <51965700.5040504@redhat.com> <766183827.2397987.1369039695708.JavaMail.root@redhat.com> <519A1129.9070002@redhat.com> <1369132467.2645.1.camel@fdeutsch-laptop.local> Message-ID: <1369134517.2645.2.camel@fdeutsch-laptop.local> Am Dienstag, den 21.05.2013, 12:34 +0200 schrieb Fabian Deutsch: > Am Montag, den 20.05.2013, 08:03 -0400 schrieb Mike Burns: > > On 05/20/2013 04:48 AM, Alon Bar-Lev wrote: > > > > > > > > > ----- Original Message ----- > > >> From: "Mike Burns" > > >> To: "node-devel" , announce at ovirt.org > > >> Sent: Friday, May 17, 2013 7:12:48 PM > > >> Subject: [node-devel] RC for oVirt Node 3.0.0 is now available > > >> > > >> What can I test? > > >> You can focus on hardware support, package integration, the > > >> installation (all paths) and the TUI. > > > > > > Hi! > > > > Thanks for the testing Alon! > > Yes! Thanks for testing. > > > > > > 3. I don't understand the difference of gray and non gray fields... I can access both... > > > > Do you have examples? > > > > Fabian, can you investigate? > > Sure. > Alon, > one example I could find were "options", e.g. on the NIC details page > (where you set the bootprotocol of a nic etc) the options were also gray > (instead of black, to signal that you can change them). > It is intended - and it widely is this way - that gray fields can not be > edited/changed. > Have you got another example of a field which is gray and can be > edited/changed? Checkboxes had the same problem. fabian > Thanks! > fabian > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From 358127112 at qq.com Tue May 21 02:06:20 2013 From: 358127112 at qq.com (=?gb18030?B?0e68w8P6?=) Date: Tue, 21 May 2013 10:06:20 +0800 Subject: [node-devel] help Message-ID: hello,ovirt I have something to ask,how to create new users for ovirt engine? 2013-May-21, 10:01:01 Failed to run VM vm01 (User: admin at internal). 4a19395b 2013-May-21, 10:01:01 Failed to run VM vm01 on Host node03. 4a19395b 2013-May-21, 10:01:01 VM vm01 is down. Exit message: internal error client socket is closed. How to solve this?Thank you! -------------- next part -------------- An HTML attachment was scrubbed... URL: From mburns at redhat.com Tue May 21 12:09:45 2013 From: mburns at redhat.com (Mike Burns) Date: Tue, 21 May 2013 08:09:45 -0400 Subject: [node-devel] help In-Reply-To: References: Message-ID: <519B6409.1090305@redhat.com> moving this to the users list (bcc node-devel to end the thread there) On 05/20/2013 10:06 PM, ??? wrote: > hello,ovirt > I have something to ask,how to create new users for ovirt engine? > 2013-May-21, 10:01:01 Failed to run VM vm01 (User: > admin at internal). 4a19395b > 2013-May-21, 10:01:01 Failed to run VM vm01 on Host node03. 4a19395b > 2013-May-21, 10:01:01 VM vm01 is down. Exit message: internal error > client socket is closed. > How to solve this?Thank you! > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel > From mburns at redhat.com Tue May 21 14:52:43 2013 From: mburns at redhat.com (Mike Burns) Date: Tue, 21 May 2013 10:52:43 -0400 Subject: [node-devel] oVirt Node Weekly Meeting Minutes -- 2013-05-21 Message-ID: <519B8A3B.3080908@redhat.com> Minutes: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-21-14.02.html Minutes (text): http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-21-14.02.txt Log: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-21-14.02.log.html ================================= #ovirt: oVirt Node Weekly Meeting ================================= Meeting started by mburns at 14:02:29 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-21-14.02.log.html . Meeting summary --------------- * agenda (mburns, 14:02:36) * 3.0.0 updates/plans (mburns, 14:04:42) * future plans/features (mburns, 14:04:49) * Node 3.0.0 release (mburns, 14:06:53) * RC spun on Friday (2013-05-17) (mburns, 14:07:35) * new patches fixing compatibility with distros using python 2.6 (EL6 and derivatives) (mburns, 14:07:56) * targeting new build for Thursday (2013-05-23) (mburns, 14:09:13) * systemd update fixed some issues in the beta build (mburns, 14:09:43) * ovirt-node-plugin-vdsm initial build posted as well (mburns, 14:10:02) * some issues with registration due to bugs in the engine_page logic (mburns, 14:10:15) * vdsm plugin is part of the oVirt release, so not under pressure to get fixed for node 3.0.0 GA (mburns, 14:10:44) * f19 needs some additional patches posted (mburns, 14:13:26) * may need update release for 3.0.0 to add F19 support (mburns, 14:13:45) * ovirt.debug.log will move to /var/log and be rotated (due for 3.0.0 RC) (mburns, 14:24:26) * puppet plugin will be included in 3.0.0 RC2 (mburns, 14:24:39) * cleanup of edit node manifests and manifest diffs will be in 3.0.0 RC2 (mburns, 14:24:56) * future plans/features (mburns, 14:25:28) * engine has a feature to create the management network itself (mburns, 14:26:08) * this has an implicit requirement that the device being used is not a bridge device since engine supports bridgeless networks (mburns, 14:26:51) * this requirement currently cannot be met by ovirt-node (mburns, 14:27:04) * plan is to investigate for 3.1 (mburns, 14:27:15) * initial design: make a configuration option that can be set by a plugin to create/not create the bridge (mburns, 14:27:44) * default configuration would be to create the bridge (mburns, 14:28:39) * need to check for where we make assumption of a bridged network (mburns, 14:28:49) * also need to add a configuration for locking out the network management locally (mburns, 14:29:21) * so that the vdsm plugin can lock it without having to depend on finding a bridge named ovirtmgmt (mburns, 14:29:39) * use case for bridgeless management network -- a system with multiple nics where vms only run on the non-management nic (mburns, 14:30:21) * background discussion is on the arch at ovirt.org list (mburns, 14:31:12) * Networking (mburns, 14:31:52) * somewhat related to the previous, but we may want to re-design some of the networking setup (mburns, 14:32:15) * this is somewhat to make it more modular (mburns, 14:32:38) * there is hesitation to making these changes until the NetworkManager bridge support is in (mburns, 14:32:57) * (currently supposed to land in F19) (mburns, 14:33:07) * something to consider doing if it can be done in such a way that we can simply replace calls with calls to NM api (mburns, 14:33:44) * otherwise, i'd rather wait for this support to land in Fedora (mburns, 14:34:06) * also -- unknown if EL will get this support or not (mburns, 14:34:28) * Installation flow (mburns, 14:35:38) * need to rework some of the installation flow (mburns, 14:35:48) * make it more modular so that new things can be easily plugged in (mburns, 14:36:19) * things like plugins, iscsi, different flows, puppet, etc (mburns, 14:37:05) * also need to make the backend more modular and debuggable (mburns, 14:37:26) * this can probably start now and focus on modularizing and isolating (mburns, 14:40:27) * Logging (mburns, 14:40:41) * need to get logging cleaner and easier to read (mburns, 14:40:54) * make sure that everything we want logged gets logged (mburns, 14:41:11) * make it so that we can change logging level for additional debugging (mburns, 14:41:29) * make all components log correctly (and distinctly) (mburns, 14:41:59) * also, would be good to get things that we end up needing if certain areas fail (mburns, 14:47:11) * for example -- if an upgrade fails, would be good to perhaps get the state of various things (blkid, labels, etc) (mburns, 14:47:16) * it may be that we need to add a sos plugin or something (mburns, 14:47:23) * some libvirt logging seems spurious at the moment -- rbarry to work with libvirt/vdsm people to debug (mburns, 14:47:40) * storage config (mburns, 14:47:49) * we may want to investigate the work being done by the anaconda team with blivet (mburns, 14:48:09) * perhaps some of the anaconda work for bootloaders as well (mburns, 14:49:46) * also some generic modularizing and isolating of the various functions (mburns, 14:50:21) Meeting ended at 14:51:52 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mburns (126) * fabiand (51) * ovirtbot (7) * jboggs (6) * rbarry (3) * papabur (1) * jbelka (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From mburns at redhat.com Thu May 23 11:58:58 2013 From: mburns at redhat.com (Mike Burns) Date: Thu, 23 May 2013 07:58:58 -0400 Subject: [node-devel] [3.3 release process] feature freeze readiness In-Reply-To: <519DF477.9000300@redhat.com> References: <519DF477.9000300@redhat.com> Message-ID: <519E0482.9000803@redhat.com> On 05/23/2013 06:50 AM, Moran Goldboim wrote: > we are about a week away from feature freeze of oVirt 3.3 (May 31st). In > order to be able to converge to this date we would need your help > (feature owners) understanding feature/overall status. > > I have updated OVirt 3.3 release-management page [1] with features > status table [2]. having this complete table filled will help us > determine this version readiness. > > a test page addition is needed for each feature (link through the table) > - this will enable us good visibility and testing of those features in > test-day. > > I have left the old 3.3 feature overview -just below the new table, to > make sure i have taken all needed from that info. please verify all you > need is in the table, since this part will be deleted on feature freeze > readiness review - next Wednesday meeting. > > completing filling this table should be done no later than Tuesday May > 28th. An example of a testing chart is available on [4] Mike [4] http://www.ovirt.org/Features/Node_vdsm_plugin#Testing > > Thanks. > > [1]http://www.ovirt.org/OVirt_3.3_release-management > [2]http://www.ovirt.org/OVirt_3.3_release-management#Features_Status_Table > [3]http://www.ovirt.org/OVirt_3.3_release-management#Features > > _______________________________________________ > Arch mailing list > Arch at ovirt.org > http://lists.ovirt.org/mailman/listinfo/arch From mgoldboi at redhat.com Thu May 23 10:50:31 2013 From: mgoldboi at redhat.com (Moran Goldboim) Date: Thu, 23 May 2013 13:50:31 +0300 Subject: [node-devel] [3.3 release process] feature freeze readiness Message-ID: <519DF477.9000300@redhat.com> we are about a week away from feature freeze of oVirt 3.3 (May 31st). In order to be able to converge to this date we would need your help (feature owners) understanding feature/overall status. I have updated OVirt 3.3 release-management page [1] with features status table [2]. having this complete table filled will help us determine this version readiness. a test page addition is needed for each feature (link through the table) - this will enable us good visibility and testing of those features in test-day. I have left the old 3.3 feature overview -just below the new table, to make sure i have taken all needed from that info. please verify all you need is in the table, since this part will be deleted on feature freeze readiness review - next Wednesday meeting. completing filling this table should be done no later than Tuesday May 28th. Thanks. [1]http://www.ovirt.org/OVirt_3.3_release-management [2]http://www.ovirt.org/OVirt_3.3_release-management#Features_Status_Table [3]http://www.ovirt.org/OVirt_3.3_release-management#Features From fabiand at redhat.com Thu May 23 14:20:59 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Thu, 23 May 2013 16:20:59 +0200 Subject: [node-devel] Looking at allowing different network topologies in Node Message-ID: <1369318859.7449.24.camel@fdeutsch-laptop.local> Hey, during a discussion on the arch list (and a request by the Engine team) the need for a node without it's "default bridge" was raised. Typically Node is creating a bridge for the to be configured NIC (which results in a bridge named "br$SLAVE_IFNAME", where SLAVE_IFNAME is the name of the actual NIC). It's a central assumption in Node that such a bridge exists, and this is reflected in the number of places where this bridge plays a role. - networking - * Obviously is the code for creating the bridge just handling this topology. * The function get_system_nics() does a lot of information merging to build a coherent model (so to merge the SLAVE NIC and bridge informations into one model) * The cleaning of the current network setup expects the bridge * This module is used in the installer and setup - init/stateless - * The stateless code has it's own logic to setup networking (using the bridge topology). * The iscsi code is also reusing infos related to the bridge - tui - * The tui code - which is also a start to consolidate and refactor the existing code base - has similar problems as the networking module above. So, the code related to "the bridge" is large areas of Node's code base. And central points like all auto-installation paths and the whole TUI , especially the network configuration. Surely it's possible to change the code to have the current behavior as default (to have backwards compatibility) and to switch to the no-bridge-but-single-NIC topology using some flag. But this change is rather invasive and testing the changes is another big challenge. In general I don't have any objections in allowing the simplified topology. Greetings fabian From 120828490 at qq.com Fri May 24 04:50:09 2013 From: 120828490 at qq.com (=?gb18030?B?zOzM7NDQtq8=?=) Date: Fri, 24 May 2013 12:50:09 +0800 Subject: [node-devel] node-devel Digest, Vol 21, Issue 8 Message-ID: >Hi all My environment is based oVirt Node Hypervisor 2.6.1, comes to the hardware installation ovirt-node server and enter admin into the background (. / Usr / libexec / ovirt-config-setup), after configuring the network and access to ovirt-engine rear , click on "Network" printed on the screen after the following prompt char: "parse_file:reading '/lib/udev/rules.d/71-biosdevname.rules' as rules file parse_file:reading '/lib/udev/rules.d/75-net-description.rules' as rules file parse_file:reading '/lib/udev/rules.d/75-tty-description.rules' as rules file parse_file:reading '/lib/udev/rules.d/79-fstab_import.rules' as rules file parse_file:reading '/lib/udev/rules.d/80-tuned-iosched.rules' as rules file parse_file:reading '/lib/udev/rules.d/90-hal.rules' as rules file ...................................../95-key.................. ...................................../95-udev-late.................. ...................................../95-keymap.................. ...................................../99-live-mount.................. ...................................../99-root.................. udev_rules_new:temporary index used 18680 bytes unable to open device '/sys/class/net' /bin/sh :vdsmdummy:command not found I do not know newt or a python-urwid library issues, or other problem, ask people to help me solve cattle pointing ah. Thank you very much -------------- next part -------------- An HTML attachment was scrubbed... URL: From 120828490 at qq.com Fri May 24 04:50:33 2013 From: 120828490 at qq.com (=?gb18030?B?zOzM7NDQtq8=?=) Date: Fri, 24 May 2013 12:50:33 +0800 Subject: [node-devel] node-devel Digest, Vol 21, Issue 12 Message-ID: >Hi all My environment is based oVirt Node Hypervisor 2.6.1, comes to the hardware installation ovirt-node server and enter admin into the background (. / Usr / libexec / ovirt-config-setup), after configuring the network and access to ovirt-engine rear , click on "Network" printed on the screen after the following prompt char: "parse_file:reading '/lib/udev/rules.d/71-biosdevname.rules' as rules file parse_file:reading '/lib/udev/rules.d/75-net-description.rules' as rules file parse_file:reading '/lib/udev/rules.d/75-tty-description.rules' as rules file parse_file:reading '/lib/udev/rules.d/79-fstab_import.rules' as rules file parse_file:reading '/lib/udev/rules.d/80-tuned-iosched.rules' as rules file parse_file:reading '/lib/udev/rules.d/90-hal.rules' as rules file ...................................../95-key.................. ...................................../95-udev-late.................. ...................................../95-keymap.................. ...................................../99-live-mount.................. ...................................../99-root.................. udev_rules_new:temporary index used 18680 bytes unable to open device '/sys/class/net' /bin/sh :vdsmdummy:command not found I do not know newt or a python-urwid library issues, or other problem, ask people to help me solve cattle pointing ah. Thank you very much -------------- next part -------------- An HTML attachment was scrubbed... URL: From mburns at redhat.com Fri May 24 13:33:07 2013 From: mburns at redhat.com (Mike Burns) Date: Fri, 24 May 2013 09:33:07 -0400 Subject: [node-devel] node-devel Digest, Vol 21, Issue 12 In-Reply-To: References: Message-ID: <519F6C13.8010703@redhat.com> This particular bug is fixed in the master branch by this commit[1]. Fabian, A new vdsm is supposed to come out in the next week or so. We should probably backport this fix and spin a new 2.6.x iso. Mike [1] http://gerrit.ovirt.org/#/c/13872/ On 05/24/2013 12:50 AM, ???? wrote: > >Hi all > > My environment is based oVirt Node Hypervisor 2.6.1, comes to the > hardware installation ovirt-node server and enter admin into the > background (. / Usr / libexec / ovirt-config-setup), after configuring > the network and access to ovirt-engine rear , click on "Network" printed > on the screen after the following prompt char: > > "parse_file:reading '/lib/udev/rules.d/71-biosdevname.rules' as rules file > parse_file:reading '/lib/udev/rules.d/75-net-description.rules' as rules > file > parse_file:reading '/lib/udev/rules.d/75-tty-description.rules' as rules > file > parse_file:reading '/lib/udev/rules.d/79-fstab_import.rules' as rules file > parse_file:reading '/lib/udev/rules.d/80-tuned-iosched.rules' as rules file > parse_file:reading '/lib/udev/rules.d/90-hal.rules' as rules file > ...................................../95-key.................. > ...................................../95-udev-late.................. > ...................................../95-keymap.................. > ...................................../99-live-mount.................. > ...................................../99-root.................. > udev_rules_new:temporary index used 18680 bytes > unable to open device '/sys/class/net' > /bin/sh :vdsmdummy:command not found > > I do not know newt or a python-urwid library issues, or other problem, > ask people to help me solve cattle pointing ah. Thank you very much > > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel > From fabiand at redhat.com Fri May 24 14:00:42 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Fri, 24 May 2013 16:00:42 +0200 Subject: [node-devel] node-devel Digest, Vol 21, Issue 12 In-Reply-To: <519F6C13.8010703@redhat.com> References: <519F6C13.8010703@redhat.com> Message-ID: <1369404042.29735.1.camel@fdeutsch-laptop.local> Am Freitag, den 24.05.2013, 09:33 -0400 schrieb Mike Burns: > This particular bug is fixed in the master branch by this commit[1]. > > Fabian, A new vdsm is supposed to come out in the next week or so. We > should probably backport this fix and spin a new 2.6.x iso. Yes, I think the new vdsm release is a good point to do another release. - fabian > Mike > > [1] http://gerrit.ovirt.org/#/c/13872/ > > On 05/24/2013 12:50 AM, ???? wrote: > > >Hi all > > > > My environment is based oVirt Node Hypervisor 2.6.1, comes to the > > hardware installation ovirt-node server and enter admin into the > > background (. / Usr / libexec / ovirt-config-setup), after configuring > > the network and access to ovirt-engine rear , click on "Network" printed > > on the screen after the following prompt char: > > > > "parse_file:reading '/lib/udev/rules.d/71-biosdevname.rules' as rules file > > parse_file:reading '/lib/udev/rules.d/75-net-description.rules' as rules > > file > > parse_file:reading '/lib/udev/rules.d/75-tty-description.rules' as rules > > file > > parse_file:reading '/lib/udev/rules.d/79-fstab_import.rules' as rules file > > parse_file:reading '/lib/udev/rules.d/80-tuned-iosched.rules' as rules file > > parse_file:reading '/lib/udev/rules.d/90-hal.rules' as rules file > > ...................................../95-key.................. > > ...................................../95-udev-late.................. > > ...................................../95-keymap.................. > > ...................................../99-live-mount.................. > > ...................................../99-root.................. > > udev_rules_new:temporary index used 18680 bytes > > unable to open device '/sys/class/net' > > /bin/sh :vdsmdummy:command not found > > > > I do not know newt or a python-urwid library issues, or other problem, > > ask people to help me solve cattle pointing ah. Thank you very much > > > > > > > > _______________________________________________ > > node-devel mailing list > > node-devel at ovirt.org > > http://lists.ovirt.org/mailman/listinfo/node-devel > > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From mgoldboi at redhat.com Tue May 28 14:01:11 2013 From: mgoldboi at redhat.com (Moran Goldboim) Date: Tue, 28 May 2013 17:01:11 +0300 Subject: [node-devel] [3.3 release process] feature freeze readiness In-Reply-To: <519DF477.9000300@redhat.com> References: <519DF477.9000300@redhat.com> Message-ID: <51A4B8A7.4070809@redhat.com> On 05/23/2013 01:50 PM, Moran Goldboim wrote: > we are about a week away from feature freeze of oVirt 3.3 (May 31st). > In order to be able to converge to this date we would need your help > (feature owners) understanding feature/overall status. > > I have updated OVirt 3.3 release-management page [1] with features > status table [2]. having this complete table filled will help us > determine this version readiness. > > a test page addition is needed for each feature (link through the > table) - this will enable us good visibility and testing of those > features in test-day. > > I have left the old 3.3 feature overview -just below the new table, to > make sure i have taken all needed from that info. please verify all > you need is in the table, since this part will be deleted on feature > freeze readiness review - next Wednesday meeting. > > completing filling this table should be done no later than Tuesday May > 28th. > > Thanks. > > [1]http://www.ovirt.org/OVirt_3.3_release-management > [2]http://www.ovirt.org/OVirt_3.3_release-management#Features_Status_Table > > [3]http://www.ovirt.org/OVirt_3.3_release-management#Features > > _______________________________________________ > Arch mailing list > Arch at ovirt.org > http://lists.ovirt.org/mailman/listinfo/arch Thanks for everyone who updated their status on the table. Still there are missing features around virt, infra, storage and sla, please complete statuses on this missing features today so we can attend to understand the release status tomorrow's meeting. Thanks. From mburns at redhat.com Tue May 28 14:56:17 2013 From: mburns at redhat.com (Mike Burns) Date: Tue, 28 May 2013 10:56:17 -0400 Subject: [node-devel] oVirt Node Weekly Meeting Minutes -- 2013-05-28 Message-ID: <51A4C591.8030101@redhat.com> Minutes: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-28-14.00.html Minutes (text): http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-28-14.00.txt Log: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-28-14.00.log.html ================================= #ovirt: oVirt Node Weekly Meeting ================================= Meeting started by mburns at 14:00:21 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2013/ovirt.2013-05-28-14.00.log.html . Meeting summary --------------- * agenda (mburns, 14:00:42) * bug review (mburns, 14:00:46) * release status (mburns, 14:00:53) * patch process update (mburns, 14:01:02) * 3.0 bug review (mburns, 14:04:56) * LINK: https://bugzilla.redhat.com/showdependencytree.cgi?id=947475&hide_resolved=1 (mburns, 14:05:05) * password changes not working correctly (mburns, 14:07:01) * workaround/fix should be available later today (mburns, 14:07:09) * https://bugzilla.redhat.com/show_bug.cgi?id=922593 (mburns, 14:07:25) * issue is blocked by changes in dracut between el6 and f18 (mburns, 14:08:51) * solution should be posted today (mburns, 14:08:57) * patch review (mburns, 14:10:28) * LINK: http://gerrit.ovirt.org/#/q/status:open+project:ovirt-node,n,z (mburns, 14:10:36) * 16 patches pending (mburns, 14:10:55) * 1 is a duplicate that needs to be dropped (http://gerrit.ovirt.org/#/c/15015/) (mburns, 14:11:19) * http://gerrit.ovirt.org/#/c/14737/ (mburns, 14:12:15) * ACTION: mburns to follow up on concerns with approach of this patch (mburns, 14:17:40) * overall -- not a blocker, but a nice to have (mburns, 14:17:55) * http://gerrit.ovirt.org/#/c/15045/ (mburns, 14:18:03) * fileConfig for logging (mburns, 14:18:09) * blocker for 3.0 release (mburns, 14:18:16) * code review +1 (mburns, 14:18:22) * http://gerrit.ovirt.org/#/c/15082/ (mburns, 14:20:22) * log rotate for ovirt node logs (mburns, 14:20:33) * blocker for 3.0 (mburns, 14:20:39) * needs review (mburns, 14:20:48) * ACTION: rbarry to review logging patches (mburns, 14:21:31) * http://gerrit.ovirt.org/#/c/14962/ (mburns, 14:21:40) * tuned configuration (mburns, 14:21:46) * not a blocker, but nice to have (mburns, 14:21:50) * mburns has followup work to do (mburns, 14:21:56) * ACTION: mburns to update patch 14962 (mburns, 14:22:07) * http://gerrit.ovirt.org/#/c/14491/ (mburns, 14:22:29) * reboot task running async (mburns, 14:22:37) * code review -1 (mburns, 14:22:43) * ACTION: jboggs to followup and update patch (mburns, 14:22:53) * http://gerrit.ovirt.org/#/c/14958/ (mburns, 14:23:30) * catch upgrade exceptions (mburns, 14:23:42) * code-review -1 (mburns, 14:23:44) * ACTION: jboggs to followup and update (mburns, 14:23:50) * http://gerrit.ovirt.org/#/c/15079/ (mburns, 14:24:13) * Draft patch (mburns, 14:24:19) * related to 966354, blocker for 3.0 (mburns, 14:25:01) * update expected today (mburns, 14:25:08) * http://gerrit.ovirt.org/#/c/15015/ <-- duplicate of 14737 (mburns, 14:25:28) * http://gerrit.ovirt.org/#/c/14600/ (mburns, 14:25:39) * code review -1 (mburns, 14:25:43) * needs to be abandoned -- obsoleted by new patch (mburns, 14:25:55) * ACTION: jboggs to abandon 14600 (mburns, 14:26:18) * http://gerrit.ovirt.org/#/c/13089/ (mburns, 14:26:23) * awaiting feedback from submitter (mburns, 14:26:30) * not a blocker (mburns, 14:26:34) * http://gerrit.ovirt.org/#/c/14664/ (mburns, 14:26:53) * puppet plugin (mburns, 14:26:57) * rbarry close to making it work with automake (mburns, 14:28:28) * should be updated today (mburns, 14:28:37) * http://gerrit.ovirt.org/#/c/14956/ (mburns, 14:28:49) * upgrade log file name (mburns, 14:28:55) * awaiting feedback from mburns (mburns, 14:29:01) * ACTION: mburns to give feedback on 14956 (mburns, 14:29:16) * http://gerrit.ovirt.org/#/c/14970/ (mburns, 14:29:31) * fix edit-node file name when nvr isn't correct (mburns, 14:29:50) * currently +1 in code review (mburns, 14:30:00) * ACTION: jboggs to review and ack/nack 14970 (mburns, 14:30:28) * http://gerrit.ovirt.org/#/c/15018/ (mburns, 14:30:30) * log dir sync with iso on boot (mburns, 14:30:42) * needs testing/review/update from mburns (mburns, 14:30:54) * not a blocker (mburns, 14:31:03) * ACTION: mburns to update 15018 (mburns, 14:31:19) * http://gerrit.ovirt.org/#/c/14960/ (mburns, 14:31:32) * upgrade lock file (mburns, 14:31:40) * needs review (mburns, 14:31:47) * ACTION: jboggs to update the patch (mburns, 14:32:19) * blocker for 3.0 (mburns, 14:32:39) * http://gerrit.ovirt.org/#/c/13625/ (mburns, 14:32:47) * old patch for partition table removal during re-install (mburns, 14:33:02) * not a blocker, but should be reviewed/updated/abandoned (mburns, 14:33:14) * currently code-review -1 (mburns, 14:33:24) * ACTION: fabiand to look at 13625 (mburns, 14:33:44) * release status (mburns, 14:34:20) * going to slip out beyond 31-May (mburns, 14:34:35) * IDEA: (mburns, 14:36:13) * IDEA: get all blocker bugs and patches resolved by EOD thursday (mburns, 14:36:32) * IDEA: build new beta/RC on Friday (mburns, 14:36:46) * IDEA: target release for late next week (mburns, 14:36:57) * AGREED: resolve issues by thursday eod, build friday, release next week (mburns, 14:37:43) * ACTION: fabiand to update dates on release management (mburns, 14:38:02) * patch process update (mburns, 14:38:23) * there is logic in gerrit for marking patches post/modified when they go through certain stages (mburns, 14:39:03) * based on Bug-Url in the commit message (mburns, 14:39:14) * LINK: http://lists.ovirt.org/pipermail/infra/2013-May/003154.html (mburns, 14:39:29) * AGREED: -- add Bug-url to all new patches (mburns, 14:41:12) * Other Topics (mburns, 14:42:31) * urwid support in el6 (mburns, 14:42:51) * el6 and derivatives (centos, scientific linux, etc) have an old version of python-urwid (mburns, 14:43:24) * which is incompatible with some aspects of the new tui codebase (mburns, 14:43:40) * it's an uphill battle to get urwid updated in el6 and derivatives (and probably at least 6 months for derivatives) (mburns, 14:44:21) * ACTION: jboggs to file bug (mburns, 14:51:58) * ACTION: fabiand to investigate whether we can work around these issues (mburns, 14:52:09) * Other Topics (mburns, 14:53:06) Meeting ended at 14:54:50 UTC. Action Items ------------ * mburns to follow up on concerns with approach of this patch * rbarry to review logging patches * mburns to update patch 14962 * jboggs to followup and update patch * jboggs to followup and update * jboggs to abandon 14600 * mburns to give feedback on 14956 * jboggs to review and ack/nack 14970 * mburns to update 15018 * jboggs to update the patch * fabiand to look at 13625 * fabiand to update dates on release management * jboggs to file bug * fabiand to investigate whether we can work around these issues Action Items, by person ----------------------- * fabiand * fabiand to look at 13625 * fabiand to update dates on release management * fabiand to investigate whether we can work around these issues * jboggs * jboggs to followup and update patch * jboggs to followup and update * jboggs to abandon 14600 * jboggs to review and ack/nack 14970 * jboggs to update the patch * jboggs to file bug * mburns * mburns to follow up on concerns with approach of this patch * mburns to update patch 14962 * mburns to give feedback on 14956 * mburns to update 15018 * rbarry * rbarry to review logging patches * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mburns (165) * fabiand (37) * Yamaksi_ (14) * jboggs (14) * jvandewege (8) * rbarry (6) * ovirtbot (5) * RobertM (1) * fabiand_afk (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From dneary at redhat.com Wed May 29 07:55:30 2013 From: dneary at redhat.com (Dave Neary) Date: Wed, 29 May 2013 09:55:30 +0200 Subject: [node-devel] [3.3 release process] feature freeze readiness In-Reply-To: <51A4B8A7.4070809@redhat.com> References: <519DF477.9000300@redhat.com> <51A4B8A7.4070809@redhat.com> Message-ID: <51A5B472.3030509@redhat.com> Hi, On 05/28/2013 04:01 PM, Moran Goldboim wrote: > Thanks for everyone who updated their status on the table. > Still there are missing features around virt, infra, storage and sla, > please complete statuses on this missing features today so we can attend > to understand the release status tomorrow's meeting. The features still missing a status and owner are: * GlusterFS Storage Domain * Allow resign/force re-election of SPM Also, a number of features have not set a release priority - especially for red and orange features, we need to know whether the feature is considered "must"/"should"/"optional" for 3.3, because those are the ones that will end up delaying a release. * RAM snapshots * noVNC console * Non Plugin RDP Invocation * Instance Types After that, we can start looking at red flag features to help set the release date. A few things jumped out at me: == Red features marked as Must For each of these, we need an estimate of how long the feature will take to complete - these will almost certainly delay the release. * Multiple Gateways * Edit Connection Properties * oVirt scheduler * Scheduling API * Networking QoS Next priority is the orange musts - one in particular jumps out at me: "Watchdog engine support" has a comment "REST API missing" - which sounds ominous. Thanks to everyone for filling this out! And thanks to Moran for taking the lead on this, it's very useful. Cheers, Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From fabiand at redhat.com Fri May 31 11:50:22 2013 From: fabiand at redhat.com (Fabian Deutsch) Date: Fri, 31 May 2013 13:50:22 +0200 Subject: [node-devel] ovirt-node-devel-check to check your patches Message-ID: <1370001022.2596.13.camel@fdeutsch-laptop.local> Hey, there is now a job ovirt-node-devel-check [0] which runs make check-local in the src/ dir of our code, to do some basic checks. Jenkins will report any failed run back to gerrit and review it with -1. This is another step in the make-Node-testing-fun efforts. Greetings fabian -- [0] http://jenkins.ovirt.org/view/ovirt_node/job/ovirt-node-devel-check/