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