13:00:16 <mburns> #startmeeting ovirt-node weekly sync
13:00:16 <ovirtbot> Meeting started Tue Jul 17 13:00:16 2012 UTC.  The chair is mburns. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:16 <ovirtbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:00:24 <mburns> #topic roll call and agenda
13:00:34 <mburns> #chair jboggs READ10 pmyers fabiand
13:00:34 <ovirtbot> Current chairs: READ10 fabiand jboggs mburns pmyers
13:00:45 <mburns> Agenda:
13:00:45 <mburns> action item review
13:00:46 <mburns> release status
13:00:49 <mburns> other topics
13:01:15 * jboggs here
13:01:54 * READ10 here
13:02:13 <mburns> #topic action item review
13:02:18 * RobertM here
13:02:32 <mburns> #link http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-10-13.00.html
13:02:50 <mburns> only 1 action item last week -- and that was for me to look at 2.5.0 bugs
13:03:17 <mburns> #info mburns moved all 2.4.1 bugs to 2.5.0
13:03:34 <mburns> #info mburns deferred non-applicable 2.5.0 bugs to 2.5.1 (temporarily)
13:03:38 <mburns> #link http://goo.gl/OqoE3
13:04:49 <mburns> #action mburns to add 2.7.0 release and future release, and move 2.6.0/2.5.1 bugs around appropriately
13:05:19 <mburns> that's it for actions for last week
13:05:26 <mburns> #topic Release Status
13:05:39 <mburns> #info we're going to be shipping 2.5.0 with the ovirt 3.1 release
13:05:59 <gestahlt> mburns: Is the 2.5.0 node image released?
13:06:04 <mburns> gestahlt: not yet
13:06:18 <mburns> quick look at bug list:
13:06:28 <mburns> 2 NEW
13:06:32 <mburns> 2 ASSIGNED
13:06:34 <mburns> 1 POST
13:07:01 <mburns> jboggs: can this be moved to MODIFIED:  https://bugzilla.redhat.com/show_bug.cgi?id=753302 ?
13:07:25 <mburns> fabiand: same question for 824595 and 831668
13:07:35 <jboggs> mburns, its in the repo but not yet packaged does that matter?
13:07:52 <mburns> jboggs: it's not included in ovirt-node-tools?
13:08:05 * mburns thought we did that a long time ago...
13:08:12 <jboggs> yeah its in there
13:08:14 <fabiand> justa second
13:08:49 <mburns> jboggs: then is there something missing from the packaging?
13:08:53 <mburns> is the man page packaged?
13:09:15 <fabiand> mburns, 824595 - yes.
13:09:21 <fabiand> (done)
13:09:56 <jboggs> not sure about the signature part for #3?    #4 isnt finished
13:10:08 <jboggs> just need to determine location and format
13:10:20 <fabiand> I'll give 831668 another look
13:11:00 <mburns> jboggs: ok, so mostly done, but not quite complete
13:11:24 <mburns> jboggs: let's split out the parts that aren't done in a separate bz
13:11:27 <mburns> and close this one
13:11:33 <jboggs> ok
13:11:57 <RobertM> Is 2.5 getting plug-in or is that getting pushed to 2.6?
13:12:18 <mburns> #info bz on mburns -- move to modified, merged a while ago -- patch supplied by community (yay!)
13:12:26 <mburns> RobertM: 2.5 will have plugins
13:12:38 <mburns> there might be issues here and there, but it will be there
13:12:43 <RobertM> cool
13:13:20 <mburns> RobertM: essentially the equivalent of a tech preview
13:13:35 <mburns> idea is to get people testing with it now
13:14:00 <RobertM> That is what the 1st release is generally
13:14:50 <mburns> #action jboggs -- 753302 -- split the bz into multiple parts, target unfinished to 2.5.1 and mark original as MODIFIED
13:15:12 <mburns> #action fabiand -- review 831668 to see if it is fixed or not
13:15:26 <mburns> #action mburns to review all patches posted
13:15:32 <mburns> #undo
13:15:32 <ovirtbot> Removing item from minutes: <MeetBot.items.Action object at 0xa34264c>
13:15:45 <mburns> #action mburns to review all patches posted -- including patch for 811584
13:15:57 <fabiand> I'd give the remaining patch from apevec a go
13:16:10 <mburns> fabiand: perhaps for 2.5.1
13:16:14 <fabiand> okay
13:16:26 <mburns> thats a change i'm not willing to make in 2.5.0
13:16:30 <fabiand> It's changing some "core paths"
13:16:38 <mburns> yep
13:16:44 <fabiand> okay, right
13:17:07 <mburns> other than that, i think we're in good shape as long as we get a good vdsm build
13:17:18 <mburns> #action mburns to follow up on vdsm build
13:17:32 <mburns> anything else for release status?
13:18:06 <mburns> ok
13:18:12 <mburns> #topic Other Topics
13:18:22 <mburns> anything else to mention here?
13:18:29 <fabiand> I can given an update on automation - and the problems ..
13:18:37 <mburns> fabiand: sure
13:18:55 <fabiand> I spend quite much time on enabling tui installs
13:19:26 <fabiand> basically I had to fight with some unknown bugs
13:19:58 <fabiand> like ai failing some times
13:20:19 <fabiand> It was hard to differentiate to see if this was a hypervisor or guest fault
13:20:37 <fabiand> I'll be adding a junit compatible output format so we can re-use the appropriate jenkins plugin
13:21:03 <fabiand> eedri has done some nice work for engine (or vdsm?) and I'd like to get in a comparable state for node
13:21:45 <fabiand> So, right now we've got working tui and auto installs (currently failing)
13:21:55 <eedri> fabiand, what are we talking about?
13:22:20 <mburns> fabiand: is the auto-install thing the bug i saw filed earlier today?
13:22:30 <fabiand> eedri, I just mentioned you - I've just seen your presentation on jenkins/ovirt/foreman integration, nice work
13:22:36 <eedri> fabiand, thanks
13:22:36 <fabiand> mburns, I suppose yes
13:22:49 <mburns> fabiand: ok
13:22:49 <eedri> fabiand, mostly engine testing automation
13:23:04 <fabiand> mburns, there were a couple of bugs that hindered (?) me, like the nic trouble, now this auto-install regression, then reboot issues ...
13:23:22 <mburns> fabiand: you can try adding something to drop to a shell before reboot to see what's going on
13:23:25 <fabiand> The testcases are now kept upstream
13:23:29 <fabiand> (migrated them yesterday)
13:23:48 <mburns> fabiand: a patch posted to upstream gerrit will trigger a build
13:23:52 <fabiand> and the next steps will be to ease the addition of new testcases
13:23:54 <mburns> in the -devel builds
13:24:13 <fabiand> mburns, a -devel build will trigger an -at build?
13:24:24 <mburns> fabiand: you own the -at build
13:24:41 <fabiand> yep - I just didn't get what triggers what :)
13:24:42 <mburns> so you can make it trigger
13:25:01 <mburns> patch submitted to gerrit in ovirt-node triggers ovirt-node-devel build
13:25:09 <mburns> ovirt-node-devel build triggers ovirt-node-iso-devel
13:25:12 <fabiand> ah, you want me to add that trigger? mburns
13:25:26 <mburns> ovirt-node-iso-devel *could* trigger -at build
13:25:40 <fabiand> yes, currently the test take about 10-15min
13:25:41 <mburns> if you want it to, then you can add the last step
13:26:02 <mburns> fabiand: actually, let's discuss offline
13:26:06 <fabiand> yes
13:26:11 <mburns> -at build runs on a different jenkins...
13:26:15 <fabiand> that was just my small summary
13:26:33 <mburns> ok, anything else to cover today?
13:26:38 <fabiand> yes, well, there was this offer on the infra list. maybye we can also run some jobs on that cluster ..
13:27:10 <mburns> fabiand: yes, when it's up and running, getting testing there would be good
13:27:16 <mburns> but it would be nested virt...
13:27:20 <fabiand> ah true
13:27:36 <fabiand> I just forgot about that
13:27:44 <mburns> fabiand: but that's future
13:27:50 <fabiand> yep
13:27:55 <mburns> let's see what we can handle now
13:28:23 <mburns> ok, anything else today?
13:28:28 <mburns> pmyers: jboggs READ10?
13:28:33 <jboggs> nothing from me
13:28:34 <READ10> mburns: nothing here
13:28:35 <pmyers> nada
13:28:39 <mburns> ok
13:28:47 <mburns> then back to work! ;-P
13:28:53 <mburns> thanks!
13:28:57 <mburns> #endmeeting