09:00:23 #startmeeting nova-net-to-neutron-migration 09:00:24 Meeting started Tue Mar 10 09:00:23 2015 UTC and is due to finish in 60 minutes. The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:27 The meeting name has been set to 'nova_net_to_neutron_migration' 09:00:30 hello 09:01:02 obondarev mikal gus 09:01:16 o/ 09:02:07 anteaya:hi, how are you? 09:02:18 obondarev: good thanks 09:02:21 and yourself? 09:02:39 me too, thank you :) 09:02:43 good 09:03:03 might just be you and I 09:03:18 mikal had told me he expected to be here for this meeting 09:03:19 looks so 09:03:29 perhaps he will be here before the end 09:03:32 so onward 09:03:42 #topic the state of the Neutron spec (obondarev) 09:03:48 anything new? 09:03:53 nope 09:04:01 next then 09:04:09 ok 09:04:16 #topic the state of implementation (obondarev) 09:04:30 no changes on db patch which is expected as jlibosva is unavailable till April 09:04:39 as we agreed, the patch is ready for testing 09:04:46 great 09:04:49 I put a comment on the patch with the steps which allowed me to migrate data for FlatDHCP model 09:04:52 (hi) 09:05:36 nova-net proxy patch is ready for testing as well, except floating ips and security groups 09:05:53 #link https://review.openstack.org/#/c/150490/ 09:05:56 obondarev: I saw that, that was a nice amount of detail. 09:06:11 so in fact the two patches may be tested together: migrating data first and enabling proxy mode on nova-api and nova-compute 09:06:20 okay 09:06:26 so nice work 09:06:29 I post a comment on the proxy patch with the steps for testing as well 09:06:36 great 09:06:39 next plans are to test more cases - add/remove fixed ips for vms 09:06:45 okay 09:06:56 the more important is to get feedback 09:07:31 however I didn't ask dansmith to review is since we retarget it for Liberty 09:07:40 obondarev: yes 09:07:44 and nova folks may probably have more important reviews at this stage of the cycle 09:07:57 well I had a long discussion with dansmith last week 09:08:05 so I hope he'll take a look when has time for it 09:08:24 anteaya: interesting 09:08:33 and though you still want to pursue this direction, he indicated to me that he doesn't support it 09:08:42 and I had talked to mikal afterwards 09:08:48 who I had hoped would be here 09:09:12 but we have to proceed with what we have 09:09:23 and you have done a lot of work and have something to test 09:09:24 well done 09:09:29 anteaya: I'd ask Dan to post the comment with his thoughts and concerns on the review 09:09:58 as now I'm unsure what exactly he doesn't like 09:10:08 so do you want ot get some feedback first or keep working on it 09:10:15 the whole approach 09:10:27 yep 09:10:29 was what I heard him say 09:10:40 so since we don't have mikal 09:10:44 I leave the choice to you 09:10:49 what do you want ot do now? 09:11:05 well, I remember Dan was concerned that the approach will not work for complex cases 09:11:12 like allocate_for_instance 09:11:15 oh you heard that 09:11:18 oh good 09:11:38 now the patch allows is 09:11:42 it* 09:12:34 so.. 09:13:00 I'd really like to know what problems do folks see with the approach 09:13:18 well it sounds like you have made a decision 09:13:22 go get some feedback 09:13:47 and I just got an email from mikal, he is at a conference and won't be attending this week 09:13:52 but it was nice of him to email 09:13:53 yes, because I'm probably missing something 09:14:12 okay so you have a way forward for next week 09:14:20 anything else under this topic? 09:14:33 sorry, which way do you mean? 09:14:42 ask Dan for feedback? 09:14:45 getting feedback on your work thus far 09:14:47 yes 09:14:56 anteaya: ok, thanks 09:14:59 great 09:15:06 okay to move to the next topic? 09:15:13 yep 09:15:14 #topic documentation 09:15:23 I have nothing new here 09:15:44 the patch hasn't changed 09:15:54 next 09:15:58 #topic testing 09:16:17 so can we talk about testing the patches we have? 09:16:37 we can 09:16:39 you have been successful with a flat network setup obondarev? 09:16:58 flatdhcp actually 09:17:16 awesome 09:17:28 so I think we should get some addition testers 09:17:30 had to disable floating ips migration though 09:17:40 as it's not ready 09:17:42 gus: are you in any position to be able to test the current patches? 09:17:47 in both patches 09:18:27 I can run through a basic devstack scenario, but it's probably a repeat of what obondarev has already performed. 09:18:31 obondarev: is the fact you had to disable floating ips migration in your notes on the patches? 09:18:42 I don't have any larger/different setups that I can test unfortunately. 09:18:43 gus: I see value in that 09:19:07 I'm fine if we can confirm obondarev's findings 09:19:13 anteaya: yes it is, in the comment on the db migration patch 09:19:41 anteaya: sure, I'll give it a go. 09:19:56 obondarev: the proxy patch doesn't mention the db migration patch in the commit message 09:20:00 (It won't be until next week however - I'm out helping high school kids with robots for the rest of this week) 09:20:00 do you think it should? 09:20:09 gus: thank you 09:20:20 gus: oh cool, that sounds like a lot of fun 09:20:27 gus: how are they doing with them/ 09:20:29 ? 09:20:29 anteaya: actually no, it is not dependent 09:21:19 obondarev: I didn't say dependent, but if you don't have a link to the db migration patch in the notes on the proxy patch, how should a reviewer or potential tester find it? 09:21:34 let's make it easy for people 09:21:47 anteaya: so testing proxy may be independent from testing db migration 09:22:04 you just said you tested them together 09:22:17 yeah, but that's not necessary 09:22:18 so testing them together is a scenario, is it not? 09:22:29 I am fine with it not being necessary 09:23:00 but I would like to make it possible for people who would like to, to find the db migration patch from the proxy patch 09:23:04 ok, I can add a note to the commit message that it can be tested together with db migration 09:23:11 wonderful thank you 09:23:20 anteaya: sure, np 09:23:41 anything more on testing this week? 09:24:05 moving on 09:24:11 #topic open discussion 09:24:25 so sdague and others are at the ops meetup 09:24:35 apparently there are about 180 people there 09:24:39 they had a good first day 09:24:49 the migration didn't come up yet 09:25:04 but about 75% of the people in attendance are already running neutron 09:25:17 #link https://etherpad.openstack.org/p/PHL-ops-tags 09:25:42 this is based upon someone asking the question what service are they running and then guesstimating the show of hands 09:25:57 would be nice to know how many of those who're using nova net is still interested in neutron migration 09:26:02 I found the etherpad informative 09:26:18 agreed 09:26:46 though we can't take the folks who show up to the meetup in the states as definitive of what our users need 09:27:00 agree 09:27:10 as we know some folks in some countries can't get to the states 09:27:24 but yes, as much info as possible would be good 09:27:45 I trust sdague will do his best to gather as much info as he can from the group on the topic 09:27:58 I wouldn't have any ability to contact him now anyway 09:28:21 I could email but couldn't guarentee he would read it before he presents 09:28:31 anything more for open discussion? 09:28:56 I'll go with no 09:29:04 thanks for all your hard work obondarev 09:29:09 it is awesome 09:29:16 and thanks gus 09:29:17 anteaya: thanks 09:29:21 for just being you 09:29:26 obondarev: :) 09:29:31 happy roboting 09:29:37 see you next week! 09:29:40 yes, thanks obondarev 09:29:46 * gus waves 09:29:48 #endmeeting