15:01:15 #startmeeting oVirt Weekly Sync 15:01:15 Meeting started Wed Nov 19 15:01:15 2014 UTC. The chair is bkp. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:15 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:01:31 #topic Agenda and Roll Call 15:01:38 #info infra update 15:01:38 #info 3.5.z updates 15:01:38 #info 3.6.0 status 15:01:38 #info conferences and workshops 15:01:39 #info other topics 15:01:56 * sbonazzo here for integration 15:02:04 * mlipchuk here for storage 15:02:18 Okay, I think we are back on track with the meeting schedule. Apologies to all for the confusion these last few weeks. 15:02:28 * lvernia is here. 15:02:44 * ofrenkel here 15:03:18 Great, good to hear from everyone! 15:03:20 * rgolan rgolan here 15:03:21 #topic infra update 15:03:30 * rgolan here 15:03:44 Hey rgolan , we got you. 15:03:54 What's the word from infra? 15:04:28 dcaro? 15:05:29 eedri? Anything from infra? 15:05:58 bkp: we had an outage in phx2 lab a couple of days ago 15:06:23 bkp: should be at least partially solved since I can see most of the slaves up and running 15:07:13 bkp I don't have more details on the forensic of the case 15:07:27 sbonazzo: we apparently lost our f21 slave, which we try to run functional vdsm tests on 15:07:47 danken: please send an email to infra@ovirt.org 15:07:59 sbonazzo: the state of vdsm jenkins jobs is a mess :-( 15:08:00 there are many false failures on engine patches, we really need to recover these, as jenkins becomes non reliable for developers 15:08:14 danken: it's not only vdsm.... 15:08:27 sbonazzo: we communicated with dcaro, but ok. 15:08:44 sbonazzo: is opening a ticket better from your perspective? 15:09:27 danken: maybe, yes. sadly infra team is understaffed, any help from developers is welcome for maintaining jenkins jobs 15:09:38 danken: I would say a ticket is better just from a documentation/accountability perspective. 15:09:53 sbonazzo: exactly my point - I want to own a slave, so phoracek can fix the vdsm job 15:10:16 sbonazzo: but he's waiting for 2 weeks for slave credentials 15:10:24 danken: for taking ownership of the slave I guess a formal vote on infra@ovirt.org is needed 15:11:37 danken: ok, let's push this offline on mailing list 15:12:05 sbonazzo: Agreed. Maybe there should be a streamlining of that vote process. 15:12:55 Anything else? 15:13:07 bkp please add action item on dcaro to review the status of danken 's request 15:13:29 Already have it prepped. 15:14:26 bkp I guess that's all for infra for now 15:15:00 Okay. 15:15:08 #info Infra We had an outage in phx2 lab a couple of days ago, seems to be resolved. 15:15:11 #info Infra We apparently lost our f21 slave, on which we try to run functional vdsm tests 15:15:14 #info Infra The state of vdsm jenkins jobs is a mess, people are waiting a long time to get their credentials. 15:15:17 #action Infra dcaro: Discuss on mailing list how slave ownership process can be sped up, per danken concerns in this week's meeting 15:15:20 #info Infra The team is understafffed and looking for help from developers to maintain Jenkins jobs. 15:15:23 Moving on... 15:15:32 #topic 3.5.z updates 15:15:43 sbonazzo: What's the word? 15:15:44 sbonazzo: /me just sent a formal request to own the job and its slave(s) 15:16:08 bkp: sent a status report this morning here: http://lists.ovirt.org/pipermail/users/2014-November/029282.html 15:16:29 bkp we still have 4 blockers open and 5 regression to be reviewed 15:16:36 bkp RC is scheduled for next week 15:16:48 bkp so we need an ETA on the blockers 15:17:26 bkp also bug count is still high, remaining bugs must be scrubed and postponed to later releases if not blocking / urgent 15:18:56 sbonazzo: That RC is for 3.5.1, correct? 15:19:01 bkp yes 15:19:40 sbonazzo: Also, should there be a status on the addition of el7 support to the 3.5.x cycle? Issues with the test builds? 15:19:55 * tal here 15:19:59 bkp: as far as I know el7 build is completed 15:20:07 bkp it should be fully testable on el7 15:20:36 bkp: help testing nightly snapshot before RC is welcome 15:21:10 bkp http://www.ovirt.org/OVirt_3.5.z_Release_Management#Nightly_Builds 15:21:17 Coolness. Anything else? 15:21:50 bkp that's all for 3.5 on integration / releng side 15:22:13 bkp: sbonazzo I suppose I'm a little late :/ 15:22:42 dcaro: A bit. :) Did you have anything to add to the infra discussion? 15:23:25 sbonazzo: Acknowledged on the 3.5 news. 15:23:57 #info 3.5.z updates Full report at http://lists.ovirt.org/pipermail/users/2014-November/029282.html 15:24:00 #info 3.5.z updates Highlights from report: 4 blockers open, 5 regressions to be reviewed 15:24:03 #info 3.5.z updates RC for 3.5.1 is scheduled for next week, so ETA needed on blockers 15:24:06 #info 3.5.z updates Bug count is still high (150), review and either scrub or postpone to next release if not blocking or urgent. 15:24:09 #info 3.5.z updates .el7 support for engine is completely built and fully testable on el7. Help testing nightly snapshot prior to RC next week is welcome. 15:24:44 bkp: we did an engine upgrade and jenkins upgrade last week, the engine upgrade is not finalized yet (had some issues with vdsm, looking into it) but the system is stable now, have to plan with caution to finish the upgrade 15:25:04 speaking of 3.5 - has anybody noticed a problem installing on el6.6 hosts? 15:25:05 #topic infra update part 2 15:25:07 (engine is 3.5, there's on ehost with vdsm 3.5, all the others are 3.4) 15:25:39 danken: installed yesterday for log-collector testing, no issue on engine side 15:26:20 there's a confusing report about libvirtd interfering with vdsm 15:26:22 Bug 1162539 - libvirtd cannot be started using upstart if started manually using sysvinit 15:26:31 I wonder if anybody noticed something similar 15:26:34 dcaro: ETA on that plan? 15:26:54 dcaro: We currently investigating an issue which could be related when creating a volume on RHEL 6.6 15:27:25 dcaro: but that is still under investigation 15:27:54 mlipchuk: good to know, can you add me to the list if any? So I'll be aware? 15:28:11 bkp: not really yet, but hopefully next week 15:28:17 dcaro: though the version is 3.4 15:28:30 #info Infra An engine upgrade and jenkins upgrade were performed last week. The engine upgrade is not finalized yet (had some issues with vdsm, looking into it) but the system is stable now, have to plan with caution to finish the upgrade. (Hoipefully next week) 15:28:32 dcaro: this is the bug https://bugzilla.redhat.com/show_bug.cgi?id=1160620 15:28:34 #info Infra We currently investigating an issue which could be related when creating a volume on RHEL 6.6, but that is still under investigation 15:29:31 mlipchuk: oh, no the issue I had was that vdsm removed all the network configuration so the host was unreachable, strangely after one day the host came back online (I rebooted it like 50 times in the meantime, trying to get ILO console to work) 15:31:31 #topic 3.5.z updates part 2 15:31:42 #info 3.5.z updates There may be a problem installing on el6.6 hosts. Bug 1162539 libvirtd cannot be started using upstart if started manually using sysvinit. Let's check this one out, please. 15:31:51 Okay, let's keep going... 15:32:00 #topic 3.6 status 15:32:14 Any burning issues for 3.6 this week? 15:32:23 bkp sent a status report this morning here: http://lists.ovirt.org/pipermail/users/2014-November/029283.html 15:32:36 bkp no blockers as expected so early in the release cycle 15:33:13 bkp discussion about release process / release criteria should have been closed last week, but no progress since its opening 15:34:00 bkp added External Project Schedules to the report for having a look at what will be out with ovirt 15:34:11 sbonazzo: If there's no input, things should probably stay as proposed, shouldn't they? 15:34:45 lvernia: 2 proposal 15:34:47 1) keeping the same release criteria we had for 3.5 [2] 2) review the proposed changes [3] and prepare new release criteria for 3.6 15:34:57 [2] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria [3] http://lists.ovirt.org/pipermail/devel/2014-September/008695.html 15:35:12 lvernia sbonazzo I would say so. If you don't chime in, then that's implicit approval. 15:35:13 lvernia: poll open :-) 15:36:17 bkp so both option acknowledged or indifferent? just pick one and go with that? 15:36:52 sbonazzo: You suggested [3] due to deficiencies you noticed in [2]? 15:37:01 lvernia: yep 15:37:06 sbonazzo: I would hope not. 15:37:09 So there's one vote for [3] over [2] :) 15:37:21 lvernia: thanks :-) 15:37:28 But lvernia has a point. 15:38:07 bkp: I agree 15:38:28 I will make on more entreaty here to get people to chime in. 15:38:36 Anything else? 15:38:48 * lvernia Googles "entreaty". 15:39:18 bkp scheduling / timeline is not yet defined for 3.6 hope to get a cleaner view on what's going to be in for next week 15:39:21 lvernia: See: harrass 15:39:42 Well, I see both [2] and [3] suggest 3.6 be released 6 months after 3.5. 15:40:08 Was there any input on why it wouldn't be 6 months? 15:40:45 lvernia: http://lists.ovirt.org/pipermail/users/2014-November/028875.html 15:41:28 Ahh yes, I remember reading those :) 15:41:29 Thanks. 15:42:00 And you're saying the deadline for deciding was a week ago? :) 15:42:32 lvernia: well... yes according to existing process 15:42:41 Which is what we're voting on :p 15:42:48 lvernia: yep 15:43:17 Let's move that offline, and try to get more input on all of these. 15:43:24 bkp: +1 15:43:29 Yes, same as two and three weeks ago... 15:43:48 * rgolan have no clue on what this is about 15:43:57 lvernia: well, at least we have your vote :-) 15:44:09 rgolan: Deciding on a time frame for 3.6. 15:44:17 Well, if no one cares, then we'll leave it to team leads. 15:44:17 rgolan: Nobody seems to care so no decision is made :p 15:44:37 lvernia: I figured that out from the mail archive... :P 15:45:02 #info 3.6 status Full report at #info 3.5.z updates Full report at http://lists.ovirt.org/pipermail/users/2014-November/029282.html 15:45:05 #info 3.6 status No blockers! Well, that's expected. 15:45:07 #info 3.6 status External Project Schedules to the report for having a look at what will be out with oVirt 15:45:10 #info 3.6 status Discussion about release process / release criteria should have been closed last week, but no progress since its opening 15:45:13 #action 3.6 status All: If you want to have a say in the release process, get in on the discussion: http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria http://lists.ovirt.org/pipermail/devel/2014-September/008695.html 15:45:17 #info 3.6 status scheduling / timeline is not yet defined for 3.6 hope to get a cleaner view on what's going to be in for next week. 15:45:20 #info 3.6 status Still looking at 6 months out in both release process proposals, but danken has a proposal to extend the cycle. http://lists.ovirt.org/pipermail/users/2014-November/028875.html 15:45:24 #action 3.6 status All: let's examine and vote on proposal to extend the cycle. http://lists.ovirt.org/pipermail/users/2014-November/028875.html 15:45:27 Okay, any other 3.6 issues? 15:45:39 bkp: danken was the one suggesting shortening the cycle. 15:45:49 bkp: If I understand correctly. 15:46:01 Ah, misread the thread. 15:46:18 lvernia: right. I'd like to have more small cycles 15:46:18 bkp: lvernia which I think is kind make sense for big features 15:46:18 bkp: I would say there's disagreement on the ideal length of a minor version :) 15:46:30 which means more test days 15:46:41 and less horrible slips in scheduule. 15:46:56 #info 3.6 status CORRECTION: Still looking at 6 months out in both release process proposals, but danken has a proposal to change the cycle. http://lists.ovirt.org/pipermail/users/2014-November/028875.html 15:47:00 #action 3.6 status CORRECTION: All: let's examine and vote on proposal to chage the cycle. http://lists.ovirt.org/pipermail/users/2014-November/028875.html 15:47:35 Unfortunately, we need to discuss offline, have to wrap this up. 15:47:42 bkp ok 15:47:46 #topic conferences and workshops 15:47:47 danken: this would probably mean the feature evolves differently than putting all in into a single version no? 15:48:01 #info LISA14 went pretty well. Booth traffic was solid, gshereme and bkp answered a fair amount of general questions about oVirt, and talked to a lot of sysadmins with specific queries on oVirt. 15:48:05 #info FOSDEM is the next big event. OSAS will be very much on the scene, and oVirt has applied for a booth at the event. There is still time to get your talks into the IaaS and Virt devrooms. 15:48:09 #info Now that travel is wrapped up, I am working on getting meetup and workshop materials ready for anyone who wants to present on oVirt at a local event. 15:48:24 Any other conference news? 15:49:21 Okay, moving on. 15:49:24 bkp: do we know what people at FOSDEM would like to here on oVirt or we just come up with something (not very interesting probably...) 15:49:29 bkp 11th Intl. Conf. on Open Source Systems CFP Open Through Jan. 10 call for papers http://www.oss2015.org/call-for-papers/ 15:49:38 bkp: s/here/hear 15:50:40 rgolan: JUst submit something you think is interesting. 15:50:45 #info 11th Intl. Conf. on Open Source Systems CFP Open Through Jan. 10 call for papers http://www.oss2015.org/call-for-papers/ 15:51:11 #topic other topics 15:51:23 #info A big welcome to our new OPW interns! Be ready to assist with any of their questions as they lurk about the channel and the lists! 15:51:26 #info It was brought to my attention this morning that ovirt.org/stats has not been working for a while. I have asked misc to look into it. 15:51:29 #info Speaking of stats, downloads for oVirt engine in Oct. totaled 1460 from resources.ovirt.org. This is down from 2194 downloads in Sept. Likely now that 3.5 is rolling out, this trend will likely change. 15:51:33 #info One of the big goals we should have for 2015 is figuring out a way to determine actual installs of oVirt. If anyone has ideas on how we can pull such information together, let's get a discussion going on the users mailing list. 15:51:37 #info Finally, there is an informal survey out on the users mailing list now about extending oVirt support to Debian/Ubuntu. Got thoughts on this? Here's the thread: http://lists.ovirt.org/pipermail/users/2014-November/029209.html 15:52:00 rgolan: yes. it means that big feature should have smaller milestones. which I think is a Good Thing 15:53:02 Does anyone want to raise an issue? discuss something? 15:54:04 Going once? 15:54:49 Okay, thanks, see you all next week. 15:55:01 #endmeeting