14:01:34 #startmeeting oVirt Weekly Sync 14:01:34 Meeting started Wed Jun 6 14:01:34 2012 UTC. The chair is oschreib. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:34 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:01:45 #topic agenda and roll call 14:01:51 * aglitke is here 14:01:56 * mgoldboi is here 14:02:01 * oschreib here 14:02:29 * fabiand is trying to speak for node 14:02:31 Agenda is 14:02:31 * itamar his here 14:02:36 1. Release status 14:02:44 2. sub project status 14:02:46 * danken is lurking 14:02:54 3. workshops/conferences 14:03:02 4. Other topics that people have 14:03:06 * dustins here 14:03:07 anything else? 14:03:14 * doron here 14:03:32 \me here 14:03:36 waiting 1 min for roll-call 14:03:44 * rickyh here 14:03:44 * sgordon_ is here 14:04:21 * mestery lurking ... 14:04:32 #topic Release status 14:04:44 #info devel freeze June 7 (tomorrow) 14:04:50 #info Beta shortly after 14:04:56 #info GA June 27 14:05:07 #info test day June 14 14:05:21 #link https://bugzilla.redhat.com/show_bug.cgi?id=822145 14:05:30 Fedora 17 patch finally merged 14:06:27 engine <-> vdsm version issue solved 14:06:35 only one issue blocking node - https://bugzilla.redhat.com/show_bug.cgi?id=824420 14:06:51 #link https://bugzilla.redhat.com/show_bug.cgi?id=824420 14:07:07 one node blocker 14:07:32 agreed with mburns that we can enter feature freeze 14:07:48 so, any objections on entering feature freeze tomorrow? 14:08:03 feel free to +1 it 14:08:10 +1 14:08:12 mgoldboi: +1 14:08:20 +1 14:08:23 +1 14:09:04 #agreed ovirt 3.1 feature freeze will be 07.06.2012 (tomorrow) 14:09:09 +1 14:09:17 #info node should be ready few days after 14:09:35 another small issue - I going to one week vacation 14:10:13 mburns volunteered to replace me as release manager for next week 14:10:31 (he's in japan currently, I'm speaking in his name) 14:10:40 any objections? or +1's? 14:11:06 mgoldboi: +1 14:11:34 +1 14:11:39 +1 14:11:42 +1 14:11:47 #info vdsm is in feature freeze 14:12:35 +1 14:12:42 #chair aaglitke 14:12:42 Current chairs: aaglitke oschreib 14:13:09 #chair aglitke 14:13:09 Current chairs: aaglitke aglitke oschreib 14:13:16 :) 14:13:17 I think it would be nice if vdsm has a version bump for the freeze (4.9.7) 14:13:31 #agreed mburns will be release manager next week 14:14:05 #action mburns to replace oschreib as release manager next week 14:14:06 can it go with 4.10 to match what it reports to engine? or will it go to 5.0 for next version instead? 14:14:06 danken, I assume the bug fixes then would not bump the version? 14:14:18 ok 14:14:25 danken: +1 on bump if engine can handle that. 14:14:28 if we're already talking about vdsm 14:14:29 #topic sub project status -- vdsm 14:14:46 doron: yeah, we'd keep reporting 4.9... 14:14:53 :) 14:14:58 vdsm uses x.y.z versions 14:15:13 aglitke: indeed, bug fixes are on top of that version - could be rpm releases 14:15:18 so best we could do is 4.10.0 and lie to engine 4.10 14:15:23 are we sure we want to change it? won't it break anything? 14:15:56 how does engine handle the version bump? (assuming 4.10) ? 14:15:59 aglitke: for some reason abaron (and you?) were against 4.10 yeasterday, not? 14:16:29 danken, for a release I would think 4.10.0 is okay 14:16:38 aglitke: it could work out of the box, but Engine should probably say that it supports 4.10. 14:16:42 since it involves a feature freeze 14:16:49 yep 14:17:18 bug fixes could bump it to 4.10.x++ 14:17:29 but it would still appear as 4.10 to engine 14:17:54 can you decide about the version until tomorrow? (+patch and test it?) 14:18:02 14[[07Release Notes Draft14]]4 !N10 02http://www.ovirt.org/w/index.php?oldid=3479&rcid=3568 5* 03Sgordon 5* (+648) 10Populated draft release notes page for 3.1 14:18:05 danken, engine only needs to say it supports 4.10 if vdsm doesn't say it support 3.1, which it already does. 14:18:14 aglitke: I did not understand why you and ayal said no for thaton yesterday vdsm call,... 14:18:34 14[[07Release Notes Draft14]]4 !10 02http://www.ovirt.org/w/index.php?diff=3480&oldid=3479&rcid=3569 5* 03Sgordon 5* (+18) 10/* Engine */  14:18:44 danken, I didn't want to bump it just to work around an engine version parsing problem. 14:18:59 14[[07Release Notes Draft14]]4 !10 02http://www.ovirt.org/w/index.php?diff=3481&oldid=3480&rcid=3570 5* 03Sgordon 5* (+22) 10/* VDSM */  14:19:07 It's logical to bump the 'y' part of the version for an ovirt release. 14:19:08 aglitke: ah 14:19:26 on our end, the version needs to be 4.10.0 14:19:29 agreed? 14:19:49 I'll have to understand abaron's yesterday's rejection of this 14:20:00 ok... 14:20:03 danken: can you close it until tomorrow? 14:20:04 but my opinion is positive for this 14:20:11 oschreib: yes 14:20:20 #agreed vdsm version should be bumped 14:20:21 otherwise - it's 4.9 still. 14:20:35 #action danken to handle vdsm version until tomorrow 14:20:43 anything else from vdsm? 14:20:50 not from me... 14:21:15 #topic sub project status -- engine 14:21:22 how do things look on the engine side for devel freeze? 14:22:14 doron: ? itamar? 14:22:29 oschreib: afaik pretty much there. 14:23:00 #info things in good shape on the engine side 14:23:01 should go to feature freeze. if anything worth while we could discuss an exception to it when raised (can't think of any now) 14:23:31 #topic sub project status -- node 14:23:55 fabiand: ? 14:24:10 well, we are on a good track 14:24:21 we had some trouble with selinux changes and blocker that kept us a while from progressing 14:24:40 are you talking about https://bugzilla.redhat.com/show_bug.cgi?id=824420? 14:24:42 We've got hope that we can fix this in the next days 14:25:18 yes, our major effort is currently to get node working on an F17 base 14:25:39 #link https://bugzilla.redhat.com/show_bug.cgi?id=824420 14:26:01 #info node should support F17 in the next couple of days 14:26:17 fabiand: please update that bug with some relevant info 14:26:23 oschreib, sure 14:26:50 #action fabiand to update BZ#824420 14:27:17 #topic Workshops and Conferences 14:27:57 itamar: quaid_ : any info about that topic? lh is not here 14:28:58 barak and mburns are presenting in linux con japan this week :) 14:29:08 no other updates i'm aware of. 14:29:40 #info bazulay and mburns are presenting ovirt in linux con Japan this week 14:29:40 upcoming ovirt day in linuxcon NA, then 2.5 co-hosted with kvm forum in linuxcon europe 14:30:55 cool 14:31:43 #info there will be an ovirt day in n linuxcon NA, then 2.5 co-hosted with kvm forum in linuxcon europe 14:31:48 #topic Other Topics 14:31:55 one thing from me: 14:32:25 I have two things after oschreib 14:32:28 I've created http://www.ovirt.org/releases/beta/fedora/17/ 14:32:45 with pre feature freeze F17 build 14:32:51 feel free to test them 14:33:24 #link http://www.ovirt.org/releases/beta/fedora/17/ 14:33:40 #info pre feature freeze F17 builds 14:33:52 who's taking the lead on test day next week? 14:34:33 I was going to ask the same. I would like to encourage my team at IBM to participate. 14:35:40 ykaul1: yeylon_: any volunteers ? 14:36:15 aglitke: that would be great, we need someone to arrange it though 14:36:38 I'm afraid I don't have the bandwidth to lead it. 14:36:47 I'll have to take it to the mailing list. 14:36:51 ok. 14:37:03 #action oschreib to look for test day lead 14:37:08 aglitke: anything elese? 14:37:23 yes 14:37:50 danken wanted me to mention that the vdsm verb setupNetwork is broken. It is missing some basic features such as adding a nic to an existing bond device. 14:38:14 setupNetwork is part of the release criteria I guess. 14:38:29 do we have an 3.1 blocker bug on it? 14:38:34 I think this just needs to be noted in the meeting log for posterity. 14:38:40 I can check, 14:38:55 aglitke: can you make https://bugzilla.redhat.com/show_bug.cgi?id=822145 depends on it? 14:39:01 oschreib, mgoldboi did a great job last time, i say why kill a winning coiw... ;) 14:39:11 oschreib, sure. 14:39:15 #info vdsms's setupNetwork is broken 14:39:48 #action aglitke to link setupNetwork bug on https://bugzilla.redhat.com/show_bug.cgi?id=822145 14:40:06 aglitke - actually, we could debate if setupNetworks is on the release criteria, or allowing old api for 3.1 is a good enough resolution 14:40:57 (assuming it isn't broken as well) 14:40:58 itamar, ok. I defer to the experts :) 14:41:18 aglitke: please make sure engine-devel is updated with that issue 14:41:26 we will have to discuess it next meeting 14:41:27 but agree nework working is blocking 14:41:38 anything else? 14:41:43 not for me 14:42:12 +1 for dropping setupNet from release criteria 14:42:20 I think it is immature in all levels 14:42:45 danken: please send such an offer to the relevant list 14:42:52 we will revisit it next meeting 14:43:49 ok 14:44:14 ending meeting in 5 14:44:19 4 14:44:20 danken: and what is the alternative to setupNet? 14:44:34 * oschreib reset counter 14:45:28 old-fashioned api of 3.0 release 14:45:30 ykaul: ^^ 14:45:59 Perhaps we can discuss the whole issue on the list when danken sends out the email. 14:45:59 danken: but that requires some work, that is not going to be done in time for the 3.1 release, or we'll have to delay it, no? 14:46:45 ykaul: what "requires some work"? 14:46:49 ykaul, why? we still support it in both engine and vdsm for 3.0 clusters. we just need to say 3.1 clusters use old code path in engine 14:47:00 * danken ahhh battary low 14:47:25 itamar: in theory, yes. In practice, I don't know. And I'm pretty sure the UI is still broken. Also, will VDSM advertising as 3.1 would work with old API? 14:47:39 yes, it will work with old api 14:47:40 or 4.9.7 VDSM or whatever version we end up with. 14:47:57 yeah, we keep backward compat 14:48:06 old api is NOT deprecated 14:48:23 we could spend some time stabilzing setupNet 14:48:39 I'm just saying that I feel that 1 month may be a bit too short a time 14:49:51 oschreib: forgot to respond that I will not be leading the test day. Nor will yeylon. Will have to find someone from the community. 14:50:10 ykaul: got that. 14:50:22 danken: sounds like a (very) long discuession 14:50:44 danken: can you lead the discussion on @ovirt.org ? 14:51:09 oschreib: regarding setupNetwork? 14:51:18 yes 14:51:43 regarding it's maturity for ovirt 3.1 14:52:04 ok. until I do, setupNet is in the release criteria, and we'll strive to stabilize it 14:52:14 indeed 14:52:34 danken: I thought the release criteria was about network working, setupNetwork is a small implementation detail. 14:52:52 danken: I suspect the UI is a bit broken as well. not sure the latest status. 14:54:29 anything else? 14:54:37 or can we end the meeting? 14:55:21 end meeting in 5 14:55:23 4 14:55:27 3 14:55:30 2 14:55:34 1 14:55:40 #endmeeting