13:00:41 #startmeeting 13:00:41 Meeting started Wed Mar 12 13:00:41 2014 UTC. The chair is alinefm. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:41 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:00:42 #meetingname scrum 13:00:42 The meeting name has been set to 'scrum' 13:00:59 #info Agenda 1) Status 2) Open discussion 13:00:59 anything else? 13:02:16 so... 13:02:17 #topic Status 13:02:17 #info Please provide your status using the #info command: #info 13:03:10 #info alinefm closed issues #301, #330, #312 13:03:57 #info alinefm fix extend logical pool: use "lsblk" command instead of "blkid" to verify the disk exists in the system. 13:04:22 #info alinefm set default flags for virDomain.state() function 13:04:41 #info rotru have worked in several Bugzilla tickets and other Kimchi bugs. Some BZ fixed: #100954 (fixed Network window buttons); #103632 (changed window to create Template with remote ISOs); #104940 (Kimchi was not able to create a vm which use iSCSI pool, fixed) 13:05:13 #info royce get volume ref number merged, fixed vm cannot start on logical pool problem, about using raw format and logical path error usage 13:05:37 #info vianac closed bug #200, sent patchsets "Rebuild .po files when running "make", "Do not show a success msg when creating a template" and "Fix help Makefile" 13:06:13 #info rotru investigated and fixed Issue #339: Kimchi fails when deactivate Storage Pools that are not persistent 13:07:02 #info royce sent patch of work around nfs permission of creating vm, took care of other little bugs such as 4 ide device limitation 13:08:47 royce, how is going the 4 IDE device limitation? 13:08:59 I mean, your investigation 13:09:41 #info AdamKingIT1 fixed issue 294, fixed cdrom patch, fixed ajax error propagation, improved guest action menu, reviewed host repo & sw update ++ 13:09:50 #info shaohef send network address check patch and iso permission check patch 13:10:57 This is limitation of IDE is each controller have two IDE interfaces and each interface can carry two devices. Thus one IDE controller can have up to 4 devices.REF: http://computer.howstuffworks.com/ide4.htm 13:10:57 #info AdamKingIT1 triaged issues. Opened a couple new ones. 13:10:57 I assume this is a limitation at most platforms, but if we really want to fix this, we can add an extra controller to guest xml, I would suggest an alert for just 4 devices can be supportted, is that acceptable? 13:11:03 #info danielhb working in "kimchi runs as root" patch. Trying a RPC approach. Will try to do a different approach if stuck 13:12:35 royce: I remember seems x86 has this limitation. 13:12:51 iirc its part of the definition of IDE 13:12:54 royce, yes - we should also add doc for it 13:12:56 What about using SATA? 13:13:14 scsi device will work. 13:13:22 I investigated change the driver to SCSI, but libvirt returns error of SCSI driver 13:13:36 scsi-hba + scsi disks. 13:14:10 hard to believe libvirt doesn't support scsi 13:14:11 Or virt-scsi? 13:15:09 it is not libvirt does not support scsi 13:15:13 AdamKingIT1, I think it is because of Qemu's short of scsi support. 13:16:02 wait a min, I will reproduce the error 13:16:07 But qemu upstream should support them. 13:16:30 What about SATA? 13:16:58 ming_ by scsi-hba +scsi disks, how do we reflect it in libvirt xml? 13:17:45 AdamKingIT1, I don't know about SATA cdrom actually, does cdrom support this driver , ming_? 13:18:11 The physical CD in my kids computer is SATA 13:19:12 royce, not sure about SATA, But SCSI should work 13:19:16 In virt-manager they just support ide cdrom, but I will debug SCSI cdrom, too 13:19:41 maybe a limitation of qemu 13:20:15 As our disks are virtio disks, do we really want more than 4 cdroms? 13:21:36 royce, I don't think we need that much 13:22:03 the other advantage of non-IDE is we can eventually support hot-plug 13:22:11 royce, ming_, 4 seems much to me too 13:22:14 I don;t think IDE can support that 13:22:22 I am doing a test here 13:23:48 royce, ming_, AdamKingIT1, I've just changed "ide" to "sata" on guest xml and seems it worked 13:23:53 starting the guest now 13:24:01 AdamKingIT1: Maybe, if the chipset of qemu is too low, it will not support SATA. 13:24:38 alinefm, thanks, can you see the cdrom? 13:24:53 royce, a minute - starting the guest 13:24:55 -) 13:24:56 =) 13:25:35 My libvirtd crashed and cannot restart, I will paste the SCSI error later 13:27:16 royce, yeap! http://fpaste.org/84646/46308271/ 13:27:22 seems it really worked 13:27:32 royce, did you try sata? 13:27:52 I will try scsi, maybe it is a problem on some specific libvirt version 13:28:53 alinefm, I haven't, let me check how many sata devices we can carry 13:29:07 royce, failed with scsi here too: http://fpaste.org/84648/39463093/ 13:29:11 AdamKingIT1, ming_ ^ 13:30:05 alinefm, I got a diffrent error, but is that because your id set wrong? 13:30:15 can you check the controller section? 13:30:35 ops... changed the device unit and it worked 13:30:35 As you got Duplicate ID 'drive-scsi0-0-0' for drive 13:30:51 royce, yes - I changed it and now it works 13:31:02 booting the guest again 13:32:32 royce, http://fpaste.org/84650/31144139/ 13:32:49 royce, which distro and libvirt version are you using? 13:33:47 libvirt-bin 1.0.2-0ubuntu11.13.04.4 amd64 13:33:52 alinefm, how about lspci in your guest with scsi cdom devices? 13:35:07 royce, it seems your libvirt is a bit out of date. in FC20 is tmp@FC20-Kimchi kimchi]$ libvirtd --version 13:35:07 libvirtd (libvirt) 1.1.3.4 13:35:08 [tmp@FC20-Kimchi kimchi]$ 13:35:56 2014-03-11 10:00:00.916+0000: 1620: error : qemuBuildDriveStr:2258 : internal error SCSI controller only supports 1 bus 13:36:00 This is my error 13:36:44 rotru, I am with an older libvirt than you: 0.9.13-0ubuntu12.6 13:36:46 I don't have two SCSI bus actually 13:37:08 royce, let me see your xml 13:37:12 ming_, a min 13:37:33 ming_, my system becomes too slow with vm running =/ 13:37:38 be patient =) 13:37:58 alinefm: we have to get you a faster hampster 13:38:48 AdamKingIT1, I accept any donation =P 13:39:01 hahaha 13:39:18 13:39:18 13:39:18 13:39:18 13:39:18 13:39:18
13:39:20 13:39:52 ming_, http://fpaste.org/84652/31586139/ 13:40:05 royce, try change the bus to 0 13:40:14 and change the unit to 1 13:40:46 Alinefm, it seems that you get much scsi controllers 13:42:08 I will test it after scrum after reboot my desktop.... My libvirtd restart fails hundreds of times... 13:42:32 ok 13:42:38 Let's move on 13:42:39 let's move on 13:42:46 and we can continue after meeting if needed 13:42:54 #topic Open Discussion 13:43:06 what are the topics for today? 13:43:59 ok - I have one =) 13:44:06 today is the end of sprint 4 13:44:16 and then start the code freeze phase 13:44:26 I sent repository management patch and found PUT repository doesn't work, as I mentioned in my patch 13:44:33 Seems need a fix 13:44:48 hlwanghl, great! I will take a look on backend 13:45:06 hlwanghl, update UI is ready, right? 13:45:23 If I don't put the field enabled, it will work 13:45:33 Yes, I sent it just now 13:45:58 I can set cdrom as sata, and the vm can start. but the console report it can not find from CDROM. 13:46:11 Add loading icon and message when waiting for data 13:47:01 then it read from boot from hd. 13:47:22 hlwanghl, great! thanks 13:47:25 shaohef, =/ 13:47:47 is the sata drive lower in the boot order than the HD? 13:48:10 alinefm :) 13:48:23 Let's finish items for S4 13:48:52 AdamKingIT1: I set it higher. 13:48:55 I got a topic about the multi-thread in the front end. I found that when I tried to create and download the debugreport file, the front end contiguously to query the task state. 13:49:15 That will make the front-end frozen and can not switch to other pages. 13:49:34 alinefm: what does =/ mean? 13:49:48 shaohef, a sad emotion 13:49:56 same as =( 13:50:12 We do have async task support in the back end and how can we leverage that async task in the front end? 13:51:02 the async task will need to be polled for status updates, but maybe at a slower interval 13:51:18 ming_ I don't understand the situation, let me check with you tomorrow 13:51:31 :=( 13:51:52 JS is asynchronous in nature, I don't think there is such problem. 13:52:19 http://en.wikipedia.org/wiki/List_of_emoticons 13:53:10 AdamKingIT1, thanks! 13:53:25 hlwanggl, I mean the page stayed at the degbureport creating page and can not switch to other pages until the report was created successfully. 13:53:53 ming_, if you close the debug report creation window the task will continue con backend 13:54:00 ming_ that would indicate that its either making a sync request, or its polling with 0 wait 13:54:03 OK. You can click "x" to close it. 13:54:08 and you can switch to other tab without stop the debug report generation 13:54:33 ah, if you can close the window its probably not either of my guesses 13:54:39 AdamKingIT1, I will try, it seems that I didn't notuce the 'x' there. 13:54:57 s/notuce/notice 13:55:24 It's somewhat confused, though. User doesn't know whether the task is stoped if you close it 13:55:59 hlwanghl, yes - maybe we can add a message for it 13:56:26 "Closing this window will not stop the debug report generation" 13:56:29 or something like that 13:57:05 The ideal flow is: click x -> ask: stop task or just close window 13:57:32 hlwanghl, but we can not stop task on backend yet 13:57:50 Add we add support at back-end to allow stop a task like POST /task/1/cancel 13:58:04 Yes 13:58:25 Just an explanation to ming_ 13:58:30 ok 13:58:41 we just have 2 min and I'd like to share some info with you 13:58:55 in this code freeze phase we need to test kimchi in all supported distros 13:59:05 and make sure all feature are working properly there 13:59:18 I'd like to have focal points for each supported distro 13:59:34 any volunteers? =) 13:59:53 the focal point will be responsible to verify kimchi features, report bugs, etc... 14:00:17 basically, we need 4 focal points: for rhel, fedora, opensuse and ubuntu 14:00:59 I have ubuntu 13.04, what versions do we need alinefm? 14:01:08 Do we have matrix? 14:01:26 I can do test on FC20, FC19, FC18 14:01:32 royce, not yet - I am planning to create the matrix today 14:01:45 royce, but for ubuntu it would be 13.04 and 13.10 14:01:57 alinefm I'm using fedora 18 14:02:01 ming_, great! you can focus only on FC20 and FC19 14:02:06 FC18 is too old 14:02:17 OK, sure, I can download one 13.10 and try nested 14:02:35 We need someday to cover RHEL 7 14:02:51 s/someday/somebody 14:02:56 the tests can be done by everyone but I'd like the focal point to consolidate all results 14:03:10 ming_, rhel7 is not out yet 14:03:14 is it? 14:03:23 is there a beta? 14:03:23 Also, RHEL 7 beta is put. 14:03:57 royce, will you be the ubuntu focal point? 14:04:06 ming_, will you be the fedora focal point? 14:04:14 of course, alinefm 14:04:15 NP 14:04:19 need volunteers for rhel and opensuse 14:04:32 shaohef, ^ 14:05:08 We should do same for browsers. 14:05:15 The libvirt and qemu version of RHEL 6.5 is a bit obsolete. 14:05:22 FF, Safari, Chrome, IE 14:05:31 Yes AdamKingIT1 14:05:38 Browser focal? 14:05:45 AdamKingIT1, yeap 14:05:46 alinefm: OK 14:05:53 shaohef, which one do you prefer? 14:05:58 I have the browsers 14:06:04 (10:05:32 PM) alinefm: need volunteers for rhel and opensuse 14:06:05 (10:05:32 PM) alinefm: shaohef, ^ 14:06:14 any is OK 14:06:16 shaohef, rhel or opensuse? 14:06:45 shaohef, this is an obscure answer:P 14:06:53 I have access to all 4, though I rarely use Safari 14:06:55 one 哦发opensuse 14:07:06 one of rhel and opensuse ? 14:07:16 yes 14:07:16 rhel. 14:07:18 shaohef, choose one 14:07:20 ok =) 14:07:34 AdamKingIT1, hlwanghl, you can split the work 14:07:40 maybe 2 browser for each one 14:07:45 what do you think? 14:07:53 Which is easier to use? F18 is too old, I need a newer OS 14:08:05 Ok 14:08:18 Let me take safari 14:08:27 #info royce focal point for ubuntu tests 14:08:32 FF & IE will need more than 1 version tested. Chrome and Safari maje it hard to be backlevel 14:08:40 #info ming_ focal point for fedora tests 14:08:42 hlwanghl Do you have a mac? 14:08:49 Y 14:08:50 #info shaohef focal point for rhel tests 14:09:04 ok. the other safari's are always backlevel 14:09:16 ok, you want IE or FF to go w./ your Safari? 14:09:36 Y. Seems safari on other platform is stopped updating 14:09:47 Ok 14:09:54 Ff 14:10:07 ok, need to test latest FF, and latest FF ESR 14:10:18 I'll do IE10 & 11, and Chrome 14:10:29 #info hlwanghl focal point for FF and Safari browser compatibility tests 14:10:36 IE on Windows, FF on Windows and MacOS, Safari on MacOS 14:10:46 #info AdamKingIT1 focal point for Chrome and IE browser compatibility tests 14:11:04 try latest FF on linux too 14:11:39 OK I can take FF on F19 14:11:51 FF gets updated even on 18 14:11:53 f18 14:12:11 Ok 14:12:24 great! 14:12:27 if there isn't more volunteers I will take care of opensuse 14:12:32 last chance... =p 14:12:51 alinefm, feel free to assign~ 14:13:26 ok 14:13:27 #info alinefm focal point for opensuse tests 14:13:47 I think we have a good plan for tests 14:13:56 make sure to update the test matrix, etc 14:14:13 anything else for today? 14:14:58 AdamKingIT1 seems we have overlap with backend tests, we can focus on Windows and MacOS, and they will cover most Linux cases 14:15:19 i mean test the browser running on linux 14:15:33 ah. We are focal... 14:15:54 If someone testing the backend is using latest FF that would suffuce 14:15:57 suffice 14:16:09 Just need to ensure we have version coverage 14:16:10 AdamKingIT1, yes! 14:16:21 x platform variation 14:16:54 I mean we can choose one Linux distro to do browser tests, and they can choose one browser (FF) to do backend tests AdamKingIT1 14:17:39 FF 27 should be the same on all linux, its just not quite the same as FF27 on Windows 14:18:38 I know that. Anyway, just a suggestion. Do the plan and I'll follow 14:19:09 AdamKingIT1, I think hlwanghl is suggesting to you don't test FF and Chrome in all Linux as we will have one of them to do the backend tests 14:20:04 agreed, We shuold endure FF 27 is tested on at least one linux, along w./ latest FF ESR. Testing on all would be excessively redundant 14:21:45 AdamKingIT1, yeap 14:21:57 I will finish the meeting, but we can continue after it 14:22:03 #endmeeting