14:01:45 #startmeeting oVirt Weekly Sync 14:01:45 Meeting started Wed Apr 15 14:01:45 2015 UTC. The chair is sbonazzo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:45 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:01:45 #topic Agenda and Roll Call 14:01:45 #info infra_ownr|dcaro: Security incident status 14:01:45 #info bkp: conferences and workshops 14:01:45 #info ydary: Sync future and format change 14:01:46 #info sbonazzo: Outages in Jenkins due to no space left on master 14:01:46 #info sbonazzo: Blockers review for 3.5.2 GA 14:01:48 #info sbonazzo: Packages review for 3.5.2 GA 14:01:48 #info sbonazzo: Next week is feature submission deadline: plans for reviewing submitted features 14:01:50 #info sbonazzo: Support for JDK 1.8 / Wildfly progress updates / Contingency plan of building Java7 rpms for Fedora 22. 14:01:50 #info SvenKieske: review Bug 1156115 - [RFE] don't use dd to copy sparse images in order to save time and bandwith from exportdomain 14:01:56 ovirtbot pingall Who's here for oVirt Sync meeting? 14:01:56 Who's here for oVirt Sync meeting? 14:01:56 a1-away aaviram abonas AbyssOne_ ahadas alinefm alitke alkaplan alonbl apahim apuimedo asadpanda Asmadeus aterribleloss autoditac bazulay bdperkin bitchecker bkorren bkp BlackPanx bobdrad1 brad_mssw bsanford capri_on CAPSLOCK2000 cereal chasmo77 christyp clarkee 14:01:56 clouseau cmestreg cnanakos_away Comnenus coreping coxn cpb crobinso crobinso_ cshereme Cybertinus cyclonis d4n13L danken dasjoe dbrandon delhage Dick-Tracy didi dignus djasa dl9pf_ doron_ dougsland dustinm` DV_ dyasny ecohen edong23 eedri emesika engkur evil_steve 14:01:56 evilissimo1 ewoud fgeorgalas firemanxbr frolland fromani fsimonce funnel fw G-virt garrett_ gchaplik gergc gklein gotgnu gshereme HK hmpf Hubert ichdasich inetpro infra_ownr|dcaro IOMonster iranzo ishaby itamar j0lly jboggs jbrier jbrooks jhernand jinzo jmh_ro 14:01:56 jniederm johnbt jotun jurekr jvandewege kamdard kanagaraj karimb karnan Killsudo killsudo_m KindOne KriP LaercioMotta lagarcia laine Larsen lbianc lveyde lyang0 masayag_ mbetak mehdi___ mikedep333 misc mivaho mlipchuk mmucha Mossel movciari mshira msivak mskrivanek 14:01:56 mtayer NoiseDoll Norky novae nsoffer nus NuxRo oliel omachace OnTheRock opuk Orphis_ outi oved Overand overyander ovirtbot pankaj pdangur pgrunt phoracek pixelb pkliczew plustwo primalmotion quaid RameshN ramonn raso Raylaan rbarry rgolan rmatinata rnori RobertM 14:01:56 robin5210 Rockybalo rssfed23 rtsq rvalles Rydekull sagarC___ samppah sbonazzo sgordon sgotliv shaharh shaunm Shiva6 shubhendu shug side_control silug singler_ sir_iw sp33t srepetsk sshnaidm straff Svedrin SvenKieske tal Telsin Thalamus tier timbyr tiraboschi_ 14:01:56 tjelinek tlitovsk tomased tomaw tuxbiker varesa vincent_vdk w0lfeh wgao wicope wojtek1 xnaveira xrsanet YamakasY ybronhei ydary ykaplan yzaspits zeddii zerick Zordrak 14:01:56 Who's here for oVirt Sync meeting? 14:02:10 * infra_ownr|dcaro 14:02:38 not me 14:02:38 * alitke here 14:02:48 * fromani here 14:03:06 #chair infra_ownr|dcaro alitke fromani 14:03:06 Current chairs: alitke fromani infra_ownr|dcaro sbonazzo 14:03:46 #topic Security incident status 14:03:50 * tal here 14:04:00 infra_ownr|dcaro: do you want to update us? 14:04:14 #chair tal 14:04:14 Current chairs: alitke fromani infra_ownr|dcaro sbonazzo tal 14:05:07 so, from previous discussion with infra_ownr|dcaro: 14:05:16 sbonazzo: ok 14:05:18 #info We did got hacked, a couple of files where uploaded but no privilege escalation. 14:05:18 #info oVirt infra solved the issue though they are still scanning for more security and planning to highly improve the security asap 14:05:18 #action oVirt infra to highly improve the security asap 14:05:53 sbonazzo: yep :) 14:06:01 infra_ownr|dcaro: any more info ? 14:07:28 ok, let's keep it offline if there are more info available 14:07:37 * lvernia is here. 14:07:41 #topic conferences and workshops 14:07:41 #info the most important thing is yet-another request for help at Grazer Linux Days in Graz, Austria this weekend 14:07:41 #info Rene Koch is seeking backup help manning the booth at that event 14:07:41 #link http://lists.ovirt.org/pipermail/users/2015-April/032251.html 14:07:41 #info All other event and conference news is the same as two weeks ago. 14:07:42 #link http://plain.resources.ovirt.org/meetings/ovirt/2015/ovirt.2015-04-01-14.02.log.html 14:07:49 #chair lvernia 14:07:49 Current chairs: alitke fromani infra_ownr|dcaro lvernia sbonazzo tal 14:08:03 any other new conference to be noted? 14:09:21 ok, if there are any new conference please update offline 14:09:25 #topic Sync future and format change 14:09:25 #info bkp sent some thoughts to mailing list 14:09:25 #link http://lists.ovirt.org/pipermail/users/2015-April/032389.html 14:09:40 we started the discussion in last meeting 14:09:53 but we had no decision yet 14:10:21 #link previous meeting logs: http://plain.resources.ovirt.org/meetings/ovirt/2015/ovirt.2015-04-08-14.09.log.html 14:10:23 * danken knows not if the approaching kvm-forum deadline was mentioned 14:10:53 danken: yes it was: 14:47:04 Planning for KVM Forum is up and running. KVM- and oVirt-related talks should be submitted at http://events.linuxfoundation.org/events/kvm-forum/program/cfp 14:11:22 14:47:08 before May 1. 14:11:58 does anybody something to share about the future format change? 14:12:36 action item was "Please reply to mail on sync format with ideas on how to change this meeting's format to something more useful and engaging. Link: http://lists.ovirt.org/pipermail/users/2015-April/032185.html" 14:13:33 there was a proposal from misc:14:37:26 more a office hours, saying to people "if someone ask a question on irc, someone should answer" 14:13:47 +1 14:14:40 bkp: also said in his email to ml: 14:14:41 What I suggest, then, is a series of "office hours," where a rotating set of oVirt team members will commit to being on IRC to answer questions and be generally available. This could be done by one or two people, a few times a week/once a week, and not even a whole hour. Once a schedule is figured out, it would be posted and people would be openly encouraged to participate. This would be an open session on IRC... suppor 14:15:20 sbonazzo: This sounds reasonable. 14:15:31 sbonazzo: sounds interesting indeed 14:15:37 sbonazzo: And further discussion could be carried over the mailing list if need be? 14:15:40 so let's vote, looks like we have at least 3 +1 14:15:55 lvernia: I think so 14:16:01 +1 for me too 14:16:03 sbonazzo: As sometimes the "volunteer" would likely not have all the answers... 14:16:13 lvernia: I agree 14:16:19 let's make it simpler 14:16:26 anybody against the proposal? 14:16:41 I'm in for that, I think that even if the "volunteer" will not know all the answers, he will know who to turn to to get the information needed 14:17:14 ok, looks like we have an agreement 14:17:34 #agreed on a series of "office hours," where a rotating set of oVirt team members will commit to being on IRC to answer questions and be generally available. This could be done by one or two people, a few times a week/once a week, and not even a whole hour. Once a schedule is figured out, it would be posted and people would be openly encouraged to participate. This would be an open session on IRC... support questions, c 14:18:13 #agreed on moving to carry over to the mailing list topics that need to be covered there because the volounteer doesn't have the answers 14:18:20 #undo 14:18:20 Removing item from minutes: AGREED by sbonazzo at 14:18:13 : on moving to carry over to the mailing list topics that need to be covered there because the volounteer doesn't have the answers 14:18:35 #agreed on carrying over to the mailing list topics that need to be covered there because the volounteer doesn't have the answers 14:19:00 anything else to be added? 14:20:06 I'll take it like a no, let's move on 14:20:11 #topic Outages in Jenkins due to no space left on master 14:20:32 infra_ownr|dcaro: we had several issues in last few days with jenkins master going out of space 14:20:45 infra_ownr|dcaro: anything we can do for preventing it to happen again? 14:22:09 sbonazzo limit all your jobs history to ~100 tops 14:22:39 infra_ownr|dcaro: do we need to change manually all of them? or do we have a global config? 14:24:36 #info we had several issues in last few days with jenkins master going out of space 14:24:36 #info solution is to limit job history to ~100 tops 14:24:36 #action jenkins job owners to review their jobs and fix them if needed 14:24:36 #action infra owner to check if a global config may enforce it 14:24:37 sbonazzo: the yaml ones there's no need, but non-yaml ones must be changed manually 14:24:46 #undo 14:24:46 Removing item from minutes: ACTION by sbonazzo at 14:24:36 : infra owner to check if a global config may enforce it 14:24:51 infra_ownr|dcaro: thanks 14:25:01 I changed the ones that took most space 14:25:19 infra_ownr|dcaro: ok, that should save us for a while 14:25:25 let's move on 14:25:31 #topic Blockers review for 3.5.2 GA 14:25:51 #link oVirt 3.5.z status: http://lists.ovirt.org/pipermail/devel/2015-April/010261.html 14:26:12 lvernia: news about the network blockers? 14:26:20 sbonazzo: Pffff. 14:26:45 sbonazzo: We're half-clueless. It's not even clear that it's reproducible outside our testing environment. 14:26:52 lvernia: I've understood it's affecting mostly ovirt-node and it's not reliably reproducible 14:27:02 sbonazzo: But we're working on it. Me, fabiand, ibarkan and mburman. 14:27:07 sbonazzo: Exactly. 14:27:14 lvernia: so maybe not worth to block 3.5.2 GA 14:27:27 sbonazzo: Depends whether GA includes node or not. 14:28:00 lvernia: historically node arrives a week or so after GA but uses vdsm from GA 14:28:15 sbonazzo: So this might not necessarily be the case... 14:28:16 lvernia: so if the fix is going to be in vdsm maybe an async release will be needed 14:28:23 sbonazzo: That seems likely. 14:28:36 sbonazzo: But sure, I don't mind releasing vdsm first without node. 14:28:48 sbonazzo: We have no indication that this happens on other hypervisor OSs. 14:29:51 lvernia: ok, let's see if we discover something before GA date (22 Apr) and let's decide then what to do 14:30:17 tal: storage issues? 14:30:20 sbonazzo: Ack. 14:30:50 No, currently working on our major RFEs 14:30:55 Updates on those? 14:31:43 So i guess we can change topic :-) 14:31:43 Ceph integration - We gave QE a scratch build and it underwent first pre-integration, we got feedbacks from them, some are irrelevant anymore since more work has been done after the scratch build given to them and some was relevant and we are working on it 14:31:54 SPM removal - nothing new from last week, work is still in progress 14:32:01 #topic Storage updates 14:32:02 Resize LUN - We had our first meeting with QE, no feedbacks from them yet 14:32:14 #info Ceph integration - We gave QE a scratch build and it underwent first pre-integration, we got feedbacks from them, some are irrelevant anymore since more work has been done after the scratch build given to them and some was relevant and we are working on it 14:32:22 #info SPM removal - nothing new from last week, work is still in progress 14:32:28 Those are the major ones, the rest of the RFEs there's nothing to report for now, work is in progress 14:32:33 #info Resize LUN - We had our first meeting with QE, no feedbacks from them yet 14:32:41 #info the rest of the RFEs there's nothing to report for now, work is in progress 14:32:45 tal thanks 14:32:49 tal before you leave 14:33:06 for 3.5.2 we're going to release an update to qemu-kvm-rhev 14:33:46 tal can you confirm if we want qemu-kvm-rhev-1.5.3-86 here and not qemu-kvm-ev-2.1.2-23 14:33:59 mskrivanek: ^^ for virt side too 14:34:10 fromani: ^^ 14:34:55 #topic Packages review for 3.5.2 GA 14:34:56 sbonazzo: Not sure, I have to do my homework on this one, one thing I do know is that we found a bug with qemu >2 and certain storages 14:35:13 tal so likely we'll have 1.5 there 14:35:32 sbonazzo: for virt side I'm not aware of any need for qemu-rhev > 1.5, so 1.5 should be good for us 14:35:32 sbonazzo: All the data is in that bug - https://bugzilla.redhat.com/show_bug.cgi?id=1209034 14:35:35 #link candidates to 3.5.2 GA: http://lists.ovirt.org/pipermail/devel/2015-April/010259.html 14:35:45 And the bug that is blocking it, please review before your decision 14:37:24 #info qemu-kvm-rhev-1.5.3-86 is best candidate for 3.5.2 GA due to https://bugzilla.redhat.com/show_bug.cgi?id=1209034 related to qemu-kvm-ev-2.1.2-23 14:37:53 #action maintainers please review the package list and ensure it's all you expect to be released there 14:38:28 #topic Support for JDK 1.8 / Wildfly progress updates / Contingency plan of building Java7 rpms for Fedora 22. 14:38:51 #info infra update: Proceeding well with 3.6 items, fence refactoring is almost done, VDSM events work is in progress, host upgrade manager is progressing well both in the host and engine side, and more. We will also start looking at Jboss-widlfly support in a few days, and see how we can proceed with supporting it. 14:39:24 so I guess we can postpone this to next week meeting or to mailing list for updates 14:39:48 #action infra to follow up on Jboss-widlfly support for 3.6 14:40:24 #action integration to check if contingency plan of using jdk7 may work 14:40:47 #topic SvenKieske: review Bug 1156115 - [RFE] don't use dd to copy sparse images in order to save time and bandwith from exportdomain 14:40:54 SvenKieske: around? 14:41:02 yes 14:41:13 SvenKieske: looking at the bug looks like you're all set 14:41:16 sbonazzo: I already did get a reply 14:41:28 sometimes sending a mail helps ;) thanks! 14:41:32 SvenKieske: great, so moving on 14:41:45 #topic Next week is feature submission deadline: plans for reviewing submitted features 14:42:03 so, next week is feature submission deadline 14:42:21 how are you with feature pages / bugs and so on? ready for the review? 14:43:21 how do we want to review them? sync meeting? every team to plan a session for presenting the features? 14:43:32 ... 14:43:32 lvernia: Error: ".." is not a valid command. 14:43:40 sbonazzo: I already noticed at least in the google doc are many features pages missing 14:43:54 I don't know if they exist in the wiki, didn't bother to search for them yet 14:43:58 Many are not worth a feature page, BZ includes all relevant information. 14:44:14 At least for networking there are more than a couple. 14:44:36 lvernia: well, I think that if that's the case, on the feature column there should be something like "minor feature, no feature page needed" 14:44:39 afaik release management rules say that for each feature there must be a feature page, but ymmv 14:45:02 I can understand if it's too much overhead for small features 14:45:20 I can mark the spread sheet accordingly, not leave anything empty. 14:45:32 Instead be explicit about what doesn't need one, in my opinion. 14:45:36 SvenKieske: well, feature page may be the bug itself provided it contains: feature, contingency plan, test case, release notes if it's a really small feature 14:46:44 so we're going to take for granted that if a feature is missing the feature page, the bug itself has to be considered as the feature page 14:47:00 Usually such features wouldn't need e.g. a contingency plan. 14:47:08 And test cases will be relatively obvious. 14:47:09 etc. 14:47:20 On the spreadsheet we have anything that's an RFE, not only big features. 14:47:24 lvernia: ok. I see there are also features without bz 14:47:34 sbonazzo: That's weird :) 14:47:46 #link features spreadsheet: http://goo.gl/9X3G49 14:48:10 Network looks safe :p 14:48:35 #info features without a feature page will take the bugzilla page as feature page to be reviewed 14:48:52 #info Usually such features wouldn't need e.g. a contingency plan and test cases will be relatively obvious. 14:49:26 #action features owner to ensure all features have at least the bugzilla entry to be reviewed 14:50:07 #info submission deadline is April 22th 14:50:40 about the review method, sync meeting? team organized meetings? 14:50:52 mailing list discussion? 14:51:54 If I remember correctly for 3.5 and 3.4 each team organized a presentation of the features 14:52:08 in irc / video conf 14:52:09 It varied. 14:52:18 I think bigger features merited their discussions. 14:52:25 But others were only discussed on mailing lists. 14:52:40 In 3.4 I remember we presented vNIC profiles and labels. 14:52:50 But in 3.5 we had no complex features. 14:53:38 ok, let's take this to the mailing list, looks like we need more people to decide how to handle 14:54:07 Ack. 14:54:15 #action follow up on how to review the proposed features (irc, hangout, ...) 14:54:18 :) 14:54:25 #topic Other topics 14:54:49 anybody want to discuss about something oVirt related? 14:55:34 do you want to report on feature progress for 3.6? we said it can be done by email / newsletter but we still have some time for it in this meeting 14:57:05 or we can end the meeting here... 14:58:03 going twice 14:59:02 ok guys, have a nice week 14:59:06 #endmeeting