09:31:44 <BobBall> #startmeeting XenAPI 09:31:45 <openstack> Meeting started Wed Aug 5 09:31:44 2015 UTC and is due to finish in 60 minutes. The chair is BobBall. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:31:46 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:31:48 <openstack> The meeting name has been set to 'xenapi' 09:31:56 <BobBall> Morning johnthetubaguy 09:32:08 <johnthetubaguy> hello 09:32:31 <BobBall> We can also say good morning to jianghuaw 09:32:48 <BobBall> And is John or Huan also here? 09:33:00 <jianghuaw> hello 09:33:20 <BobBall> Agenda at https://wiki.openstack.org/wiki/Meetings/XenAPI as usual 09:33:36 <BobBall> #topic Blueprints / Reviews 09:33:46 <BobBall> OK - so - johnthetubaguy the first is a question for you really 09:33:53 <BobBall> Welcome huazhihao 09:34:04 <huazhihao> :bobball Thank you. 09:34:11 <BobBall> We've found there are some bugs running XenAPI in a HVM guest 09:34:16 <BobBall> and lots of people are trying to do this 09:34:44 <huazhihao> Yes 09:34:45 <BobBall> We need to fix those - do we have to raise a BP or are these justifiable as bugs or 'features without BPs' since it's very clear what we're trying to do? 09:35:37 <BobBall> huazhihao / jianghuaw is Huan joining us? 09:36:13 <BobBall> johnthetubaguy: What are your thoughts on that? 09:36:26 <BobBall> johnthetubaguy: (the BP question - not Huan :) ) 09:36:36 <johnthetubaguy> sounds like a bug fix 09:36:44 <BobBall> OK, good. 09:36:57 <johnthetubaguy> it is bug triage day today, if that helps 09:37:00 <huazhihao> bobball: She is disconnected because of some unknown reasons. 09:37:07 <BobBall> Can I also introduce jianghuawwho is the second team member in Nanjing 09:37:26 <BobBall> Huan is the third team member but she's not online at the moment 09:38:05 <BobBall> huazhihao / jianghuaw: johnthetubaguy is the current Nova PTL, ex Citrix employee and one of the largest contributors to the XenAPI driver 09:38:34 <johnthetubaguy> cool, good to meet you all, welcome to Nova! 09:38:44 <BobBall> OK, well if we don't need a BP then I'm happy. We'll add some bugs + fix them as we get to them. 09:38:47 <BobBall> Already have one bug raised 09:38:55 <BobBall> Speaking of nova bug triage day... 09:38:58 <BobBall> #topic Bugs 09:38:59 <jianghuaw> hi johnthetubaguy 09:39:08 <BobBall> #link https://bugs.launchpad.net/nova/+bug/1204631 09:39:08 <openstack> Launchpad bug 1204631 in OpenStack Compute (nova) "Image created from boot from iso missing min_ram and min_disk" [Low,Confirmed] 09:39:08 <johnthetubaguy> the reviewers may think otherwise, but it feels like a bug fix to me 09:39:12 <BobBall> This bug is one that claims it may be fixed 09:39:18 <uvirtbot> Launchpad bug 1204631 in nova "Image created from boot from iso missing min_ram and min_disk" [Low,Confirmed] 09:39:19 <uvirtbot> Launchpad bug 1204631 in nova "Image created from boot from iso missing min_ram and min_disk" [Low,Confirmed] https://launchpad.net/bugs/1204631 09:39:21 <BobBall> I thought you might have some insight into whether you agree it's fixed 09:39:39 <BobBall> From looking at the code I suspect it has been fixed 09:39:45 <BobBall> so I'd be happy to just close it 09:39:55 <BobBall> but I know that RAX has been more involved in the boot from iso work 09:42:50 <BobBall> johnthetubaguy ? :) ping! 09:43:03 <johnthetubaguy> sorry, I am having lots of pings right now 09:43:32 <johnthetubaguy> I have no idea if thats fixed, we don't really use that feature much 09:43:45 <BobBall> I'll close it based on the code review then 09:43:56 <johnthetubaguy> OK 09:43:59 <BobBall> #topic Open Discussion 09:44:03 <johnthetubaguy> they can always reopen I guess 09:44:10 <BobBall> in stack.sh in devstack there are references to tty.gz 09:44:18 <BobBall> These are XenServer specific 09:44:25 <BobBall> but I have no idea what they are for or why they are there 09:44:29 <BobBall> Do you have any clue? 09:44:33 <johnthetubaguy> do you have a link? 09:44:45 <BobBall> They were added in the original commit to devstack by rackspace 09:45:19 <BobBall> 10:43 < johnthetubaguy> sorry, I am having lots of pings right now 09:45:19 <BobBall> 10:43 < johnthetubaguy> I have no idea if thats fixed, we don't really use that feature much 09:45:26 <BobBall> Sorry - wrong paste! 09:45:32 <BobBall> That was just from me clicking the screen out of habit 09:45:36 <BobBall> http://git.openstack.org/cgit/openstack-dev/devstack/tree/stack.sh#n1190 09:45:58 <BobBall> I have no idea what "UPLOAD_LEGACY_TTY" is for 09:46:19 <johnthetubaguy> isn't that the image file? 09:46:35 <BobBall> An image file for what though 09:46:44 <BobBall> We don't use it anywhere as far as I can tell 09:46:46 <johnthetubaguy> I thought for booting from 09:47:11 <BobBall> Yes - but why do we need a tty aki+ami image? 09:47:26 <BobBall> What's the purpose of the image in general 09:47:40 <johnthetubaguy> I think it was just the first one that was added, as the only image that worked 09:47:49 <johnthetubaguy> like the xenserver specific one 09:47:58 <BobBall> Ah ok 09:48:06 <BobBall> So we can remove it now we just use cirros? 09:48:20 <johnthetubaguy> I would have thought so 09:48:30 <BobBall> hi huanxie. johnthetubaguy - this is huan, the final team member in Nanjing 09:48:52 <BobBall> OK - I will raise a ticket to remove it then 09:48:56 <johnthetubaguy> huanxie, welcome to nova! 09:48:56 <BobBall> Next question... 09:48:56 <huanxie> hi 09:49:03 <BobBall> Separation of plugins 09:49:18 <BobBall> We have a vaguely useful plugin version identifier in nova now 09:49:33 <BobBall> How would you feel about separating the plugins from nova to a different repo on stackforge? 09:49:42 <johnthetubaguy> seems like a bad idea 09:49:55 <BobBall> The main reason I'd like to do this is to make a clear distinction for develpoment so we can rely on the plugin versioning information 09:49:57 <johnthetubaguy> they are required to run Nova, and basically Nova ocde 09:50:16 <johnthetubaguy> why not use the Nova versioning for the deployment? 09:50:46 <BobBall> You mean remocve the current plugin version? 09:50:50 <johnthetubaguy> no 09:51:00 <johnthetubaguy> just use the nova version for the deployment 09:51:25 <johnthetubaguy> the version is just an internal interface protection system really 09:51:43 <johnthetubaguy> we don't make nova-compute deploy using the manager RPC version right? 09:51:56 <BobBall> Right 09:52:08 <BobBall> Let me explain what I would ideally like 09:52:27 <BobBall> My ideal would be for Nova to install, over XenAPI, the correct version of the plugins 09:52:53 <BobBall> This would clearly need to work for dev versions, so the 'nova version' wouldn't cut it for that 09:53:07 <johnthetubaguy> the nova version has a dev version already 09:53:15 <johnthetubaguy> each commit has its own version, I believe 09:53:48 <BobBall> Uhhh how? If someone has downloaded the tgz (i.e. no git repository) then Nova can't know what its version is 09:53:51 <BobBall> can it? 09:54:01 <johnthetubaguy> not quite sure how that works 09:54:35 <BobBall> And I'm sure that using nova to query git would be rejected ;) 09:55:19 <BobBall> Is it worth raising a BP to discuss or are you dead set against separating the plugins out? 09:55:38 <johnthetubaguy> you could, it doesn't sound right to me 09:56:00 <BobBall> Ok - final topic. Sorry for taking so long huazhihao 09:56:05 <johnthetubaguy> we can add stuff to make packaging easier 09:56:07 <BobBall> #topic Mirantis Plugin 09:56:17 <BobBall> Can you give us a brief update on what's working with the fuel plugin 09:56:22 <BobBall> and what the next steps are? 09:56:54 <huazhihao> SUre 09:56:58 <huazhihao> Sorry 09:57:45 <huazhihao> The automation has covered most of tasks 09:58:17 <BobBall> Great - btw johnthetubaguy - next meeting we hope to have an update on Neutron integration (not a working solution, just something to discuss!) 09:58:44 <johnthetubaguy> OK, cool 09:58:52 <johnthetubaguy> have you reached out to the rackspace folks about that? 09:59:24 <BobBall> Yes - at the last summit 09:59:33 <johnthetubaguy> who did you talk to? 09:59:48 <BobBall> Long story short, we can't use quark in the short term so will be focusing on ml2+ovs 10:00:01 <BobBall> Some of the quark devs + andy hill 10:01:00 <johnthetubaguy> OK, we should probably catch up about they why at some point, but snowed under right now 10:01:20 <BobBall> so huazhihao - the update I guess is that we have a workable user interface story and a plugin that will install; now we're focused on automating the xenserver customisation in the post-install tasks 10:01:24 <BobBall> is that right? 10:01:38 <huazhihao> Exactly 10:01:59 <huazhihao> Sorry my typing is slow. 10:02:06 <johnthetubaguy> OK 10:02:18 <johnthetubaguy> not sure what you mean by user interface story, but I guess thats for next time 10:02:21 <BobBall> Sure johnthetubaguy - short version is that there is a bunch of stuff that quark depends on in udev rules etc that are not open source and are highly custom to rackspace's environment. We might want to get those open + updated to work in other environments too. 10:02:47 <BobBall> The other issue is that Mirantis OpenStack already has good supprot for ml2+OVS so it's a lot easier to integrate with that point 10:02:48 <johnthetubaguy> yeah, that was my thinking, no reason for those to be closed 10:03:03 <johnthetubaguy> if it works, and is easier, thats cool 10:03:07 <BobBall> User interface story = it looks good :) 10:03:13 <BobBall> Anyway, we're 3 minutes over now 10:03:21 <BobBall> so we'll end the meeting here. 10:03:23 <BobBall> #endmeeting