16:02:09 #startmeeting Networking 16:02:09 Meeting started Wed Jul 6 16:02:09 2016 UTC. The chair is gundalow. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:09 The meeting name has been set to 'networking' 16:03:00 #chair privateip 16:03:00 Current chairs: gundalow privateip 16:03:16 hi all 16:03:29 Hey Peter 16:03:43 ayyyy 16:04:13 Hello 16:04:46 Anyone have anything for the Agenda today? 16:05:08 i have one thing (sorry i know i said i had nothing) 16:05:12 :) 16:05:30 privateip: cool, #topic and it's all yours :) 16:05:48 i wanted to give everyone an update on 2.2 networking refactor 16:06:08 as many of you have noted we are going through a fairly major refactoring of the networking shared module code 16:06:11 #topic 2.2 networking refactor 16:06:21 to take advantage of ziploader introduced int 2.1 16:06:40 ultimately this will greatly simply both the code base and the ability to test it 16:07:05 as we work through this networking will occasionally break in devel 16:07:17 please just bear with us on this as we work through the issues 16:07:36 we will do our best to minimize any disruptions 16:07:53 as you see things, please file bug reports via the std issues process 16:08:37 unless there are any questions, thats all i have for today 16:08:59 #info Large refactor taking place to make use of the ziploaded work in 2.1. This will result in much cleaner and easier code that we can test. No doubt that things will break. Please report issues via the usual way 16:09:24 Is there documentation on ziploader? 16:09:45 It's new to me 16:10:03 yes 16:10:12 lol if i could only find the link 16:10:33 http://docs.ansible.com/ansible/developing_program_flow_modules.html#ansiballz 16:10:53 great! 16:10:56 how are these changes expected to affect network equipment that's managed via transports other than ssh/telnet? like http/s? 16:11:50 on the surface no changes, everything will continue to just work ... under the covers though we have remove copious amounts of duplicate code so we can better test moving forward 16:14:50 one other note 16:14:58 #topic newblood 16:15:07 i want to "officially" introduce you all to gundalow 16:15:16 he just join Ansible this week 16:15:24 * gundalow waves :) 16:15:29 and will be driving much of the community activity for networking 16:15:43 * dag- applauds 16:15:46 im very excited to have him on board 16:15:49 gundalow: congratulations! 16:15:53 he is a *great* resource 16:15:54 hey dag- :) 16:16:00 Thanks all 16:16:10 Congrats! 16:16:16 and very approachable for any questions or issues you have working with ansible and networking 16:16:24 Glad to be offically part of the team 16:16:26 he will be driving this weekly meeting moving froward 16:16:30 forward* 16:16:37 with that ... over to you gundalow 16:16:43 Thanks privateip 16:17:43 So I'll be initially looking at the community side, how to help you lovely people and improving the QA side of things 16:18:11 One of the first things I'll be looking at is documentation 16:18:28 * privateip claps 16:18:30 As a recap the main things are 16:18:40 1) https://www.ansible.com/network-automation 16:18:48 2) http://docs.ansible.com/ansible/intro_networking.html 16:19:07 3) Individual network modules documentation (subset of http://docs.ansible.com/ansible/list_of_network_modules.html) 16:19:38 looking at what gaps we have, what could be better explained, etc 16:20:27 So if there has been anything that hasn't been clear then feel free to ping me on here (direct message is fine) or throw github tickets and @gundalow them so I'll see them 16:21:14 So that's it from me 16:21:23 #topic open floor 16:21:42 Anyone got anything else their like to raise, or any documentation issues? 16:21:47 One quick thing is that the module examples don't mention 'provider' or any connection params. Also, it would be good if the modules mentioned connection: local 16:22:42 privateip: excellent. What's your github so I'll make sure you see the review? 16:23:04 phil-dileo 16:23:14 cool 16:23:32 I am grybak-arista, if you don't mind adding me as well. 16:25:21 cool, I'll make sure any sizable PRs get mentioned on here 16:26:01 I've created a standing agenda (rather one per meeting), feel free to subscribe to https://github.com/ansible/community/issues/110 to receive updates 16:26:07 anyone got anything else 16:28:37 Cool. So I guess we'll close the meeting now 16:28:45 No meeting next week 16:28:52 or maybe the week after 16:29:09 If people subscribe to https://github.com/ansible/community/issues/110 then will be informed of when the next meetings are 16:29:22 #info No meeting next week 16:29:27 #endmeeting