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