16:01:23 #startmeeting ironic_neutron 16:01:24 Meeting started Mon Mar 21 16:01:23 2016 UTC and is due to finish in 60 minutes. The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:28 The meeting name has been set to 'ironic_neutron' 16:01:43 sambetts: You beat me to it - :-) 16:01:51 o/ 16:01:54 o/ 16:01:57 0/ 16:02:01 Sukhdev: :) 16:02:10 #topic: Agenda 16:02:16 #link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_March_21.2C_2016 16:02:37 #topic: Announcements 16:02:53 Mitaka is around the corner 16:03:30 We should have a short meeting this morning - hopefully 16:03:42 Any body has any announcements? 16:04:03 jroll : are you going to join us today? 16:04:10 morning :) 16:04:21 #topic: Patches for April push 16:04:43 I took a crack at listing the critical patches needed for push in April 16:04:52 I came up with 4 16:05:04 let me post them here 16:05:21 #link https://review.openstack.org/#/c/285852/ 16:05:36 #link: https://review.openstack.org/#/c/139687/ 16:05:52 #link: https://review.openstack.org/#/c/206244/ 16:06:00 #link: https://review.openstack.org/#/c/206144 16:06:10 Can anybody think of any other one? 16:06:16 so 139687 should probably be abandoned in favor of 285852 16:06:22 it's meant to replace it 16:06:41 other than that I mostly agree 16:07:03 I would also like to get CI running on this before releasing it (which will require some additional patches to our devstack plugin etc) 16:07:09 and then we'll need to deal with nova as well 16:08:00 how about https://review.openstack.org/#/c/213262/ ? 16:08:01 yup - sorry - I missed the nova one 16:08:56 oh yes, that last one is also needed 16:09:57 My bad - of the 4 I listed I meant this one and not 139687 16:10:20 hshiina jroll : thanks for correcting me 16:10:28 cool 16:10:34 Sukhdev, you're welcome 16:10:55 So these 4 patches are reasonably well tested 16:11:18 jroll : I have not been paying attention to the CI side 16:11:35 devstack patches also look good 16:11:37 Sukhdev: it's in progress, the devstack changes look good 16:11:40 I tested the earlier version 16:11:55 vsaienko is pushing on getting the job in the experimental queue 16:12:05 and there's tempest changes up that look sane 16:12:46 I have not tested tempest patch - has anybody tested it? 16:13:40 no, I'd like the CI job to do that for me :) 16:14:01 jroll : ha ha real engineers believe in God :-) 16:14:25 once the job exists it will be easy to test 16:15:26 Anything else on these patches? 16:16:42 sambetts : I was going to skip through the rest of agenda - unless you want to discuss about VLAN aware BMs? 16:18:20 sambetts: ? 16:18:48 Sukhdev: Not sure if there is much change, I believe we just wanted to highlight that we've got prototypes up for the port mapping and multi-vlan 16:19:34 sambetts : Is this in conjunction with the work being done in neutron and nova? 16:20:30 Sukhdev: you mean in parallel to VLAN aware VMs..? 16:20:40 lazy_prince : yes 16:21:09 Sukhdev: simply put no, it just uses neutron ports not trunk ports etc 16:21:10 actually - in unison with 16:21:30 I think it has to be.. otherwise they will conflict and end up rework in Ironic later.. 16:21:43 lazy_prince : +1 16:22:05 sambetts : so, is this a short term hack then 16:23:00 sambetts : the correct model (based upon my preliminary understanding) is that for the access port - we will do port_create() 16:23:36 and for subsequent ports - for tagged vlans, we will do something equivalent of sub-port create 16:24:03 so, I agree with lazy_prince that this will have to be changed later 16:24:37 Sukhdev: Yes, I need to update the spec and the prototype for multivlan to use those new structures 16:25:28 so does it mean it will be aligned with VLAN aware VMs and is not a hack except portgroups..? 16:25:31 sambetts : It is my understanding that the work has already commenced in the neutron - my suggestion will be to coordinate with the author 16:26:18 lazy_prince: I have the current prototype working with some minor changes in the ml2 plugin 16:26:35 lazy_prince: without merging with the vlan aware vms 16:26:37 works 16:26:52 yeah.. neutron is implementing it as a service and no hacks in ML2.. 16:27:44 lazy_prince : correct - there may be some mods to the ml2 drivers - but, I have not assessed the impact yet 16:28:25 Sukhdev: not sure how it will affect the local_link_information we send either, if at all 16:28:26 sambetts : so should we hold of reviewing your patches for now? 16:28:55 let's stick to the spec for now, with the code as reference 16:29:04 Sukhdev: The specs need the eyes, the patches are more there for reference for the spec 16:29:05 we'll almost certainly chat about this in austin 16:29:07 if we hold, it will be held up till octa.. not the right thing.. 16:29:25 sambetts: I like it when we agree :) 16:30:00 sambetts : it will not impact the local_link_information -just the change in the api - i.e. create port vs create sub-port 16:30:11 fine with reworking later... but not fine with blocking dev.. 16:30:14 Sukhdev, jroll, lazy_prince: I'd appreciate any comments for the port-mapping spec. 16:30:27 baoli_: I don't know what that is 16:30:50 baoli_: do you have a url..? 16:30:52 sambetts : In ML2 driver, we need to plumb either access ports or tagged ports on the switch 16:30:58 jroll: I put the link to the spec on the meeting topic. 16:31:26 https://review.openstack.org/#/c/279148/ 16:31:45 baoli_: thanks 16:32:02 Sukhdev: Yes, the ml2 drivers should already support that if they trunk vlans down to their compute hosts 16:32:09 * lazy_prince will review soon.. 16:32:26 baoli_: okay, seems like something on top of sambetts vlan aware BM spec 16:32:37 (... maybe) 16:32:53 baoli_ : I looked at the patch - but, held off from any comments until we finalize sambetts's spec/patches 16:33:38 Sukhdev: thanks for looking at the patches. 16:34:33 sambetts : correct - ML2 drivers already support trunk vlans, but, now they will have to pick which way to plumb for the main port vs. sub-ports 16:35:25 sambetts: some of the nuts and bolts are already there, may have to add some logic to act correctly upon the type of resource which is used - i..e main port vs. sub-port 16:35:25 Sukhdev: Yeah, the BM case is a little weird because we aren't running an agent 16:36:41 sambetts : So, I held off from posting any review comments on your patch(s) pending review from the neutron side first 16:37:10 sambetts: agent as in guest image..? 16:37:30 lazy_prince: No, agent as in neutron agent 16:37:36 FWIW, I'm going to propose a neutron/nova/ironic session in austin to try to work a bunch of these interactions 16:37:44 so we can get all of the eyes on this 16:37:50 sambetts: thats on mech driver implementation.. right.. 16:38:07 jroll : excellent idea 16:38:12 +1 16:38:27 jroll : the way we did in Vancover 16:38:31 lazy_prince: in a compute host you have a neutron agent that does half the work and the switch part that does half the work, in the BM senario the switch part does it all 16:39:00 Sukhdev: hopefully with more people participating and less people taking up chairs just to listen 16:39:13 jroll :) 16:39:25 :-) 16:39:52 jroll : let me know I will be happy to coordinate from the neutron side 16:39:55 Having a 3 way (nova, neutron, ironic) cross project would be great, 16:40:20 we will need Sukhdev for sure.. 16:40:27 Sukhdev: I'm going to tackle the PTLs directly and make them do it :P 16:41:02 jroll : ha ha - good luck :-) 16:41:30 jroll : the question is one session vs. multiple 16:41:52 I would suggest we host one session and pull the right people into it 16:42:06 ++ 16:42:31 Sukhdev: yeah, that's my plan 16:42:39 a session like the nova ironic one in tokyo would be good 16:42:58 jroll : the work is already in progress - we essentially need to pull all the relevant people in the room so that everybody knows who is who and that way we can coordinate the work 16:42:58 I will let y'all know how it goes 16:43:29 Sukhdev: well, I'm not sure neutron or nova folks are very aware of it - and I want to make sure what we're doing is sane on their side 16:43:47 I'm talking about the stuff going forward, to be clear, not the things currently in flight 16:44:52 jroll : do not know about the nova side, but, in neutron it has gone through lots of discussion and review process 16:45:18 Sukhdev: the vlan aware baremetal spec has? 16:45:31 not baremetal - VMs only 16:45:57 jroll: https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms 16:45:58 right, I want eyes on the baremetal part 16:46:33 jroll : I have been keeping eye on it to make sure that it will work for us for baremetals- 16:47:13 Sukhdev: cool, I still want some neutron cores to say this spec isn't insane :) 16:47:31 vlan aware vms got bumped to Newton too looking at the comments from armax 16:47:34 jroll: sure - agree 1000% 16:47:46 \o/ 16:48:39 Anything else on this? 16:49:22 Nothing from me 16:49:38 #topic: Open Discussion 16:50:19 Folks, for a personal reason, I may be traveling out of country next Monday - 16:50:43 I may not be able to run this meeting next week 16:50:53 can somebody else do it ? 16:50:59 Or we can skip next week 16:51:43 thoughts? 16:51:45 let's go ahead and skip it, it's release week :) 16:51:49 (imo) 16:51:55 +1 for skip... 16:52:33 sounds good - I will update the agenda on the wiki 16:52:33 Sure :) 16:52:52 we have 8 min - anything else? 16:53:12 looks like we are done 16:53:18 thanks for attending 16:53:21 bye 16:53:23 o/ 16:53:28 #endmeeting