14:03:25 <bkp> #startmeeting oVirt Weekly Sync 14:03:25 <ovirtbot> Meeting started Wed Aug 20 14:03:25 2014 UTC. The chair is bkp. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:25 <ovirtbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 14:03:37 * awels is here for ux 14:03:45 * amureini here for storage 14:03:47 * sbonazzo here for integration 14:03:56 <bkp> #topic Agenda and Roll Call 14:04:06 * oved is here (will have to leave in the middle) 14:04:32 <bkp> #info infra update 14:04:33 <bkp> #info 3.4.z updates 14:04:33 <bkp> #info 3.5 status 14:04:33 <bkp> #info conferences and workshops 14:04:33 <bkp> #info other topics 14:04:53 * alitke is here 14:05:06 <bkp> Okay, let's start. 14:05:16 <bkp> #topic infra update 14:05:30 <bkp> Anything from infra this week? 14:06:29 <bkp> dcaro? Infra report? 14:07:06 <dcaro> PHX setup has a working foreman-proxy running, starting to spawn vms and autoinstall directly from foreman.ovirt.org 14:07:10 * lvernia is here, apologies for being late. 14:07:34 * danken is even later 14:07:43 <dcaro> also jenkins and gerrit to be upgraded soon (hopefully this week) 14:08:19 <danken> dcaro: we have a new task of migrating master-related vdsm jobs to f20/f21. 14:09:30 <bkp> #info infra PHX setup has a working foreman-proxy running, starting to spawn vms and autoinstall directly from foreman.ovirt.org 14:09:30 <bkp> #info infra jenkins and gerrit to be upgraded soon (hopefully this week) 14:09:30 <bkp> #info infra New task created of migrating master-related vdsm jobs to f20/f21 14:09:34 <eedri> dcaro, +1 14:09:48 <eedri> dcaro, great to hear phx lab is progressing 14:09:55 <bkp> Indeed, kudos to infra team! 14:10:01 <bkp> Anything else, dcaro? 14:10:02 <amureini> +1! 14:10:03 <eedri> danken, on the same note - is there agreement to stop runnin on f19? 14:10:33 <sbonazzo> eedri: we still need f19 on 3.5 branches untill we verify upgrade path to F20 on 3.5.z 14:10:43 <sbonazzo> eedri: opened a bz about it this morning 14:10:46 <dcaro> bkp: nop, those are the most relevant news 14:10:58 <bkp> Awesome, dcaro! 14:11:05 <danken> sbonazzo: but vdsm jobs should move to f21. 14:11:11 <bkp> #topic 3.4.z updates 14:11:12 <sbonazzo> danken: agree 14:11:31 <sbonazzo> bkp: sent oVirt 3.4.4 RC status: http://lists.ovirt.org/pipermail/users/2014-August/026823.html 14:11:43 <sbonazzo> bkp we seems to be on track 14:11:57 <bkp> sbonazzo: Can you sum up? I literally just got off the train. 14:12:07 <sbonazzo> bkp: 7 bugs still open there 14:12:11 <sbonazzo> bkp no blockers 14:12:25 <danken> sbonazzo: but note a recent patch in vdsm merged into ovirt-3.4 branch 14:12:29 <sbonazzo> bkp RC targeted to 2014-09-09 14:12:41 <danken> sbonazzo: http://gerrit.ovirt.org/31619 14:12:55 <danken> we'll need to produce a new build that includes it 14:13:21 <bkp> danken: Is that a blocker-clas big? 14:13:26 <bkp> *bug? 14:13:28 <sbonazzo> danken: do you need an async release for vdsm? can't it wait for 3.4.4? 14:14:01 <danken> bkp: it's a regression mostly evident on el7 14:14:07 <danken> for some reason 14:14:20 <danken> but other platforms are suceptible. 14:14:35 <danken> bug is https://bugzilla.redhat.com/show_bug.cgi?id=1129232 14:15:13 <sbonazzo> danken: so looks like an async is recomended 14:15:39 <danken> sbonazzo: fine 14:15:53 <sbonazzo> danken: can you build a new rpm release and send it to dcaro for publishing? 14:15:57 <danken> sbonazzo: I know that you hate it, but it affect 3.5.0 rc, too. 14:16:13 <danken> sbonazzo: I'll beg dougsland to do that ;-) 14:16:13 <bkp> I can make Yaniv sit down and do it, since it's assigned to him. He's here. 14:16:26 <bkp> :) 14:16:46 <bkp> Okay is that it, sbonazzo? 14:16:51 <danken> bkp: he's being near you was the reason I suggested dougsland ;-) 14:16:52 <sbonazzo> bkp: yes on my side 14:17:07 <bkp> danken +1 14:17:09 <amureini> bkp, sbonazzo quick question about 3.4.z releases? 14:17:14 <amureini> before you move on? 14:17:17 <bkp> Can I guilt him a little? 14:17:25 <bkp> amurenini, shoot 14:17:25 <sbonazzo> amureini: sure 14:18:32 <amureini> we found a nasty bug that prevents exporting (and probably a bunch of other operations) on vDisks that were imported to block storage from file storage - https://bugzilla.redhat.com/show_bug.cgi?id=1130761 14:18:51 <amureini> it's fixed, but we'll need a semi-manual procedure to handle disks that were previously effected 14:19:01 <amureini> where can we publish this procedure? 14:19:14 <amureini> sbonazzo, bkp ^^^ 14:19:36 <sbonazzo> amureini: I guess known issues in http://www.ovirt.org/OVirt_3.4.4_Release_Notes may be a good point 14:20:32 <amureini> sbonazzo, thanks. Is it OK to update 3.4.2 and 3.4.3 too retroactively? the bug seems to have been present there too 14:20:42 <sbonazzo> amureini: sure 14:20:47 <bkp> amureini, sbonazzo: If someone can point me to the published stuff, I can clean it up and get it posted 14:21:03 <bkp> sbonazzo, let me know what you need 14:21:15 <sbonazzo> amureini: please send also an email to users list about the update so people using those version will be aware of the doc 14:21:32 <amureini> sbonazzo, bkp there's nothing published yet, as we're still working on the procedure. I'll send tal your way once we have it verified 14:21:45 <sbonazzo> amureini: ok thanks 14:22:27 <sbonazzo> bkp: I guess we can move on 14:23:03 <bkp> #info 3.4.z updates 7 bugs still open, no blockers. 14:23:03 <bkp> #info 3.4.z updates RC targeted to 2014-09-09 14:23:03 <bkp> #info 3.4.z updates A nasty bug that prevents exporting (and probably a bunch of other operations) on vDisks that were imported to block storage from file storage - https://bugzilla.redhat.com/show_bug.cgi?id=1130761 14:23:03 <bkp> #info 3.4.z updates Documentation will be added to 3.4.4 release notes, as well as 3.4.2 and 3.4.3, retroactively 14:23:19 <bkp> Okay, here we go. 14:23:26 <bkp> #topic 3.5 status 14:23:35 <bkp> sbonazzo, highlights? 14:23:45 <sbonazzo> bkp an info line about async for vdsm for 3.4.z ? 14:24:09 <sbonazzo> about 3.5: sent oVirt 3.5.0 RC2 status: http://lists.ovirt.org/pipermail/users/2014-August/026825.html 14:24:26 <bkp> #info 3.4.z updates An async build will be made for vdsm for 3.4.z 14:24:34 <sbonazzo> bottom line, we're not ready to release RC2 tomorrow 14:25:23 <sbonazzo> btw, some major bugs have been fixed so it's worth to refresh the repository for allowing community to test them 14:26:05 <sbonazzo> also if having known blockers doesn't qualify this as a release candidate 14:26:29 <danken> sbonazzo: alitke and fsimonce reported that live merge work would not merge in a matter of days 14:26:48 <oved> sbonazzo, +1 14:26:58 <danken> a new vdsm verb is required, and it should be used by Engine. 14:27:24 <danken> we should not really call this "rc", but I would not block out testing on live merge. 14:27:25 <sbonazzo> danken: can we postpone live merge feature to a later release? 14:27:38 <amureini> sbonazzo, danken hell no. 14:27:44 <danken> sbonazzo: it's the crown jewel feature 14:28:00 <danken> we'd better postpone 3.5 14:28:04 <bkp> I concur. 14:28:10 <sbonazzo> danken: amureini so I guess we'll postpone 3.5 until it's in 14:28:29 <amureini> sbonazzo, danken however, this new verb is required, basically, to fix a "lightening hits twice" scenario - I think we can release RC without it, and fix for GA 14:28:36 <danken> sbonazzo: we have to set a deadline, thoug 14:28:39 <amureini> sbonazzo, danken bkp ^^^ 14:28:45 <bkp> danken, when you say "matter of days," what do you mean? 14:28:53 <bkp> (Re: deadline) 14:29:03 <danken> I said that it is *not* a matter of days. 14:29:08 <alitke> Patches for one issue are posted and ready for review 14:29:13 <danken> alitke can share is expectations better than me. 14:29:16 <bkp> danken: Noted, my error 14:29:23 <alitke> a patch for the new verb will be posted by me today 14:29:36 <alitke> The biggest barrier is review turnaround time. 14:30:02 <danken> alitke: note taken :-( 14:30:22 <amureini> fsimonce won't be in to review it before next Monday. nsoffer can help, but the best he'll be able to do is +1 14:30:24 <danken> alitke: have you rebased the small easy-to-consume patches? 14:30:28 <sbonazzo> alitke: danken: something we can do for speeding up the process? 14:30:37 <oved> sbonazzo, bkp we also have the jsonrpc issue, which is also mandatory for 3.5. Piotr will be back from PTO on Monday and will dive into that, hoping to get a fast fix for that. 14:30:40 <danken> nsoffer's +1 is most valued. 14:30:56 <amureini> danken, never said it wasn't 14:30:56 <alitke> danken, yes and posted... nsoffer had one minor comment which I have addressed in my local branch 14:30:59 <alitke> about to repush 14:31:40 <nsoffer> alitke, ping me when you want me to review again 14:31:41 <alitke> It'd be nice if we could have the new verb patch reviewed by others before fsimonce 14:31:56 <alitke> then all he has to do is +2 it on Monday when he returns. 14:31:58 <danken> nsoffer: it's here: http://gerrit.ovirt.org/#/c/31364/4..5/vdsm/virt/vm.py 14:32:34 <danken> fromani: (yours, too) 14:32:45 <alitke> danken, nsoffer already fixed... just need to repush 14:32:55 <fromani> danken: got it 14:33:05 <sbonazzo> danken: alitke amureini so are we targeting this to be in in a couple of weeks? Let's say end of first week of september? 14:33:45 <alitke> I hope sooner 14:33:58 <alitke> gpadgett, has some work to do on engine side too 14:34:05 <alitke> but I think that is winding down 14:34:12 <bkp> Let's call a date for first week in Sept, then pull it back if we beat the schedule. 14:34:19 <alitke> ok 14:34:25 <amureini> bkp, sounds good to me 14:34:30 <sbonazzo> bkp +1 14:34:45 <bkp> sbonazzo: Got a date in mind? 14:34:58 * sbonazzo checking the calendar 14:35:01 <bkp> You guys know your rhythms better than I... 14:35:03 <oved> bkp, sbonazzo September 4th? 14:35:55 <bkp> I defer to sbonazzo 14:36:12 <sbonazzo> oved: bkp: I would like to go for sep 3rd, it will be easier on infra if something goes wrong 14:36:27 <bkp> sbonazzo, Ack 14:36:47 <oved> sbonazzo, bkp sure. the jsonrpc issue I've mentioned earlier seems complex, so will take a few days to analyze + fix + review. but see no reason for it not to end in a week. 14:37:01 <sbonazzo> oved: great 14:37:09 <bkp> #info 3.5 status integration oVirt 3.5.0 RC2 not ready for 08-21-14 release 14:37:09 <bkp> #info 3.5 status integration Six blockers outstanding, and two dependency bugs still open, so cannot qualify for RC 14:37:09 <bkp> # info 3.5 status integration alitke and fsimonce reported that live merge work would not happen in matter of days 14:37:09 <bkp> # info 3.5 status integration 3.5 should be postponed. 14:37:10 <bkp> # info 3.5 status integration New verb to be added. Changes have been posted/will be posted today, but testing turnaround time is critical to timing 14:37:13 <bkp> # info 3.5 status integration jsonrpc issue still outstanding, which is also mandatory for 3.5. Piotr will be back from PTO on Monday and will dive into that, hoping to get a fast fix for that (in about a week). 14:37:16 <bkp> # info 3.5 status integration New RC2 target to be September 3rd 14:37:31 <bkp> Did I miss anything? 14:37:47 <sbonazzo> bkp: the refresh of the repository for tomorrow 14:38:23 <bkp> # info 3.5 status integration Repo will be refreshed tomorrow so major changes (and minor) can be tested by community at-large 14:39:23 <sbonazzo> bkp ok, that's all for 3.5 on my side. just a quick note on 3.6 14:39:32 <bkp> Go, sir 14:39:51 <sbonazzo> bkp: I started discussion about release process for 3.6: http://lists.ovirt.org/pipermail/devel/2014-August/008533.html 14:40:07 <sbonazzo> bkp it would be nice to have some feedback from maintainers about that 14:40:45 <sbonazzo> bkp that's all on my side 14:40:47 <bkp> # info 3.5 status integration discussion about release process for 3.6: http://lists.ovirt.org/pipermail/devel/2014-August/008533.html. Feedback about maintainers highly desired. 14:41:34 * oved have to drop. sorry about that. 14:41:51 <bkp> Okay, here's what I want to do... let's review the blockers that have not yet been covered, and then go over any additional team statuses for 3.5. Cool? 14:42:02 <bkp> Bye, oved! 14:42:22 <oved> bkp, speaking of blockers, there is one on infra handled by Mooli. danken - did you review it? 14:42:43 <bkp> oved, that was the first one on my list. 14:42:57 <oved> bkp, I know... that's why I'm still here. 14:43:02 <oved> danken, ? 14:43:03 <danken> oved: not yet, I'm afraid. vdsm-tool 14:43:22 <danken> is ybronhei's forte. 14:43:24 <oved> danken, can you try to do so soon? it will be nice to have it in the repo refresh. 14:44:12 <oved> not sure how available yaniv will be. 14:44:16 <oved> if any. 14:44:26 <oved> so let's try to review it without him. 14:44:27 <bkp> oved, hard to say. 14:44:37 <oved> also, Mooli said he has a deal with you regarding that :-) 14:44:38 <danken> oved: that sounds a bit optimistic :-( 14:44:50 <oved> danken, so complete your part of the deal :-) 14:44:54 <bkp> danken, Got a better time in mind? 14:45:29 <bkp> (Though if I see ybronhei swing from chandeliers, I will put him to work.) 14:45:52 <oved> need to drop. moolit - please review the discussion, and answer any questions (if any). 14:47:58 <bkp> Let's ping SLA... there are two blockers outstanding there. Status? 14:48:33 <danken> saggi, alonbl and others could help review http://gerrit.ovirt.org/#/c/31400/2 too. 14:48:47 <danken> and the rest of http://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:configurators_reorg,n,z 14:50:04 <moolit> danken: I all ready got +1 from alonbl on all patches at some point, saggi was asked to review but didn't have any comments 14:51:50 <danken> moolit: cool 14:52:09 <danken> moolit: except of his religious war against inheritence 14:52:58 <bkp> #info 3.5 status infra BZ 1127877 Awaiting review from danken, with ybronhei at LinuxCon. 14:52:58 <bkp> #info 3.5 status infra BZ 1127877 Assistance to review http://gerrit.ovirt.org/#/c/31400/2 and the rest of http://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:configurators_reorg,n,z requested; These were +1d or had no comments 14:53:03 <moolit> danken: I welcome religious wars but as I commented It isn't really relevant in the reorg patch since it only moved it 14:53:09 <bkp> Who's here from sla? 14:54:03 <msivak> bkp: I am, but I was not tracking the team issues since Doron has returned 14:54:26 <msivak> bkp: if you give me the bug numbers I can take a look 14:54:38 <danken> the prepareImage bugs are set on sla for some reason? 14:54:38 <bkp> msivak: Bugs 1128261 and 1130038 14:54:40 <Rydekull> (When you're done) whoever that's able to look at this i'll be very happy. Trying to compile ovirt-engine on Debian. http://fpaste.org/126842/48179114/ Thanks :-) 14:55:04 <bkp> Yeah, that's what sbonazzo had. 14:55:47 <msivak> bkp: the first one is something for kernel, are you sure about the number? 14:56:07 <bkp> 1129261 14:56:10 <bkp> Sorry 14:56:23 <bkp> While msivak is looking, amureini, did we cover all of storage's blockers? 14:56:34 <msivak> jmoskovc: ping, what is the status of 1130038? 14:56:50 <amureini> bkp, AFAIK, yes. 14:57:22 <jmoskovc> msivak: depends on: https://bugzilla.redhat.com/show_bug.cgi?id=1129261 14:57:29 <msivak> danken: I suppose because somebody decided we should use the storage api differently 14:57:42 <msivak> jmoskovc: that is the other one bkp is interested in 14:58:36 <jmoskovc> msivak: ah, they're waiting for the logs, going to append it there 15:00:25 <danken> msivak: yeah, now I see Federico doing this 15:00:27 <bkp> #info 3.5 status sla BZ 1129261 waiting for the logs, going to append it there 15:00:27 <bkp> #info 3.5 status sla BZ 1130038 waiting for the logs, going to append it there 15:00:27 <bkp> #info 3.5 status storage Blockers covered earlier in meeting 15:01:17 <bkp> That's all the blockers. Is there anything else that needs to be raised for 3.5? 15:02:22 <bkp> Going once for 3.5... 15:03:02 * sbonazzo need to leave 15:03:10 <bkp> bkp does, too. 15:03:19 <bkp> Moving on... 15:03:44 <bkp> #topic Conferences and Workshops 15:03:44 <bkp> #info Conferences and Workshops LinuxCon NA in progress. Three oVirt talks scheduled, lots of booth time for me. (Including now) 15:04:00 <bkp> #topic Other Topics 15:04:13 <bkp> Are there any open topics that need addressed? 15:04:53 <bkp> (Sorry for the rush, but oVirt's fans await...) 15:05:28 <bkp> Going once... 15:06:15 <bkp> Twice... 15:06:38 <bkp> Thanks to all! From the Windy City, good night! 15:06:48 <bkp> #endmeeting