Community: Network Working Group Meeting Agenda

[gundalow]

MOVED TO NEW AGENDA https://github.com/ansible/community/issues/247

[caphrim007]

@gundalow I've updated comments for PR554. PR1000 is read to ship if others are pleased with it

[gundalow]

https://github.com/ansible/ansible/pull/16434 - Enabling possibility to use different configuration modes for juniper modules - What version of Python?

UPDATE: py2.4 needs to be supported still

[caphrim007]

• (bugfix) https://github.com/ansible/ansible-modules-extras/pull/2907 does this need to branch off of a different upstream branch?

Edit by gundalow: The above PR is to a module that was added in 2.2. As 2.2 hasn't been branched yet devel is the only place this code needs to go. I've merged it into devel

[gundalow]

@privateip It would be good to get the following bugfix into 2.2 https://github.com/ansible/ansible-modules-extras/pull/3216

< caphrim007> in a perfect world, but its not a total disaster if it doesnt
< caphrim007> it can go in a .1 release if needed
< gundalow> I'd be suprised if there wasn't another RC, though you never know
< caphrim007> the bug doesnt affect any running config, it just affects the reported changed-ness

[gundalow]

< skg-net> did you know whether @privateip got a chance to upload the vendor agnostic role from AnsibleFest

[gundalow]

skg-net also asked for a list of Network changes between 2.2 RC1 and RC2

[gundalow]

Ansible 2.2 Networking blog post https://www.ansible.com/blog/ansible-network-updates

[ericchou1]

Hi, for the standing meeting, I would like to get some feedback on the a10_command / a10_config modules that I'd like to contribute to. In the new API, a10 consolidated cli.showInfo (for show outputs) and cli.deploy (for pushing configs) into just cli.deploy. For config it will return status code where show commands it will also include the output. I would like to know if the community prefers having two modules: a10_command + a10_config that is similar to other vendors today, or just one module a10_config that perhaps include a knob to capture returned outputs. Thanks!

Discussed 2016-11-09

• Separate modules
• Eric will provide a VM for testing
• New modules will come with tests, we can assist with that

[ganeshrn]

• ansible/ansible-modules-core#5679
• ansible/ansible-modules-core/issues/5483
• ansible/ansible-modules-core/issues/5636

IRC: ganeshnalawade, gnalawad

[gundalow]

@ericchou1 Change POST body in axapi_call_v3() and axapi_authenticate_v3()
https://github.com/ansible/ansible/pull/18104

[gundalow]

[network] Default key_policy to ignore
https://github.com/ansible/ansible/pull/18238

[gundalow]

nxos_vlan returns "Command does not support JSON output"
https://github.com/ansible/ansible-modules-core/issues/3876

[phil-dileo]

Just a few comments:

• [x] Banner support for eos_config
• [x] Is there a plan to support updates when using src in eos_config
• [x] Can we set the timeout for module execution in eos_command. EG, if I'm downloading a file, the module will exit/fail before it completes.

[gundalow]

https://github.com/ansible/ansible-modules-core/pull/4912

[gundalow]

https://github.com/ansible/ansible-modules-core/issues/5041

[gundalow]

https://github.com/ansible/ansible-modules-core/issues/5214

[gundalow]

Update on timeout work (2.2 and 2.3)

[ericchou1]

Proposing an Ansible Network group Sprint for PyCon 2017, https://us.pycon.org/2017/ sometime between May 22 - 25.

[ganeshrn]

https://github.com/ansible/ansible-modules-core/issues/5738

[gundalow]

More details about upcoming repo merge
Important to review for those looking to contribute to module development https://groups.google.com/forum/#!topic/ansible-project/9WpXraBSLz8

[gregdek]

@ericchou1 want to ping me via email about Networking sprint? I've got some ideas. greg at ansible dot com.

[ganeshrn]

Add support to retrieve below ansible facts from device

• operating system
• kernel
• architecture
• ip address
• memory

[gundalow]

There are no IRC meetings this week.

[ismc]

asa_config does not make config change

https://github.com/ansible/ansible/issues/19183

@ismc What's your IRC nick?

[gundalow]

No IRC meetings next week. Next meeting is on Wednesday 4th Jan.

[gundalow]

Should we add jxmlease & junos-eznc into test/runner/requirements/units.txt

https://github.com/ansible/ansible/pull/20034 Add unit testcase for junos_command module

Discussed 2017-01-11

• Mock the interface, rather than require junos-eznc
• We will have Junos testing via Shippable, which will include this library
• Currently (Jan 2017) Junos is the only network platform that requires 3rd party libraries.
• In the future fortigate box management may require pyfg

[dentarg]

I would like to know when https://github.com/ansible/ansible-modules-extras/pull/3350 is going to ship, and if there's anything I can do to help to get it to ship ASAP :) Unfortunately I can't attend tonights meeting (19:00 UTC) (I will be in the channel, but idle).

[bjolivot]

As discussed with @gundalow in irc channel :
here's my situation
I need to add fortigate box management in ansible
I allready have public library doing lot of work (connection, cli, configuration update...)
the lib : https://github.com/spotify/pyfg
I don't understand how use networkmodule helper with it and i'm currently using only ansiblemodule helper
I understand I need to add some fortigate provider in module_utils
Don't know how to do this.

Other questions:
Is there some helper for ip adress value check
idem for netmask
idem for complex ip address (1.2.3.4/21 or 1.2.3.4 255.0.0.0)

[gundalow]

@dentarg https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/roadmap/ROADMAP_2_3.rst states February/March 2017 for 2.3

[gundalow]

Based on discussion with from trepanning_io (@dgjnpr) on networktocode

• One would assume that _facts modules populate the standard ansible_facts
• http://docs.ansible.com/ansible/junos_facts_module.html#return-values
  
  
  
  • Does the returns template need to make it clearer that these values need to be registered: + links to doc
  
  
• Should all _facts modules have an example of register
• What's the longer term plan for _facts modules, will they populate the main ansible_facts

[dgjnpr]

Since this update there has been some further discussion on this matter with @privateip

• junos_facts does return the facts learned from the Junos device - but you have to know which facts are returned in order to access them
• the above behaviour appears to be consistent with the setup module used by default on servers

In light of what's been learned I suggest the documentation makes it clear what is meant by returned values. The current documentation makes it appear that a variable (of type dict()) called ansible_facts is returned which can be accessed by subsequent tasks/plays.

[gundalow]

From @robphoenix
https://github.com/ansible/ansible/issues/19281 Feature Idea: Cisco IOS confirm option

Although I can see a use-case for this, I'm not sure how this would be idempotent, of if it fits within Ansible's way of working.

[gundalow]

https://github.com/ansible/ansible/issues/19382 [regression over 2.2] ios_config now returning .updates

We've discussed this a bit, though we didn't come formalise it.
Perhaps we should be returning .commands instead?
We may wish to standardise this across all network modules.

[gundalow]

https://github.com/ansible/ansible/pull/20262 nxos_vxlan_vtep_vni.py improvements
Inc changes to module_utils/netcfg.py

[ganeshrn]

https://github.com/ansible/ansible/issues/19107

[gundalow]

Notes from 2016-02-08

• We will be doing a blog post on the improvements to the networking modules shortly (thanks to andriusb for putting that together) it will get announced here (in this ticket & in IRC meeting)
• Partner submission deadline for Ansible 2.3 for Networking changes is 14th Feb

[dgarros]

Discuss what are the next steps for all aos_* modules & dynamic inventory scripts:
https://github.com/ansible/ansible/pulls/dgarros

2017-02-15: privateip to review and merge

[gundalow]

2017-02-15 Meeting Log
https://meetbot.fedoraproject.org/ansible-meeting/2017-02-15/ansible_networking.2017-02-15-16.18.html

[gundalow]

Ansible 2.3 RC1 has been released for testing
Please see https://groups.google.com/forum/#!topic/ansible-devel/V2ESSQqLnS0 for details
As you may know there have been many changes to the networking code between 2.2 and 2.3.
We would appreciate your help testing.
Any issues, please raise at https://github.com/ansible/ansible/issues/new
Thanks!

[gundalow]

Hello lovely network people

Just a reminder to please test Ansible 2.3 RC1.

If you could please make the time to test RC1 against your existing playbooks that would help us a lot. Most of the networking common code and a large chunk of the modules have been rewritten. It's possible there maybe some edge cases that we haven't identified. After all, we can only fix what we know is broken :)

RC1 details https://groups.google.com/forum/#!topic/ansible-devel/V2ESSQqLnS0

If during your testing you notice anything we could improve regarding logging and debug support please add a comment to https://github.com/ansible/ansible/issues/22703

[calfonso]

2017-03-22 Meeting Log
https://meetbot.fedoraproject.org/ansible-meeting/2017-03-22/network_meeting.2017-03-22-16.00.html

[gundalow]

New blogpost on Network Device Authentication with Ansible 2.3 https://www.ansible.com/blog/network-device-authentication-with-ansible-2-3

Ansible 2.3 RC3 is due to be released on Friday 31st March

Please do take the time to read the blog post and test Ansible 2.3

[gundalow]

Ansible 2.3 RC3 has been released https://groups.google.com/forum/#!topic/ansible-devel/X8sYLl-ZuTY

Please test at your earliest convenience. There have been a lot of changes to Networking in 2.3.

RC3 adds various bug fixes as well as better logging, which should help if you have connection issues

https://groups.google.com/forum/#!topic/ansible-devel/X8sYLl-ZuTY

In case you've not seen them, we have two blog posts:

https://www.ansible.com/blog/network-device-authentication-with-ansible-2-3
https://www.ansible.com/blog/networking-features-in-ansible-2-3

We welcome your feedback, after all, we can only fix what we know is broken. If you spot any issues please raise via https://github.com/ansible/ansible/issues/new

Thanks again for your help

[gundalow]

Ansible 2.3.0 FINAL has been released. Thank you for all your help with this release
https://groups.google.com/forum/#!topic/ansible-project/aKnggI-Y8dk

In the network space:

• We’ve introduced new performance upgrades and additional vendor support. For more information about what’s new with Ansible Networking, take a look at our blog post (https://www.ansible.com/blog/networking-features-in-ansible-2-3), and check out the expanded list of Network Modules now available here: http://docs.ansible.com/ansible/list_of_network_modules.html.
• This release brings the total number of networking modules up to 267.

[dgjustice]

https://github.com/ansible/ansible/issues/20260 nxos_vxlan_vtep_vni specifically and general nxos cleanup.

Merged into devel, cherry picked into stable-2.3

[privateip]

https://github.com/ansible/ansible/issues/23517 discuss a refresh of the ipaddr.py filters for 2.4

2016-04-19

• PR added https://github.com/ansible/ansible/pull/23526
• Need to review document and add unit tests to defend the documentation & implementation

[trishnaguha]

https://github.com/ansible/ansible/pull/23728 if dell os maintainer turns up. MERGED

[privateip]

discuss adding feature to auto add ssh key per host as option instead of global auto add of ssh keys for persistent connections

[gundalow]

https://github.com/ansible/ansible/pull/24024 Splitting of modules/networking/ DONE

https://docs.ansible.com/ansible/list_of_network_modules.html

https://docs.ansible.com/ansible/list_of_net_tools_modules.html

[gundalow]

Ansible 2.2.3 FINAL released, 2.1.6rc1 and 2.3.1rc1 available for testing

All of these releases address at least one CVE (listed below). Users of 2.2.x should upgrade to 2.2.3 as soon as possible. The CVE impacting 2.1.x and 2.3.0 is MODERATE in nature, however users should look to upgrade as soon as the final releases are done.
https://groups.google.com/forum/#!topic/ansible-devel/etlpnJDerY0

A number of fixes for Network modules have been included

[gundalow]

Ansible Contributor Summit 4 (Part of AnsibleFest 2017 London)

We are happy to announce our fourth Ansible Contributors Summit!
AnsibleFest London (http://www.ansible.com/ansiblefest) will be on Thursday 22nd June, and the Contributor Summit will be held on Wednesday 21st June, from 9:30am to 4pm (time subject to change).

Contributors Summit is a day-long working session with the core team and key contributors to discuss important issues affecting the Ansible community. You can participate in person or online

Proposed topics: https://public.etherpad-mozilla.org/p/ansible-summit-june-2017

See https://groups.google.com/forum/#!topic/ansible-devel/stUITiM6hMs for more info

[calfonso]

2017-05-17 Meeting Log
https://meetbot.fedoraproject.org/ansible-meeting/2017-05-17/network_meeting.2017-05-17-16.01.log.html

[trishnaguha]

Ansible 2.3.1rc2 is available for testing which can be found here https://releases.ansible.com/ansible/.
A number of fixes for Network modules have been included.

[caphrim007]

~~ https://github.com/ansible/ansible/pull/24848 MERGED

[trishnaguha]

2017-05-24 Meeting log
https://meetbot.fedoraproject.org/ansible-meeting/2017-05-24/network_meeting.2017-05-24-16.00.log.html

[gundalow]

Ansible 2.4 Partner submission deadline
The next version of the open source Ansible project (version 2.4) is currently in development, and Ansible Engineering would like to provide ample notice for partners interested in having code reviewed and included in time for its release. The following milestones have been created as submission deadlines for code (core code, modules, plug-ins, etc.) in order for proper expectations to be met:

• Core Code Development Freeze Date: 2017-Jul-15
• Partner Modules Submission Deadline: 2017-Jul-15
• Partner Modules Development Freeze Date: 2017-Aug-01
• GA: August/September (tentative, subject to change)

In order for partner modules to be properly triaged, reviewed, tested, and included into Ansible 2.4, all module updates and submissions must be completed by 2017-Jul-15 for high probabilities of inclusion (subject to review).

Testing Expectations for Network Modules
In an effort to ensure the highest quality of network modules, all contributions must now include unit tests to exercise each feature of the module. Additionally, do to the nature of mocked interfaces unit tests use, network modules should also include integration tests. The integration tests should be runnable against supported versions of network devices as well as their virtual machine images or containers if available.

Examples of existing unit tests can be found in https://github.com/ansible/ansible/tree/devel/test/units
Examples of existing integration tests can be found in https://github.com/ansible/ansible/tree/devel/test/integration

[gundalow]

https://github.com/ansible/ansible/pull/25680 asa_config

[gundalow]

Ansible Contributor Summit 4 (Part of AnsibleFest 2017 London)

Agenda for Contributor Summit has finalised can be found at https://public.etherpad-mozilla.org/p/ansible-summit-june-2017-agenda.

As a reminder, it will be in #ansible-meeting and BlueJeans

Note that there are sub pages for each topic. It's on the sub pages where you can add any topics there, rather than on the main agenda page.

Note that there isn't a specific Networking section, we have a lot of other topics to cover in the limited time. If people as interested we could organise a online Networking meetup, or have a more structured IRC meeting to go over some of the topics if people can attend.

[mikewiebe]

Want to discuss resolution of the following issues in advance of the Core Code Development Freeze Date: 2017-Jul-15.

NXOS Impacting Errors in 2.4

https://github.com/ansible/ansible/issues/25541
https://github.com/ansible/ansible/issues/25515
https://github.com/ansible/ansible/issues/25514
https://github.com/ansible/ansible/issues/25513
https://github.com/ansible/ansible/issues/25511
https://github.com/ansible/ansible/issues/25510
https://github.com/ansible/ansible/issues/25509
https://github.com/ansible/ansible/issues/25507
https://github.com/ansible/ansible/issues/25505
https://github.com/ansible/ansible/issues/23926
https://github.com/ansible/ansible/issues/23924

[gundalow]

@bdlamprecht It sure is. Can you join #ansible-meeting on freenode IRC now? What's your IRC name? We have a meeting going on right now :)

[bdlamprecht]

Yeah, I'm on there now, same username: bdlamprecht

[gundalow]

Due to Contributors Summit & AnsibleFest

NO MEETING: Wednesday 21st June

NEXT MEETING: Wednesday 28th June

[saichint]

Would like to discuss the PR in tomorrow's meeting.
https://github.com/ansible/ansible/pull/26156 fix for nxos_acl_interface idempotenc MERGED

[gundalow]

https://github.com/ansible/ansible/issues/26146 Error with paramiko 2.1.0 <--> 2.2.1: Unicode-objects must be encoded before hashing

[gundalow]

https://github.com/ansible/ansible/pull/26142 Add nxos_acl_interface integration tests CLOSED

[mikewiebe]

https://github.com/ansible/ansible/pull/25966 Fix nxos_acl module and add IT tests MERGED

[gundalow]

https://meetbot.fedoraproject.org/ansible-meeting/2017-06-28/network_working_group.2017-06-28-16.00.html
https://meetbot.fedoraproject.org/ansible-meeting/2017-06-28/network_working_group.2017-06-28-16.00.log.html

[jmighion]

~Would like to add PR #26261 to the agenda MERGED

[gundalow]

#ansible-network is the place to be on Freenode to be, please join, even if you only idle.

[jmighion]

https://github.com/ansible/ansible/pull/26625

[rahushen]

PR
ansible/ansible#26617 MERGED

Issues
ansible/ansible#26024
ansible/ansible#26159
ansible/ansible#26260
ansible/ansible#26262
ansible/ansible#26544

[mikewiebe]

PR
https://github.com/ansible/ansible/pull/26616 MERGED

[dagwieers]

~https://github.com/ansible/ansible/pull/26029 New module: access Cisco ACI (network/aci/aci_rest)~

[caphrim007]

• https://github.com/ansible/ansible/pull/26842 MERGED
• https://github.com/ansible/ansible/pull/27035 MERGED

[dagwieers]

Could be useful to list the technology domains in the Network WG member list. I already did as an example.

Also added an ACI page to the wiki to help in collaboration. This may be helpful for the specific technology domains to collaborate. We may want to list this somewhere in the Network WG info page ?

[privateip]

That's a great idea..... +1 for sure

On Jul 18, 2017 1:05 PM, "Dag Wieers" [e-mail] wrote:

Could be useful to list the technology domains in the Network WG member
list
https://github.com/ansible/community/blob/master/group-network/README.md#active-members.
I already did as an example.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ansible/community/issues/110#issuecomment-316130557,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZToi3DoltmOcRhQV4CEUMn9cWNLnDqks5sPOXggaJpZM4JGPlT
.

[FrederikSuijs]

Hello, I'm working on a playbook to automate some IOS routers. I'm stuck at task where a ios_command expects returns a prompt and asks for a confirmation. It looks ansible can't handle this. I found something similar at https://groups.google.com/forum/#!topic/Ansible-project/Sb4EIJIOGY8 or https://stackoverflow.com/questions/40045342/ansible-cisco-ios-and-reload-command
I cant find any official documentation about this or the capability to handle a prompt.
I tried in the Ask an Expert - Networking session, but they pointed me to here.

Is there any way to accomplish what I'm trying to do?

[calfonso]

Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-19/network_working_group.2017-07-19-15.59.html
Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-19/network_working_group.2017-07-19-15.59.log.html

[jmighion]

https://github.com/ansible/ansible/pull/27130

[rahushen]

PRS:
ansible/ansible#26924

Issues:
ansible/ansible#26024
ansible/ansible#26260
ansible/ansible#26262
ansible/ansible#26827
ansible/ansible#27066
ansible/ansible#27138
ansible/ansible#27139
ansible/ansible#27177
ansible/ansible#27289
ansible/ansible#27292

[mikewiebe]

PRs:
https://github.com/ansible/ansible/pull/26913
https://github.com/ansible/ansible/pull/27190

[calfonso]

Meeting minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-26/network_working_group.2017-07-26-15.59.html

Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-26/network_working_group.2017-07-26-15.59.log.html

[skg-net]

• Vendor Neutral Model - Roadmap
• CliConf for DellOS modules
• Openswitch Ansible Modules

[akmohammed]

Lenovo CNOS module reference on CHANGELOG.md file

[rahushen]

PRs:
ansible/ansible#26924
ansible/ansible#27652

Issues:
ansible/ansible#26262

[Qalthos]

Meeting minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-08-02/network_working_group.2017-08-02-15.59.html

Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-08-02/network_working_group.2017-08-02-15.59.log.html

[amuraleedhar]

ansible/ansible#27767 MERGED

[rahushen]

PRs:
ansible/ansible#26924 MERGED
ansible/ansible#27935 MERGED

Issues:
ansible/ansible#26024

General discussion:

• adoption of N9K virtual machines for integration testing by ansible
• some P1 issues marked with 2.5.0 milestones which need to be 2.4.0

[amuraleedhar]

Hi,

Can u please merge
PR
ansible/ansible#28056
ansible/ansible#28057

The changes are addressing issues reported by coverity on static code analysis, dynamic code analysis and security vulnerabilities in module code

[gundalow]

Ansible Contributor Summit 5 (Part of AnsibleFest 2017 San Francisco)

When: 2017-09-06:
Notes: https://public.etherpad-mozilla.org/p/ansible-summit-september-2017
Event will be in person + online (Video + IRC)

Agenda is open for topics for the next Contributors Summit

Please add (and vote +1) for any topics.

[salman1485]

Can we discuss https://github.com/ansible/ansible/issues/26577 in today's meeting? - Salman

IRC:Salman_ = GitHub:@AnsiNoob

[dagwieers]

Can we discuss the Cisco ACI modules ? And how this relates to the module freeze ?

Update from Gundalow: We've reached module freeze so no new modules for 2.4, so closing this item

[MeganLiu]

Is it possible to go though https://github.com/ansible/ansible/pull/26855 on today meeting? I forgot to add it but realized that I should have added before. I am joining the meeting and waiting there. MERGED

[Qalthos]

Meeting minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-08-16/network_working_group.2017-08-16-16.01.html
Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-08-16/network_working_group.2017-08-16-16.01.log.html

[gundalow]

NOTE: meetings are canceled for the week Aug 21st to 25th due to 'all hands' meeting for the core team. We will resume normal schedule after that.

[amuraleedhar]

ansible/ansible#28589 MERGED

This contains fix for bug on Image download onto switches. Bug was that even though download succeeds the status of play book shows as failed

[gundalow]

NOTE: meetings are canceled for the week September 4th through 8th due to AnsibleFest San Francisco. We will resume normal schedule after that.

[gundalow]

New Parsing feature in 2.4.0
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/playbooks_filters.rst#network-cli-filters

We would welcome lots of testing on this new feature. Any feedback via #ansible-network on Freenode or in GitHub issues. Thanks in advance.

[gundalow]

For those joining for the Contributors Summit (in person or via IRC/BlueJeans) we will be having a "Network Working Group" session. Feel free to add topics to
https://public.etherpad-mozilla.org/p/ansible-summit-september-2017

[gundalow]

@saichint No IRC meetings this week.

NOTE: meetings are canceled for the week September 4th through 8th due to AnsibleFest San Francisco. We will resume normal schedule after that.

[ganeshrn]

Decide on Ansible version to remove top level credential arguments https://github.com/ansible/ansible/pull/28984
The decided version needs to be added in deprecation warning.

Agreed: Top-level arguments will be present in 2.8, removed in 2.9

[amuraleedhar]

Please merge ansible/ansible#29953 bug fixes pertaining to vlan name set and device errors MERGED

[amuraleedhar]

Can we discuss ansible/ansible#29018 in today's meeting? - Anil RESOLVED

[gundalow]

Wednesday 13th September 2017

Key points

• ACTION everyone please review https://github.com/ansible/community/wiki/Network:Core-roadmap-2.5 - Feedback in #ansible-network
• Proposals will be created for the larger blocks of work in 2.5.
  
  
  
  • This will allow discussion on interface and implementation detail to take place
  
  
  • Once created proposals will be linked from the agenda
  
  
  • Proposals for 2.5 will be discussed in weekly IRC meetings. Comments also welcome on the proposals themselves.
  
  
• Ideas for Ansible 2.6 and later releases
  
  
  
  • We welcome suggestions for future releases at any point.
  
  
  • Larger blocks of work should also use the proposals process as well
  
  
  • Monthly (schedule to be announced) will be used to discuss Ansible 2.6+ issues and proposals
  
  
• Top-level credentials (username:, password:, host:)
  
  
  
  • top-level credentials will be supported until 2.8 and deleted in 2.9
  
  
  • Run time deprecation notes will be updated to detail the above
  
  
  • Options will still be valid under provider:
  
  
• Ansible 2.4 Release Candidates (RCs) and Final Release
  
  
  
  • 2.4rc3 is about to be released. Please test ASAP. There is only a short time window between this and the final release.
  
  
  • 2.4rc4 (expected to be the final rc) will be release on Saturday. Should be rc3+few NXOS fixes
  
  
• New network platforms
  
  
  
  • If you are interested in creating a new network platform please speak to us #ansible-network before you start coding so we can guide you in the right direction.
  
  

Please review the following links for full discussion:

• Summary: https://meetbot-raw.fedoraproject.org/ansible-network/2017-09-13/network_working_group.2017-09-13-16.00.html
• Full log: https://meetbot-raw.fedoraproject.org/ansible-network/2017-09-13/network_working_group.2017-09-13-16.00.log.html

Proposals: https://github.com/ansible/proposals/ (networking items to be created

[gundalow]

Ansible 2.4.0 RC3 is available for testing.
Lots of networking improvements in 2.4, so if you can find the time to test it this week that would be great
If you find any issues please report them at https://github.com/ansible/ansible/issues/new
https://groups.google.com/forum/#!topic/ansible-devel/PjBtOkwbt5I
Thanks in advance

[amuraleedhar]

Please merge ansible/ansible#30404
This contains bug fixes pertaining to image download on to new devices MERGED into devel and released in 2.4.0

[gundalow]

All,
If you could raise PRs to update the list of Network Group members on https://github.com/ansible/community/tree/master/group-network that would be very helpful given the large and growing community.
Add GitHub, real name, company/affiliation and IRC name (if different to GitHub)
Thanks in advance.

[gundalow]

Proposals for 2.5 that we'd like your input on:

• https://github.com/ansible/proposals/issues/71 Hold off and redesign Aggregates
• https://github.com/ansible/proposals/issues/70 Hold off and redesign Declarative Intent

We welcome all of your input on this, making sure we implement something that's useful and easy to understand.

[Gelob]

Can we discuss https://github.com/ansible/ansible/issues/30250 ?

Migrated to new agenda https://github.com/ansible/community/issues/247#issuecomment-330794213

[caphrim007]

• https://github.com/ansible/ansible/pull/30577
• https://github.com/ansible/ansible/pull/30584

Migrated to new agenda https://github.com/ansible/community/issues/247#issuecomment-330795472

[gundalow]

Ansible 2.4.0 FINAL

https://groups.google.com/forum/#!msg/ansible-announce/IrLR3pjNZnk/J8s-uC5EAgAJ
Lot of network improvements, especially to NXOS
Please do take a look
If you find any bugs please report them at https://github.com/ansible/ansible/issues/new

Thank you all for your help during this release.

[gundalow]

Hi, now that 2.4.0 is out I've created a fresh agenda.

Please subscribe to https://github.com/ansible/community/issues/247

NO MORE COMMENTS HERE, PLEASE USE https://github.com/ansible/community/issues/247

[dagwieers]

@gundalow You can lock the conversation. That's what we do when moving the agenda. (Just did it here)