14:02:19 #startmeeting oVirt Weekly Sync (Open Format) 14:02:19 Meeting started Wed Apr 22 14:02:19 2015 UTC. The chair is bkp. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:19 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:02:42 Good day all, welcome to the open session weekly meeting. 14:03:09 * sbonazzo here for the open session 14:03:29 This is going to be more free form than meetings past, as we transition from the status-report type meetings to something more discussion oriented. 14:04:08 #topic Agenda 14:04:33 #info 3.5 news 14:04:45 #info 3.6 news/discussion 14:04:55 #info Open Discussion 14:05:26 * awels here 14:06:01 ^^^ If this works. We still haven't set a schedule/structure for "Office Hours" so I don't want to ignore release status completely at this time. 14:06:15 bkp +1 14:06:35 #topic 3.5 news/discussion 14:07:06 Is there anything needed to report about the 3.5 branch? 14:07:33 bkp I sent a general status email to mailing list a couple of hours ago: http://lists.ovirt.org/pipermail/devel/2015-April/010315.html 14:07:53 for 3.5.2 we looks good to go with GA on april 28 14:07:59 only one bug still on QA 14:08:49 I'd like to ask if maintainers reviewed the package list I sent on RC4 release 14:09:08 to be sure that listed packages correspond to the ones maintainers want to release 14:11:09 Noted? Any other items to discuss on 3.5 status? 14:11:53 Okay... 14:11:56 I think that's all. I've not seen new bugs opened against 3.5.2 RC4 but also didn't get positive feedback 14:12:10 maintainers reviewed the asadpanda package list I sent on RC4 release Asmadeus 14:12:18 so I just assume that for example ovirt-live is working great :-) 14:12:34 maintainers reviewed the asadpanda package list I sent on RC4 release Asmadeus 14:12:37 10:09 sbonazzo: to be sure that listed packages correspond to the aterribl~ ones maintainers want to release 14:12:44 Hm 14:12:47 :-) 14:12:58 #info 3.5 general status email: http://lists.ovirt.org/pipermail/devel/2015-April/010315.html 14:13:01 #info 3.5.2 looks good for April 28 14:13:03 #info 3.5.2, only one bug in QA 14:13:04 Ah, there we go. 14:13:07 #info sbonazzo needs maintainers to review the package list he sent on RC4 release, to be sure that listed packages correspond to the ones maintainers want to release 14:13:12 Keymap not working right 14:13:29 #topic 3.6 news/discussion 14:13:30 bkp, for reference the package list is here: http://lists.ovirt.org/pipermail/devel/2015-April/010259.html 14:13:49 sbonazzo: Noted. 14:14:15 bkp sent a brief general status for 3.6 here: http://lists.ovirt.org/pipermail/devel/2015-April/010310.html 14:14:19 News or discussion matters for 3.6 development? Feature freeze is today, correct? 14:14:45 we currently have el6 repository broken by the removal of vdsm from it 14:15:14 we need to address it in the next couple of days 14:15:23 today is feature submission deadline 14:15:40 so we should start reviewing the submitted features 14:16:18 Who needs to address the broken repo? 14:16:26 we have a planned alpha release for may 6 14:17:01 bkp: for ovirt-host-deploy a ticket as been opened on infra for fixing the build job excluding 36 master from the build matrix 14:17:13 bkp for vdsm-node fabiand? 14:17:37 These are the instructions for converting centos into a host, right? http://www.ovirt.org/Quick_Start_Guide#Install_Fedora_or_CentOS_Host 14:18:16 mr_chris: That should work. Holding a meeting now, sorry. 14:18:39 sbonazzo: Anything else? 14:18:49 bkp, It doesn't. All it says to do is install the repo and configure iptables and disable network manager. 14:19:06 It doesn't say what to install for vdsm. 14:19:19 bkp let me check 14:19:24 mr_chris: Noted. Please stand by. 14:19:30 bkp, Thanks. Standing by. 14:20:02 I'd like to ask dev infra if there are news about jdk 1.8 / wildfly support 14:20:14 any progress on it? 14:21:24 on my side, I tried to rebuild jdk 1.7 from f20 on f22 and it didn't work very well as contingency plan 14:21:40 too many broken deps by the downgrade 14:21:51 and 1.7 can't be installed side by side with 1.8 14:21:51 Any one here form infra? 14:21:52 bkp, hey - all green from the Node side. 14:22:03 bkp, Node is building nicely and we are cleaning up and preparing for 3.6 14:22:06 fabiand: Noted, thanks. 14:22:17 fabiand: there's a small issue in vdsm deps on el6 14:22:28 Indeed 14:22:36 fabiand: http://lists.ovirt.org/pipermail/devel/2015-April/010312.html 14:22:39 Currently we are blocked by a dep issue, but that is hopefully just transient 14:22:55 fabiand: issue is that vdsm is not built anyymore on el6 for master 14:23:29 fabiand: so node on el6 can be dropped 14:23:36 for master 14:23:40 indeed, for master 14:23:41 yes 14:23:47 I thought that we've already done that 14:24:55 fabiand: loosk like some related job is still building rpms for el6 14:24:58 lloks 14:25:00 looks 14:26:08 bkp no more news on my side for 3.6 14:26:26 Okay, and no one from infra to answer the jdk question? 14:27:30 bkp:naybe mperina? masayag? 14:28:11 bkp ok, looks nobody around 14:28:17 Noted. 14:28:29 #info Brief general status for 3.6 here: http://lists.ovirt.org/pipermail/devel/2015-April/010310.html 14:28:32 #info el6 repo broken by the removal of vdsm, infra and node (fabiand) must address in the next couple of days 14:28:35 #info Node needs to be dropped on el6, which, according to sbonazzo some related job is still building RPMs for el6 14:28:38 #info Today (22.4.15) is feature submission deadline for 3.6 14:28:40 #info Submitted features need to be reviewed. 14:28:43 #info An alpha release of 3.6 is scheduled for May 6 14:28:44 #topic Open Discussion 14:28:46 #info Inquiry about jdk 1.8 / wildfly support for dev infra, no initial response. Using jdk 1.7 as a fallback is not optimal, sbonazzo reports 14:28:49 #info Node is building nicely and the team is cleaning up and preparing for 3.6, fabiand reports 14:29:13 For this, I open the virtual floor for any remainin dav/community issues. 14:29:24 *dev 14:29:56 One thing to resolve: if we move to office hours instead of this weekly meeting, how many would we like to hold? 14:30:00 bkp last week there was a report about a security issue with ovirt servers dcaro|lunch looks away, maybe he can update offline on hardening status 14:30:16 sbonazzo: Got it. 14:30:28 sbonazzo: I'm here 14:30:39 dcaro: hope you enjoyed the lunch :-) 14:31:15 dcaro: Any updates on locking things down? 14:31:30 sbonazzo: we are waiting for the sec team to finish the checks and give more feedback on best practices 14:31:57 dcaro: can you drop the directory listing template in the meanwhile? it's not working anymore 14:32:02 sbonazzo: but the immediate issue is solved 14:32:15 sbonazzo: what? 14:32:39 dcaro: http://resources.ovirt.org/pub/ 14:32:46 dcaro: it says it's empty 14:32:59 dcaro: while http://plain.resources.ovirt.org/pub/ shows content 14:33:04 sbonazzo: I see it ok 14:33:15 both 14:34:00 dcaro: weird, just refreshed clearing browser cache and now it works 14:34:04 dcaro: nevermind 14:35:18 sbonazzo: happened before, I think it's apache related, have to investigate but does not seem too problematic 14:35:32 so low prio 14:35:35 dcaro: ok 14:35:37 Okay, thanks, dcaro 14:35:52 bkp about your topic 14:35:58 Re: office hours: I was thinking three times a week? Two? 14:35:58 "if we move to office hours instead of this weekly meeting, how many would we like to hold?" 14:36:39 * dcaro 14:36:45 I'd like an early-morning one that will catch the EU/west Asia community members 14:36:46 I would 14:36:50 bkp I guess 2 may be enough, wed and fri ? middle week and end of week? 14:37:25 fri would not catch the guis in israel 14:37:33 *guys 14:37:41 dcaro: tue and thu? 14:37:45 Then maybe one that would be more conveient for Pacific region 14:37:55 Tue and Thurs seem good 14:37:57 sbonazzo: ok for me 14:38:54 I was also thinking these would be moderated (lightly) and the moderators could be just people who signed up and would rotate. 14:40:08 let's start without moderation and see if it's needed 14:40:17 So, the storage team already has a community gardener person who rotates. I would suggest that this could be a standing thing for them. 14:40:33 we have 200 quiet users here :-) 14:40:43 sbonazzo: How would that work? 14:41:32 I'm thinking there needs to be a scheduled time that people would absolutely know someone was available to answer questions/host discussions. 14:42:44 +1 14:42:54 Questions would still be answered at any time of the day, but knowing there was an open/planned meeting time would be useful, too 14:43:15 bkp and we can commit to be there I mean, ok for the days, ok for the hours, ok for rotating, not sure that a moderator is needed during the 1/2 hour or full hour of presence 14:43:19 sbonazzo: ^^^ That's all I mean by moderation. 14:43:30 bkp: oh 14:43:32 bkp ok 14:44:01 They could come on, say "I'm here," "Is there anything we need to go over?" 14:44:25 bkp +1 14:44:41 If yes, off they go to help. If no, then "I'll be here until ___, so feel free to ask" 14:45:06 Then they would have to make sure they keep an eye on the channel during the office hour period. 14:45:36 But if it's quiet, there's nothing that says the moderator can't just keep working on whatever. 14:47:01 Does that seem reasonable? 14:47:51 Also, how long do we think will be useful? 30 minutes? 60? Something else? 14:49:08 bkp looks ok to me. I'd start with 30 minutes and see if more if needed 14:49:36 bkp: maybe better ask on the list so the team leads can say how much will they allow 14:49:55 dcaro sbonazzo +1 (x2) 14:50:57 Okay, any other issues outstanding? 14:52:09 Going once... 14:53:32 Twice... 14:53:45 #info On the issue of server hardening, dcaro reports that we are waiting for the sec team to finish the checks and give more feedback on best practices 14:53:48 #info bkp suggests that office hours be held for set half-hour periods, moderated by a rotation of community members. Format should be open, answering all questions and discussing any cross-team/community-wide issues as needed. Twice a week, Tuesdays and Thursdays. 14:53:52 #action bkp will ask on community mailing lists to finalize discussion on office hour format 14:54:05 Then we are done for today! Thanks! 14:54:10 #endmeeting