13:01:14 <mburns> #startmeeting oVirt Node Weekly Meeting 13:01:14 <ovirtbot> Meeting started Tue Sep 4 13:01:14 2012 UTC. The chair is mburns. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:14 <ovirtbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 13:01:25 <mburns> #chair fabiand jboggs pmyers_ READ10 13:01:25 <ovirtbot> Current chairs: READ10 fabiand jboggs mburns pmyers_ 13:01:27 * fabiand is here 13:01:34 <mburns> #topic agenda and roll call 13:01:42 * jboggs here 13:01:46 <mburns> agenda: 13:01:50 <mburns> 1. status updates 13:02:02 <mburns> 2. other topics 13:02:06 * READ10 here 13:02:29 <mburns> #topic status updates 13:02:30 <pmyers_> mburns: might be good to discuss the ovirt node openstack integration work 13:02:41 <mburns> pmyers_: yes, on my list for other topics... 13:03:00 <mburns> hey all, welcome back 13:03:15 <mburns> first time we've had one of these in a few weeks between vacations and linuxcon, etc... 13:03:48 <mburns> updates from me: 13:04:12 <mburns> #info ovirt workshop node presentation was well received, good questions, seemed like genuine interest 13:04:36 <mburns> #info people very excited about plugins and stateless, especially 13:05:35 <mburns> jboggs: what are you working on at the moment? 13:05:53 <jboggs> some plugin fixes and other rhev-h 6.4 items 13:06:01 * RobertM here 13:06:50 <mburns> jboggs: excellent 13:06:52 <mburns> fabiand: ? 13:07:12 <mburns> #info jboggs working mostly on bug fixes 13:07:18 <fabiand> mburns, I'm actually doing some bug hunting today 13:07:23 <mburns> #info both in core ovirt-node and plugins 13:07:37 <mburns> #info fabiand working on bug fixing and openstack integration 13:07:40 <fabiand> mburns, but besides that I'm looking into the openstack+node topic 13:08:17 <mburns> ok, great 13:08:24 <lhornyak> is gerrit dead? 13:08:46 <mburns> #info additional update: ovirt-node is currently not usable due to a kernel bug 13:08:51 * mburns looking for bz number 13:09:15 <RobertM> lhornyak, Gerrit is workingfor me 13:09:43 <lhornyak> RobertM: ah yes, responding, just dead-slow when pushing changes 13:09:45 <mburns> #link https://bugzilla.redhat.com/show_bug.cgi?id=845660 13:10:00 <mburns> jboggs: can you chase down where this is? 13:10:05 <jboggs> sure 13:10:09 <mburns> looks like vdsm might have a workaround for it 13:10:23 <mburns> but i heard last week that there was something that still needed fixing in vdsm as well 13:10:42 <mburns> #topic release status 13:10:51 <mburns> mostly just info 13:11:15 <mburns> #info ovirt-node 2.5.1 release doesn't build successfully for EL7 builds 13:11:29 <mburns> #info a couple patches posted to gerrit to fix some of these issues 13:11:46 <mburns> #info mostly around dracut and systemd 13:12:04 <mburns> #info need a new upstream tarball to incorporate the changes though 13:12:32 <mburns> #info so looking to make a 2.5.2 release this week, if we can get those changes merged 13:13:21 <mburns> i've tested them manually in mock environments and the changes seem to work correctly 13:14:08 <mburns> #topic ovirt-node/openstack integration 13:14:15 <mburns> fabiand: any updates here? 13:14:25 <fabiand> Yep 13:14:51 <fabiand> I've been working with apevec from the openstack camp to see whatwe can do on the node side to allow a better integration 13:15:09 <fabiand> we created a simple plugin which pulls in the appropriate openstack components 13:15:17 <mburns> #info fabiand and apevec working together to make integration simpler 13:15:22 <mburns> #info simple plugin created 13:15:27 <mburns> #undo 13:15:27 <ovirtbot> Removing item from minutes: <MeetBot.items.Info object at 0x8e6b62c> 13:15:31 <mburns> #info simple plugin created for openstack components 13:15:47 <fabiand> The plugin is still a bit rough around the edges and the whole functionallity has not yet been tested 13:15:51 <mburns> fabiand: just fyi, i saw your email earlier, but haven't read through it yet 13:15:53 <fabiand> but the daemons seem to be working 13:15:58 <fabiand> np :) 13:15:58 <mburns> fabiand: ack 13:16:13 <fabiand> one thing that came up is: there are a lot of things to configure in openstack 13:16:18 * mburns has 7101 unread emails right now 13:16:24 <fabiand> and there rose a demand for some kind of configuration management system 13:16:43 <fabiand> mburns, wey hey ... 13:17:26 <mburns> #info potential problem identified with openstack plugin 13:17:30 <mburns> #info lots of things to configure 13:17:41 <mburns> #info need some sort of configuration management 13:18:03 <mburns> #info investigating having some sort of puppet plugin 13:18:09 <fabiand> besides that we singled out the important conf params and added cmdline parsing for them to do the initial configuration 13:18:15 <fabiand> so compatible to what we have been doing in the past 13:18:41 <mburns> excellent 13:19:14 <mburns> fabiand: what are you doing about vdsm? 13:19:17 <mburns> disabling it? 13:19:24 <mburns> removing it? 13:19:29 <fabiand> ah 13:19:30 <fabiand> yes 13:19:41 <fabiand> there are also components conflicting with openstack components, like vdsm 13:19:50 <fabiand> the idea is to carve them out, and put them in separate plugins 13:20:03 <fabiand> this way we are getting a node core, which the other "spins" build upon 13:20:11 <jboggs> would a removal tool in edit-node be useful? 13:20:18 <mburns> fabiand: ok, what are you doing for testing right now? 13:20:29 <mburns> jboggs: i'd much rather avoid removing in plugins 13:20:35 <jboggs> ack 13:20:39 <fabiand> jboggs, I'd rather go with bsae node + plugins, rather than fat node - rpms + plugin 13:20:55 <fabiand> mburns, apevec is currently playing with the plugin and will be testing it 13:21:07 <mburns> one of our basic assumptions is that plugins add net-new (or in some cases updating) 13:21:09 <fabiand> when it's basically working I can setup a job to do the regular testing 13:21:24 <fabiand> btw. the image size was increased by about 10m if i recall it correctly 13:21:30 <mburns> if we start removing, then we open a whole new can of worms 13:21:53 <mburns> #agreed want to limit plugins to additions only, no remove 13:22:16 <mburns> #info image size increased by ~10MB 13:22:25 <mburns> fabiand: re: image size, that's not too bad 13:22:34 <fabiand> nope 13:22:42 <mburns> one thing we have to watch is the 256MB limit 13:22:50 <fabiand> okay, we are not reaching that 13:22:51 <mburns> if we get bigger than that, we break 13:23:09 <mburns> b/c Root and RootBackup are only 256MB 13:23:13 <fabiand> the worst case was openstack (glance, nova, keystone) + puppet client (jsut into the blue) at abotu 197mb or so 13:23:19 <fabiand> ahh okay 13:23:25 * mburns hit that when he accidently didn't minimize an image 13:23:32 <fabiand> btw. we came to puppet because it is common in the openstack domain 13:23:48 <mburns> fabiand: seems to be common in general these days 13:24:18 <fabiand> yep, also present in foreman .. 13:24:31 <mburns> fabiand: jboggs: we have some work to do in general with minimizing and plugins, but that's the next topic 13:24:40 <mburns> fabiand: anything else here? 13:25:06 <fabiand> The current plugin code is hosted here http://fedorapeople.org/cgit/fabiand/public_git/ovirt-node-openstack-plugin.git/ 13:25:21 <mburns> #link http://fedorapeople.org/cgit/fabiand/public_git/ovirt-node-openstack-plugin.git/ 13:25:22 <fabiand> I'm done for now 13:25:30 <mburns> ok, thanks for the update 13:25:50 <mburns> #topic plugins 13:25:56 <mburns> jboggs: any updates here? 13:26:30 <jboggs> booting on latest node should be working once dracut patch is acked 13:26:51 <fabiand> jboggs, which one? 13:26:54 <mburns> jboggs: ok, /me will look today 13:26:55 <jboggs> and also the patch for isomd5sum but otherwise stable 13:27:05 <mburns> ok, great 13:27:20 <mburns> some things came out of the workshop, w.r.t. plugins 13:27:26 <mburns> 1. we need example plugins 13:27:40 <mburns> 2. we need guidelines for writing/developing plugins 13:28:14 <fabiand> yeah 13:28:21 <mburns> 3. we need to make sure we have support for things like firewall and service generation 13:28:59 <jboggs> wouldnt that be handled with the rpm itself? 13:29:12 <jboggs> nothign against adding it just seems like the %post would handle it 13:29:16 <mburns> service stuff probably yes 13:29:30 <mburns> firewall config probably needs work on our part 13:29:46 <mburns> pretty sure changing the firewall in %post is frowned upon 13:30:05 <fabiand> apevec, and myself also came to this points - the question is if we should provide a common api to wrap the different services providing the functionality 13:31:03 <mburns> my thought is that the services should be installed 13:31:28 * fabiand thinks that we still need a way to en-/disbaled services at runtime ... there was a bz# 13:31:38 <mburns> and started based on whether or not they're configured 13:31:43 <mburns> similar to how we do cim 13:32:18 <mburns> and we can open/close firewall ports the same way 13:32:55 <mburns> fabiand: i agree, but it's just not easy to do in livecd environment 13:33:22 <mburns> and enable/disable would probably require either commandline access or new UI 13:33:44 <jboggs> once the services are figured out as a base it shouldnt be hard layering on top of that firewall etc 13:33:54 <mburns> ok 13:34:03 <mburns> firewalld should mak this easier too 13:34:14 <jboggs> I have the services bz I belive 13:34:52 <mburns> jboggs: i was thinking we could turn cim and snmp into example plugins 13:35:10 <mburns> and drop them from the base image 13:35:23 <fabiand> maybe we can also use the openstack plugin too 13:35:27 <jboggs> yeah that should be fine 13:35:32 <fabiand> I've tridd to make it quite clear, it has also cmdline parsing 13:36:09 <mburns> fabiand: yes, openstack is a good candidate as well 13:36:19 <mburns> but it's much more complex, i think than cim and snmp 13:36:31 <fabiand> okay 13:36:44 <mburns> though i haven't really looked at it yet 13:37:10 <mburns> ok, anything else on plugins? 13:37:17 <apevec> re. big cmdline - I'd look at removing direct access to /proc/cmdline, instead reading e.g. /etc/cmdline 13:37:40 <apevec> ovirt-early would append /proc/cmdline to that file 13:37:58 <apevec> while plugin could inject base values into it 13:38:11 <apevec> just an idea, I'll try to express it as a patch :) 13:38:18 <fabiand> apevec, I'd favor /run/cmdline - because the cmdline can change between boots, /etc is more static in my eyes 13:38:30 <apevec> ahyes, /run is the new location 13:38:38 <mburns> apevec: yes, something like that could work 13:38:44 <apevec> I think dracut is doing smthg like that 13:38:57 <mburns> apevec: i was thinking more like having /etc/default/ovirt file 13:39:09 <apevec> /etc/default/ovirt should be gone :) 13:39:10 <mburns> which we already write out to 13:39:19 <mburns> right, but whatever replaces it 13:39:32 <apevec> it's not FSTD compliant, I have posted one mega RFC some time ago 13:39:41 * mburns makes note to review apevec 's patch to remove /etc/default/ovirt 13:39:50 <mburns> apevec: it was posted, but just bad timing 13:40:00 <apevec> Node is not devel frozen now? 13:40:05 <mburns> no time to review it 13:40:12 <mburns> apevec: no, not frozen 13:40:25 <mburns> was just too busy with other issues to review and incorporate 13:40:26 <apevec> so time is right for bigger changes! 13:40:27 <fabiand> I updated apevec 's patch a couple of times 13:40:37 <fabiand> (rebased) 13:40:51 <mburns> apevec: yes, time is right to review and get it in for 2.6.0 13:42:15 <mburns> ok, anything else to cover today? 13:42:43 <apevec> fabiand, could you please take over that fstd patch? 13:42:52 <apevec> I even lost link to it :) 13:42:53 <fabiand> apevec, sure, I'd be happy to do so 13:43:09 <fabiand> apevec, this one http://gerrit.ovirt.org/#/c/2686/ ? 13:43:21 <apevec> yep, that's the one 13:43:46 <apevec> mburns, I'm good 13:44:29 <mburns> #action fabiand to take over http://gerrit.ovirt.org/#/c/2686/ and update it 13:44:54 <apevec> fabiand, did you push your rebases to gerrit? There's only original patch set 1 13:44:54 <mburns> ok, if nothing else... 13:45:18 <fabiand> apevec, no, I never pushed it, just had it locally, and rebased it with my other pending branches 13:45:38 <fabiand> apevec, I'll have to rebase it on the lastest cdoe style changes, I'll push it afterwards 13:45:39 <dneary> Hi 13:46:00 <dneary> Anyone know how I can find a revision ID from which a branch was made? 13:46:16 <fabiand> gitk ;) 13:46:30 <dneary> fabiand, Smart-ass ;) 13:46:45 * mburns could have pointed to gitweb... 13:46:55 <fabiand> hehe 13:46:55 <apevec> dneary, revision ID = hash? 13:46:56 <mburns> but that would be even uglier... 13:46:58 <dneary> In svn there was a "stop on branch" argument to svn log 13:47:15 <mburns> ok, /me ending node meeting 13:47:17 <mburns> #endmeeting