17:08:42 #startmeeting XenAPI 17:08:43 Meeting started Wed Jan 30 17:08:42 2013 UTC. The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:08:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:08:46 The meeting name has been set to 'xenapi' 17:09:06 so did people like the format last week? please +1 or -1 17:09:50 the meeting format? 17:09:55 by which I mean should we use the formal agenda, or just raise questions at the start? 17:10:04 yes, sorry I meant meeting format 17:10:20 +1 17:10:23 for formal agenda 17:11:13 +1 17:11:42 OK, well didn't get any email about adding things to the agenda 17:11:48 please to add to the wiki page 17:11:55 #link http://wiki.openstack.org/Meetings/XenAPI 17:12:03 for future meetings :-) 17:12:11 I will try email the request next time 17:12:14 Ok... 17:12:25 #topic Actions from last meeting 17:12:43 the only action was for me 17:12:58 I looked into the python situation in Dom0 17:13:01 The swift client, right? 17:13:03 just to report back... 17:13:17 installing EPEL breaks yum a little bit 17:13:27 but installing python 2.6 from EPEL is fine 17:13:35 they are independent issues really 17:13:52 speaking to some XenServer/XCP folks that is as expected 17:14:00 I got a clean install of the swift client 17:14:09 I think your notes on it are good 17:14:24 thanks, I should add that link... 17:14:49 #link http://wiki.openstack.org/XenServer/PostInstall 17:14:54 its documented above 17:14:57 cool 17:15:06 questions? 17:15:14 more a comment 17:15:18 sure 17:15:33 we haven't had a chance to try it out in our enviornments, but DO plan to pursue that path longer-term 17:15:48 cool, sounds good 17:15:58 it seems like the right way to go about doing it, but we've got to see how it works at scale, etc, etc :) 17:16:04 drop me a line if you have issues 17:16:07 totally 17:16:13 john, did you tried to use the swift client, or just did the installation? 17:16:39 matelakat: it seemed to work, but I honestly didn't try it out too much 17:16:42 i also want to ping our xenserver guy (who is out right now) to see what (if any) concerns he has for our environment 17:16:57 cool 17:17:07 more to follow! that's all for now from us 17:17:14 johnthetubaguy: ok 17:17:16 #topic blueprints 17:17:21 johnthetubaguy: thanks for your help so far 17:17:33 not got anything myself, anyone got anything they want to raise 17:17:46 I have a sort of draft stuff. 17:17:55 I was planning on having another XenAPI session at the summit, or at least submitting one 17:18:08 so at some point we can thinking about Havana stuff 17:18:15 but that's more about a review, not really the blueprint itself. 17:18:23 anything people have hanging for Grizzly? 17:18:33 matelakat: OK feel free to post a link 17:18:37 #link https://blueprints.launchpad.net/cinder/+spec/xenapinfs-glance-integration 17:19:04 this is the bp, and the change is: #link https://review.openstack.org/20790 17:19:38 awesome, this is the integration between XenAPI, Cinder and the NFS SR 17:19:41 cool stuff 17:19:46 OK anything else? 17:19:56 So if you guys have any comments on that, comment on that. 17:20:17 no 17:20:24 #topic docs 17:20:42 lots have lovely features have dropped, are we all OK getting some docs in? 17:21:30 there is a nice getting started guide #link http://wiki.openstack.org/Documentation/HowTo 17:21:39 and the reviewers have always been very kind to me! 17:22:35 ... silence ... we probably need someone to take this on 17:22:52 #action advertise to get more help for XenAPI docs 17:22:59 #topic QA 17:23:10 Any pressing bugs, or reviews, or issues this week? 17:23:30 I am looking at the devstack readme at the moment, and try to add some comments to it, to make it easier to get started with devstac/XS 17:23:39 sounds good 17:24:42 #topic AOB 17:24:50 #topic Open Discussion 17:25:03 OK so any other questions from people? 17:25:56 I assume people are OK with this time next week 17:26:13 feel free to edit the wiki to add any topics you have #link http://wiki.openstack.org/Meetings/XenAPI 17:27:34 Ok, so there are some things we have 17:27:44 XenAPI lib into Oslo 17:27:52 to share between nova and cinder 17:27:57 what do people think? 17:29:13 ?? 17:29:22 So the lib, that would be pulled up, is a sort of xenapi interface, right? 17:29:23 I am +1 for the idea 17:29:31 At the moment looking at the cinder stuff. 17:29:40 Let's look at the code, give me a sec.. 17:29:49 yes, a layer on top of the very low level XenAPI python driver 17:30:05 to share code between Cinder and Nova talking to XenAPI 17:30:11 #link ttps://github.com/openstack/cinder/blob/master/cinder/volume/drivers/xenapi/lib.py 17:30:16 #link https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/xenapi/lib.py 17:30:34 This is the candidate - at least from my side. 17:30:43 But I wouldn't pull up the whole to oslo. 17:30:52 At the same time, we were thinking about tidying up the exception handling 17:31:43 XenAPI exceptions tend to pop out, and calling code needs to translate the codes, where as that should probably be part of that shared code, so calling code doesn't need to keep catching exceptions 17:31:50 should be easier to test that way 17:32:18 So, we should probably raise this at the summit so it gets more attention 17:32:35 And/or just submit things to Oslo for review 17:32:53 OK, any more comments or questions? 17:33:07 or random XenServer questions? 17:33:09 How could we pull things up to oslo, I mean what is the procedure? 17:33:41 #link http://wiki.openstack.org/Oslo 17:34:49 OK, so I think we are done for this week 17:34:51 thanks all 17:34:57 thanks, bye 17:35:03 same time next week 17:35:21 #endmeeting