09:32:12 #startmeeting XenAPI 09:32:13 Meeting started Wed Nov 2 09:32:12 2016 UTC and is due to finish in 60 minutes. The chair is BobBall. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:32:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:32:16 The meeting name has been set to 'xenapi' 09:32:29 Good morning/afternoon everyone 09:32:45 johnthetubaguy pingity ping? 09:32:56 Good morning BobBall. 09:33:28 #topic Blueprints / specs 09:33:38 Hello all 09:33:46 So - jianghuaw - can we have an update for your two specs from the discussions at the summit? 09:34:37 yes. For "generalizing PCI devices", the cores agreed that's a long term direction but don't think it should be in Ocata. 09:35:47 as the PCI refactoring as resource object is still in progress. 09:35:54 Is there any pre-work needed that's happening in ocata? 09:36:03 IS that expected to finish in Ocata or not? 09:36:35 Per Jay's input, PCI refactorying should be done in Ocata. 09:37:01 after that, it should be suitable for "generalizing PCI" going to P. 09:37:11 I see. 09:37:34 And you mentioned yet another different proposal for vgpu? 09:38:03 For seeking support VGPU, Jay suggested to use the custom resource class for VGPU. 09:38:50 That sounds full circle back to what we proposed in Liberty which is what Dan was not in favour of? 09:38:58 define single VGPU types in the section of [placement] in nova's configure file. 09:40:51 in liberty, we proposed to create a top resource for VGPU. and also rejected by Jay IIRC. 09:42:14 ok perhaps I don't understand the difference between those two? 09:42:19 But it seems it's determined to support custom resource classes. 09:42:44 it seems there is plan to support FPGA with custom resource type also. 09:42:58 I see 09:43:55 In liberty, the refactoring for resource pool is at the early phase. 09:44:33 and there is no concept of the custom resource class. All resources are defined as top resources. 09:45:03 Understood 09:45:14 so for vgpu we need to rewrite the spec to work on custom resource types 09:45:23 vGPU attempt #4 09:45:49 Unfortunately it seems yes. 09:46:25 OK - any other updates from the summit? 09:47:15 the nova-network will be removed from ocata, so we should think to remove our nova network CI accordinly? 09:47:59 Deprecated or removed? 09:48:21 deprecated iirc 09:48:24 Typically we remove after a cycle of deprecation 09:48:32 so nova network may continue to work for Ocata I think? 09:48:40 or yes. 09:48:50 We should probably continue testing until Infra remove their nova network CI 09:48:58 Once that's gone, then yes, let's disable ours. 09:49:05 fair enough. 09:49:33 OK - any more for any more? 09:50:25 https://etherpad.openstack.org/p/ocata-nova-neutron-session 09:50:35 For some reason my compute keeps locking up - I may disappear unexpected. 09:50:36 this link gaves plan on nova-network 09:51:15 * johnthetubaguy wonders in very late and hides at the back 09:51:19 "we can't drop nova-network until cellsv2 is available for upgrading from cellsv1" 09:51:45 Ah - ok 09:51:52 yeah, we have just put a patch to stop nova-network starting, unless you are using cells v1 09:51:54 so we should keep our nova-network CI for the forseable future :D 09:52:06 oh right maybe not 09:52:22 because our CI isn't using cells (unless it's devstack default?) 09:52:40 Got a link to the patch johnthetubaguy ? Just worth us looking to see if it does stop our CI working 09:55:14 just digging it up 09:55:32 https://review.openstack.org/#/c/392236/ 09:55:53 If it stops nova-network starting, it surely will break our CI once that patch got merged. 09:56:02 awesome - yes - it does break our nova-network CI 09:56:06 yeah, we have a -ve vote from lots of CI on there 09:56:13 which is expected 09:56:34 So we should just double check that the failure is due to nova network being disabled 09:56:46 and if it is, let's stop nova-network from voting 09:56:52 then we can remove it entirely once this patch has merged. 09:57:05 http://dd6b71949550285df7dc-dda4e480e005aaa13ec303551d2d8155.r49.cf1.rackcdn.com/36/392236/2/check/dsvm-tempest-nova-network/11cfd32/logs/screen-n-net.txt.gz 09:57:08 awesome 09:57:38 That'll free up some CI resources for the fun new test that huazhihao is working on :) 09:57:51 Indeed 09:58:15 awesome. 09:58:23 OK 09:58:26 Rapidly running out of time 09:58:29 #topic AOB 09:58:32 Let's skip to AOB 09:58:37 Anything else we should cover today? 09:58:39 For this spec, generally I think we've got agreement. But we need some cores help to review and approve it before the spec freezing date. 09:58:40 Link: https://review.openstack.org/#/c/379279/ 09:59:09 Ah yes - your review on the os-xenapi spec would be appreciated johnthetubaguy :) 09:59:24 yeah, there was that wording to iron out, looks like thats done now :) 09:59:36 Hope you can help review my vif hotplug patch, maybe we can discuss it next time https://review.openstack.org/#/c/365505/, thanks:) 09:59:40 We have the library created and are committing code to it 09:59:56 oh, whats the formatting on line 19 about? 09:59:58 so first release of the library shouldn't be too far away at which point we can do the Nova changes. 10:00:08 https://review.openstack.org/#/c/379279/3/specs/ocata/approved/add-os-xenapi-library.rst@19 10:00:28 looks like a merge or cut and paste error I guess? 10:00:34 Looks like a newline was added in the wrong place 10:00:37 look at the changes from 2-3 10:00:53 added a newline rather than deleting part of the formatting 10:00:54 indeed, will revise it. thanks. 10:01:14 cool 10:01:28 ping me when thats ready in the main channel 10:01:46 +1 10:01:48 Awesome 10:02:06 So johnthetubaguy - did you spot the query about reviewing the vif hotplug patch? 10:02:30 not yet 10:02:36 09:59 < huanxie> Hope you can help review my vif hotplug patch, maybe we can discuss it next time https://review.openstack.org/#/c/365505/, thanks:) 10:02:41 I didn't mean did you review it :) 10:04:12 huanxie: I made you the assignee on the blueprint, so that should help you edit it, if needed. 10:04:34 johnthetubaguy, Thanks 10:04:43 will try take a peak 10:04:48 Perfect. 10:04:49 would be good to get that added 10:04:51 Any more for any more? 10:04:59 especially now neutron is... more important 10:05:02 :D 10:05:11 new patch upload 10:05:12 Let's close there then. 10:05:14 uploaded. 10:05:14 Thanks everyone. 10:05:18 #closemeeting 10:05:18 thanks. 10:05:20 Thanks all:) 10:05:21 #endmeeting