13:01:29 #startmeeting oVirt Node Weekly Meeting 13:01:29 Meeting started Tue May 6 13:01:29 2014 UTC. The chair is fabiand. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:29 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:01:35 #chairs jboggs rbarry 13:01:40 * jboggs here 13:01:44 #topic Agenda 13:01:46 morning jboggs 13:01:49 morning 13:02:02 * rbarry here 13:02:09 morning rbarry 13:02:34 #info Build Status (3.0.5) 13:02:41 #info Feature Status for 3.5 13:02:52 #info Other Items 13:02:57 #topic Build Status 13:03:12 One action item last week was the preparation of a beta for 3.0.5 13:03:17 I am actually sitting on this 13:03:37 But I also wanted to check with rbarry about the missing ovirt.pp file. 13:03:43 rbarry, did you gain some more insight yesterday? 13:04:09 No, not yet. I'll need to add debugging information to ovirt-node-selinux's %post 13:04:17 okay 13:04:32 Oh - it affects only master anyway .. 13:04:37 It strongly appears as if semodule -s targeted -i... isn't running, but I can't verify that without checking 13:04:47 okay 13:05:20 #info fabiand is one 3.0.5 beta 13:05:36 #topic Feature Status for 3.5 13:05:46 Any updates on this? 13:06:01 * fabiand has trouble building images with lmc and imgfac .. 13:06:29 still working on hosted engine, mostly installation issues with the network config 13:06:44 Backend for registration is probably 50% done, but I haven't tested against an actual engine yet 13:06:51 also the ha agent/broker not starting, but think that's related to networkign hardware that I'm swapping out this am 13:07:44 #info hosted-engine still issues with the network after installation 13:08:02 #info generic registration: Backend work progresses no testing with engine yet 13:08:35 #info ovirt-appliance: Build problems with lmc/imgfac - mainly debugging is hard 13:08:56 Okay, let's try to look at those features a bit more in depth next week 13:09:50 #topic Other Items 13:10:01 #info ml merge did not happen yet, but is probably coming up 13:10:31 One itme which was brought up today by dnaken is that vdsm does not work nicely with NM 13:11:16 So we should probably sit together or talk about what we plan for th elong future .. 13:11:57 IIRC we started to use NM-glib to gathe rlife informations via pyhon calls 13:12:06 Those calls would break if we removed NM 13:12:21 Additionally we rely on sysv network init scripts or NM to bring up the ocnfigured interfaces 13:12:48 And that basically means we depend on NM at least in Fedora 13:12:59 So we should clarify how we do this on the long run .. 13:13:34 rbarry, jboggs - does someone of you want to look into this? 13:13:47 Otherwise I'd come up with an email to strat the discussion/sync between vdsm and us 13:13:58 that may be best 13:14:01 Email may be better for visibility 13:14:07 Yep 13:14:15 I'd use the "new" ovirt-devel list 13:14:47 I'm happy keeping NM, especially with the changes in F20, but I don't know if the esoteric cases (bonds, bridging, vlans on top of either, etc) made it into EL7 13:15:00 Yeah, I also favor NM 13:15:14 And IIRC those chanegs went into el7 13:15:15 It'd be nice to move to the systemd networking bits eventually, but I have absolutely no idea whether they ever intend to cover those use cases either 13:15:37 rbarry, they'd be alos an option, but they will probably not land in el7 13:15:46 at leats not in the beginnig. they seem way to young .. 13:15:53 otoh they'd cover our cases .. 13:15:58 as far as I can tell 13:16:43 they should cover basics up to wireless 13:16:53 but who knows .. 13:17:15 #action fabiand to send out email to coordinate network stuff with vdsm 13:17:25 Okay 13:17:39 Anthing else, jboggs rbarry ? 13:17:46 nothing from me 13:17:58 Nothing 13:18:01 Ack 13:18:04 Then thanks! 13:18:07 #endmeeting