16:02:08 #startmeeting Ansible Network Working Group 16:02:08 Meeting started Wed Nov 27 16:02:08 2019 UTC. 16:02:08 This meeting is logged and archived in a public location. 16:02:08 The chair is Qalthos. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:08 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:08 The meeting name has been set to 'ansible_network_working_group' 16:02:32 Liaf: oh it's meeting time, so there maybe others here that can help you 16:02:38 #chair ganeshrn justjais privateip pabelanger dmellado 16:02:38 Current chairs: Qalthos dmellado ganeshrn justjais pabelanger privateip 16:03:15 #topic Core Updates 16:03:33 gundalow: I've never been to the meeting. Any rules I should be aware of? 16:05:36 Not a lot new to mention since the last meeting. 16:07:07 #info {platform}_static_routes resource modules are in PRs for inclusion in 2.10 16:07:50 That's for the six platforms that the Ansible Core Team directly supports 16:08:18 Liaf: nop, just start typing in a bit when Qalthos asks for any other topics 16:09:41 #info We are officially announcing dropping `connection: local` for platforms using the persistent connection framework 16:10:21 +1 16:10:45 #info The exact details and timing of such will be clarified when we have more concrete details 16:11:25 * ganeshrn waves 16:11:31 But it has effectively moved from "someday" to "soon" 16:12:51 #info Note: this only affects modules using the persistent connection framework. This more or less means if you can use `connection: network_cli` instead today, you should already be doing that 16:14:11 #info Modules which only work with `connection: local` and have no other alternative will generally be unaffected 16:14:33 Qaltos: dropping connection local will be applicable only for 6 platforms that Ansible network team supports right? 16:15:58 iirc there are still some community platforms that support connection local with persistent connection and have not yet moved to network_cli 16:16:05 ganeshrn: The same issues that led to this change will also affect all other platforms that use persistent connections 16:16:27 Which issue? 16:16:33 So just off the top of my head, dellos{6,9,10) for example 16:17:53 ganeshrn: Rewriting the connection plugin inside the platform's action plugin 16:22:08 That's all that's new for this week, I think 16:22:40 #link https://github.com/ansible/community/labels/network is where this meeeing's agenda can always be found 16:23:20 And I don't see our ASA contributor around, so 16:23:24 hiya folks 16:23:29 #topic Open Floor 16:24:14 I want to connect to a microsense switch and get an "unreachable" back from ansible though the switch is reachable. I use ansible_connection: ssh with the module raw and have no idea how to debug this. 16:24:19 Qalthos: so this change will e applicable for platforms that handle network_cli/httpapi in the action plugins 16:25:09 thx, ios_config src vs lines and match exact seems to still generate an error about lines not being present. I think it's this error (https://github.com/ansible/ansible/issues/19884) still present 16:25:23 ganeshrn: If the action plugin rewrites the PlayContext connection value, then it will be affected 16:28:49 Liaf: The easiest way for anyone to help you debug that is if you post the output with at least `-vvvv` to some pastebin so others can see exactly what is happening 16:35:04 Qalthos: here's the pastebin: https://pastebin.com/hcua7B7s 16:38:25 Liaf how are you settling login credentials? 16:39:30 I have a groupvars/microsense.yml with ansible_user: admin and ansible_password: !vault.... 16:39:46 group_vars* 16:44:55 Liaf: Can you share the playbook as well? It looks like the only thing you are doing is sending "Logout" to the device, and the device happily closes the connection 16:48:40 Qalthos: actually I currently just send "Logout" because I wanted to test the connectivity before sending commands. 16:49:56 Qalthos: here's the playbook and the tasks.yml of the role I use for testing: https://pastebin.com/QuhXa4Lw 16:52:18 Liaf: Yeah, I'm not sure what you're trying to accomplish here. ansible sends "Logout" to the device, the device closes the connection, and ansible doesn't get a response and so marks the host as unreachable 16:53:13 Well I get the same result if I use "Device.Port.config[1/1].alias = 1.1" as a command. 16:57:23 And I can see on the switch that the conneciton is successful but no command gets send to the switch 17:00:02 Again, without logs there's very little I can guess about how ansible is interacting with a platform I've never used 17:01:03 qalthos any thoughts on ios_config w/"src" not working with the same features as "lines" seems kind of counter intuitive 17:01:12 Liaf: If you want to post the result of `ansible -m raw test-switch -a "Device.Port.config[1/1].alias = 1.1" -vvvv` I might be able to find something 17:02:48 idlemind: Sure does, but as far as I recall, it is still the expected behavior. 17:04:03 qalthos thx, so if i have a jinja template that i need match exact w/a before i'll need to render that to an array of lines (lookup/var/fact) and pass it to lines instead of using src 17:04:21 just want to make sure i'm going down the "right" path vs inventing a monster 17:05:25 and would patches be taken to improve src function or is it being intentional kept at that functionality? 17:05:41 idlemind: I believe that is the simplest workaround, and what is recommended in general (as templating through src has its own complications) 17:06:09 idlemind: If you're willing to go through it and clean it up, we won't say no 17:06:51 qalthos k cool thx, i'll start w/the workaround and i've feeling brave i may wonder into writing some code in the handling of src beyond just browsing which has taught me a lot already 17:08:23 Liaf: We can keep working through this if you like, but I'm going to close the meeting now 17:08:40 Thanks everyone for showing up 17:08:52 Qalthos: okay 17:09:46 Now that the meeting is over - I am going to re-ask this question. 17:09:49 hello ansible-networking folks. When it comes to merging pull requests, is there a traditional community review process? I notice the git project allows immediate merging of the proposed code and I am hesitant to just push it without review. 17:09:57 When it comes to merging pull requests, is there a traditional community review process? I notice the git project allows immediate merging of the proposed code and I am hesitant to just push it without review. 17:10:04 bah cant edit 17:10:10 My guess is that we will only have three more meetings this year, and then 12/25 and 1/1 will be skipped 17:10:16 #endmeeting