15:01:32 #startmeeting oVirt Weekly Sync 15:01:32 Meeting started Wed Nov 5 15:01:32 2014 UTC. The chair is bkp. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:32 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:01:47 #topic Agenda and roll Call 15:01:59 * lvernia is here. 15:02:07 #info infra update 15:02:08 #info 3.5.z updates 15:02:08 #info 3.6.0 status 15:02:08 #info conferences and workshops 15:02:10 #info other topics 15:02:23 * sbonazzo here 15:02:25 Hey, lvernia 15:02:29 bkp: Yo. 15:02:31 And sbonazzo 15:03:25 Let's start with the first topic... 15:03:37 #topic infra update 15:04:17 Who's here for infra? 15:04:36 bkp: while waiting for dcaro to show up, a few notes from jenkins 15:04:59 bkp: engine is failing build on master and 3.5 probably due to infra issues 15:05:42 bkp: a nasty bug in F21 rpm package have been solved so failures related to fedora 19 builds on f21 slaves are solved 15:06:47 bkp: some build failures are expected in next days due to missing dependencies on el7 and f21 while building engine for those distributions 15:07:23 bkp that's all from my side for infra 15:07:50 dcaro? Anything from you? 15:09:19 dcaro anything for infra 15:09:21 ? 15:10:06 Does not seem like it. 15:10:17 #info infra update: engine is failing build on master and 3.5 probably due to infra issues 15:10:21 #info infra update: a bug in F21 rpm package has been solved so failures related to fedora 19 builds on f21 slaves are solved 15:10:24 #info infra update: some build failures are expected in next days due to missing dependencies on el7 and f21 while building engine for those distributions 15:10:27 Moving on... 15:10:37 #topic 3.5.z updates 15:10:57 sbonazzo: Anything? 15:11:26 bkp we're on track for now, 1 blocker around, tiraboschi_ is taking care of it 15:11:54 bkp sent a status email this afternoon: http://lists.ovirt.org/pipermail/users/2014-November/028942.html 15:12:13 bkp still an high count of bugs 15:12:53 hello, is ovirt 3.5 ready to be installed on centos7? 15:13:06 bkp there's time before RC but maintainers should start review them 15:13:21 afics_: in a meeting now, but not yet 15:13:36 ok, what's the ETA? 15:13:55 afics_: 3.5.1 if everything goes well, ~ 1 month 15:14:14 sbonazzo: thank you, sorry to disturb you 15:14:54 sbonazzo: Anything else? 15:15:31 bkp: as just said to afics_ we're trying to get el7 support ready for 3.5.1, we're now working on master for that 15:15:50 bkp still missing deps on epel repository 15:15:57 bkp but we're on it 15:16:29 bkp that's all for me on 3.5 15:16:38 #info 3.5.z updates: 1 blocker around, tiraboschi_ is taking care of it 15:16:39 #info 3.5.z updates: 181 bugs still outstanding. Maintainers should be taking a look at these now. 15:16:42 #info 3.5.z updates: trying to get el7 support ready for 3.5.1, we're now working on master for that 15:16:52 #topic 3.6 status 15:17:12 Okay, opening this up, anything got news, topics for 3.6? 15:17:47 bkp release criteria definition in progress, we should reach a decision for next week meeting according to release process 15:18:30 bkp sent a recap this afternoon: http://lists.ovirt.org/pipermail/users/2014-November/028944.html 15:18:45 bkp we need to decide if just take 3.5 release criteria as is 15:19:25 bkp or define new release criteria (and define them) 15:20:05 bkp there is also an ongoing discussion on the release process 15:20:22 bkp about having a 10 month release cycle for 3.6 including all the features 15:20:36 bkp or having features splitted over 2 releases 15:20:40 And as always... 15:20:45 with a shorter release cycle 15:21:01 It's not clear whether we want this to be timeframe-oriented or content-oriented. 15:21:17 lvernia: +1 15:22:14 lvernia: the whole release process should be reviewed. you're welcome to comment on http://lists.ovirt.org/pipermail/devel/2014-September/008695.html 15:22:28 Yeah yeah :) 15:22:32 I have to say I don't have a solid opinion. 15:22:44 It *is* tricky. 15:22:57 What are we actually trying to achieve by releasing 3.6? 15:24:19 That question is complicated by the fact that 4.0 is on the horizon, and a longer release cycle might make sense there, as well. 15:24:38 This is clearly something for the discussion thread. 15:24:41 has anyone encountered an issue with 3.5.0 api not adding disks because disk_profile is required? 15:24:46 * YamakasY has tea 15:24:51 #info 3.6 status: Release criteria definition in progress, we should reach a decision by next week's meeting according to release process 15:24:54 #info 3.6 status: Specifically, should we keep the existing 3.5 criteria for 3.6, or add these changes http://lists.ovirt.org/pipermail/devel/2014-September/008695.html? 15:24:57 #info 3.6 status: There is also an ongoing discussion to lengthen the 3.6 release cycle to 10 months and keeping all the proposed features (http://lists.ovirt.org/pipermail/users/2014-November/028875.html) or splitting features across multiple releases. 15:25:01 #info 3.6 status: Discussion is invited here: http://lists.ovirt.org/pipermail/devel/2014-September/008695.html 15:25:02 lvernia: we've not deicded yet the full list of features to be included in 3.6 15:25:06 Any thing else on 3.6? 15:25:14 yap free servers! 15:25:19 running out of them 15:25:20 ;) 15:25:44 DougBishop: yes its a know issue, the solution right now is to manually add a disk profile. 15:26:05 bkp: work for fedora 21 support for 3.6 is ongoing as well as the el7 support 15:26:47 #info 3.6 status: work for fedora 21 support for 3.6 is ongoing as well as the el7 support 15:26:48 sbonazzo: Of course we haven't... 15:26:48 so I have disk profiles, but even when i send the profile id in my XML data during the post, I get the error 15:27:00 sbonazzo: Because we don't know if we have to fit them into 6 months or not... 15:27:06 keep in mind I am trying to add a new disk to an existing VM 15:27:40 DougBishop: Oh I misread, that you were trying to do it with the UI, not the api, in that case I am not sure 15:28:09 Okay, let's keep the 3.6 discussion going, but we can move on here... 15:28:14 Ack... 15:28:29 #topic conferences and workshops 15:28:39 ah okay, yeah this currently breaks rbovit/fog thus breaking foreman provisioning. Just trying to see if there is anything I am missing 15:28:44 #info OpenStack Summit is going on now in Paris. Red Hat has a sharp presence there, and oVirt should be getting attention via a video demo at the Red Hat/RDO booth. 15:28:47 #info LISA'14 will be next week, and we'll have a big footprint there with oVirt at LISA Lab and at the Red Hat booth. 15:28:50 #info Planning is ongoing for FOSDEM on Jan. 31-Feb 1. Get your submittals in for the IaaS and Virt devrooms soon! 15:29:27 Anyone else got event news? 15:30:33 bkp looks like a no 15:30:34 I should mention that we're getting more interest in meetups, and I am always welling to help people get those set up? 15:30:43 Okey dokey... 15:30:48 jhernand: Can you help DougBishop with his issue, looks like something you might be able to help with. 15:30:53 #topic other topics 15:31:03 I will be working with rbowen, the RDO Community Liaison, to create a position paper on oVirt and RDO. This is something that should have been done on the commercial side a while back, but the time has come to properly position each project. oVirt is getting a lot more attention at events now, and making sure it is differentated from OpenStack is key. 15:31:20 To that end, I am looking for feedback on how we can best position/market oVirt. If you have any ideas, let me know. 15:31:29 #info bkp will be opening a discussion on the [users] mailing list to best figure out how to position oVirt and RDO. 15:31:47 #info A reminder: this week not withstanding, the oVirt weekly syncs will be at 1400 UTC (one hour earlier than when we started this week). Please adjust your calendars accordingly. 15:32:09 Anything else for the meeting? 15:33:23 Going once? 15:34:28 Twice? 15:35:20 And we're outta here. 15:35:24 #endmeeting