14:00:11 #startmeeting oVirt Weekly Meeting 14:00:11 Meeting started Wed Jul 17 14:00:11 2013 UTC. The chair is mburns. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:11 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:23 #topic agenda and roll call 14:00:30 #info 3.3 status update 14:00:42 * ofri here 14:00:47 #info Workshops and Conferences 14:00:50 #info infra update 14:00:53 #info Other Topics 14:01:04 * dustins_ntap here 14:01:08 * ecohen here 14:01:11 * sahina here 14:01:39 * mskrivanek here 14:02:22 doron: here 14:02:27 * doron here 14:03:07 #topic 3.3 status update 14:03:22 meeting here? hmm, where are the drinks? ;) 14:04:06 mburns, I just notified that 3.3 setup has a bug with all in one plugin with iptables 14:04:16 * lvernia here 14:04:37 #info otopi ovirt-host-deploy ovirt-image-uploader ovirt-iso-uploader ovirt-log-collector all posted 14:04:43 * danken is here 14:04:50 * oschreib here 14:04:55 #info ovirt-node base images available, will produce vdsm images once vdsm is available 14:05:05 hetz: ok 14:05:31 i'm still missing engine vdsm cli/sdk 14:06:01 mburns: don't we have nightlies with vdsm's rc1? 14:06:03 and reports/dwh, guest-agent 14:06:28 I'll take care of the engine build (good to be back, btw) 14:06:29 danken: perhaps, but we've generally had independent (non-jenkins) builds for beta posting 14:07:10 fsimonce, would you take care for that? ^^^^ 14:07:28 oschreib: welcome back! 14:07:52 there are some features that were not clearly done that mgoldboi wanted me to check on 14:08:13 indeed 14:08:20 glance integration ( fsimonce ) 14:08:38 neutron integration ( lpeer / mskrivanek ) 14:09:01 mburns: vdsm side of glance has been scrambled in just after vdsm's rc1 14:09:11 cloud-init 14:09:20 plugable scheduling ( doron ) 14:09:20 glance integration will be merged in 10 min 14:09:26 sgotliv: awesome! 14:09:28 mburns: cloud-init is stuck on REST API for 2 weeks already 14:09:39 would be in rc2 14:09:46 danken: can we spin rc2 for beta? 14:10:04 mskrivanek: what's blocking it? 14:10:11 about the schedualing 14:10:11 mburns: sure 14:10:24 oVirt scheduler - will go in today/tomorrow 14:10:32 Scheduling API - will probably take 1.5-2 weeks. 14:11:05 ofri: is scheduling a blocker for beta? 14:11:13 mburns: just maintainer's acceptance. The other virt features are in 14:11:17 danken: thanks 14:11:38 doron? 14:11:44 mburns: scheduling api should be blocker for rc, not beta. 14:11:55 doron: ok 14:12:06 mburns: would you add this to fsimonce's action item ("build vdsm -rc2 which includes glance for F18/F19/EL6") 14:12:19 mburns: well, worth to mention - on top of OSinfo feature we are adding Ubuntu and SUSE support (support is a strong word, it's just adding them to the list of OSes) and we were planning to have that by 3.3 FF as well but also stuck on REST issues 14:12:19 ofri: doron: does scheduler impact both vdsm and engine? or just engine? 14:12:28 mburns: engine only 14:12:57 mskrivanek: ok, probably an RC blocker, not a beta blocker 14:13:21 #info vdsm rc1 does not include glance 14:13:30 #info respin to happen to include glance changes 14:13:39 mskrivanek, if I may barge in: which SuSE? Open SuSE and SLES/SLED are 2 different things 14:13:47 #action fsimonce to rebuild vdsm rc2 to include glance 14:13:49 danken, did you tag rc2 already? 14:14:08 fsimonce: no, but I've just promissed mburns that I would 14:14:14 ok 14:14:17 #info ovirt scheduler (engine impact only) to merge today/tomorrow 14:14:25 and that it would include the Ayal-merged glance patch. 14:14:34 #info scheduling api need 1.5-2 weeks (not a beta blocker) 14:14:35 (for the record :) 14:15:22 mskrivanek: who is the maintainer you're waiting for with the cloud-init stuff? 14:15:48 hetz: SLES/SLED only. it's configurable now, though, so one can add whatever 14:16:02 mburns: mpastern 14:16:27 #info cloud-init waiting on maintainer acceptance ( mpastern ) 14:17:21 what about neutron? 14:17:40 oschreib: also was just cc'ed on this bug: https://bugzilla.redhat.com/show_bug.cgi?id=985168 14:17:44 mburns: there are a lot of patches, which one? 14:17:46 that may be an issue with 3.3 beta 14:17:58 lvernia can tell us all about neutron 14:17:58 mburns: most of the Neutron integration code is merged. 14:18:20 mskrivanek: can you follow up with mpastern to see what needs to be done with cloud-init 14:18:26 lvernia: excellent! 14:18:29 mburns: some UI patches are still under review, but they're small fixes. 14:18:34 #info neutron is merged 14:18:37 mburns: I'll take a look 14:18:51 lvernia: ack, that's ok, as long as we're feature complete... 14:19:01 mburns: one feature is still missing, and that is adding a network provider when installing a new host. 14:19:06 mburns, mskrivanek: i asked oliel to review it, afaik he acked 1-3/6 14:19:16 mburns: (backend patch is under review process) 14:19:35 lvernia: wait, if they're under review then they're not merged... 14:19:41 lvernia, mburns, but this is not a beta blocker 14:19:45 mburns: also regarding the guest agent - we will officialy have Ubuntu support, but there are still few other patches pending which we want to finish before releasing it, would it be ok to have it by RC as well? It's complete and +2'd, there are just merge dependencies pending 14:19:57 mpastern: great news! 14:20:30 mskrivanek: previous guest-agent packages still work, correct? 14:20:39 mskrivanek: can you please check this with ofrenkel (just to be on a safe side) 14:20:41 is there any feature that we really want available in beta? 14:21:26 mpastern: however no +2 for neither of them 14:22:06 mburns: yes, previous guest agent is good enough. All the way to guest agent 3.0 it should be fine 14:22:13 mskrivanek: ok 14:22:20 mburns: all big chunks of the UI are in, whatever's not in is nice to have or small bug fix. 14:22:27 mpastern, mskrivanek still no ack after latest changes (fixes to comments) 14:22:28 #info guest-agent packages are pending, not blockers for beta 14:22:33 lvernia: ack 14:23:33 mpastern: is there an eta for cli/sdk packages for 3.3 beta? 14:23:55 ydary: how about reports/dwh packages for 3.3 beta? 14:24:24 mburns: I sent them to Moran a few days ago. 14:24:49 oschreib: can you hold off building engine until tomorrow so we get the ovirt scheduler stuff in ? 14:24:56 ydary: ok, i'll get them from mgoldboi 14:24:58 thanks 14:25:16 mburns: well, holding off isn't that hard 14:25:33 oschreib: just want to make sure we're getting everything in for beta 14:25:52 mburns: I'll build only when all needed features are in 14:26:05 #info ovirt-engine build to happen after scheduler code gets in 14:26:24 #info reports was delivered to mgoldboi, mburns to get it and upload to ovirt.org 14:26:44 any other major features that are not ready? 14:27:09 how about a major GUI overhaul? :) 14:27:21 Network QoS is in but is unusable untill the vnic profiles part will be done. 14:27:40 this will take at least 1.5 weeks 14:27:56 ofri: beta blocker? 14:28:16 yes 14:28:51 so there is no point in going any further... 14:29:00 beta has to be delayed 14:29:47 ofri: so end of next week? 14:29:49 mburns: can we use an exception? 14:30:06 doron: we can go forward if you tell me it shouldn't block beta 14:30:24 but if it's a beta blocker and it's going to take 1.5 weeks to finish... 14:31:00 mburns: so it will be an rc blocker, and we'll handle it for rc. 14:31:34 doron: i'm fine with that, if you're comfortable with the lack of beta testing... 14:31:45 but is it the only Red "Must"? I see another one in the table 14:31:53 mburns: we have no alternative. 14:32:14 I'd say cloud-init may also be considered a blocker, it's quite a change and not really tested extensively. It's only in RunOnce, but still...don't know what you guys think? 14:32:52 mskrivanek: but it should be merged within a day or so, right? 14:33:02 fsimonce: do you know what's with http://www.ovirt.org/Features/Manage_Storage_Connections ? 14:33:05 so getting it merged and tested in beta... 14:33:10 mburns: yeah, we're counting on that for 2 weeks by now;-) 14:33:13 mburns: the code is inside, i have issues with java make, i guess ~1h, can you build (make rpm) sdk-python/cli? 14:33:37 mskrivanek: has cloud-init ever been declared as a feature "Must"? 14:33:47 if not, we should not wait for it. 14:33:47 danken: that's what I don't know 14:34:15 mskrivanek: well, it was not declated as such in http://www.ovirt.org/OVirt_3.3_release-management 14:34:18 so it is not. 14:34:38 QoS *was* declared as such so THERE we have a problem. 14:34:42 no danken, maybe abonas knows more 14:35:02 mpastern: if you have a tarball, you can use this jenkins job: http://jenkins.ovirt.org/view/All/job/manual-build-tarball/ 14:35:09 danken: how can I tell from the page, btw? 14:35:31 mskrivanek: the table has a "release priority" columnt 14:35:44 and cloud-init is a "?", not a Must 14:36:12 danken: aah, yeah, sorry. I missed that, all virt has ?, good for me then:) 14:36:15 we have enough to work on for ovirt-3.3 14:36:31 danken: which btw doesn't mean it's not a must, it just mean not decided 14:36:52 i think the QoS and scheduling api can be exceptions 14:37:10 given the concern around lack of testing with cloud-init, i'd like to see it at least merged and available for beta 14:39:03 I'll go on a scouting mission to fetch an answer from abonas 14:40:32 danken, what answer are you looking for? 14:41:01 abonas: manage storage connections 14:41:11 abonas: marked as red in the wiki and listed as a Must feature 14:41:23 mburns, I never marked it as red, in fact I do not know who did 14:41:46 abonas: so it's good? 14:41:52 mburns, most of the code is ready and already merged 14:41:58 abonas: excellent, thanks 14:42:06 mburns, I'm doing testing on the REST part, it's not merged yet 14:42:21 abonas: it was red since the code was missing. time that you change it to green. 14:42:42 so to summarize overall, for many features "core code is in, but rest is not ready yet" 14:42:48 s/rest/REST 14:42:55 danken, I'm not managing the colors table. I have a feature page where I update daily the status and what's ready 14:43:21 danken, it's up to managers to decide what color they want to put on it 14:44:21 ok, i'm going to propose the following: 14:44:29 merge the scheduler changes today/tomorrow 14:44:30 abonas: "managers"? what is this? 14:44:40 build the engine and vdsm packages 14:44:45 mburns, what scheduler? 14:44:55 post engine and vdsm packages 14:44:59 send announcement for beta 14:45:12 abonas: it's your feature, and your manager should have told you that you should publicize its real state in the table. 14:45:13 mburns: +1 from me 14:45:13 with disclaimer that REST API for many new features is still unstable 14:45:45 abonas: different feature, not yours.... 14:45:50 mburns, got it 14:46:03 any objections to this plan? ^^ 14:46:52 nope 14:47:18 #info plan going forward 14:47:30 #info merge scheduling stuff today/tomorrow 14:47:37 #info build new vdsm and engine 14:47:45 #info post everything up after build tomorrow 14:47:52 danken, you can clarify it with abaron. I am updating him daily , and also in the feature page on the status of the feature. noone talked to me about the colors. 14:48:23 #info send announcement that the beta is available with a disclaimer that many features are not yet available in rest api 14:48:43 fsimonce: oschreib: let me know when you have the updated packages. 14:48:55 moving on to our other topics 14:48:58 sure 14:49:05 #topic conferences and workshops 14:49:17 theron: any updates? 14:49:39 #info KVM Forum/LinuxCon EU/CloudOpen EU CFP closes on 21-July 14:50:03 #info KVM Forum/LinuxCon EU/CloudOpen EU CFP takes place on 21-23 October 14:50:35 abonas: well, we are all here, and we are all asking you to update the release management table with the true state of your feature 14:51:36 #info planning on a oVirt Developers meet-up during this timeframe 14:51:51 * mburns will re-visit if he gets more info 14:51:57 #topic Infra update 14:52:05 ewoud: any updates? 14:52:10 #chair ewoud 14:52:10 Current chairs: ewoud mburns 14:53:02 danken and abona: I will update the table 14:53:15 sgotliv: thanks 14:53:29 #info there was no infra meeting this week due a lack of people 14:53:49 mburns: sorry, I have one more update re 3.3 readyness. "New Host" doesn't work in GUI 14:53:57 *readiness 14:54:14 mskrivanek: something that could be fixed before re-building tomorrow? 14:54:18 mburns: I think we need that in so please don't build right now 14:54:23 #info fedora 19 slaves on rackspace servers were added and more and more of their configuration is being puppeted 14:54:33 ewoud: awesome 14:54:36 mburns: tomorrow is fine, ok. it's a trivial fix 14:54:48 oschreib: note the fix mskrivanek mentioned... 14:55:32 mburns: the discussion about quaids mail about a project coordinator for the infra team is also getting started, so I hope we can say more about it next week 14:55:34 noted 14:55:45 ewoud: ack 14:55:53 oschreib: doesn't have a bug yet. We just found out that someone broke it, will update you tomorrow morning 14:56:01 mburns: and I think that's all the news 14:56:01 #info infra team looking for a new project coordinator, more details next week 14:56:08 ewoud: excellent thanks 14:56:22 #topic 3.3 readiness (revisited) 14:56:37 #info new bug found in engine -- "New Host" does not work. 14:56:40 #info trivial fix 14:56:49 #info oschreib to wait on engine build until the fix is merged 14:56:55 #topic other topics 14:57:01 any other topics people want to bring up? 14:58:19 going once... 14:58:35 twice.. 14:59:13 gone. 14:59:15 thanks all 14:59:17 #endmeeting