16:00:38 #startmeeting Network Meeting 16:00:38 Meeting started Wed Aug 31 16:00:38 2016 UTC. The chair is gundalow. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:38 The meeting name has been set to 'network_meeting' 16:00:45 #chair Qalthos 16:00:45 Current chairs: Qalthos gundalow 16:00:52 #topic roll call 16:00:54 * gundalow waves 16:01:02 * misc wave back 16:01:23 misc: hey :) 16:01:52 hiya 16:02:07 #topic 2.2 update 16:02:14 Work on Ansible 2.2 continues 16:02:32 Hey All 16:02:40 We are getting very close to the code freeze, see https://groups.google.com/forum/#!topic/ansible-devel/Ce5uNA5TnJ0 16:03:10 * mhite waves 16:03:24 From the Network side I believe we only have one OpenSwitch, and a few Junos updates left 16:03:37 Then lots of testing 16:04:03 :( I have ten more modules to submit before then... 16:04:29 As some of you may be aware there have been lots of changes to how network modules are implemented, so we will be looking to the community to help testing 16:04:43 let me hurry up..Peter was mentioning Sep 16th 16:05:01 skg_net: The purpose of the code freeze is to ensure we don't break other things 16:05:53 @gundalow: ok 16:05:54 New modules don't affect anything else, so we may be able to take their changes much closer to the final release 16:06:21 skg_net: TL;DR, keep doing what you are doing and you should be fine :) 16:06:33 Thx, anyway I will try push as early as possible 16:06:36 #topic Dell Modules 16:07:07 I have couple of questions 16:07:08 So, introducing skg_net from Dell :) 16:07:11 Sure, go for it 16:07:44 Where do we documents the caveats 16:08:11 such as? 16:08:24 like from which release version we support Ansible module 16:08:56 for OS9, we need to increase the connection rate limit in order for Ansible to work 16:09:48 You can add things in the `notes:` DOCUMENTAION for caveats like that 16:10:11 Thx 16:10:54 for network facts, we dont have some info for facts to fill...like filesystems 16:11:14 and we want add some more facts.. 16:11:38 how to go about that.. 16:12:01 is it a fixed standard, we need to follow on facts... 16:12:11 might be able to dig up our previous discussion on that 16:12:16 should be in our meeting notes somewhere 16:12:20 but it's a topic from a while ago 16:12:48 all the minutes are under https://meetbot.fedoraproject.org/sresults/?group_id=ansible-meeting&type=channel 16:12:49 i think in the end it was determined that if you can, go for it, but don't feel obligated to model to a specific fact layout 16:13:14 mhite:Thanks will take a look at it 16:13:29 mhite: Thanks 16:13:37 no problem 16:14:10 skg_net: Have a look at ios_facts, I believe that's might be a decent example 16:14:13 caphrim007: hi :) 16:14:29 heyo. bus was late *grumble* *grumble* 16:14:44 Thx 16:14:48 It's in the 5/18/2016 meeting notes, btw. 16:15:09 on the PR..I have addressed all the comments.. 16:15:27 is there something I need to do to restart the review 16:15:36 https://meetbot.fedoraproject.org/ansible-meeting/2016-05-18/networking_working_group.2016-05-18-16.03.log.html 16:16:01 Do they Dell Team are planning on pushing in around 16 new modules, the first two are in https://github.com/ansible/ansible-modules-core/pull/4599 We'd welcome other eyes on that so they can apply the feedback to their other modules 16:16:27 skg_net: "When you are done, please comment with text 'ready_for_review' and we will put this PR back into review." 16:16:39 that will kick Ansibull-bot to update the status 16:16:48 Sorry its 12 16:17:05 skg_net: Fewer means less things for us to review :) 16:17:12 ok I will mark them accordingly 16:17:14 so no need to be sorry 16:17:50 :) 16:17:53 we will incorporate the comments given in this module, in others as well 16:17:57 cool 16:18:15 skg_net: Once these PRs are done please do the other modules as one module per PR 16:18:25 Do you have any other questions? 16:19:34 sure will do 16:19:40 nope thats it for now.. 16:21:22 cool 16:21:36 topic Open Floor 16:21:39 #topic Open Floor 16:21:46 What else do people have? 16:22:27 do we need compatible for python3 as well 16:22:31 I guess yes 16:22:49 yes :) 16:23:09 all new modules MUST work with py3 16:23:21 we test it ? 16:23:34 ok 16:23:41 (because afaik, we just test compilation on python3, which may not be enough) 16:24:11 misc: We are running a lot of the functional tests against py2 *and* py3 16:24:31 good good 16:24:50 You make a good point though 16:25:03 misc: Feel free to joing the Test Working Group Meeting tomorrow :) 16:25:15 gundalow: I likely have others meetings :/ 16:25:18 is there a restriction/guidelines for importing modules in Ansible? 16:25:38 misc: :( 16:25:45 (connection is being lagguy) 16:26:28 skg_net: It's fine if your module depends on other modules as long as you handle missing dependencies gracefully and add to DOCUMENTATION requirements: 16:26:44 anything already available in Ansible for XML 16:26:49 ok.. 16:28:14 I'm not aware of anything 16:28:48 ok, will check it out.. 16:29:00 Feel free to stop via #ansible-devel to ask any of these questions, there should normally be people there from UK, eastcoast, westcoast 16:29:03 :) 16:29:13 Anyone got anything else 16:29:22 caphrim007: Do you have any more modules planned? 16:29:26 or anyone else? 16:31:25 gundalow: one more 16:31:30 but i havent made a pr for it yet 16:31:40 its for ssl cert mgmt 16:31:47 caphrim007: cool, @gundalow it for attention :) 16:31:51 Sounds good 16:31:59 so guessing we are done 16:32:27 As always please add stuff to https://github.com/ansible/community/issues/110 16:32:33 Thansk everyone! 16:32:35 #endmeeting