15:59:57 #startmeeting Ansible Network Working Group 15:59:57 Meeting started Wed May 29 15:59:57 2019 UTC. 15:59:57 This meeting is logged and archived in a public location. 15:59:57 The chair is Qalthos. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:57 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:59:57 The meeting name has been set to 'ansible_network_working_group' 16:00:47 #chair ganeshrn ikhan justjais pabelanger privateip trishnag dmellado 16:00:47 Current chairs: Qalthos dmellado ganeshrn ikhan justjais pabelanger privateip trishnag 16:01:19 There's a lot of issues on the agenda today, so I'll try to get through as many as I can 16:02:09 First, though a slight review of the PR review process 16:02:24 Specifically https://github.com/ansible/ansibullbot/blob/master/ISSUE_HELP.md#when-will-your-pull-request-be-merged 16:03:46 If you are a maintainer of a platform, as most of the people adding PRs to this meeting's agenda are, please make sure that the maintainer list in https://github.com/ansible/ansible/blob/devel/.github/BOTMETA.yml is up to date 16:05:17 and especially if you have more than one maintainer, help out the people reviewing your PR by using shipit 16:07:07 The more feedback you can get on a PR before someone from core has to look at it, the quicker that process will be 16:07:19 Now, then 16:07:51 #link https://github.com/ansible/community/labels/network is where the agenda for this meeting is always available 16:08:00 And it's a long one, so let's get moving 16:08:17 #topic Meraki 16:08:36 I listed four PRs which need review and merge if reviewer is happy. 16:08:43 https://github.com/ansible/ansible/pull/56818 16:09:25 Anything in particular to mention about any of them? Do we ahve all the prerequisite PRs in now? 16:09:57 Yes. All the prereqs should be in place. I don't think there's anything interesting about any of them. 56818 and 48971 are on the same codebase, but I tested a merge earlier and there weren't any conflicts. 16:10:23 56929 is a new module and it hasn't yet been reviewed, so I don't necessarily expect it's perfect. 16:11:17 56818 is commenting out tests? 16:12:19 I didn't see that. Let me review that. 16:13:11 I can test tonight and update PR. 16:16:37 Okay, will keep on to review pile and move on then 16:17:05 https://github.com/ansible/ansible/pull/48971 16:17:09 #topic CloudEngine PRs 16:17:50 https://github.com/ansible/ansible/pull/57123 16:17:57 add a new module 16:18:03 want to use ftp 16:23:13 xuxiaowei0512: I'm not sure I follow what this module has to do with CE specifically 16:23:49 It looks like it just transfers a file to or from a remote FTP server? Is there more to that? 16:24:25 yes, A new module uses FTP to transfer files 16:24:59 Some scenarios must be used 16:26:19 xuxiaowei0512: can you not do this with https://docs.ansible.com/ansible/latest/modules/get_url_module.html 16:27:02 Some network environments can only use FPT 16:27:23 We already have some support for FTP transfers, and if you need more, it almost certainly should not be in a networking platform module 16:27:38 CloudEngine cant not use that 16:27:41 xuxiaowei0512: get_url supports ftp:// urls 16:28:17 (somewhat opaquely, but still) 16:28:46 CE software does not support it 16:29:48 I tested this method many times in our lab 16:31:11 I've noticed that way before, but it's useless. So we developed a FTP module 16:31:43 xuxiaowei0512: regardless, if you are looking for expanded FTP capabilities, either a PR to get_url or an new module in net_tools would be more appropriate 16:33:33 The next two PRs look reasonable 16:34:02 I'm going to skip to 57057 for a bit 16:34:38 xuxiaowei0512: Are terminal_initial_prompt and terminal_initial_answer actually used anywhere? 16:35:30 Oh, nevermind, I see how this works now 16:35:55 57057 is fine, too 16:36:04 thank you 16:37:04 As for the snmp PR, that is gonna need a more thorough review, and we need to move on. I'll see that someone looks over it 16:37:43 Ok 16:38:25 #topic onyx_telemetry_agent https://github.com/ansible/ansible/pull/57066 16:38:58 If you're in here, I don't know what your IRC handle is 16:40:49 Okay then, movin on 16:41:28 #topic Avi PRs 16:43:54 We have added few new modules and split avi_credentials due to no log handling 16:48:51 chaitanyaavi: so let's get into that avi_credentials thing for a bit 16:50:45 What exactly should be in avi_login_info? 16:51:43 username, tenant, controller ip, avi_version etc can go in avi_login_info 16:52:01 Is it a consistent enough set of fields that you could use suboptions here? 16:52:05 (https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_documenting.html) 16:53:56 For that matter, you could instead keep avi_credentials unified, document the various suboptions, and tag only the sensitive ones as no_log 16:55:36 Ok I will check and update the PR 17:08:10 As for the module PRs, there are a few notes, and none of them appear to have tests 17:11:54 we will add the tests are there any guidelines for the tests ? 17:12:40 chaitanyaavi: We do require unit tests (https://docs.ansible.com/ansible/latest/dev_guide/testing_units.html#testing-units) on all new modules. 17:14:11 We are way over, and I don't see the last person in here anyway 17:14:23 Ok we will add those 17:14:40 Thanks everyone for your time and patience 17:14:52 #endmeeting