09:00:43 #startmeeting nova-net-to-neutron-migration 09:00:44 Meeting started Tue Jan 13 09:00:43 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:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:48 The meeting name has been set to 'nova_net_to_neutron_migration' 09:00:51 hi 09:01:00 jlibosva: hello 09:01:05 o/ 09:01:10 welcome, I'm glad you are here 09:01:18 obondarev: oleg how are you? 09:01:24 me too:) 09:01:28 obondarev: how were your holidays? 09:01:32 hi 09:01:34 obondarev: :D 09:01:35 anteaya: Good, thank you :) 09:01:40 belmoreira: welcome 09:01:43 anteaya: how are you? 09:01:45 obondarev: wonderful 09:01:57 obondarev: good thanks, enjoying a lovely new zealand evening 09:02:08 anteaya: wow, cool! 09:02:09 anyone else here for the migration meeting? 09:02:14 obondarev: it is lovely 09:02:26 obondarev: we have to figure out how to get you to lca next year 09:02:42 anteaya: sorry, where?) 09:02:56 obondarev: linux conference austrailia 09:03:13 anteaya: ah, I see) 09:03:30 so we do have a bit of an agenda 09:03:36 let's take a look, shall we? 09:03:41 #link https://wiki.openstack.org/wiki/Meetings/Nova-nettoNeutronMigration 09:04:07 #topic the state of the Neutron spec (obondarev) 09:04:15 anteaya: yep 09:04:19 obondarev: would you care to share your thoughts? 09:04:28 sure 09:04:32 so I continue working on the spec, uploaded new revision yesterday 09:04:41 wonderful, thank you 09:04:51 thanks to Joe Gordon, Jacub and others for being active reviewers 09:05:15 still would be good to have more people taking part in the discussion 09:05:22 on gerrit 09:05:24 yes, I agree 09:05:35 I'm also working on the prototype in parallel 09:05:42 how do you mean? 09:05:46 which is the first part of the proposed plan - Neutron proxy mode 09:06:16 I mean in arallel with spec discussions 09:06:20 p* 09:06:31 okay 09:06:36 where are you working on that? 09:07:03 mostly locally, haven't posted anything to gerrit yet 09:07:13 can you put something up? 09:07:23 I don't want to see effort wasted 09:07:32 and would like to see where you are heading 09:07:46 may I jump in here with some additional comments? 09:07:52 or would you like to continue? 09:07:56 Yeah, I think I'll post initial version in two days 09:08:07 sure 09:08:14 okay thanks 09:08:47 so there are a few people involved in this who are at linux conference australia in auckland this week 09:09:03 so we took the time to sit down on monday and share some thoughts 09:09:24 michael still took nots on an etherpad and has had the time to post that link publicly yet 09:09:48 but we want to share the information with everyone whcih is why we put it in and etherpad 09:09:53 sorry I don't have that link 09:10:25 no worries 09:10:37 so I was there and michael still, joe gordon, mark, angus 09:10:47 cool! 09:10:57 jim blair and david lyle (mostly because they were available) 09:11:15 anteaya: the discussion in lca diverged from the spec? 09:11:21 and we think that there needs to be more attention on the spec so that is good 09:11:36 belmoreira: well I think mostly we agreed that it needs more detail 09:11:47 and we acknowledge oleg is doing a great job 09:11:50 for sure 09:12:05 I mean more details) 09:12:05 but needs more support than he has gotten so far 09:12:14 yes more details 09:12:23 more details for testing 09:12:38 a better understanding of what priorties are important to cern 09:12:53 such as tolerance for downtime and allowance for rolling upgrades 09:13:00 those sorts of questions 09:13:15 cern being the model use case for deployers here 09:13:19 Joe posted some of those question on the spec 09:13:33 yes, we are trying to capture this in the spec 09:13:44 and trying to work together to get some answers 09:13:58 the over all direction I believe is where we want to go 09:14:12 we just need to work now to get some more exact answers 09:14:20 + 09:14:26 so gus, mark and I are going to sit down this week 09:14:35 and work on another patchset to the spec 09:14:43 I hpoe that is okay with you obondarev 09:14:51 sure 09:14:58 to fill in the blanks on some of these questions 09:15:02 obondarev: thank you :D 09:15:13 and then go through a review cycle again 09:15:18 thank you all:) 09:15:39 now mark, joe, michael still and myself will be at the nova mid-cycle in two weeks 09:16:03 obondarev: it would be awesome to have you there too, oleg but that would be too difficult to arrange now I think 09:16:28 I think so too 09:16:37 and hopefully by continuing to work on the spec we can be a little closer to agreement on how to implement the migration 09:16:50 does this sound acceptable? 09:17:07 yes 09:17:14 one point from Joe was that it'll be good to break the spec in its curent state in two parts 09:17:18 great, thanks so much for your understanding 09:17:24 one describing the overall process, what we're trying to achieve eventually 09:17:32 which starting points and which end points 09:17:46 this I guess should be a cross project specification 09:17:50 obondarev: yes, right now joe is advocating for a two part/two patch approach 09:18:09 the other describing technical implementation details 09:18:09 well lets' see how much we can retain within neutron 09:18:21 since everytime we expand we introduce more waiting time 09:18:36 agree 09:19:00 I'll work with angus and mark to see if we can capture the details in joe's idea of a two part approach in the spec 09:19:08 so taht it makes sense with everyone 09:19:23 great, thank you 09:19:42 so hopefully that should be up for review by the end of thursday 09:19:51 thursday new zealand time 09:20:11 so I look forward to your review and comments on that patchset 09:20:27 so anything more here on this topic? 09:20:36 not from my side 09:20:46 belmoreira: anything more right now? 09:21:00 sorry I don't know much the names mentioned here :) 09:21:08 I wanted to ask whether there are also folks from nova 09:21:11 jlibosva: ah sorry 09:21:18 as we'll probably need to file a nova spec too 09:21:37 jlibosva: yes a good question, I shouldn't assume everyone knows eveyone else 09:21:38 I saw there were some concerns about contacting conductor directly 09:21:45 michael still is the nova ptl 09:21:49 anteays: no, thx 09:21:49 right, that's on the agenda 09:21:53 joe gordon is a nova core 09:22:06 ah, thanks :) I should have probably known that 09:22:08 so yes, we have some input from nova here 09:22:21 jlibosva: good question it is important to check 09:22:38 jlibosva: you can't know everything 09:22:48 and I prefer people ask 09:23:04 since if you do't know there are probably others that don't know either 09:23:11 thanks for giving me the chance to clarify 09:23:20 so yes, let's move onto the next topic 09:23:33 #topic Nova spec, do we need one? if yes, who will create it? 09:23:54 so right now joe doesn't feel we need a separate nova spec 09:24:08 or if we do, it will just be a pointer to the neutron spec 09:24:35 we have gotten permission from michael still to have a nova spec exception if we need it 09:24:45 since this is a high priority effort 09:24:50 anteaya: but there are any nova changes expected? 09:25:01 belmoreira: I guess so 09:25:03 belmoreira: good question 09:25:11 well I don't know exactly 09:25:35 this is one of the things I want clarified in the next patchset for the neutron spec 09:25:58 so after that patchset is posted hopefully we all will have a clearer picture 09:26:08 not sure it's good to include technical detail of changes in neutron and in nova into one single spec.. 09:26:11 ok 09:26:20 obondarev: true 09:26:32 but let's see what shape the new patchset takes 09:26:42 and then comment in reviews 09:26:54 makes sense 09:27:10 but the short version is that _if_ we need a nova spec, we have gotten permission to create one 09:27:19 even though it is passed the deadline 09:27:22 awesome 09:27:33 anteaya: great 09:27:34 one of the things we talked about at our in person meeting 09:27:47 is that this effort keeps being hindered by the release cycle 09:27:57 so we need to keep up this effort 09:28:05 we don't know if we can make kilo or not 09:28:17 but if we don't, we need to stay focused and keep working 09:28:33 since dropping off work due to a release really puts us behind 09:28:44 so we are going to focus on agreeing to the work first 09:28:56 and not worry about deadlines for releases 09:29:06 anteaya: +1 09:29:15 folks on both sides neutron and nova have agreed to this 09:29:44 so if we see an obstacle we have support to keep working and have folks help to move the obstacle out of the way 09:30:03 any more thoughts here or comments? 09:30:45 I'll take that as no 09:30:54 and move onto the next topic 09:31:05 #topic documentation 09:31:16 so in patchset 3 of the neutron spec 09:31:33 annegentle_ offered to recommend someone to help with documentation 09:31:39 so Edgar was willing to help with this 09:31:41 I think this is a great idea 09:31:45 obondarev: wonderful 09:31:55 we can't ahve too much help in documentation 09:32:04 as he stated here: https://etherpad.openstack.org/p/kilo-nova-nova-network-to-neutron 09:32:04 didn't have a chance to reach him yet 09:32:14 agree 09:32:16 I would like to follow up with annegentle_ to see who she might recommend 09:32:25 obondarev: great, would you like to follow up? 09:32:46 obondarev: can you talk with both edgar and annegentle_? 09:32:59 sure 09:33:02 better to have too much help in documentation rather than not enough 09:33:18 I'll reach Edgar shortly 09:33:19 plus that also gets us more review eyes on patches 09:33:25 obondarev: great thanks 09:33:39 let's keep documentation as a regular topic for this meeting 09:33:57 +1 09:33:59 so we can have your report obondarev next week on how you have made out 09:34:03 great thank you 09:34:10 sure 09:34:16 any one have anything else for documentation? 09:34:26 nope 09:34:30 great 09:34:32 moving on 09:34:38 #topic testing 09:35:15 so right now the testing portion of the spec is a little thin 09:35:25 it is 09:35:33 that is to be understood as how to test this migration is largely unknown 09:35:48 belmoreira: have you given any thought to what you would like to see for testing? 09:36:05 I'd say it's known on a high level 09:36:19 obondarev: okay 09:36:27 anteaya: what we are looking is if can be sone by stagaes (cell by cell) 09:36:33 but I think we need some detail 09:36:43 belmoreira: okay 09:37:11 belmoreira: have you made any comments or suggestions in the testing portion of the spec yet? 09:37:26 sorry I haven't gone though the history of all the comments 09:37:30 we can setup "test cells" that we migrate for testing 09:37:49 belmoreira: we meaning cern or we meaning openstack infra? 09:38:33 anteaya: this is how we at CERN are thinking to test all of this 09:39:10 belmoreira: great, can you add some comments to the spec outlining what you have thought about for testing from CERN's point of view? 09:39:27 anteaya: yes 09:39:28 infra will be limited regarding what we can test 09:39:54 belmoreira: great thank you, that way we can incorporate what processes you can offer into the spec 09:40:19 is there anything else we can talk about regarding testing right now? 09:41:11 I think we have a good place to start expanding that section then 09:41:14 thanks belmoreira 09:41:20 I'll move on 09:41:30 #topic Open Discussion 09:41:54 does anyone have anything they would like to mention or discuss that we haven't already covered? 09:42:32 I would just like to update I did some work on dump/translate/restore nova db to neutron as per discussion with Oleg 09:42:43 jlibosva: thank you 09:42:49 great! 09:42:51 have you a link to your work? 09:43:32 nope, only locally. I plan to push WIP once it does some real translation (e.g. translate and create network) 09:43:54 jlibosva: let's get in the habit of submitting things to gerrit early 09:44:00 even if they don't work 09:44:08 and marking them work in progress 09:44:21 ok 09:44:26 thank you 09:44:37 I think it will save time in the long run 09:44:47 and help others to see what we are thinking 09:44:57 and hopefully reduce false starts 09:45:14 and let's bring the urls for those wip patches to this meeting 09:45:23 so we can look at them and discuss them 09:45:32 makes sense 09:45:37 agree 09:45:38 thanks jlibosva 09:45:58 and thanks for your work here, I look forward to reviewing the patches 09:46:17 I want you to feel supported in your work 09:46:24 so let's show it off 09:46:39 anteaya: many thanks for your help and for for organizing these meetings 09:46:50 obondarev: my pleasure, glad to help 09:47:03 and thanks for understanding and supporting my role here 09:47:08 :D 09:47:21 shall we discuss anything else? 09:48:31 well I think we have had a good second meeting, thanks obondarev for including a log of the first meeting in the ml post 09:48:46 anteaya: sure 09:49:02 thanks everyone for joining! 09:49:27 thank you all for this amazing effort 09:49:32 #link http://lists.openstack.org/pipermail/openstack-dev/2014-December/053522.html 09:49:49 and on that note, let's conclude the meeting 09:50:09 see you all next week, don't stay quiet if you encounter blocks 09:50:16 find someone and get unstuck 09:50:24 thank you all 09:50:28 #endmeeting