13:00:21 #startmeeting oVirt Node Weekly Sync 13:00:21 Meeting started Tue Mar 27 13:00:21 2012 UTC. The chair is mburns. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:00:31 #chair mburns jboggs pmyers fabiand 13:00:31 Current chairs: fabiand jboggs mburns pmyers 13:00:37 * pmyers here 13:00:38 #topic Roll Call and Agenda 13:00:41 * jboggs here 13:00:46 * fabiand here 13:00:49 1. Action Item Review 13:00:54 2. Release Status 13:00:59 3. Stateless status and update 13:01:04 4. CIM status and update 13:01:10 5. Other topics 13:01:30 anyone have other topics? 13:01:46 #topic action item review 13:01:58 #link http://ovirt.org/meetings/ovirt/2012/ovirt.2012-03-20-13.02.html 13:02:23 #info systemd patches posted 13:02:37 #info systemd patches reviewed and merged 13:02:53 #info bugs updated for 2.3.0 release 13:03:31 #info mburns still hasn't looking into stateless yet 13:03:38 but we'll discuss that later 13:03:45 #topic release status 13:04:02 #info oVirt Node 2.3.0 Released 2012-03-26 13:04:26 #link http://www.ovirt.org/wiki/Node_Backlog 13:04:48 i updated the 2.3.0 link there, added a 2.5.0 link and an untargeted link 13:05:31 oVirt Project release is targeting May for their next release 13:05:59 we should target 2.4.0 for end of April, then do 2.4.1, 2.4.2 as needed during that next month 13:06:07 thoughts? 13:06:22 sounds ok to me 13:06:32 to me too 13:06:47 14[[07Node Backlog14]]4 !10 02http://www.ovirt.org/w/index.php?diff=2961&oldid=2960&rcid=3045 5* 03Mburns 5* (+7) 10 13:06:56 ok, updated backlog page with that date 13:07:12 #agreed 2.4.0 targeted for 2012/04/30 13:07:50 given that, we need to review the bug list for 2.4.0 and move out bugs that we can't get done 13:08:19 jboggs: fabiand: can you see what's assigned to you and what you think you can reasonably get done for that date? 13:09:02 jboggs: fabiand: also taking into account other responsibilities you have beyond just ovirt-node 13:09:34 mburns, mine are obscure ones that are probably going to be pushed anyways, can possibly take on some you guys want to push 13:09:35 #action jboggs fabiand mburns to review bugs assigned and move to 2.5.0 where appropriate 13:10:00 jboggs: i expect most of your time will be spent on plugin development 13:10:13 i'd like to get that and stateless in for 2.4.0 13:10:24 ok that works 13:10:25 mburns, we'll have to talk about where else I could be working on 13:10:39 network manager conversion? 13:10:42 that's probably important 13:10:42 :) 13:10:43 14[[07Vdsm TODO14]]4 !10 02http://www.ovirt.org/w/index.php?diff=2962&oldid=2676&rcid=3046 5* 03Danken 5* (+241) 10/* What Can You Do for Vdsm */  13:10:50 fabiand: yes, you've done a good job grabbing bz's 13:11:07 fabiand: i'd like to get automation stuff going a bit as well 13:11:07 :) 13:11:13 mburns, definetly! 13:11:19 I'd also like to get some automated testing 13:12:09 suggestion, one should not 'feature freeze' on 2012-04-31 (http://www.ovirt.org/wiki/Second_Release) ;) 13:12:12 mburns: :) 13:12:19 mburns: how's the stateless node coming? 13:12:46 #action mburns to work with fabiand on mapping out automation plan 13:13:40 hitvx: yeah, hard to freeze on a day that doesn't exist 13:14:32 we'll target 2012/04/30 for our 2.4.0 and that will allow us to meet the 2012/05/31 release date for the overall project 13:14:40 xTs_w: stateless is the next topic 13:16:00 14[[07Second Release14]]4 !10 02http://www.ovirt.org/w/index.php?diff=2963&oldid=2795&rcid=3047 5* 03Mburns 5* (+0) 10/* Timeline */ change feature freeze to 30-April since 31-April doesn't exist 13:16:11 ok, anything else for releases? 13:16:34 #info oVirt 3.1 release targeted for 2012-31-05 13:16:49 #info oVirt 3.1 feature freeze 2012-04-30 13:16:56 ok, on to stateless 13:17:01 #topic Stateless 13:17:21 #link http://www.ovirt.org/wiki/Node_Stateless 13:18:01 #action mburns to update wiki page 13:18:10 #undo 13:18:10 Removing item from minutes: 13:18:15 #action mburns to update wiki page for stateless 13:18:44 i've been using stateless locally to test images 13:18:52 it seems to be fairly stable 13:19:09 but we're still limited by the lack of support for stateless nodes by vdsm and engine 13:19:15 xTs_w: speaking of stateless, any chance you can help push that along re: some patches? If we had some more folks helping in the community we could make a lot more progress here :) 13:19:23 mburns, would be nice if you added your notes how to do this to the wiki 13:19:33 fabiand: how to run stateless? 13:19:40 mburns, yes 13:19:57 mburns: stateless for vdsm/oVirt Engine is outside the scope of oVirt Node project... we'll do what we can to make Node stateless (as much as possible) and then leave the rest to vdsm team 13:20:05 pmyers: I'd like to help, but recently had to kill my whole testing equipment, because we needed the parts somewhere else :( 13:20:15 that's a bummer :( 13:20:16 fabiand: ok, i'll put up a quick wiki page, but in short, add "stateless" to the kernel command line 13:20:16 I've currently got no stuff to test 13:20:26 you can do dev work on Node in a VM though 13:20:35 so even if you have a single box with kvm on it, it's good enough :) 13:20:35 mburns, right - I can go trough the scripts to see what's happening :) 13:20:55 yes, i do most install testing in vms first, and develop on a vm 13:21:03 then move to real hardware once i work out bugs there 13:21:35 * mburns has even been known to run test installs on vms running inside ovirt-engine on ovirt-node 13:21:54 mburns, nesting? 13:21:59 overall, most of the basic steps for stateless are done 13:22:02 fabiand: mostly 13:22:18 you can't run vms on the nested or virtualized ovirt-nodes 13:22:21 mburns, nesting would be nice for testing - but later more on this 13:22:34 but you can do most of the rest 13:22:49 at least it would be nice to allow virtualized nodes to be registered with engine - for testing 13:23:25 #action mburns to review current stateless state and get a todo list together 13:23:57 fabiand: yes, registration should actually work with virtualized nodes 13:24:06 they should just come up non-operational 13:24:26 ok, anything else to cover on stateless? 13:24:31 right 13:25:05 ok, moving on to cim 13:25:10 #topic CIM Status 13:25:47 #info sblim-sfcb service starts, firewall port is opened, cim password can be set correctly 13:25:58 #info remote systems cannot query however 13:26:38 DV gave me some pointers on node-devel@ earlier and looking through the logs he suggested, i found that it's failing to load the libcmpiutil.so library 13:26:50 this is because we blacklisted that package 13:27:13 * mburns will have a patch soon to un-blacklist it and re-test cim 13:27:45 cool 13:28:18 #other topics 13:28:42 #action mburns to patch missing libcmpiutil package and retest cim 13:28:46 #topic Other Topics 13:29:01 Automation 13:29:21 fabiand: we can work up a high level plan for automation, then we can send it to node-devel@ 13:29:31 sounds good 13:29:47 makes more sense to do that off line to me rather than in a meeting like this 13:30:02 Network Manager conversion 13:30:12 pmyers: i didn't completely ignore your comment earlier 13:30:37 we're going to need to move toward supporting the network manager api in the near future 13:30:39 I'd say we should start this early .. 13:30:51 fabiand: yes, i agree 13:31:08 mburns: I know you didn't which is why I didn't poke you a second time :) 13:31:16 using NM api should hopefully clear up alot of the networking scenarios from potential failures 13:31:31 it appears that vdsm is going to eventually make NM their default interface for network management, so at the very least we need to start including it 13:31:40 jboggs: i hope so as well 13:32:14 i think what we'll do is have jboggs focus on the plugins 13:32:28 fabiand: on the automation stuff 13:32:40 mburns: on the stateless 13:32:43 all of us fixing bugs 13:33:05 and whoever gets through the big ticket stuff first takes the first pass at designing the NM changes 13:33:50 Maybe the last one getting thourgh should get NM? ;) 13:33:58 haha 13:33:58 i'll try to get a wiki feature page up for NM this week 13:34:01 fabiand: ;-) 13:34:12 #action mburns to post wiki page for NM feature 13:34:32 anything else for NM? 13:34:41 not sure there is much to talk about at the moment here 13:34:53 ok, one other thing from me then 13:34:57 #link http://ovirt.org/wiki/Node_Troubleshooting 13:35:05 i threw this together yesterday 13:35:18 so it's really just a dump of stuff off the top of my head 13:35:26 feel free to add anything else you've found 13:35:38 or add additional topics 13:36:04 or even erase what i wrote as being horribly wrong... 13:36:30 that's all i have for today 13:36:32 Don't know if it's relevant for the meeting, but the /data-not-beeing-mounted bug seems quite important to me 13:36:43 because it will make updates difficult, afaiu 13:36:54 sure we can cover it briefly 13:37:01 #topic mountpoints not getting mounted 13:37:15 #link https://bugzilla.redhat.com/show_bug.cgi?id=806349 13:37:38 background -- /data is not getting mounted correctly on reboot 13:37:51 and i've heard that /var/log isn't either 13:37:55 yep 13:37:59 just Config 13:38:26 thus, logging and data as well as bind-mounting /data/images to the libvirt path doesn't happen 13:38:47 fabiand: has investigated and found that this is due to a systemd bug where it recognizes that the unit file that does the /etc/fstab mounting was updated, but doesn't reload 13:39:03 I wouldn't say it's a bug .. 13:39:06 he's posted a workaround fix already and filed a systemd bug on this 13:40:00 (swap is also affected) 13:40:38 At least: A couple of paths are not mounted correctly, including the images path and that ain't to good in my eyes 13:41:07 /data/images is only a problem if the user wants to upgrade from engine or run a "local" storage domain 13:41:42 HostVG-Logging and Swap not working right are larger concerns for me 13:41:53 ah okay - I thought that /data/images is the "main entry point" 13:41:59 (for storing images) 13:42:39 i'm pretty sure vdsm manages that in another location, though the actual location escapes me atm 13:43:11 I believe it will be libvirts default location (~ /var/lib/libvirt/images) 13:43:36 no, it's something like /engine/data-center or something like that 13:43:44 oh that one. ok 13:43:54 they do whatever mounting they need there 13:44:12 anything else to discuss on this? 13:44:18 i think it's well in hand currently 13:44:29 we have a workaround and bug filed for the original problem 13:44:35 and a separate bug to revert the fix 13:44:44 err...revert the workaround 13:45:10 ok, thenk 13:45:14 #topic Other Topics 13:45:23 anything else to bring up today? 13:45:50 going once... 13:46:05 twice.. 13:46:16 gone 13:46:22 thanks everyone 13:46:25 #endmeeting