14:00:21 #startmeeting oVirt Weekly Meeting 14:00:21 Meeting started Wed May 29 14:00:21 2013 UTC. The chair is mburns. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:24 mburns: working on self hosted engine feature 14:00:31 #topic agenda and roll call 14:00:34 sbonazzo: ok 14:00:34 mburns: I don't have engine yet 14:00:58 * ofri_ here 14:01:10 #info 3.2.x update 14:01:14 * lvernia here 14:01:21 * dustins_ntap is here 14:01:29 #info 3.3 status 14:01:34 * jb_netapp here 14:01:50 #info other topics 14:02:11 * danken here 14:02:14 * mburns notes that he *will* be somewhat distracted today... 14:03:24 #topic 3.2 updates 14:03:44 * yzaslavs here 14:03:57 #info all pending builds are updated on ovirt.org/releases 14:04:49 #info expected updates coming shortly: sdk/cli and vdsm 14:05:49 * mgoldboi here 14:05:53 mgoldboi: hi 14:05:58 mburns: hello 14:06:12 mgoldboi: any news on sdk and cli updates? 14:06:30 mburns: i thought it was closed last week 14:06:50 mgoldboi: sdk/cli weren't included in the update because i didn't have the packages 14:07:02 they were posted somewhere internally that i didn't have access to 14:09:02 mgoldboi: if you can get them to me, i'll get them uploaded 14:10:18 #info no other updates planned at this time 14:10:43 #topic oVirt 3.3 status update 14:10:55 (besides the pending vdsm async build with http://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:ovirt-3.2,n,z ) 14:11:11 fsimonce is going to build it soon, I'm told. 14:11:15 danken: right, that's captured above 14:11:21 #link http://www.ovirt.org/OVirt_3.3_release-management 14:11:45 * oschreib here 14:12:53 looking at the feature table, we cannot possibly go into code freeze this week 14:13:48 mburns: i would say postpone schedule at at least 2-3 weeks 14:14:08 #idea delay schedule 2-3 weeks 14:14:15 mgoldboi: I say month from what I see. 14:14:54 doron: we'll need to see if we can push it and re-estimate in 2 weeks from now based on the progress 14:15:21 let's delay and re-visit in next couple weeks 14:15:25 mgoldboi: agree, but having a few people missing in the coming weeks I can say 14:15:30 much is missing. 14:15:58 doron: all of the features are must 14:16:26 anything we can focus on and maybe drop one or two in order to make schedule ? 14:16:50 yes, i think we need to prioritize the features 14:17:08 agreed. 14:17:20 doron: mgoldboi: who can prioritize? 14:17:46 doron: it's your realm - should be done by you 14:17:49 mburns: I'd say we need a representative for each area 14:18:34 ok 14:18:39 is there anyone from storage? 14:19:20 mburns: I suggest we discuss the prio's next week and then make an educated decision. 14:19:30 agreed 14:19:31 they have a Must feature http://www.ovirt.org/Features/Edit_Connection_Properties 14:19:31 slated to be ready on 2013-06-30 14:20:00 we need to make sure we have a rep' from each area for next week's mtg. 14:20:09 #agreed maintainers/reps from each area will prioritize and we'll reschedule at next week's meeting 14:20:21 mburns: action on me 14:20:40 just a sec - I missed the agreement: we postponing the beta date without setting a new one? 14:20:41 #action mgoldboi to ensure rep from each area will be present next week 14:21:51 not much else we can discuss on 3.3 until we have the right people 14:21:53 mgoldboi, mburns: we have network, sla, infra, node - only storage is missing. why should we wait for another week? 14:22:26 danken: we really need to get the details filled out on the chart 14:22:39 and get features prioritized correctly 14:23:10 mburns: but if only storage is missing we can start to do the work this week 14:23:19 sure 14:23:21 mgoldboi: exactly. 14:23:36 i saw it more as an offline thing, but we can do it on here 14:23:58 #chair mgoldboi 14:23:58 Current chairs: mburns mgoldboi 14:24:16 mburns: danken: table should include must and should though, so it should be straight forward 14:24:23 mburns: I prefer to decide on a new beta date. if storage is unhappy, let then apply for postponing it. 14:24:46 mburns: mgoldboi: the table has Must/Should/Optional 14:25:14 danken: hard to decide a beta date if we don't have info on must/should/optional on a lot of features 14:25:18 features are way too red. so clearly we need to postpone the beta date. 14:25:20 danken: and no target dates 14:25:25 danken: yes 14:25:59 Few features request June 16 14:26:13 one Must feature of storage request June 30 14:26:37 mburns: danken: so june 26? 14:26:38 sla features are requesting 1-july for some features 14:26:45 and they're listed as must 14:27:01 doron is here to state if this is indeed the case 14:27:26 danken: indeed this is the case. we need enough time to complete the new oCirt scheduler. 14:27:42 * mburns notes that one UX feature requests 31-June which doesn't actually exist 14:27:45 (oVirt) 14:28:03 doron: and are you comfortable with July 1? 14:28:19 hi evryone 14:28:27 mburns: that a polite way to say that the ux feature would never finish ;-) 14:28:29 danken: hopefully yes. 14:28:40 so latest date filled out is 1-july 14:28:47 so it sounds like a 1 month slip 14:28:51 i face some problems with a new installation of ovirt on a Fedora 18 14:29:05 after a reboot of the systems 14:29:13 ovirt is on 14:29:15 start 14:29:28 but i got nothing on my browser 14:29:40 mburns: I would like to set this date in stone. 14:29:42 seems like it not responding 14:29:58 mabsKenpachi: as topic suggests we're in a meeting now. can you retry later please? 14:29:58 if someone is uncomfortable about it, they should at least show up. 14:30:06 danken: doron: mgoldboi: let's set dates to current plan +1 month 14:30:14 agreed. 14:30:25 so ga Aug 1 14:30:25 freeze on july 1 14:30:30 danken: mburns: i would say 2-3 weeks and re-evaluate 14:30:42 mgoldboi: evaluate what? 14:30:56 mgoldboi: next statement was going to be that we have a checkpoint in 2 weeks to make sure we're still on track 14:31:01 does anyone have see like a problems 14:31:01 danken: status, what can we pass on and what is in 14:31:16 ok 14:31:18 sorry 14:31:20 mgoldboi: i'd rather slip once than slip multiple times 14:31:23 mgoldboi: sure. 14:31:43 mburns: +1 14:31:48 +1 14:31:59 danken: i'm afraid that putting a one month delay can put people into sleep 14:32:03 mburns: but another month's slip won't be so nice! 14:32:26 mburns: but i guess time will tell... 14:32:48 mgoldboi: we can set re-prio 3 weeks from now 14:33:02 so everything not ready for now+1m will be removed. 14:33:19 doron: i'd say in 2 weeks 14:33:25 that's about the halfway point 14:33:38 no objections. 14:33:39 and doesn't give people the chance to fall asleep as much 14:34:00 mburns: ok, sounds reasonable 14:34:08 #info delay release and all other dates 1 month 14:34:41 #info checkpoint on features still at risk in 2 weeks (12-May) 14:35:01 #action mburns to send schedule update announcement 14:35:47 #idea all features listed on the chart that do *not* have ETA or must/should/optional are dropped 14:35:51 thoughts on that ^^ 14:36:15 mburns: time to be tough... 14:36:40 mburns: +1 14:37:16 i think it is 14:37:19 ++1 14:37:43 #agreed features missing priority or ETA are dropped on 12-May 14:37:56 ok, anything else on 3.3? 14:38:01 mburns: we need to put a date on it though 14:38:12 date on...? 14:38:26 mburns: my bad 14:38:47 oh, date on when we drop features missing information 14:38:56 yes, at the re-sync in 2 weeks 14:39:35 ok, moving on 14:39:40 #topic Conferences and workshops 14:39:54 dneary: anything new this week? 14:40:38 #info there will be a booth at Red Hat Summit (June 11-14) 14:41:01 Sorry - giving a webinar 14:41:11 mburns: we have guys in LinuxCon Japan now 14:41:21 #info presentations going on at LC Japan as well 14:41:35 IIRC we have heron there, and Lsazlo giving a session on oVirt intro+SLA 14:41:38 how's feature freeze looking? 14:41:48 Theron is in Japan this week 14:42:24 For Summit plans: is there a list of everyone from oVirt who is at the Summit? 14:42:34 That would be helpful to us 14:42:41 dneary: we have features that are 1 month away from freezing, so we're delaying 1 month with a checkpoint in 2 weeks 14:43:15 Also, perhaps we could have next week be a "feature triage" meeting, where we bump anything red to 3.4 unless we get better visibility on when it'll be release-ready 14:43:29 dneary: that's the plan for 2 weeks from now 14:43:35 Sounds good 14:43:46 dneary: i'll work on a list of people who are attending summit 14:43:59 mburns, Thanks 14:44:28 #topic infra report 14:44:33 ewoud: anything to update this week 14:45:14 mburns: actually yes 14:45:25 #chair ewoud 14:45:25 Current chairs: ewoud mburns mgoldboi 14:45:40 #info with the help of rackspace dcaro managed to install the rackspace server 14:46:10 #info installing ovirt on it so we get more jenkins slaves helping us run more tests 14:46:35 #info our foreman/puppet environment is starting to take shape 14:47:07 #info work in progress on installing monitoring software (icinga) so we can spot out of disk space ahead of time 14:47:41 mburns: that should be the important highlights 14:47:53 ewoud: ok, thanks! 14:48:11 #topic other topics 14:48:15 anyone have anything else? 14:48:56 Can I just say: it's awesome to have the feature matrix 14:49:38 +1 14:49:42 It really makes it clear how realistic/unrealistic the release dates are 14:49:55 Next challenge is keeping it updated 14:50:01 yep 14:50:19 ok starting the countdown... 14:50:21 And getting a decision meeting on which of those red "Musts" we can bump 14:50:23 going once... 14:51:04 twice.. 14:51:32 gone. 14:51:35 thanks everyone 14:51:38 #endmeeting