13:00:25 #startmeeting oVirt Node Weekly Meeting 13:00:25 Meeting started Tue Sep 16 13:00:25 2014 UTC. The chair is fabiand. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:25 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:00:30 #chairs dougsland rbarry 13:00:45 #topic Agenda 13:00:50 #topic Action Item Review 13:00:54 #info oVirt 3.5 13:00:58 #info Jenkins 13:01:16 #info Next-Gen Node 13:01:23 #info Other Items 13:01:49 * rbarry here 13:02:46 here 13:03:57 dougsland, rbarry hi 13:04:11 #topic oVirt 3.5 13:04:24 #info Testing and some smaller bug ficxing happend last Friday 13:04:30 Thanks a lot to dougsland and rbarry 13:04:41 #info rbarry created a new iso 13:04:45 (which I am currently uploading) 13:04:55 <[trip]> Anyone have USB redirection working using Remote Viewer and a Window's Client? 13:04:58 rbarry, do you know what packages you pulled in? 13:05:04 Was it already 3.5rc2? 13:05:16 It was RC2 13:05:31 cool 13:05:54 Then we can use your iso for the test day tomorrow 13:06:19 It's just pending to publish the relevant rpms. 13:06:44 #info ovirt-node-iso-3.5.0.ovirt35.20140912.el6.iso contains 3.5rc2 packages 13:06:51 #info ovirt-node rpms need to be published 13:07:13 rbarry, have you tried creating the ovirt-node-iso using th eovirt-3.5 branch of th every same repository? 13:07:37 I have not yet tried using the 3.5 branch of ovirt-node-iso, no 13:08:13 Okay .. 13:10:17 right 13:10:36 We've got a testday iso which is good 13:10:54 #action fabiand to generate rpms for 3.5rc2 iso 13:11:01 :-> 13:11:05 #action fabiand to ask dcaro to publish iso 13:11:22 #action fabiand to go over and give Netbulae the iso 13:11:24 #undo 13:11:24 Removing item from minutes: ACTION by fabiand at 13:11:22 : fabiand to go over and give Netbulae the iso 13:11:25 ;) 13:11:33 nice 13:11:55 :) 13:11:55 dougsland, rbarry just as a reminder - tomorrow is testday .. 13:12:35 So we should hang out here to see if someone is having issues with Node 13:12:41 The usual stuff for a testday ... 13:12:53 okay, now, back to the action item review 13:12:56 which i missed. 13:13:05 #topic Action Item Review 13:13:16 #link http://lists.ovirt.org/pipermail/devel/2014-September/008713.html 13:13:33 #info fabiand to fix appliance job during the next week 13:13:42 #link http://jenkins.ovirt.org/view/All/job/ovirt-appliance_master_merged/ 13:13:46 when 3.5 will be released ? 13:14:02 The build is fixed as in the rootfs is build, ubt the ova creator has currently some issues 13:14:17 I'm optimistic that we have an ova at the end of this meeting 13:14:20 so be patient .. 13:14:36 #info appliance rootfs is built, ova is currentl not created, but WIP 13:14:57 carrying on 13:15:00 #topic Jenkins 13:15:09 rbarry, we also spoke about it last week, and actually many times .. 13:15:15 consolidation of Jenkins jobs 13:15:23 But I believe we agreed to move that out after 3.5 .. 13:15:45 vidalinux, take a look here to get an idea of the schedule: http://www.ovirt.org/OVirt_3.5_release-management 13:16:01 After 3.5 is probably better. Hopefully we can also move to EL7 builders at the same time 13:16:56 Indeed 13:17:04 And consolidate into few streams as possible 13:17:27 rbarry, can we do anything to prepare the move? 13:17:32 Maybe already shut down jobs we do not need? 13:17:43 dougsland, also for you .. 13:17:50 We might want to merge jobs 13:18:01 * fabiand thinks about merging jobs which are relevant per release 13:18:09 make sense 13:18:17 i.e for 3.4 we should have a job (theoretically) combining base + vdsm plugin 13:18:34 for 3.5 we should have a job combinding base + vdsm plugin + he plugin .. 13:18:50 so just building the final image .. 13:19:43 carrying on .. 13:19:53 #topic Next-Gen Node 13:20:09 #info Stable job which builds the rootfs 13:20:17 #undo 13:20:17 Removing item from minutes: INFO by fabiand at 13:20:09 : Stable job which builds the rootfs 13:20:21 #info Stable job which builds the runtime layout 13:20:27 This includes Fedora 20 + imgbased 13:20:40 The runtime layout is an image which can be used inside qemu to test imgbased 13:20:41 #link http://www.ovirt.org/OVirt_3.5_release-management 13:20:53 #info Stable job to run functional tests on runtime layout image 13:21:43 The job is running some sanity tests (checking for denials, checking for mandatory binaries, checking that imgbase is working) 13:21:53 #link http://www.ovirt.org/OVirt_3.5_release-management 13:22:14 rbarry, you started looking into puppet for managing the local configuration ... 13:22:23 Could you summarize what you are thinking about? 13:23:28 At present, I'm thinking of ripping the guts out of ovirt.node.config.defaults and shipping small puppet manifests which match each bit (kdump, ntp, rsyslog, etc al) 13:23:53 Then assigning variables with hiera and pushing from there 13:24:01 rbarry, that sounds nice! 13:24:12 Especiall because if they are individual manifests then we can push the upstream .. 13:24:23 I looked at how packstack does it, but they're writing the templates on the fly and inserting variables, which isn't very pretty 13:24:33 okay .. 13:24:37 Well, the upside to this is that upstream puppet should already handle almost everything we need to configure 13:24:50 Indeed, and we can contribute the rest .. 13:25:38 rbarry, do you know if it's also possible to do the configuration of 13:25:42 - network 13:25:45 There also appears to be an etcd hiera provider, which could be very interesting (under the assumption that nodes will be configured similarly), but that's likely a task for a future release beyond next-gen 13:25:53 (with bonding, bridging...) 13:26:38 I haven't found a provider for that yet, but I haven't spent a lot of time looking 13:27:12 I suspect that using the Anaconda configuration bits for that may be better, since even if puppet does support networking, it's likely to be fairly basic (since most puppet configurations assume networking is already up) 13:27:34 right 13:28:08 rbarry, would you mind creating a page, summarizing all the configration topics (snmp, cim, ntp, network, ..) we need to address in a table 13:28:19 Where we can then also provide links to manifests 13:28:30 or note that the configuraiton should take place using anaconda .. 13:28:38 (or a different technology) 13:30:11 Sure, I can do that. I think that linking to puppet resource types/modules may be what you mean here rather than manifests 13:30:15 Ala https://github.com/razorsedge/puppet-snmp 13:30:45 Yeah, I think I was wrong about the terminology 13:30:47 thx 13:31:32 yeah 13:31:45 it's clases/modules/types i was thinking about .. 13:32:14 #info Idea to do configuration using puppet - early investigationsdone by rbarry 13:32:28 #info ripping the guts out of ovirt.node.config.defaults and shipping small puppet manifests which match each bit (kdump, ntp, rsyslog, etc al), assigning variables with hiera and pushing from there 13:32:48 #info etcd hiera provider is also interesting to configure many nodes at once 13:33:30 #action rbarry to create a wiki page summarizing all the compoents which need a module, also specifying if it can be done with puppet or needs something else 13:33:49 rbarry, sounds good in general 13:34:08 rbarry, if you start writing anything .. 13:34:14 then we can include it in the appliance build 13:34:31 also, think of adding tests right from the beginning, then we can add the testing to the check function job .. 13:35:09 Okay 13:35:12 carrying on .. 13:37:50 #topic Other Items 13:38:00 anything else you want to bring up rbarry dougsland ? 13:38:21 not really, let's have a great 3.5 release :) 13:38:30 Netbulae, right? =) 13:38:32 +1 13:39:24 btw 3.5 looks really great I'm testing the rc1 on one lab server 13:39:25 :) 13:39:33 ~_~ 13:39:34 vidalinux, cool 13:39:47 why still rc1? 13:40:00 I like rc2 better :-) 13:40:04 rbarry, https://forge.puppetlabs.com/razorsedge/network 13:40:08 rbarry, https://forge.puppetlabs.com/adrien/network 13:40:17 I think is rc2 don't remeber lol 13:40:21 great, then thanks dougsland and rbarry 13:40:29 Going once 13:40:48 guys is posible to manage docker on ovirt ? 13:41:27 twice 13:42:28 That's why I'm looking, fabiand :) They exist, but I haven't had a chance to test if any of them test more exotic configurations, I suppose 13:42:38 yes yes 13:42:39 :) 13:42:48 I think we need to carefully look at them .. 13:43:12 Especially I'd take care to not bind us to much to fedora/rhel/centos, but also open node to debian based distors 13:43:14 distros 13:43:17 third time 13:43:19 #endmeeting