16:00:52 #startmeeting networking-guide 16:00:53 Meeting started Thu Jan 14 16:00:52 2016 UTC and is due to finish in 60 minutes. The chair is emagana. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:56 The meeting name has been set to 'networking_guide' 16:01:11 I am sure Sam-I-Am is around! 16:01:23 howdy 16:01:37 emagana: whats up with the calendar confusion? 16:01:41 it is just you and me 16:01:56 Hi 16:01:59 Am I wrong? 16:02:05 hi navinrio 16:02:11 o/ 16:02:13 emagana: did you see the post on the -dev list? 16:02:25 Sam-I-Am: I though we were fine 16:03:13 emagana: dunno, i reloaded the ical and the meeting is next week, but i dont think it hurts to talk now anyway since we're here 16:03:19 and the networking guide needs work, as usual 16:03:37 indeed! 16:03:56 action# review the calendar and make ajustment based on the ical 16:04:17 i dont see you around much these days 16:04:35 let's make this one focus on the guide assignments 16:05:06 I am thinking to work on Legacy to DVR - TBD ( H ) 16:05:11 Is it ok with team 16:05:19 we were hoping to get more people self-assignments from the etherpad #link https://etherpad.openstack.org/p/networking-guide 16:05:22 navinrio: sure, if you're up for that task 16:05:23 what is the timeline and 16:05:29 navinrio: asap :) 16:05:44 navinrio: or... 2 releases ago? 16:05:47 navinrio: thanks, yes we need to add content asap 16:06:14 migration to dvr rather than reinstalling increases adoption of dvr 16:06:23 people don't want to greenfield if they can avoid it 16:06:27 navinrio: I just added your name to the etherpad 16:06:54 I am taking Debugging 16:07:10 Sam-I-Am: you have already configuration. 16:07:18 emagana: yeah, and i need to update the scenarios 16:07:24 with that we will have covered some of the ( H ) areas 16:07:27 the prep/cleanup patch merged which is nice 16:07:36 You you want me to do testing 16:07:44 Sam-I-Am: where we are on the versioning? 16:07:46 of legacy DVR 16:07:48 emagana: done 16:07:57 stuff next gen DVR fixed 16:08:07 navinrio: yeah, any procedures/instructions need to be validated 16:08:34 emagana: if you want to patch liberty now (which we have to do for the scenarios), you hit master then backport 16:08:40 For some reason i saw the sc68cal patch for versioning abandoned 16:08:51 emagana: it was an errant backport 16:08:57 Sam-I-Am: my bad! 16:08:58 ^this 16:09:03 sc68cal: hi there! 16:09:05 which turned out to be a front-port because it came before when we cut stable/liberty 16:09:23 so instead we just backported about a dozen patches to the already-cut stable/liberty 16:09:48 so we're good to go now... and the web site is rendering properly 16:10:00 only issue is that the juno net guide points to kilo, but nothing we can (or should) do about that 16:10:01 Ok Thanks for adding my name to Legacy to DVR - TBD ( H ) 16:10:15 unless you want to backport things to a dead release 16:10:24 Sam-I-Am: excelent! OK, time to look for the future ;-) 16:11:24 Other important section is VPNaaS 16:11:39 yeah 16:11:42 well, all the *aas 16:11:44 I wil try to talk to Paul M. from Cisco 16:12:07 Indeed! 16:12:19 I will take LBaaS 16:12:19 it supposedly works multi-node now (mostly) so we need to test that... and then figure out how we document deployment 16:12:30 in other words, can we say "take scenario X, and do these things" 16:12:37 or do we need a completely new scenario 16:12:52 I go for the first option 16:13:02 creating more scenarios feels like we will repeat a lot of conenct 16:13:06 content* 16:13:09 the question here is can vpnaas work between 2 routers in the same cloud, or does it require more than 1 cloud 16:13:20 if its between two routers, we can probably augment an existing scenario 16:13:43 Sam-I-Am: I haven't not use it.. let's find out sone neutrinos to give us advice 16:14:01 the annoying thing about vpnaas is it replaces the l3 agent, so we'll have to replace the conventional l3 agent in the scenario we use 16:14:16 rather than building up from scratch assuming the operator wants to deploy vpnaas 16:14:24 #action ask armax if vpnaas will work between 2 routers in the same cloud, or does it require more than 1 cloud 16:15:15 i can also find people to ask 16:16:01 its a simple question that lets us get started 16:16:04 ok 16:17:06 lbaas and fwaas also need some use cases 16:17:12 Sam-I-Am: you have this one merged: https://review.openstack.org/#/c/267245/ 16:17:14 they're a little less involved, imo 16:17:23 I was wondering if we still need a spec for Mitaka changes? 16:17:26 emagana: yes, cleaned up a lot of stuff. changed legacy to classic. 16:17:30 we do need a spec for mitaka changes 16:17:36 i wrote a BP yesterday 16:17:42 of course we're still doing liberty work :/ 16:17:47 but a lot of it will apply to mitaka too 16:17:55 like separation of agent config into new files 16:18:07 please, include the link for the BP 16:18:44 Sam-I-Am: could you also include the work needed for mitaka in the etherpad to keep track of it 16:18:49 #link https://blueprints.launchpad.net/openstack-manuals/+spec/networkguide-mitaka 16:19:12 yeah, i'm going to write a spec for the basics... update scenarios, etc. 16:19:22 #link https://blueprints.launchpad.net/openstack-manuals/+spec/networkguide-mitaka 16:19:28 i hope we can get more done, but there's just not a lot of contributions 16:19:33 i can only work 24 hours a dat 16:19:34 day 16:19:43 Sam-I-Am: Thanks for the assignation of that BP :-) 16:20:03 So, the specs is needed then? 16:20:08 I guess it is! 16:20:12 we need something to track updates for mitaka 16:20:17 however thats going to work 16:20:26 ok.. 16:20:34 ideally someday we'll have a lot of the static content done, and then our changes are like the install guide "whats changed in X?" 16:20:48 the install guide has a spec for each release 16:21:50 sc68cal: anything that you want to cover? 16:22:18 For Legacy DVR what shall be Contents 16:22:22 is how to do 16:22:38 is it how to configure Legacy DVR and USed case 16:22:59 navinrio: I would suggest to follow the same format that we have for the other legacy scenarios 16:23:10 some inputs from team what are they looking to see in that Topic 16:23:25 I mean to say Legacy DVR 16:23:30 navinrio: you deploy conventional multi-node OVS with at least 2 net nodes and 2 compute nodes... deploy conventional routers on it with some VMs... then convert the deployment to DVR. 16:23:39 emagana: sorry no 16:23:43 navinrio: and you document how you did all of it 16:23:49 Got It 16:23:51 thank U 16:24:09 Thank U 16:24:14 Appreciated 16:24:19 navinrio: you can extend the classic-with-ovs scenario with more nodes 16:24:37 right now 3 nodes doesn't get you much with dvr 16:24:45 so you need several more to see if dvr even works 16:24:56 Ok 16:25:02 come to think of it, you can probably use the DVR scenario, just dont deploy DVR on it 16:25:03 when do u want to complete this 16:25:13 sooner the better 16:25:16 Ok 16:25:17 got it 16:25:19 thank U 16:25:23 will focus on it 16:25:30 navinrio: Thanks! 16:25:42 Please, include us in the review once you have initial pacthes. 16:26:03 Understood will do 16:26:15 navinrio: even if the patch is not ready, we could start providing guidence before you have spent a lot of time is probably wrong direction 16:26:29 Ok 16:26:33 so shall send email 16:26:46 to you and touch base offline 16:27:00 navinrio: as long as you include us in the gerrit review, you will get the emails 16:27:08 Ok 16:27:11 Got it 16:28:08 we are having this meeting next week, in order to adjust to the calendar changes for the new year. 16:28:18 Is there something else to discuss today? 16:28:30 emagana: is that the conclusion on the calendar problem? 16:28:34 I am fine and thank You for providing me inputs 16:28:36 all of my meetings were messed up the last 2 weeks 16:29:17 Sam-I-Am: not sure what else we can do! 16:30:05 yep, just want to make sure i'm not crazy 16:30:11 well i am, just not crazy in that instance 16:30:17 you have to be crazy to openstack 16:30:58 LOL 16:31:15 Sam-I-Am: indeed.. take a break.. 16:31:34 then things dont get done 16:31:44 #action emagana will send a reminder for next week meeting 16:31:45 anyway, i think we're good here 16:31:53 Sam-I-Am: we have a lot of work.. 16:31:53 expect to see some liberty-mitaka scenario updates from me soon 16:32:00 emagana: i'm also working on ovn docs 16:32:18 Sam-I-Am: Thanks.. you and sc68cal are the masters! 16:32:29 ok.. take care! 16:32:30 ciao all 16:32:34 ya 16:32:39 more Sam-I-Am then me 16:32:45 *than 16:32:52 Thank You .. Bye everyone 16:32:53 lol, see y'all later 16:33:10 #endmeeting