14:01:49 #startmeeting oVirt Node Weekly Sync 14:01:49 Meeting started Tue Feb 19 14:01:49 2013 UTC. The chair is mburns. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:49 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:01:57 #chair jboggs fabiand rbarry 14:01:57 Current chairs: fabiand jboggs mburns rbarry 14:02:02 #topic agenda and roll call 14:02:06 agenda: 14:02:08 * fabiand is here 14:02:20 release updates 14:02:24 plans for the future 14:02:35 * jboggs here 14:03:40 * Rydekull is here, listening in 14:03:49 #topic Release Updates 14:04:02 #info ovirt node 2.6.0 was released last week 14:04:22 #info node-2.6 branch is available if we need async udpates 14:04:44 #info vdsm has noted that they will likely have an updated vdsm available soon 14:04:58 #info ovirt-node will need to spin a new image to pick up the new vdsm 14:06:23 mburns, do you know if that reboot bug (which I see in a VM) is a general issue? So also on real HW? 14:06:33 fabiand: i don't know 14:06:38 * mburns hasn't run it on real hardware 14:06:38 I just wonder if this might be a candidate for a minor release .. 14:06:43 Yeah, me neither .. 14:09:30 #info as of right now, we have no timeframe for ovirt 3.2 14:09:48 #info and no timeframe for node 2.7 14:10:10 #topic Plans for the Future 14:10:26 #info plan to remove vdsm and vdsm configurations from ovirt-node in 2.7.0 14:10:44 #info vdsm and config will become a separate plugin 14:11:32 nice 14:11:34 #info Proposal: move ovirt-node to a different cadence than the oVirt Project 14:11:48 mburns, any idea where? 14:12:05 * fabiand 'd say somewhere in the Fedora land ... 14:12:11 #info release in sync with Fedora Releases (and async builds as needed) 14:12:20 fabiand: where we'll ship ovirt-node? 14:12:39 mburns, yes - or where to keep/develop the base image? 14:12:57 ovirt-node rpms will be shipped in Fedora as they are now 14:13:00 I suppose you'd keep hosting and development in the oVirt Project as we are the primary consumer? 14:13:09 I suspect that the base image will be on ovirt.org still 14:13:25 but that's unclear at the moment 14:13:44 on a plus effort the base image itself could be used for any other project needing a small footprint os 14:13:55 jboggs: exactly 14:14:05 jboggs, yes - I'd see it as a Fedora-ish-Firmware 14:14:24 jboggs: the base image becomes useful for openstack, gluster, cloudstack, etc... 14:15:12 #info plan is to keep ovirt-node rpms in fedora as they are now 14:15:28 #info base image will likely be shipped on ovirt-node as it is currently 14:15:50 #info maybe eventually become a spin of fedora 14:16:38 blacklisting was the only thing holding it up last time from an official spin 14:16:49 14[[07MoM14]]4 !10 02http://www.ovirt.org/index.php?diff=7631&oldid=7630&rcid=7809 5* 03Lhornyak 5* (-2) 10/* Important MoM wiki pages */  14:17:18 jboggs: right 14:17:43 jboggs, what was the problem with blacklisting? 14:17:44 jboggs: we probably won't attempt being a spin in the near future 14:17:54 fabiand: file level blacklisting is frowned upon 14:17:59 especially of kmods 14:18:01 ah okay 14:18:32 iirc, they referred to it as "unnatural acts" 14:18:41 yeah ripping it out is frowned upon 14:18:44 hehe - nice :) 14:19:29 that's pretty much it from a future plans perspective 14:19:36 #topic Other Topics 14:19:42 anyone have other stuff to talk about? 14:19:57 The installer UI is nearl yin place 14:20:03 simple and multi-disc installs work 14:20:10 Now I just need to add the upgrade stuff .. 14:20:24 what's the quick way to call it python -M ovirt.node.installer or something else? 14:20:29 So we've got some time to test it until we can ship it in 2.7.0 14:20:40 jboggs, exactely that's the cmdline .. 14:20:48 #info new installer is nearly ready, simple and multi-disk work 14:20:52 just drop from the running installer and launch it using -m ovirt.node.installer 14:20:54 #info upgrade stuff still pending 14:21:06 once it's finished IÄ'll add ovirt-node-installer 14:21:13 (simple bash wrapper) 14:21:35 im looking to add iscsi install pages in the future once you get closer to finishing it up 14:21:48 ah nice! 14:21:53 fabiand: for 2.7, once we have the installer in place, we should remove as much of the older stuff as we can 14:22:07 mburns, yep 14:22:17 theres still a few things leftover from the ruby server version scattered 14:22:20 fabiand: and also look at moving the tui part of the codebase to autoconf/automake 14:22:35 jboggs: more than what my pending patch removed? 14:22:35 jboggs, is the iscsi page used to launch/steup the iscsi initiator? 14:22:58 mburns, yes 14:23:31 mburns, some random bits cant remember buy saw them yesterday nothing that 100% ties them to the ruby server unless you knew about them 14:23:46 fabiand, actual installer pages for iscsi root 14:23:57 jboggs, oh right, iI see 14:24:02 will have to figure out the network pages though 14:24:04 jboggs: ok, if you comment on my patch, i'll update it 14:24:11 mburns, ack 14:24:14 jboggs: you'll need the iscsi-initiator as well 14:24:42 goacid, I'm back 14:25:46 ok, anything else to talk about? 14:26:24 I'm fine 14:26:41 Nothing here 14:27:30 im good 14:27:34 ok, thanks all 14:27:38 #endmeeting