16:00:09 #startmeeting Network Working Group 16:00:09 Meeting started Wed Mar 8 16:00:09 2017 UTC. The chair is gundalow. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:09 The meeting name has been set to 'network_working_group' 16:00:15 #chair rcarrillocruz 16:00:15 Current chairs: gundalow rcarrillocruz 16:00:41 #info Agenda https://github.com/ansible/community/issues/110 16:00:44 #topic Open Floor 16:01:45 #info 2.3 is due on RC 1 is on the 15th March, there are a few networking issues we're working through 16:03:00 Isn't module freeze tonight, though ? 16:03:54 New feature freeze was (from memory) last week 16:03:57 * gundalow finds the email 16:04:05 ahh 16:04:59 Core Freeze was March 5th 16:05:10 Which means no new features (therefore no new modules) 16:05:20 I see 16:06:33 #info the `stable-2.3` branch will be created at RC1, at which point `devel` will become 2.4, and new modules & features can start to be merged again 16:08:03 That's it from me 16:12:04 allanice001: How you doing? Got anything you'd like to raise? 16:12:13 I'm good 16:12:17 Nothing from me 16:13:44 cool 16:13:53 hi 16:13:55 Will leave this running for a bit incase anyone joines later on 16:13:58 Hello resmo :) 16:14:34 I have nothing to add but kind of likes the progress in this area 16:14:53 we are already working to use it 16:14:56 resmo: what progress in particular? 16:15:06 network modules in general 16:15:13 :) 16:15:33 That's good to hear 16:17:09 since there is no other topics I would be curious how you test the network modules? 16:17:25 there seems to be an automated testing 16:17:33 how does this look like? 16:17:56 Sure 16:18:17 (only if you have time) 16:18:30 Got 5 minutes, it's a good question 16:18:47 Remo, I think time is the least worry tonight :P 16:18:47 https://github.com/ansible/ansible/blob/devel/test/integration/README.md#network-tests shows how the tests are structured 16:19:48 Tests exist in https://github.com/ansible/ansible/tree/devel/test/integration/targets/ split by module name 16:20:00 ok, that clear to me so far 16:20:02 Currently we run those manually against some VMs 16:20:10 outside of the normal CI pipeline 16:20:23 ok, so you do not have e.g. cisco nexus devices etc 16:20:36 where you test against? 16:22:25 The machines listed in https://github.com/ansible/ansible/blob/devel/test/integration/inventory.network exist as virtual machines behind a VPN that we have access to 16:22:58 Moving forward we will be spinning up Docker or EC2 instances of appliances for testing as part of the usual CI pipeline 16:23:47 So, for example if you test any of the ios_* modules (or module_utils/ios*) we will run all the ios integration tests via GitHub PRs, e.g. same as non-network code 16:24:56 That was partly working, then got a bit broken, should be added back soon 16:25:22 I had ios & vyos mostly working that way 16:25:47 Arista will be providing a Docker Container image (if that's the right term) for EOS, so that will be tested in the same way 16:26:57 resmo: that make sense? 16:27:09 Bit of a state of flux at the moment 16:28:32 Some of the network venders also have tests that they've created and run themselves. They live in test/integration/*roles* https://github.com/ansible/ansible/tree/devel/test/integration/roles 16:28:55 test/integration/targets = runnable by ansible-ci, e.g. we can spin up a Docker/EC2 instances 16:29:05 where as 16:29:26 test/integration/roles = require manually setup things to test against 16:29:51 We also have been adding unit tests 16:29:58 https://github.com/ansible/ansible/tree/devel/test/units/modules/network 16:39:20 #endmeeting