13:07:58 #startmeeting oVirt Node Weekly Meeting 13:07:58 Meeting started Tue Apr 1 13:07:58 2014 UTC. The chair is fabiand. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:07:58 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:09:12 #chair rbarry jboggs 13:09:12 Current chairs: fabiand jboggs rbarry 13:09:18 #topic Agenda 13:09:44 * jboggs here 13:10:17 #info Fedora 20 support 13:10:24 #info Platform discussion 13:10:29 #info Version disucssion 13:10:32 #undo 13:10:32 Removing item from minutes: 13:10:35 #info Version discussion 13:14:17 #info Other Items 13:14:23 #topic Fedora 20 support 13:14:31 #info rbarry has been working on this 13:14:39 #info Images have been tested 13:14:49 #info Patches are close to beeing merged 13:15:15 Which brings us quickly to the next item 13:15:20 #topic Platform discussion 13:15:46 As you might have seen - in the light of discussing the versioning a small side discussion arose around the quesiton if we really should suport more than one platform 13:15:54 So basically if we shoudl support both - Feodra and CentOS. 13:16:13 Currently we are only building CentOS images because it is easier to maintain, and doesn't break as often. 13:16:48 But as said on the thread as well, I wouldn't liek to drop Fedora support, because .. Fedora is our insurance to get such a stable Node we've currently got. 13:16:49 hahahah 13:17:01 right dr_gogeta86 13:17:15 any way to use gluster directly as export domain 13:17:18 ? 13:17:24 run fast like hell 13:17:32 The work that goes now into Fedora, is paying back some time later, when we base our ovirt-node on CentOS. 13:17:33 I've recovered a died datastore in a snap 13:17:50 but i did it manually 13:17:56 OTOH I can imagine that we continue to only release a CentOS based image, and use the Fedora platform for development. 13:18:10 is quiet good reason 13:18:37 thoughs on this rbarry, jboggs ? 13:19:03 we should still build a fedora based image in the long run 13:19:08 it does pay off like you said 13:19:20 the work done in parallel would be much easier than all at once 13:20:32 ack jboggs 13:21:19 Okay 13:21:21 then next item is 13:21:29 #topic Version discussion 13:21:37 I'd actually like to continue this on the ml 13:21:53 My reason for bringing this up was 13:22:16 For the iso rpm it's easy to see what ovirt version it targets, because it sits in a specific repo 13:22:23 It's not that easy for the ISOs themselves tho 13:22:34 To mainly solve the iso issue I brought up the discussion. 13:23:04 I agree with you there, sometimes it hard to distinguish quickly what iso/engine matches even downstream 13:23:05 #info The version discussion had to be brought up, because Engine currently makes assumptions about the namin of the iso and/or rpm 13:23:13 jboggs, yeah .. 13:23:37 jboggs, and additionally upstream it doesn't follow any discussed guidelines 13:23:58 And we've got the Engine side to take care off and the "yum"/delivery side 13:24:31 But that's it from me so far .. 13:24:51 jboggs, as said, we can just change it in coooperation with Engine .. 13:25:04 I know this has been tried in the past, and is not easy to solve, but we need to address it .. 13:25:33 Okay, that's all I have to say :) 13:26:28 #topic Other Items 13:26:53 Anyone? 13:26:55 If not, 13:26:57 ... 13:26:57 fabiand: Error: ".." is not a valid command. 13:27:02 thanks ovirtbot 13:27:29 Going once 13:27:49 twice 13:27:59 Thanks 13:28:02 #endmeeting