15:03:13 #startmeeting oVirt Weekly Sync 15:03:13 Meeting started Wed Feb 26 15:03:13 2014 UTC. The chair is doron. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:13 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:03:36 #topic Agenda and roll Call 15:03:38 #info infra update 15:03:39 #info 3.3 update releases 15:03:41 #info 3.4 progress 15:03:42 * sbonazzo here 15:03:42 #info conferences and workshops 15:03:44 #info other topics 15:04:04 hi sbonazzo lvernia ybronhei gtemple mskrivanek 15:04:14 * lvernia is here! 15:04:20 * bkp here 15:04:27 * danken is here 15:04:46 let's start 15:04:53 #topic infra update 15:05:01 dcaro: orc_orc infra updates? 15:06:22 we have a new repository layout for the repositories, and a new set of hooks (as you have noticed already) 15:06:36 * fabiand is here 15:06:48 I'd like to discuss the the bug-url rule 15:06:49 dcaro: any news about the jenkins issues? I'd love to get all resolved;-)) 15:07:16 I know there are benefits to it - but who is currently consuming the bug-url in stable branch? 15:07:22 hi fabiand 15:07:37 hi doron 15:07:48 dcaro: any other updates? 15:07:51 danken: I find it useful. What's the issue you see? 15:07:53 mskrivanek: we have just modified the open files limit in the slaves, hopefully that will solve the rpm creation issues, but there are still some other open issues 15:08:14 mskrivanek: it's sometimes annoying and pointless. 15:08:27 for example, when I backport a patch that does not solve a bug 15:08:39 it is only needed for the bug-solving patch 15:08:39 doron: the hooks use it to update the bugs, to add trackers and change the bugs to POST (when patchset is created) and to MODIFIED (when all the patches are merged) 15:08:59 danken: we're in stabilization, if it doesn't solve a bug maybe shouldn't be backported 15:09:00 danken: ^^^^^^^ 15:09:19 sbonazzo: well, it does not solve a bug PER SE 15:09:34 but it is helping another patch solve the bug 15:09:49 danken: what do you mean? some patches do resolve an issue. 15:10:20 maybe make related-to: sufficient? 15:10:38 mskrivanek: related-to makes some sense. 15:10:54 I'm more intereszted to know why it has to be an ovirt bug 15:11:06 and why a publick rhev bug is not good enough 15:11:23 danken: most bugs should be ovirt now. 15:11:31 danken: rhev bugs are rhev specific. 15:11:51 and bug url is needed in the stable branch if we want to keep it stable. 15:11:57 danken: +1. I'd say any public bug is fine. doron: I doubt it's the current state 15:12:18 mskrivanek: this is where we should be heading now. 15:12:28 doron: there are certainly many more than before, but I'd say we're there. 15:12:45 doron: many bugs are opened on rhev by rhev customers. I personally do not need the ovirt clone 15:12:49 guys, RHEV specific issues should not belong here. in general, most bugs are ovirt now. 15:12:59 I am interested to know who DOES find it useful. 15:13:24 danken: as I said, this was shifted lately. check the stats and you'll see most bugs are ovirt now, not rhev. 15:13:42 doron, we still have many bugs filed against RHEV 15:13:50 i find useful to see a clear link to an issue. And it doesn't matter to me if it's ovirt or rhev or libvirt or whatever as long as it leads to something useful 15:13:52 And I agree with danken that any bug should be okay, as long as it's public 15:13:59 fabiand: +1 15:14:03 fabiand: this is true, and they will be resolved. but in general ovirt bugs should be opened as such. 15:14:28 doron, I agree - but sometimes the bugs just pour in from a different side .. 15:14:54 fabiand: and the other side shifted lately. I suggest we check this internally as they change. 15:15:27 Guys, let's clarify one thing here, which is chaning in the past ~2 weeks; 15:16:15 RHEV bugs are opened only for specific cases. We can get some more info from QE guys, but in general the idea for ovirt 15:16:25 is to have ovirt bugs. 15:16:38 For example, 15:16:50 I'd expect CentOS to open ovirt bugs as well. 15:17:00 unless it's CentOS specific. 15:17:12 in which case they track it separately. 15:17:20 Same goes for RHEV. 15:18:17 danken: does it answer your question? 15:19:16 I'll assume yes. 15:19:22 dcaro: other updates? 15:19:28 doron: not really, since you did not explain why is that idea coming from 15:19:35 and who is enjoying from it. 15:19:45 * fabiand nods 15:19:47 as it goes, we have prolifiration of bugs 15:20:00 and I also don't see why we shouldn't use downstream (RHEV or CEntos) bugs .. 15:20:04 doron: no, nothing else 15:20:09 danken: so lets check it with rhev guys first, and reopen for discussion as needed. ok? 15:20:28 fabiand: we should use them for d/s related issues. 15:20:44 dcaro: thanks 15:21:02 moving on. 15:21:12 #topic 3.3 releases update 15:21:22 sbonazzo: 3.3.4 state of the union? 15:21:26 * fabiand needs to run 15:21:30 doron: 3.3.4 RC released yesterday 15:21:35 fabiand: in a sec plz. 15:21:44 #info 3.3.4 RC released yesterday 15:21:45 doron: 3.3.4 GA should respect schedule 15:21:55 doron: no blockers on 3.3.4 15:22:11 #info 3.3.4 GA on track. 15:22:20 doron: side thought: nobody added himself to testers on test page 15:22:36 sbonazzo: for 3.4.0? 15:22:39 doron: http://www.ovirt.org/Testing/Ovirt_3.3.4_testing 15:22:52 doron for 3.4.0 we still have 1 blocker on POST 15:23:10 sbonazzo: wait. you mean 3.4.0 test day right? 15:23:12 doron: I think 3.4.0 RC will be composed tomorrow 15:23:30 doron: above is for 3.3.4 QA / testing by community 15:23:51 doron: nobody in ovirt community has added himself as 3.3.4 tester there 15:23:58 sbonazzo: when is the 3.3.4 test day planned for? 15:24:47 doron: no, we don't plan testday for 3.3.z. but users added themselves on previous 3.3.z 15:25:04 doron and it surprise me a bit nobody did for this release 15:25:23 sbonazzo: where can users register? 15:25:55 doron: http://www.ovirt.org/Testing/Ovirt_3.3.4_testing#participants 15:26:23 #info feel free to register for 3.3.4 testing in http://www.ovirt.org/Testing/Ovirt_3.3.4_testing#participants 15:26:33 sbonazzo: I'd drop an email about it. 15:26:40 doron: thanks 15:26:44 and let's move to 3.4 15:26:49 #topic 3.4 progress 15:26:55 fabiand: still here? 15:27:42 I guss not. 15:27:53 sbonazzo: how are we doing with 3.4 blockers? 15:28:02 doron: still 1 15:28:17 doron: it's in POST, I hope it will be fixed for tomorrow morning 15:28:17 sbonazzo: which one? 15:28:30 doron: https://bugzilla.redhat.com/show_bug.cgi?id=1064829 15:28:52 ybronhei: this is infra. can you comment on its ETA? 15:29:10 or possibly jhernand? 15:29:32 doron: only merge to stable branch is missing 15:29:49 ybronhei: will it be ready for tomorrow? 15:30:05 doron: can't see any reason why it is blocked 15:30:27 ybronhei: it's missing a review. 15:30:33 doron: merge to ovirt-engine-3.4 branch goes by itamar, right ? 15:30:48 ybronhei: yes, which patch? 15:30:56 doron: http://gerrit.ovirt.org/#/c/25083/ 15:31:31 ybronhei: missing ack 15:31:47 sbonazzo: please alert tomorrow if not already merged. 15:31:49 sbonazzo: its ovirt bug. what ack? 15:31:58 ybronhei: on the patch, missig +2 15:32:01 sbonazzo: build planned for tomorrow? 15:32:06 doron yes 15:32:10 sbonazzo: thanks 15:32:14 sbonazzo: itamar should give it iiuc 15:32:27 ybronhei: itamar usually just merge 15:32:42 #info 3.4.0 RC planned for tomorrow. Currently one blocker, expected to be merged. 15:33:00 let's do a quick round from everyone 15:33:11 sbonazzo: i'll take care for review 15:33:14 sahina: gluster updates for 3.4? 15:33:20 ybronhei: +1 15:33:57 ybronhei: infra updates for 3.4 other than the bocker? 15:34:15 (blocker) 15:35:17 doron: sec.. 15:35:22 sahina ? 15:35:55 doron: we have also https://bugzilla.redhat.com/show_bug.cgi?id=1069522 . also same status 15:36:13 ybronhei: is it a bloxker? 15:36:17 (blocker) 15:36:21 ybronhei: you need to get the patch acked before i look at it... 15:36:27 doron: oh already merged. so no. only https://bugzilla.redhat.com/show_bug.cgi?id=1064829 15:36:35 ybronhei: anything else? 15:36:46 doron: i will have to run sooner, nothing interesting on the virt part, AFAICT. Other than REST API for template versions (3.4) still not in:( (should get in soon, has +2) 15:36:57 itamar: yes, sent mail to yair to check that. thanks 15:37:01 doron: no. 15:37:07 mskrivanek: will it go in by tomorrow? 15:37:13 ybronhei: thanks 15:37:44 doron: hm, depends on verification 15:37:45 #info infra updates for 3.4: one blocker, expected to be resolved for tomorrow's build. 15:38:01 mskrivanek: usually if not in the rc it misses GA 15:38:12 doron: itamar: I've one question 15:38:14 mskrivanek: is it a blocker? 15:38:18 sbonazzo: ? 15:38:40 doron: itamar: tomorrow I'll build 3.4.0 release candidate as 3.4.0-1 and bump immediately after to 3.4.1 15:38:41 doron: well, it's a feature which is already "almost" completely in.... 15:39:06 doron: itamar: would we want to stay on 3.4.0-rc1 instead? 15:39:11 mskrivanek: then it has to be in the rc build, or skip it. 15:39:24 doron: ok, will get it in (well, itamar;-) 15:39:55 mskrivanek: will itamar do verification? 15:40:03 sbonazzo: what's the difference? 15:40:25 itamar: if a new patch will be targeted to 3.4.0 will need to open a new 3.4.0 branch for adding it 15:40:50 doron: that would be sweet!:) well, rather not, he would find an issue:) Omer will 15:40:53 itamar: if I keep 3.4.0 rc no new branch is needed 15:41:00 sbonazzo: since I'd expect respins, I'll leave it with rc1 15:41:12 doron: ok 15:41:22 mskrivanek: very well, so I'm assuming this is in tomorrow's build. 15:41:25 mskrivanek: thanks 15:41:44 Can anyone give me some solid reason/s for going with ovirt over proxmox? I'm coming from a VMware based environment but have quite a bit of Linux experience. My main reasons for leaning toward ovirt is that it has native support for RHEL and doesn't require a subscription for repo's. Proxmox on the other hand has paid support and backups are integrated. 15:41:58 #info virt 3.4 updates: last patch for REST API should go in by tomorrow's build. 15:42:11 seaoftea: we're in a meeting now. sorry. 15:42:16 sorry 15:42:23 sbonazzo: integration updates for 3.4? 15:43:14 doron: no news about features since last week, just bugfixes. 15:43:20 sbonazzo: thanks. 15:43:44 #info integration updates for 3.4: no updates, mostly bug fixes. 15:43:49 lvernia: here? 15:43:55 doron: Yes. 15:43:56 sbonazzo: and if you just keep it 3.4.0 on master for a few more days? 15:44:04 lvernia: hi. network updates? 15:44:08 (for 3,4) 15:44:29 doron: Nothing major. Yesterday 27 networking bugs (!) were closed. 15:44:38 doron: Other than that, business as usual... 15:44:48 lvernia: very nice, thanks. 15:44:49 itamar: so just use a nightly for RC? 15:44:53 doron: Well, not closed, moved to POST. 15:45:01 (at least) 15:45:06 sbonazzo: guess so 15:45:20 #info network 3.4 updates: no updates. 27 bugs closed yesterday! 15:45:33 lbianc: here for ppc? 15:45:45 hi doron 15:46:03 itamar: we never did that but if it's ok I can compose rc using that 15:46:19 hi lbianc. ppc updates for 34? 15:46:46 About PPC, still missing patches to block migration ans snapshot. We had some reviews, but not enough to be merged 15:47:20 There are other similar patches that should be merged too, they are described in bugs BZ#1057178, BZ#1070189, BZ#1061774, BZ#1067605, BZ#1067561 15:47:39 lbianc: in general things missing in rc will not be in ga as well. how bad is it? 15:49:04 Well, PPC support will work, since the user use the system with restrictions, like fix a host to do not migrate and do not use memory snapshot 15:49:38 itamar: just let me know if go with _rc1 or _master 15:49:50 lbianc: can you make sure you warn about it if the patches won;t be merged? for example in the wiki? 15:49:56 doron: Vitor has some comments as well 15:49:59 doron, there will be features that will be available in the frontend, but they will not work 15:50:15 vitorlima: and how bad is it? 15:50:17 Like VM suspension, floppy support, ... 15:50:18 sbonazzo: you can keep it 3.4.0. i can avoid merging non critical items till we GA if a couple of days. i.e., just build from master for now? 15:50:34 If the user is aware of these limitations, there will be no problem, I guess 15:50:37 itamar: ok for building from master 15:50:38 sbonazzo: s/master/ovirt-engine-3.4/ of course 15:50:44 itamar: yes :-) 15:51:10 vitorlima: ok. so can you make sure it is documented in the PPC wiki? 15:51:16 doron: sure, we add that to the wiki 15:51:18 Sure, we will do it 15:51:26 lbianc: vitorlima thanks. 15:51:32 thanks 15:52:00 #info PPC updates for 3.4: still unmerged patches. If not merged by tomorrow it should be documented in the wiki. 15:52:38 #info SLA 3.4 updates: no updates. SLA is ready. 15:53:02 who's here for storage? abaron? sgotliv? 15:53:30 doron: thanks 15:53:38 gtemple: thank you. 15:53:52 who's here for storage? abaron? sgotliv? 15:55:17 #info no storage representative. Please update offline. 15:55:24 ecohen: here? 15:55:29 doron, yes, hi 15:55:29 two bugs were fixed: 15:55:29 "Bug 1066489 - Event list not updating when events happen" 15:55:29 "Bug 1068924 - tree based sub-tabs - missing action panel buttons" 15:55:29 both BZs are already in MODIFIED. 15:55:31 no other updates. 15:55:53 ecohen: welcome back and much appreciated ! 15:55:59 doron, thanks and np :) 15:56:15 #info ux 3.4 updates: 2 BZs fixed and ready for tomorrow's build. No other updates. 15:56:26 sbonazzo: anything else on 3.4? 15:57:13 doron: we're entering release candidate so only very critical bugs should be addressed 15:57:31 doron: other than that, nothing more on 3.4 15:57:49 sbonazzo: thanks 15:58:21 #info starting tomorrow's build only critical fixs are allowed in the 3.4 build. Good luck! 15:58:32 #topic conferences and workshops 15:58:37 bkp: updates? 15:58:46 SCALE went very well, talk at Infrastructure.Next well-received and we had a *lot* of booth traffic asking about oVirt, both general questions and specifics. Thanks to ecohen for her valuable time and efforts! 15:58:55 Next up is DevNation and Red Hat Summit (April 13-17), with a scheduled oVirt workshop. I have proposals for talks in at LinuxFest Northwest (April 26-27) and FISL (May 6-10). 15:59:07 doron also let me know this morning that there have been some successful talks on open source and oVirt conducted by the TLV team. 15:59:14 No other updates 15:59:49 #info SCALE went very well, talk at Infrastructure.Next well-received and we had a *lot* of booth traffic asking about oVirt, 16:00:02 +1 on thanking ecohen 16:00:19 doron, bkp - thank you, it was my pleasure. 16:00:22 #info Next up is DevNation and Red Hat Summit (April 13-17), with a scheduled oVirt workshop. 16:00:28 She also defended the booth well 16:00:47 indeed - go to @ovirt at twitter for more information... 16:00:49 #info additionally, there are proposals for talks in at LinuxFest Northwest (April 26-27) and FISL (May 6-10). 16:01:33 #info TLV team also giving some open source and oVirt talks, getting positive feedback. 16:01:39 bkp: thanks 16:01:44 #topic other topics 16:01:54 anyone wants to discuss something? 16:02:01 General community stuff... 16:02:06 google summer of code? 16:02:36 SoCapproved oVirt as a mentoring organization, congrats to all! 16:03:15 We have three ideas proposed so far, and are awaiting student interest. 16:03:34 Gathering feedback for the community dashboard at ovirt.org/stats. If you have any questions/concerns, please send me a note or ping me on irc. 16:03:43 Finally, still working on documentation for oVirt 3.3. Any edits or fixes to the Quick Start Guide at http://www.ovirt.org/Quick_Start_Guide (other than broken links, which I already know about) should be entered by March 3, so we can pull the "Draft" status down. 16:03:50 bkp: want to mention GSOC? 16:04:00 I thought I did. 16:04:06 bkp: oh, sorry. 16:04:10 anything else? 16:04:10 :) 16:04:14 I'm good. 16:04:43 #info GSOC approved oVirt as a mentoring organization, congrats to all! We have three ideas proposed so far, and are awaiting student interest. 16:04:53 anyone else? 16:05:07 Going once? 16:05:50 Going twice... 16:06:23 Thanks everyone for joining! 16:06:24 #endmeeting