16:00:12 <Qalthos> #startmeeting Ansible Network Working Group
16:00:12 <zodbot> Meeting started Wed Jun 19 16:00:12 2019 UTC.
16:00:12 <zodbot> This meeting is logged and archived in a public location.
16:00:12 <zodbot> The chair is Qalthos. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:12 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:12 <zodbot> The meeting name has been set to 'ansible_network_working_group'
16:00:48 <Qalthos> #chair ganeshrn privateip trishnag dmellado pabelanger
16:00:48 <zodbot> Current chairs: Qalthos dmellado ganeshrn pabelanger privateip trishnag
16:00:57 <Qalthos> #topic Core Updates
16:01:32 <Qalthos> #info 2.9 freeze dates are up
16:01:35 <Qalthos> #link https://docs.ansible.com/ansible/latest/roadmap/ROADMAP_2_9.html
16:02:48 <Qalthos> #info The Network project board should be getting cleaned up for 2.9 as well, soon
16:02:58 <Qalthos> #link https://github.com/ansible/ansible/projects/10
16:04:03 <Qalthos> #link https://github.com/ansible/community/labels/network is where this meeting's agenda lives
16:04:18 <Qalthos> Let's get started!
16:04:27 <Qalthos> #topic Meraki PRs
16:04:50 <Qalthos> mrproper: I made some specific comments about your DOCUMENTATION strings
16:05:07 <mrproper> Yes, I saw those. I will integrate tonight and @ you in the PR when I have resolved them.
16:05:30 <Qalthos> There is one other thing I would like to ask about regarding your tests
16:05:35 <mrproper> Of course.
16:06:26 <Qalthos> I'm not familiar with /exactly/ how your connections are made, but I don't think you should have to specify `delegate_to: localhost` for every task
16:06:57 <mrproper> I know I could specify the delegate_to as part of a block, correct?
16:07:40 <Qalthos> I don't think you should need it at all. What connection are you using?
16:08:18 <mrproper> It's an API based connection. So it does connect from local to the Meraki API (n110.meraki.com as an example). I'd have to look at the exact URL, but it shouldn't matter.
16:08:30 <Qalthos> Or are you not specifying a connection type?
16:09:00 <mrproper> Am I able to globally specify a connection type for an integration test and have it apply to all tasks in there? That would help.
16:09:47 <mrproper> I expect this behavior will change when I can implement httpapi, but that's a topic for another day.
16:11:25 <pabelanger> does meraki give a VM to download, to test locally?
16:11:36 <Qalthos> The way the core tests work is to not have the tests themselves in main.yaml, and have main.yaml import the those tasks with a connection applied
16:11:44 <mrproper> pabelanger: No. It's fully API and web driven management. Picture is like interfacing with AWS in a way.
16:11:56 <Qalthos> let me get you some examples
16:13:04 <Qalthos> https://github.com/ansible/ansible/blob/devel/test/integration/targets/eos_config/tasks/cli.yaml#L13 further abstracts this to files in a tests folder
16:13:46 <Qalthos> But you could just as easily do something like
16:14:40 <Qalthos> - include: "local.yaml ansible_connection=local"
16:15:00 <mrproper> Then local.yaml would have the tests for the respective module?
16:15:07 <Qalthos> Exactly
16:15:37 <mrproper> That's a good idea. I will update the two new modules you commented on today to take that approach and see how well it works (I expect it will work well).
16:15:57 <Qalthos> mrproper: Thanks!
16:16:25 <mrproper> Qalthos: Before we move on, if I have some design questions and "brainstorming" I'd like to do on a future enhancement, is this an appropriate forum for it?
16:17:07 <Qalthos> mrproper: We can get in to that
16:17:39 <mrproper> I'll add it to the agenda for next week. I need to do a little more research to make sure I articulate the problem properly.
16:18:23 <Qalthos> mrproper: Sounds good.
16:18:27 <mrproper> Thank you.
16:18:33 <Qalthos> Anything else you want to cover today?
16:18:58 <mrproper> Not this week. I'm probably going to have a full week next week though. But thanks for your help today.
16:21:43 <Qalthos> #topic Open Floor
16:23:14 <pabelanger> I mostly wanted to point out that we finally have our network appliances, that on zuul.ansible.com, passing tests on ansible/ansible devel.
16:23:25 <pabelanger> so, thanks to all how helps with that effort
16:23:44 <pabelanger> and moving forward, should make PRs much easier to review, by provide test results
16:24:34 <mrproper> pabelanger: For my Meraki modules, it's all API driven so I can't provide a VM. But is it possible I can provide an API key we keep secret and it can possibly automate some of them?
16:25:18 <pabelanger> mrproper: possible, but there is some concerns with that (like leaking data). But it would be interesting to learn more about it
16:25:35 <mrproper> pabelanger: Lets talk about it on the side. I'd like to investigate if it's an option.
16:25:42 <pabelanger> +1
16:34:12 <Qalthos> Anyone else have anything to bring up here?
16:35:15 <xuxiaowei0512> Cloud you please review my PRs?
16:35:21 <Qalthos> xuxiaowei0512: Unfortunately I have to once again refer you to ikhan jtanner or gregdek for more information.
16:37:28 <xuxiaowei0512> ok
16:43:35 <Qalthos> Alright then, thanks for coming, everyone
16:43:42 <Qalthos> #endmeeting