16:01:13 #startmeeting ironic_neutron 16:01:13 Meeting started Mon Oct 12 16:01:13 2015 UTC and is due to finish in 60 minutes. The chair is Sukhdev_. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:17 The meeting name has been set to 'ironic_neutron' 16:01:39 Good morning 16:01:46 #topic: Agenda 16:01:51 #link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_October_12.2C_2015 16:02:05 anybody would like to add anything to agenda? 16:02:26 #topic: Announcements 16:02:43 I really do not have any announcements - does anybody? 16:03:16 I believe Liberty is out - RC2 was out last week 16:03:36 liberty final is out later this week, actually :) 16:03:59 jroll: thanks for clarification 16:04:31 any body has any announcement before we dive in... 16:05:02 #topic: Integration Status 16:05:23 I updated etherpad with the findings of the integration testing. 16:05:36 * lazy_prince looks 16:05:49 We have been very active in identifying the issues and fixing them 16:06:29 I had noticed a weird behavior - 16:06:57 I have verified 12 works but need others to confirm.. 16:06:58 if I use private network (default generated by devstack) as tenant network 16:07:20 then BM will boot fine all the way - all the network flip, cleanup, etc. was all working fine 16:07:46 Sukhdev: you didnt change other devstack scripts ? 16:07:49 but, if I create a new tenant network and use it - then BM instance will not boot and will fail 16:08:02 selva_: no 16:08:18 Sukhdev:thanks for the information 16:08:43 during my discussion with lazy_prince, he realized that DHCP was not being set correctly for provisioning network and perhaps that was causing the issue 16:09:13 lazy_prince has pushed the updated patch - I have not had time to test it to verify. 16:09:14 Sukhdev_: thats kind of due to bug 12, which should be fixed now... but needs to be confirmed by others.. 16:09:14 bug 12 in Launchpad itself ""Next 10 messages" changes Display Settings" [Medium,Fix released] https://launchpad.net/bugs/12 - Assigned to Dafydd Harries (daf) 16:10:00 Sukhdev:Ashish has verified today it is working fine 16:10:00 I meant no. 12 bug on etherpad.. :) 16:10:01 lazy_prince: this will be my priority to test it today - will report back 16:10:11 extra_dhcp_opts value population for the port attributes 16:10:16 selva_: cool - thanks for update 16:10:53 So now that things are working and something is in place, i urge that we start addressing review comments from ironic/neutron cores.. 16:10:58 from what I could see, this was the last standing issue that has been bugging me 16:11:46 lazy_prince: I agree - I will start to bug jroll and devananda once I have verified this fix later today 16:12:14 we should start to clean these patches (to address any comments) and push for merges 16:12:30 well.. thats for comments to come.. but we already have some some comments that needs to be addressed/responded... 16:13:07 I'll also be putting up a nova blueprint (spec?) later this week, sorry I didn't get to that last week 16:13:52 yes I still have not uploaded ironic-inspector code & blueprint 16:14:00 jroll: oh cool - I was thinking about doing it - this saves me one less thing to do :-):-) 16:14:24 Sukhdev_: yeah, I'll take care of it - hoping to get something solid I can chat with nova people about during the summit 16:15:00 this patch - https://review.openstack.org/#/c/206163 has been bugging me 16:15:37 We need new owner for this to clean it up - this is a nova patch and I am ignoring it so far 16:16:08 Sukhdev_: yeah, so I think we need to collect our thoughts better on the nova changes we need/want to make 16:16:21 I'm hoping this blueprint/spec will clarify stuff 16:17:43 jroll: also, while nova is on your mind, this patch needs a small fix as well - https://review.openstack.org/#/c/194413 16:18:21 Sukhdev_: right, we need to clean up / consolidate things 16:18:23 This is a problematic as well, I have been working around it to get the testing going - please see my comment on it 16:19:17 Sukhdev_: I don't know if it's worth updating these patches until we lay out exactly what we need 16:19:40 and get consensus on the 'how' 16:19:51 +1 16:20:07 jroll: I am confused - I thought we spec'ed it out 16:20:11 this is actually a very complex thing 16:20:17 I think, we should wait for the nova spec/bp to get approved 16:20:22 Sukhdev_: all we really said was 'the nova driver will need some updates' 16:20:32 but we never got into the guts of the neutron api stuff in nova 16:20:41 jroll: Oh I see, you mean nova fixes - right 16:20:47 yeah 16:20:48 it would be nice to be part of those discussions as I only came on board after this code was written and I've basically been doing archaeology 16:21:11 the ironic drivers we should be trying to get the code / integration testing working and landed 16:21:13 yhvh :-) 16:21:34 I think while we're waiting for reviews on ironic code, someone should be working on setting up a jenkins job for this 16:21:34 yhvh: welcome to world of software development :-) 16:21:43 :P 16:23:16 is there anyone from infra team.. 16:23:29 who can help us with jenkin jobs.. 16:23:53 I'm not sure 16:23:54 what is needed? 16:24:02 there's some ironic folks that have worked on them before 16:24:05 myself included 16:24:27 Sukhdev_: a tempest job that uses this feature. 16:24:53 jroll: this would mean we need a tempest test for this, right? 16:25:36 Sukhdev_: basically run our existing tests with the proper configs/setup in devstack to use this feature 16:26:22 jroll: Oh I see - lazy_prince had done something in that regard, if my memory serves me right... 16:26:52 if we have the ovs mech drivers for baremetal, I can get it working in devstack... 16:27:19 basically, here's how it will go... change devstack code such that some localrc things will trigger the configs and setup. then change devstack-gate and/or project-config to set that up properly 16:27:59 yeah.. but we need to simulate these ops with VMs right.. 16:28:03 lazy_prince: yeah, that's what I'm not sure about. as long as the ovs mech driver accepts the params (even if it ignores them) we should be able to start 16:28:33 we probably don't need to simulate the switchport stuff for the first version 16:28:52 lazy_prince: I do not believe we need ovs mech driver - as long l2 agent is running, we should be OK 16:29:41 so for a tenant network, the packets will be tagged by neutron.. 16:29:53 and the vm should see it untagged.. 16:30:04 also the tags will be updated by who..? 16:30:30 we don't need to worry about that part yet, right? 16:30:30 My assumption was that these things are done by mech drivers.. 16:30:46 the main thing I want from this gate test is to make sure all the logic works ok, things can deploy etc 16:31:13 means, just setup, but no provisioning..? 16:31:23 no, also provisioning... 16:31:42 but we can start with just using two separate neutron networks, I think 16:31:55 yeah.. but for provisioning, the VM should be connected to correct vlan network.. 16:32:14 ohh.. you mean non vlan setup..? 16:32:37 right 16:32:37 sorry, if i sound dumb.. just trying to understand.. 16:32:40 no you're fine 16:33:08 let's get an experimental job running that sets up and uses two different networks... and uses the neutron provider for the nodes 16:33:09 umm. That could be done... 16:33:17 and we can make that better as we go 16:33:31 jroll: +1 16:33:58 okay.. will start looking into it... 16:34:46 lazy_prince: thanks 16:34:50 So we will have to update the devstack with the script changes to have neutron_plugin enabled... 16:35:00 right, that's the first step 16:35:01 and then comes the ci.. 16:35:08 that's helpful anyhow for others to be able to test 16:35:12 I mean jenkins job.. 16:35:17 I can help with the CI stuff, I've done that a bunch of times 16:35:40 cool.. will let you know once the ds it updated.. 16:35:49 jroll: cool - thanks 16:35:51 awesome, thanks! 16:36:13 this discussion is sounding better and better - I love it :-) 16:36:54 yeah, we're getting there :) 16:37:04 one last thing on the integration front - 16:37:18 yhvh: any updated on item 9 and 10 on the etherpad? 16:37:40 I saw updated patches earlier this morning and late last night - 16:37:56 not yet, last week got swallowed by linuxcon and recruitment 16:38:06 I'll dig in today 16:38:27 yhvh: cool - thanks 16:38:59 this wraps this topic for me - anybody has any questions/comments? 16:39:25 OK - moving on... 16:39:32 #topic: Documentation 16:40:04 I saw cragusa pushed updated patch for documentation - https://review.openstack.org/#/c/228496/2/doc/source/deploy/install-guide.rst 16:40:14 yes 16:40:23 addressed the comments 16:40:37 I realized that I had goofed up on my comments - I had added the comments on 2nd version of the patch 16:40:52 so one thing missing from it is the details about provisioning network and its requirements.. 16:41:02 but, for some odd reason, they were still sitting in my draft and never got pushed - so, pushed them this morning 16:42:44 lazy_prince: In my comments (old now :-)) I tried to touch on the provisioning network as well - perhaps not in that much details as you are looking for 16:42:47 like routing etc... and the configuration in ironic.conf filr 16:43:15 * lazy_prince looks 16:43:54 Sukhdev_: kind of... 16:44:06 lazy_prince: see my comment, perhaps you can add to it 16:44:42 lets all help out to get this cleaned up so that it is very clear and user-friendly for the operators as well developers 16:44:57 Well, I guess, we need to split it in to parts.. like config stuff, and then node reg, and verification etc.. 16:45:24 and yes, we will need some kind of troubleshooting section too.. I guess.. 16:46:27 Sukhdev_: I just seeing your comments now, I'll address them 16:46:31 lazy_prince: all of these are good ideas - please add comments to the spec - so that cragusa can incorporate appropriately 16:47:06 cragusa: sorry for my goof up - I wrote them long time ago - for some reason did not get pushed :-( 16:47:44 I could have pushed an update to it.. but then I am getting held up in many things.. 16:48:41 so this was ironic doc.. any update on the neutron mech driver related doc for baremetal..? 16:49:53 Sukhdev_: ^^ 16:49:58 lazy_prince: I am suppose to work on the neutron/ML2 side - I will try to get to it as soon as I have things in a more of working state 16:50:13 It seems we are almost there - 16:50:32 I will have it pushed before the summit - 16:51:03 As in the presentation (at summit), I want to have links to both documents Ironic as well neutron 16:51:41 Anything else on documentation? 16:52:02 Please keep your ideas flowing... 16:52:13 #topic Open Discussion 16:52:27 any plans to update the specs as per the deviations..? 16:52:43 or regressions..? 16:52:51 lazy_prince: good point - yes, we should - 16:53:05 lazy_prince: I will do it - unless somebody beats me to it 16:53:46 lazy_prince: I am working with order of importance - highest priority being - get the end-to-end testing going 16:54:16 Which is in good shape now.. 16:54:17 once we have things working, then will dive into completing the documents, specs, etc.... 16:54:43 lazy_prince: I will let you know later tonight 16:55:05 Well.. selva_ has verified it.. I believe.. 16:55:50 sounds good - hopefully, will work for me as well 16:55:52 oh, one quick side note: 16:56:16 there's an email on the list asking about supported switches/ML2 things from the neutron side 16:56:19 http://lists.openstack.org/pipermail/openstack-dev/2015-October/076755.html 16:56:43 you vendor folks may be interested in replying to that 16:57:35 jroll: cool - thanks. I will reply to it - lazy_prince and selva_ you should too 16:58:32 sure... 16:58:58 it is too early though - the code is not merged in Liberty - he is looking at Liberty - 16:59:13 I will reply and clarify it for him and set the expectations correctly 16:59:17 right, I clarified that in my reply already 16:59:42 So does it make sense to have a wiki with such supported device by ironic..? 17:00:12 idk, it's a neutron thing IMO 17:00:21 lazy_prince: good point - we are out of time - I will add to the agenda for next week's meeting 17:00:31 and we can debate about it in more details 17:00:40 cool 17:00:41 Thanks folks 17:00:41 cool... c ya next week.. 17:00:42 thanks all :) 17:00:46 #endmeeting