16:02:33 #startmeeting networking-guide 16:02:33 Meeting started Thu Feb 4 16:02:33 2016 UTC and is due to finish in 60 minutes. The chair is emagana. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:38 The meeting name has been set to 'networking_guide' 16:02:44 o/ 16:02:48 hello 16:03:02 we have so far njohnston Sam-I-Am 16:03:08 anyone else? 16:03:18 hey Sam-I-Am: you are also with the general documentation, right? 16:03:32 julen: Sam-I-Am is a core 16:03:35 * haleyb is lurking 16:03:42 I am Julen, by the way, from Hamburg (Germany) 16:03:56 julen: not Spain? 16:04:25 o/ 16:04:30 yeah, i do a lot of core docs 16:04:42 well... I am living in Germany now... 16:05:51 good! I have many ideas, maybe we can talk about some of them after the important stuff... 16:06:10 #topic announcements 16:06:23 any announcement? 16:07:09 ok.. moving on 16:07:19 nothing here... 16:07:30 #topic action items 16:07:56 Do we have networking guide reviews out there that need our attention? 16:08:27 nope 16:08:30 its been pretty quiet 16:08:38 i need to do another round of updates to the scenarios 16:08:55 same here.. I started the debugging section but I haven't pushed anything 16:09:04 we also never really came to a conclusion about how to handle provider networks in the classic scenarios 16:09:46 did we decided to extend the scenarios... it's fuzzy right now 16:09:54 in my mind I meant 16:10:06 yeah i think we did 16:10:15 its a lot of work, so i want to make sure we're all thinking the same thing before i work on it 16:10:21 that's what i recall as well... 16:10:31 are we talking about the network section on the install guide or about the networking guide? 16:10:37 networking guide 16:10:43 the install guide is another team 16:10:48 julen: This meeting is focus on the networking guide 16:11:13 Let's take a look to the etherpad. #link https://etherpad.openstack.org/p/networking-guide 16:11:53 I found this work: https://gist.github.com/ssrikant20/c9c9044a1b57844a227d 16:11:55 aha.. I thought the networking section of the install guide and the networking guide were somehow linked. As an extension 16:11:59 but seems to be in the wrong format 16:12:22 julen: they are somewhat linked - i work on both 16:12:55 emagana: what is this thing? 16:13:14 I just got it from the etherpad 16:13:34 hmm, not sure either 16:13:37 oh, thats really weird 16:13:42 we dont do things that way 16:13:56 Sam-I-Am: this is what I am calling it out 16:14:08 ssrikant: hello? 16:14:13 same username resides in here 16:14:16 we should NOT do that.. I will contact Sangeetha Srikanth directly 16:14:37 yeah, we need to use the regular workflow 16:14:47 #action emagana to contact ssrikant 16:14:53 then we can also compare it with existing content 16:14:55 is navinrio around? 16:15:49 guess not 16:16:26 ok.. for the new members.. could you help on any of the topics in the etherpad? 16:16:36 looking at julen and lwilliams_ :-) 16:17:14 :) i will take a closer look at some of the overview sections and see where i can help. 16:17:21 which ones? 16:17:31 most of the work needs to be done in the intro/config sections 16:17:31 we would like to complete section marked as (H) High and (M) at least 16:17:39 the scenarios are pretty good right now 16:17:43 ok 16:18:18 I have to admit that I am way late on my sections but will deliver no matter what 16:18:37 emagana: join the club 16:18:47 so many things going on.. 16:18:57 emagana: running 'sorted' on my list of to-dos returns the same list 16:19:03 not sure if you got the email but I was invited to join the User Committee 16:19:03 sorted by priority, that is 16:19:07 its always fires 16:19:12 i didnt see that 16:19:37 ok. let's move on.. 16:20:14 Sam-I-Am: Do you want to discuss? 16:20:27 sorry... hit enter before time.. 16:20:39 I meant if you have something to discuss with the team? 16:20:52 not really. just always looking for more contributors. 16:21:03 maintaining the guide is not easy 16:21:06 emagana: I might not be able to take care of any of the points completely by myself, but I can help on adding stuff, or some useful picture... 16:21:11 and it still lacks a lot of stuff 16:21:34 julen: That is great, please add you name to the sections in the etherpad 16:21:47 and more than one person can be on a topic in the etherpad 16:21:54 we have fews weeks before M-3 16:22:00 which is first week of March 16:22:01 can I just write some draft or comments? 16:22:09 that's good 16:22:17 let's target draft of those section at least 16:22:34 julen: yes, feel free to push things directly to gerrit and we will review 16:22:41 you can add us as reviewers 16:23:39 just to clarify: so, the install guide provides instructions on how to set up each and every component of openstack, and the networking guide is meant to provide a deeper understanding of all the involved concepts. Right? 16:23:54 so, sort of "the neutron manual" 16:24:32 correct 16:24:33 julen: yeah 16:24:38 good 16:24:43 the install guide is the "easy path" 16:24:59 its the quickest way to deploy a working stack while learning how all the things work 16:25:02 its just one way 16:25:16 the networking guide is aimed more toward operators who want to deploy more complex networking 16:25:32 but also provides intro material to cover the gap between physical and virtual networks 16:25:39 networking is probably the hardest thing for most people to understand 16:26:27 eventually we may integrate the networking guide with the admin guide, but right now its independent 16:27:11 let's move on 16:27:16 yep 16:27:18 #topic open discussion 16:27:20 hmm... so, if I want to bring up a topic about the networking section of the install guide, this wouldn't be the right place... right? 16:27:26 nope 16:27:42 julen go ahead 16:28:14 ok, I'll try, and if it is not the right place, I'll explain again in somewhere else 16:29:33 the floor is yours 16:29:58 so... long story short: I have an BASH version of the install guide but although I follow everything step by step, it still has some little issue 16:30:20 this is called BOMSI, and I already introduced it very shortly on the last summit in tokyo 16:30:53 ok... 16:31:09 the training guide folks also maintain shell scripts for the install guide 16:31:14 they call it osbash 16:31:21 the thing is: BOMSI might be a good way to test the install guide, as the code includes exactly, line by line the commands in the documentation 16:31:29 really? 16:31:32 yep 16:31:36 never heard about it.. 16:31:49 but this one is based on ISO... 16:32:14 and it is multinode... 16:32:21 so is theirs 16:32:26 hmm.. I have to check that code 16:32:46 but anyway, we've discussed testing via script... the problem is making sure the script and docs align for each release 16:32:58 part of the install guide is doing every step manually 16:33:02 and there's a reason for it 16:33:27 in my opinion as a operator, I will NEVER deploy anything that I want in production using bash scripts 16:33:45 emagana: well, no, however... 16:33:57 they are hard to maintain and they do not provide a repeatable way to deploy a cluster consistently 16:34:10 the next steps after a manual install are learning how to automate deployment 16:34:12 hmm.. but what is the reason not to force to do some steps manually? 16:34:24 julen: the install guide is a learning experience 16:34:41 there are much better ways to automate installs - like puppet 16:34:51 Sam-I-Am: We have Salt, Ansible, Puppet and Chef project for that 16:35:05 point is, too many people dive into automation first and then assume "things work" ... without really learning how openstacks works 16:35:06 sure.. but you don't follow the guide step by step... 16:35:08 yeap, that is my point 16:35:18 then they go deploy in production, stuff breaks, and they're crying for help 16:35:42 so the point of the install guide is a step-by-step manual procedure to learn how services talk, what they do, ports they use, etc. 16:35:52 sooooo..... 16:36:09 i think automation is important, and the next step for people is automating something simple like the install guide 16:36:23 aha... I see. So the point on providing more "manual" steps on the guides, is to help people understand what they wrote, right? 16:36:26 in other words, provide a starting people so people don't have to start all over 16:36:29 yeah 16:36:38 indeed! 16:36:42 i know chef is working on an automated version of the install guide 16:36:54 so having a bash one isnt the worst thing in the world - but we already have osbash 16:37:05 i would like to see one using ansible and puppet too 16:37:30 but that is not our goal :-) 16:37:42 not this teams goal, the install guide team's goal 16:37:47 julen: do you have something else to discuss? 16:38:11 nope, everything is clear 16:38:19 anyone else? 16:38:31 julen: feel free to join the install guide team 16:38:33 we need more people 16:39:13 not sure what to do more 16:39:45 we reached the neutron team and we sent emails to all ML lists... I had a list of people but they are not attending the meeting nor contributing 16:40:09 yeah, so goes the story with docs 16:40:21 none of the other meetings are getting attendance, so you're not alone 16:40:29 Sam-I-Am: :-( 16:40:52 well, let's keep trying 16:41:02 I will talk to PTLs to get more ideas.. 16:41:06 anything else? 16:41:09 good idea 16:41:15 nothing from me 16:41:22 no 16:41:24 just putting out more fires :) 16:41:28 #action emagana to talk with PTLs to get more contributors in networking guide 16:41:38 Thank you all! 16:41:51 emagana: Shall I just grab some sections from the etherpad? 16:41:51 yep, thanks 16:41:52 thanks emagana 16:41:54 Pelase, work on the etherpad to be sure we cover more section 16:41:55 njohnston: yes 16:42:01 njohnston: Yes! 16:42:17 OK, I will take one and get to work :-) 16:42:25 just add your name and write the docs and we will help on reviews and improvements 16:42:34 njohnston: awesome! 16:42:47 Are the ones listed as TBD open for the taking? 16:43:01 @Sam-I-Am I sent some content for networking guide few days back. 16:43:12 ssrikant: good to see you around 16:43:14 yeah, and ones with people assigned already 16:43:24 This is my first attempt so took an easy one 16:43:31 ssrikant: We want you to push your documentation in gerrit and not private github accounts 16:43:36 i sent an email to the group as well 16:43:45 ssrikant: i didnt see an e-mail 16:43:58 ssrikant: me neither 16:44:19 hmm.. it was to networking@openstacknow.com 16:44:24 * njohnston takes "Advanced configuration -> Operational" 16:44:38 I dont know that address 16:44:42 I just followed the instructions in Instructions for Contributors 16:44:50 in https://wiki.openstack.org/wiki/NetworkingGuide/TOC 16:45:00 if there is another email or steps please let me know 16:45:07 i will resubmit. 16:45:27 ssrikant: oh, that email hasnt worked in a while 16:45:31 use the docs mailing list 16:45:32 :( 16:45:32 use these ones: openstack-docs@lists.openstack.org & openstack-dev@lists.openstack.org 16:45:36 ok.. sorry did not know 16:45:39 n.p. 16:45:52 ok.. 16:46:02 ssrikant: also that wiki page is outdated 16:46:04 and I need to put it in a different repo 16:46:16 and not gist 16:46:20 for a while we were allowing people to contribute in any format or location to get content 16:46:22 yes, please 16:46:24 but that didnt work out well 16:46:30 so now you have to use the regular gerrit workflow 16:46:41 guess we need to fix that wiki page 16:46:43 ok.. if u have some basic steps for that kindly let me know 16:46:51 i will follow that procedure. 16:46:56 ssrikant: take a look: http://docs.openstack.org/infra/manual/developers.html 16:46:59 ok 16:47:11 emagana: btw i submitted a patch to remove the apac meeting, and also changed the agenda to use an etherpad for this meeting 16:47:13 you need to use the openstack-manuals repo 16:47:27 Sam-I-Am: I saw it.. make sense 16:48:19 ok.. let me read thro this and will submit the content and will also email the mailing list once done 16:48:31 great 16:48:32 @emagana @Sam-I-Am Thank you 16:48:34 ssrikant: you dont have to mail the list about contributions 16:48:38 we'll see them in the review queue 16:48:41 ok 16:48:42 yeap.. 16:48:46 just e-mail the list with questions 16:48:52 like... you cant get something to work 16:48:57 ok..got it 16:49:47 anything else? 16:50:02 What content do you think should be in the Operational section other than logging? http://docs.openstack.org/liberty/networking-guide/adv-config-operational.html 16:50:51 njohnston: maybe db management? 16:50:57 i think there's a patch somewhere for it... 16:51:21 https://review.openstack.org/#/c/276335/ 16:51:30 Thanks! 16:51:30 havent looked at it yet, but seems along those lines 16:51:50 maybe document the "cleaner" scripts 16:51:57 like ovs-cleanup or whatever its called 16:52:01 there's one for linux bridge too 16:52:19 stuff operators would need to do from more of an administrative standpoint 16:52:34 upgrades would probably go into operational bits 16:53:15 emagana: anything else? 16:53:23 no, we are good 16:53:27 Thank you all! 16:53:41 #endmeeting