14:02:20 <fabiand> #startmeeting oVirt Node Weekly Meeting
14:02:20 <ovirtbot> Meeting started Mon Jun 15 14:02:20 2015 UTC.  The chair is fabiand. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:20 <ovirtbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:02:24 <fabiand> #chairs rbarry tlitovsk dougsland
14:02:35 <dougsland> here
14:03:19 <fabiand> hey dougsland
14:03:26 * rbarry here
14:04:05 <fabiand> morning rbarry
14:04:24 <fabiand> Let's give tlitovsk a few minutes
14:04:27 <fabiand> #topic Agenda
14:04:37 <fabiand> #info ovirt-3.5 build and publish
14:04:41 <fabiand> #info ovirt-3.6 build and publish
14:04:45 <fabiand> #info Other Items
14:04:54 <fabiand> #topic ovirt-3.5 build and publish
14:05:51 * tlitovsk here
14:05:57 <fabiand> rbarry, tlitovsk -- Do you have an update of where we stand with ovirt-node (rpm) and iso builds?
14:06:02 <fabiand> for 3.5?
14:06:17 <tlitovsk> fabiand, its getting more complicated
14:06:33 <tlitovsk> fabiand, we have our ovirt-35-snapshot builds
14:06:47 <tlitovsk> but sbonazzo want seperate builds for ovirt-35
14:07:21 <tlitovsk> meaning we need to make a new job
14:07:24 * sbonazzo here
14:07:25 <fabiand> tlitovsk, I just spoke to sbonazzo and he told me that the vorit-3.5 repo has all the official ovirt-3.5 (and later) builds
14:07:32 <fabiand> so we should be fine to use the ovirt-3.5 repo
14:07:37 <fabiand> and will get everything released for 3.5
14:07:44 <fabiand> right, sbonazzo ?
14:07:48 <tlitovsk> fabiand, that another job,
14:07:52 <sbonazzo> fabiand: right, just using ovirt-3.5 is ok for getting node build on 3.5.3
14:07:59 <fabiand> tlitovsk, why another?
14:08:07 <fabiand> sbonazzo, thanks
14:08:14 <tlitovsk> since we have ajob that runs using ovirt35-snapshot
14:08:31 <fabiand> I assumed that we need -snapshot, because ovirt-3.5 did not have the latest bits.
14:08:40 <fabiand> But now it was clarified that ovirt-3.5 has the löatest official bits ..
14:08:51 <fabiand> Thus I'm fine in changing the snapshot job to use ovirt-3.5
14:09:03 <tlitovsk> but ovirt-35 has it bits only when the ovirt-35 is ready
14:09:03 <fabiand> or said different - I don't see why we need -snapshot
14:09:05 <sbonazzo> fabiand: tlitovsk: you can use a parameter in the job, take ovirt-3.5-snapshot as default and allow ovirt-3.5 for manual running
14:09:10 <fabiand> tlitovsk, which is fine
14:09:12 <tlitovsk> before this al the bits are in snapshot
14:09:34 <sbonazzo> fabiand: snapshot is ok for getting latest bits in
14:09:46 <sbonazzo> fabiand: 3.5 just contains the latest stable
14:09:48 <fabiand> right ..
14:09:50 <tlitovsk> fabiand, we use snapshot to provide the cutting edge.
14:10:10 <tlitovsk> but when there is a release sbonazzo want us to make one clean build using ovirt25 repo
14:10:12 <fabiand> So, for 3.5 - I'M fine with using either ovirt-3.5 OR ovirt-3.5-snapshots
14:10:20 <fabiand> right
14:10:31 <fabiand> To have less images, and less work I just want one stream for 3.5
14:10:36 <fabiand> and that is either 3.5-snapshot or 3.5
14:10:38 <fabiand> Not both
14:10:48 <fabiand> (based on el7)
14:11:02 <fabiand> I do not see the need to have 3.5 and 3.5-snapshot builds
14:11:17 <fabiand> The difference between 3.5 and 3.5-snapshot is to small to justify having two streams
14:11:19 <tlitovsk> fabiand, me too. but on one hand you want to have nightly and sandro want a clean build on the day we release.
14:11:33 <fabiand> tlitovsk, maybe we can find a compromise
14:11:53 <sbonazzo> fabiand: tlitovsk: snapshot may become broken between 2 stable releases
14:12:07 <sbonazzo> fabiand: tlitovsk while I'm expecting that the GA has passed QE :-)
14:12:09 <fabiand> tlitovsk, I personally do not need nightly builds :)
14:12:18 <fabiand> the reason why we do have nightlies is because of the centos changes
14:12:24 <fabiand> What we can do:
14:12:32 <fabiand> Move to weekly builds based on ovirt-3.5
14:12:34 <tlitovsk> fabiand, yes you do . remmember the ovirt-node problme we had 2 weks ago
14:12:39 <fabiand> Then we have stable bits
14:12:42 <tlitovsk> that users wanted the latest ovitr-nbode
14:13:01 <fabiand> right
14:13:12 <sbonazzo> fabiand: tlitovsk: fine for me.
14:13:17 <fabiand> but the problem back then was that the node (rpm) which was used was _to_ old - because the wrong repo was used
14:13:30 <tlitovsk> fabiand, the wrong repo was ovirt-35
14:13:45 <tlitovsk> fabiand, the one sbonazzo want us to use now
14:14:02 <fabiand> right
14:14:06 <tlitovsk> fabiand, lets just make one more job.
14:14:19 <tlitovsk> fabiand, its pretty easy.
14:14:20 <fabiand> That is why I asked if we have publishers witch push ovirt-node (rpm)s to that repository
14:14:31 <fabiand> tlitovsk, no, let's try to clean this up, and not create yet another job
14:14:37 <tlitovsk> fabiand, ooo. that means 2 more jobs.
14:15:12 <tlitovsk> fabiand, bad idea.
14:15:20 <fabiand> actually, for 2 weeks or so we try to get this straigh ...
14:15:44 <tlitovsk> fabiand, there is actually 2 seperate requirments
14:15:53 <fabiand> Please lay them out
14:15:54 <fabiand> :)
14:15:58 <tlitovsk> fabiand, nightly builds - this one we have.
14:16:01 <sbonazzo> fabiand: tlitovsk: we release stable every ~6 weeks, I'm fine releasing node rpms by hand like all the other rpms
14:16:12 <tlitovsk> fabiand, official release .
14:16:23 <tlitovsk> fabiand, the one sbonazzo just mentioned.
14:16:54 <fabiand> right
14:16:57 <tlitovsk> sbonazzo, fabiand and I dont like manual because we never have time to do this.
14:17:02 <fabiand> exactly, tlitovsk
14:17:06 <fabiand> I fully agree on that
14:17:15 <fabiand> That is why I'd liek to see builders and publishers for the required branches
14:17:32 <tlitovsk> fabiand, i can make the job addaptable and recieve the repo as paramter.
14:17:48 <sbonazzo> fabiand: tlitovsk: I suggest to include dcaro in the discussion
14:18:02 <sbonazzo> fabiand: tlitovsk: dcaro also would like to have automated ga releases
14:18:31 <tlitovsk> sbonazzo, dcaro is there some one that does automated releases in ovirt ?
14:18:55 <sbonazzo> tlitovsk: not that I'm aware of
14:19:12 <tlitovsk> sbonazzo, fabiand then we will be the first one.
14:19:34 <fabiand> let's start with the snapshot
14:19:42 <tlitovsk> sbonazzo, how do you upload rpms to the ovirt35 repo when you build manually ?
14:19:47 <fabiand> But, the story is longer, let's start at the beginning
14:19:50 <fabiand> snapshot requires:
14:20:05 <fabiand> ovirt-node (rpm) build from ovirt-3.5 branch
14:20:16 <fabiand> ovirt-node (rpm) published to ovirt-3.5-snbapshot
14:20:30 <fabiand> ovirt-node-iso (iso) build from ovirt-3.5-snapshot repo
14:20:44 <tlitovsk> +vdsm-plugin-recepies.
14:20:44 <sbonazzo> tlitovsk: I'm using repoman, developed by dcaro
14:21:00 <fabiand> ovirt-node-plugin-vdsm and ovirt-node-plugin-hosted-engine builds and publishers for ovirt-3.5 and publishing to ovirt-3.5-snapshot are also required
14:21:07 <fabiand> tlitovsk, exactly
14:21:12 <fabiand> tlitovsk, sbonazzo does that sound correct?
14:21:36 <fabiand> that will be: ovirt-node-iso-3.5-snapshot build
14:21:51 <tlitovsk> sbonazzo, fabiand a bit missleading since you mean ovirt-35 git branch and ovirt35-snapshot repo
14:22:15 <fabiand> right, I should have added the word brepo above
14:22:21 <fabiand> but I think it is consitent
14:23:11 <tlitovsk> fabiand, we have most of what you mentioned . (maybe need to yamlize vdsm-plugins)
14:23:33 <sbonazzo> fabiand: tlitovsk: I think you can use just 1 builder for both snapshot and GA releases, and one nightly publisher for the snapshots. You'll need a manual publisher for just the GA builds
14:24:12 <tlitovsk> sbonazzo, not really , since the builder knows where to build from .
14:24:26 <tlitovsk> sbonazzo, but we can parametrize it
14:24:50 <txomon|fon> did anyone have this error with glusterfs? https://gist.githubusercontent.com/txomon/8455f165adb3c8f3df28/raw/7e465d9883be21a87b0687fb6230464dd0da6c9c/etc-glusterfs-glusterd.vol.log
14:24:56 <sbonazzo> tlitovsk: the only builder that may require different repo is the one for the iso
14:25:16 <txomon|fon> When I reboot my second host, it can't go live
14:25:24 <tlitovsk> sbonazzo, thats the one I talk about.
14:25:49 <sbonazzo> tlitovsk: +1
14:26:10 <fabiand> So
14:26:34 <fabiand> That leaves us with a couple of action items:
14:26:40 <fabiand> sbonazzo, tlitovsk feel free to interrupt me:
14:26:51 <tlitovsk> fabiand, we will need to add more jobs / parametrize existing ones. ( its the same under yaml)
14:28:11 <tlitovsk> fabiand, plz continue
14:29:55 <fabiand> #action tlitovsk to create a builder for ovirt-node, ovirt-node-plugin-vdsm, ovirt-node-plugin-hosted-engine from their respective ovirt-3.5 branches
14:30:23 <fabiand> #action tlitovsk and rbarry to create publishers for ovirt-node, ovirt-node-plugin-vdsm, ovirt-node-plugin-hosted-engine builds to publish to ovirt-3.5-snapshot repository
14:30:46 <fabiand> #actio tlitovsk and rbarry to update/create an ovirt-node-iso job which builds an iso from the ovirt-3.5-snapshot repository
14:30:49 <fabiand> #action tlitovsk and rbarry to update/create an ovirt-node-iso job which builds an iso from the ovirt-3.5-snapshot repository
14:31:00 <fabiand> That should give us reliable "nightly" builds from the snapshot repository
14:31:16 <fabiand> tlitovsk, rbarry sbonazzo ?
14:31:18 <fabiand> Does this sound correct
14:31:25 <fabiand> What is the gap between what we have and this requirement?
14:31:38 <tlitovsk> fabiand, just yamelize the vdsm jobs.
14:31:48 <tlitovsk> fabiand, and thats more of nice to have
14:32:36 <tlitovsk> fabiand, I mean the vdsm plugin
14:32:56 <rbarry> It's hopefully not overly difficult, either
14:34:11 <fabiand> tlitovsk, rbarry right
14:34:25 <fabiand> I mean --  after all this should not be to far off from what we have
14:34:53 <tlitovsk> fabiand, now we left wth doing the same for ovirt-3.5 git branch for ovirt-3.5 repo
14:37:13 <fabiand> tlitovsk, let's first get one stream into shape ..
14:37:15 <sbonazzo> fabiand: tlitovsk: you have 2 identical action items :-)
14:37:21 <fabiand> I'd really like to close one for now ..
14:37:28 <sbonazzo> uh
14:37:28 <fabiand> sbonazzo, the one was missing an n ;)
14:37:37 <sbonazzo> fabiand: right, seen it
14:37:59 <fabiand> tlitovsk, rbarry -- Please let us try to close this until next week
14:38:07 <sbonazzo> fabiand: I think you already have publishers for the snapshot repo
14:38:13 <tlitovsk> fabiand, yes.
14:38:14 <sbonazzo> fabiand: but I may be wrong
14:38:25 <fabiand> sbonazzo, yes, I 'm quite sure we have soemthing along this lines.
14:38:26 <tlitovsk> fabiand, we have the publishers.
14:38:34 <fabiand> We just need to close this item, i think the gap is really small ..
14:38:45 <sbonazzo> fabiand: +1
14:38:59 <tlitovsk> fabiand, the only thing we miss for the ovirt35-snapshot is yamlizing the vdsm-plugin job.
14:39:17 <tlitovsk> fabiand, except for this the ovirt-35-snapshot line is done.
14:39:34 <tlitovsk> fabiand, and the iso we have there are nightly builds and working constantly.
14:40:14 <tlitovsk> fabiand, by yamlizing I mean we have the job its working , but its config is not in yaml repo of the jenkins.
14:40:32 <tlitovsk> fabiand, it was configured mannualy
14:40:56 <fabiand> Right
14:41:06 <fabiand> Thanks for that explanation
14:41:14 <fabiand> That sounds reasonable to close within a week
14:41:28 <fabiand> The goal is that we see ovirt-3.5-snapshot rpms in the snapshot iso
14:41:39 <fabiand> tlitovsk, please make sure to call the job ovirt-node-iso-3.5-snapshot
14:41:45 <fabiand> That makes it clear from where we get those rpms
14:41:55 <tlitovsk> fabiand, ack
14:43:45 <fabiand> great
14:43:58 <fabiand> #action tlitovsk and rbarry to name the job ovirt-node-iso-3.5-snapshot
14:44:02 <fabiand> Great
14:44:04 <fabiand> Moving on ....
14:45:22 <fabiand> #topic ovirt-3.6 build and publish
14:45:26 <fabiand> That is also on our list
14:45:35 <fabiand> But let's defere that to when we've completed 3.5
14:45:42 <fabiand> Moving on ...
14:45:47 <fabiand> #topic Other Items
14:45:53 <fabiand> rbarry, tlitovsk dougsland -- More to say?
14:46:14 <rbarry> Nothing here
14:46:21 <tlitovsk> fabiand, yes , we missing som ovirt-vmconsole package in master .
14:46:39 <fabiand> sbonazzo, do you know something about the missing package?
14:46:46 * fabiand has seen an email thread on that  ..
14:47:12 <tlitovsk> fabiand, sbonazzo ovirt-vmconsole-host is the name
14:47:33 <sbonazzo> fabiand: tlitovsk: max is working with alon for providing a job for building it
14:47:41 <fabiand> sbonazzo, thanks
14:47:51 <fabiand> tlitovsk, so we'll need to await that job
14:49:26 <tlitovsk> sbonazzo, max the one that seats near me ?
14:49:36 <tlitovsk> sbonazzo, from the CI team ?
14:49:44 <sbonazzo> tlitovsk: yep
14:51:18 <fabiand> okay
14:51:23 <fabiand> Anything else, dougsland rbarry tlitovsk ?
14:51:37 <rbarry> Nope
14:52:28 <fabiand> dougsland, ?
14:52:37 * tlitovsk nope
14:53:41 <fabiand> okay
14:53:45 <fabiand> Then thanks everybody
14:53:48 <fabiand> #endmeeting