15:01:21 #startmeeting oVirt Node Weekly Meeting 15:01:21 Meeting started Mon Feb 23 15:01:21 2015 UTC. The chair is fabiand. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:21 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:01:26 #chairs rbarry tlitovsk dougsland 15:01:33 present 15:01:42 * dougsland here o/ 15:01:45 Hey there! 15:01:49 #topic Agenda 15:01:54 #info oVirt 3.5 15:01:59 #info oVirt 3.6 planning 15:02:03 #info Other Items 15:02:30 #topic oVirt 3.5 15:02:54 So 15:02:55 3.5 15:03:05 We already see it's entertaining : 15:03:17 tlitovsk, dougsland IIUIC you tried to get Jenkins working again, right? 15:03:20 * rbarry here 15:03:33 hey rbarry 15:03:43 hi rbarry 15:03:51 we had several issues today. 15:04:03 1. please notice the new gerrit ui 15:04:12 fabiand, the ovirt-node and related projects like ovirt-node-plugin-vdsm and ovirt-node-plugin-hosted-engine should be and shape. There is a effort to make jenkins a automate job to help us in releases (still going). 15:04:33 the gerrit was upgraded and the http links to gits failed 15:04:40 dcaro fixed those. 15:05:09 we now have some missing rpms in the ovirt3.5 repos HE and VDSM and dougsland and dcaro are uploading them again. 15:05:31 super - about the links 15:05:32 after that we should be fine . and good probability the centos6 obirt node will appear too. 15:05:40 tlitovsk, sbonazzo dcaro, please let me know if you are missing any package from our side. 15:06:20 tlitovsk, douglas, great to hear that it's on progress to be working again 15:06:39 dougsland: need to review your messages, lat time I checked, ovirt-node was missing on el7 and fc20 15:06:44 And yes, I can just highlight again that we really want to settle with the automation for providing iso builds 15:06:44 last 15:07:24 #info Some automation hickups after a gerrit update 15:07:30 tlitovsk, ^ 15:07:46 #info It is beeing worked on bringing back the missing packages 15:07:57 Right 15:08:00 Thanks tlitovsk dougsland 15:08:21 Despite the automation part we've got a couple of bugs we want to get fixed in 3.5.x 15:09:59 #info Some small 3.5 updates are planned 15:10:06 #info Builds are left to jenkins 15:10:09 Okay 15:10:14 Moving on the to 3.6 15:10:18 #topic oVirt 3.6 Planning 15:10:28 #link http://resources.ovirt.org/meetings/ovirt/2015/ovirt.2015-02-16-15.00.txt 15:10:39 #info tlitovsk created the cockpit feature page 15:10:42 thanks tlitovsk 15:11:03 wellcome 15:11:22 We also spoke about using anaconda for installing Node 15:11:34 Tho I still wonder if we need a separate feature page for this 15:11:44 Or if we can just create one for the complete Next-Gen Node 15:12:11 For reference, and documentation it's probably best to create a feature page 15:12:36 dougsland, rbarry tlitovsk - Anyone stepping up to create a feature page for Using anaconda to install Next-Gen Node? 15:12:47 Otherwise I am happy to open it 15:12:54 fabiand, I can do it . between the builds 15:13:05 I mean the anaconda page 15:13:12 not next gen node 15:13:17 darn 15:13:22 I was just about to nail you on that one :) 15:13:38 tlitovsk, you had your fun :) Let' me open it if you don't mind 15:13:54 :-) . sure 15:14:12 Perfect 15:14:24 #action fabiand to open the feature page for anaconda based installation 15:15:27 Okay 15:16:01 These two features cover a lot of the changes 15:16:13 We'll probably need another feature page for the overall Next-Gen Node move 15:16:19 But nothing to critical for now 15:16:57 If there is nothing else on 3.6 Then I'm moving on 15:17:00 #topic Other Items 15:17:41 anything else you want to bring up for now, dougsland rbarry tlitovsk ? 15:17:47 Nothing here 15:17:53 not at moment. 15:18:06 I want to add csmosk to our long planned talkes 15:18:28 tlitovsk, csmosk= 15:18:37 ? 15:18:40 csmock = static code analyzer 15:18:55 Oh right 15:19:10 Additions like that are always welcome :) 15:19:46 we can put some job to run with csmock report at some close or far feature. 15:20:12 but the real taak will be cleaning all the warnings it provide. 15:20:48 I will give a current status report for our next meeting. and we can decide if its more false positives then false negatives :-) 15:22:16 tlitovsk, for now we can limit it to the "new codebase" 15:22:20 so everything under src/ovirt/ 15:22:35 we should not try to get the code under /src/ovirtnode to work with it .. 15:22:46 tlitovsk, you might want to look how the pep8 checks are run .. 15:22:53 ack. 15:22:54 I could imagine that csmoke can be hooked up there 15:22:57 But nice! 15:23:14 #info tlitovsk to look at integrating csmock 15:23:23 nice 15:23:51 If there is nothing else ... 15:24:00 Then I'm going once 15:24:13 Twice 15:24:22 And a third time 15:24:25 Thanks 15:24:27 #endmeeting