Skip to content
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.

Network Working Group Meeting Agenda 2 #247

Closed
gundalow opened this issue Sep 20, 2017 · 104 comments
Closed

Network Working Group Meeting Agenda 2 #247

gundalow opened this issue Sep 20, 2017 · 104 comments

Comments

@gundalow
Copy link
Contributor

Please leave a comment regarding any agenda item you wish to discuss. If you don't show up for the meeting, your item will be skipped.

If your IRC nick is different from your Github username, leave that as well.

See https://github.com/ansible/community/tree/master/group-network for the schedule

All Core Networking issues (most recently updated at the top):
https://github.com/ansible/ansible/issues?q=is%3Aopen+label%3Anetworking+-label%3Aneeds_revision+sort%3Aupdated-desc

Network Working Group: https://github.com/ansible/community/tree/master/group-network

#ansible-network on Freenode IRC

@gundalow
Copy link
Contributor Author

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
Copy link
Contributor Author

gundalow commented Sep 20, 2017

From @saichint ansible/ansible#29143 Integration Tests only: nxos_udld, nxos_udld_interface, nxos_vxlan_vtep_vni MERGED

Migrated from #110 (comment)

@gundalow
Copy link
Contributor Author

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

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

@gundalow
Copy link
Contributor Author

From @Gelob ansible/ansible#30250 Arista EOS module doesn't properly parse vrfs

Migrated from #110 (comment)

@gundalow
Copy link
Contributor Author

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
Copy link
Contributor Author

gundalow commented Sep 20, 2017

From @caphrim007

ansible/ansible#30577 This module allows users to manage partitions on a BIG-IP MERGED
ansible/ansible#30584 Changes ignored and maintainers for the f5 modules. MERGED

Migrated from #110 (comment)

@privateip
Copy link
Contributor

ansible/proposals#76

@eoprede
Copy link

eoprede commented Sep 30, 2017

ansible/ansible#30767 This is 1 module out of roughly 20 that I am looking to contribute. My IRC name is Gesha24

Response

In alignment with other module submissions of this type, and based on discussions with members of the core team, and what is available as documentation here within the review, we are going to decline accepting this pull request.

The primary driver is that it is an arbitrary API module, that has no definable argument spec.

Each module should typically interact with one set of functionality. Should you decide to break this module up into individual components that deal with one set of functionalities with the API that have an explicitly defined argument spec, we would be happy to re-review.

@gundalow
Copy link
Contributor Author

gundalow commented Oct 3, 2017

ansible/ansible#31202

Should we add cdp information to the lldp fact, since it is basically the same. We could add an attribute source in ansible_net_neighbors with value cdp/lldp ?

@amuraleedhar
Copy link

Please merge ansible/ansible#31401
This moves files from lenovo folder to cnos folder

@caphrim007
Copy link

caphrim007 commented Oct 9, 2017

@amuraleedhar
Copy link

amuraleedhar commented Oct 10, 2017

Resolved all issues . Please merge
ansible/ansible#31508 MERGED
ansible/ansible#31509 MERGED
ansible/ansible#31510 MERGED
ansible/ansible#31512 MERGED
ansible/ansible#31565 MERGED
ansible/ansible#31580 MERGED
ansible/ansible#31696
These are util files, plugin files and doc file for enos modules
ansible/ansible#31401
This PR is to move modules from lenovo folder to cnos folder

@amuraleedhar
Copy link

Updated my PRs to be merged List shown above

@calfonso
Copy link

We need to complete the conversation around aggregates ansible/proposals#71 and decide if we are going down the loop route or not.

@dathelen
Copy link

dathelen commented Oct 16, 2017

ansible/ansible#32162 (irc nick dt-arista) MERGED & CP'd into 2.4

@gundalow
Copy link
Contributor Author

gundalow commented Oct 18, 2017

Review wanted on ansible/ansible#31807 Docs: Network getting started example

@saichint
Copy link
Contributor

saichint commented Oct 23, 2017

I would like to to merge these 2 PRs.
ansible/ansible#29143
ansible/ansible#28933 MERGED

@amuraleedhar
Copy link

amuraleedhar commented Oct 25, 2017

I would like to to merge these 2 PRs.
ansible/ansible#31696 MERGED
ansible/ansible#31401

@amuraleedhar
Copy link

Please merge PR ansible/ansible#43194
In this PR, I am moving the legacy code for ssh connectivity from Paramiko to persistent connection of Ansible for cnos_portchannel, cnos_vlag and cnos_interface module. Along with this I am trying to take care of the new CLIs introuduced for CNOS. And I have added UT codes for this module. This done exactly in line with PR#42500. This code has been tested on a CNOS Mars switch.

@Qalthos
Copy link
Contributor

Qalthos commented Jul 25, 2018

2018-07-25

Team status update

Actions

Minutes: https://meetbot.fedoraproject.org/ansible-network/2018-07-25/network_working_group.2018-07-25-16.00.html
Minutes (text): https://meetbot.fedoraproject.org/ansible-network/2018-07-25/network_working_group.2018-07-25-16.00.txt
Log: https://meetbot.fedoraproject.org/ansible-network/2018-07-25/network_working_group.2018-07-25-16.00.log.html

@amuraleedhar
Copy link

amuraleedhar commented Aug 1, 2018

Please merge PR ansible/ansible#43534
In this PR, I am moving the legacy code for ssh connectivity from Paramiko to persistent connection of Ansible for cnos_bgp, cnos_factory, cnos_reload, cnos_save, and cnos_showrun module. Along with this I am trying to take care of the new CLIs introuduced for CNOS. And I have added UT codes for this module. This done exactly in line with PR#42500. This code has been tested on a CNOS Bacon switch. Edited cnos_bgp to move code from cnos.py in Util folder to module code itself. This was done based on one review comment that cnos.py is too large and Qalthos suggested to move its code from util file to module file. Tested it too

@gundalow
Copy link
Contributor Author

gundalow commented Aug 1, 2018

Contributors Summit, AnsibleFest Austin 2018
What would you like to see discussed at the Community Summit, this is your opportunity to to ask questions either related to Networking, or the Community in general, feel free to add any topics to:
https://etherpad.openstack.org/p/ansible-summit-october-2018

@samerd
Copy link

samerd commented Aug 1, 2018

URGENT: unable to join meeting:
got this error:
[09:06] == Usermode change: +Ri
[09:06] == gateway/web/freenode/ip.209.116.155.178 is now your hidden host (set by syn.)
[09:06] == #ansible-network Cannot join channel (+r) - you need to be identified with services

please help

@mattclay
Copy link
Member

mattclay commented Aug 1, 2018

@samerd Due to increases in spam in IRC, most of them now require you register.

@gundalow
Copy link
Contributor Author

gundalow commented Aug 1, 2018

@samerd I've removed the requirement, please try and join again

@samerd
Copy link

samerd commented Aug 1, 2018

@mattclay: thanks, I'll register ASAP

@amuraleedhar
Copy link

amuraleedhar commented Aug 1, 2018 via email

@gundalow
Copy link
Contributor Author

gundalow commented Aug 2, 2018

Ansible Contributor Summit 6 (Part of AnsibleFest 2018 Austin, Texas)

As part of http://www.ansible.com/ansiblefest

  • AnsibleFest Austin will be on both Tuesday 2nd and Wednesday 3rd October 2018
  • The Contributor Summit will also be over two days, on Monday 1st and Thursday 4th October, from 9:30am to 4pm (time subject to change).

This is your event

Ansible succeeds because of its community, and this contributor summit is for you. If you have any topics to discuss, large or small, please be sure to post those topics on the etherpad. For topics that other had added please vote by adding +1

https://etherpad.openstack.org/p/ansible-summit-october-2018

Please see https://groups.google.com/forum/#!topic/ansible-devel/ivrpVbLya8g for further info

Attending in person

We realize that not everybody can attend in person, which is why we’ll again be arranging a video conference and a meeting time on IRC in #ansible-meeting to encourage remote participation. This has worked very well for the past Contributor Summits. We’ll be sending out an email with the information for remote participation about a week before the Contributor Summit.

If you want to attend in-person please sign up at: https://www.eventbrite.com/e/ansible-contributor-conference-austin-2018-tickets-48557063484

After signing up you'll receive an email from Eventbrite with a discount code for AnsibleFest Austin.

Attending remotely

Please add your name at the bottom of this etherpad: https://etherpad.openstack.org/p/ansible-summit-october-2018

Call to action

  1. Add ideas to https://etherpad.openstack.org/p/ansible-summit-october-2018
  2. Attending in person: https://www.eventbrite.com/e/ansible-contributor-conference-austin-2018-tickets-48557063484 then use discount code to sign up to AnsibleFest
  3. Attending in person OR virtually: Add your name to the end of https://etherpad.openstack.org/p/ansible-summit-october-2018
  4. Happy automating!

Questions?

Thanks for all of your contributions to Ansible, and we hope to see you in Austin! And if you have any questions at all, please let us know.

Speak to gundalow on Freenode, or anyone else in #ansible-devel

@gundalow
Copy link
Contributor Author

gundalow commented Aug 3, 2018

ios_config fails when creating macro "timeout trying to send command:" ansible/ansible#38420

@amuraleedhar
Copy link

amuraleedhar commented Aug 10, 2018

Please review and merge the following PRs
ansible/ansible#44398 MERGED
ansible/ansible#44559 MERGED

Thanks

-Anil

@yaplej
Copy link

yaplej commented Aug 11, 2018

Would appreciate it if you could also look these.
ansible/ansible#43861
ansible/ansible#43996

@ganeshrn
Copy link
Member

ansible/ansible#35817

@samerd
Copy link

samerd commented Aug 23, 2018

Please merge ansible/ansible#44527

@Qalthos
Copy link
Contributor

Qalthos commented Aug 29, 2018

2018-08-29

Team status and updates

  • core is frozen as of last week
  • commuinity modules freeze tomorrow
  • vyos and junos cliconf bugfixes
  • fixes for nxos_system and nxos_banner
  • ios & iosl2 platform bug fixes
  • working with firepower to get ftd roles and connection in for 2.7

Actions

Logs

Minutes: https://meetbot.fedoraproject.org/ansible-network/2018-08-29/network_working_group.2018-08-29-16.00.html
Minutes (text): https://meetbot.fedoraproject.org/ansible-network/2018-08-29/network_working_group.2018-08-29-16.00.txt
Log: https://meetbot.fedoraproject.org/ansible-network/2018-08-29/network_working_group.2018-08-29-16.00.log.html

@amuraleedhar
Copy link

amuraleedhar commented Aug 31, 2018

Please Merge the following PR
ansible/ansible#44953 Merged

Thanks

-Anil

@Qalthos
Copy link
Contributor

Qalthos commented Sep 5, 2018

2018-09-05

Team status and updates

  • 2.7 is branched, devel is now 2.8
  • 2.7rc1 is tomorrow, by last report
  • fixing issues with ios_user
  • working on issues related to asa_config/asa_acl/asa_command
  • vyos provider role WIP
  • configure_user task updates for eos & nxos

Logs

Minutes: https://meetbot.fedoraproject.org/ansible-network/2018-09-05/ansible_network_working_group.2018-09-05-15.59.html
Minutes (text): https://meetbot.fedoraproject.org/ansible-network/2018-09-05/ansible_network_working_group.2018-09-05-15.59.txt
Log: https://meetbot.fedoraproject.org/ansible-network/2018-09-05/ansible_network_working_group.2018-09-05-15.59.log.html

@amuraleedhar
Copy link

amuraleedhar commented Sep 6, 2018

Please Merge the following PR
ansible/ansible#45278 Merged

CLIs used in cnos_facts, cnos_command, its UT test modules and few CLI template files are in old format. This is getting corrected to new CLI format. Though we are having backward compatibility for this CLIs, it will get deprecated from 10.9 onwards. So we want to change them all to new CLI. Hence this PR is.
Please merge this so that Customers will have all latest CLI experience.

Thanks

-Anil

@amuraleedhar
Copy link

Please Merge the following PR
ansible/ansible#45483

Thanks
-Anil

@Qalthos
Copy link
Contributor

Qalthos commented Sep 12, 2018

2018-09-12

Team status and updates

  • 2.7rc1 went out last week, is available in the usual places
  • fixed a nothing to repeat issue with nxos terminal plugin on Python 2.6
  • fixed multiple parents issue for asa
  • fixed issues with new firepower modules

Logs

Minutes: https://meetbot.fedoraproject.org/ansible-network/2018-09-12/ansible_network_working_group.2018-09-12-16.00.html
Minutes (text): https://meetbot.fedoraproject.org/ansible-network/2018-09-12/ansible_network_working_group.2018-09-12-16.00.txt
Log: https://meetbot.fedoraproject.org/ansible-network/2018-09-12/ansible_network_working_group.2018-09-12-16.00.log.html

@gundalow
Copy link
Contributor Author

Network session as part of Austin AnsibleFest Contributors Summit

We will be having a Network session which you can join in person or remotely via IRC/VideoCall

Network Agenda: https://etherpad.openstack.org/p/ansible-summit-october-2018-network
Zuul Agenda: https://etherpad.openstack.org/p/ansible-summit-october-2018-zuul

Also there are two Zuul talks at Ansible Fest:

Top level Agenda: https://etherpad.openstack.org/p/ansible-summit-october-2018

Please feel free to add comments and vote (+1) on topics.

NOTE time and location of sessions may change

For more information about the Contributors Summit see #329 (comment)

If you have questions feel free to ask here, in IRC, or ping gundalow.

Hope to see you there either in person or online.

@Qalthos
Copy link
Contributor

Qalthos commented Sep 26, 2018

2018-09-26

Team status and updates

  • AnsibleFest is next week
  • As such, no IRC meeting next week
  • Ansible 2.7rc3 was released last week
  • 2.7.0 final should be out next week

Team Updates

  • Work in progress for juniper_junos provider role.
  • sshkey_fingerprint action plugin for ios provider.
  • work on cisco_ios role - bugfixes, plugin for checking dependant role version, test for zuul.
  • Other provider role work continues on integration tests and bugs.

Logs

Minutes: https://meetbot.fedoraproject.org/ansible-network/2018-09-26/ansible_network_working_group.2018-09-26-16.00.html
Minutes (text): https://meetbot.fedoraproject.org/ansible-network/2018-09-26/ansible_network_working_group.2018-09-26-16.00.txt
Log: https://meetbot.fedoraproject.org/ansible-network/2018-09-26/ansible_network_working_group.2018-09-26-16.00.log.html

@Qalthos Qalthos closed this as completed Sep 26, 2018
@samerd
Copy link

samerd commented Oct 1, 2018

Please welcome @anasbadaha (https://github.com/anasbadaha) a new team member of Mellanox-Onyx
His first PR: ansible/ansible#46218
Please review this PR and merge if OK with you

@anasbadaha
Copy link

Thanks a lot @samerd

@Qalthos
Copy link
Contributor

Qalthos commented Oct 1, 2018

Hi, now that 2.7.0 is soon to be out I've created a fresh agenda.

Please subscribe to #363

@ansible ansible locked and limited conversation to collaborators Oct 1, 2018
@dagwieers
Copy link
Contributor

As being discussed at AnsibleFest 2018, we would like to learn how we can extend httpapi with (very) specific needs for different connection methods (all different types of REST), for Cisco this is different technologies like IMC, UCS, ACI, MSC, Tetration, ...

One problem is the lack of documentation or code annotations that help understand how we ought to extend it. The second problem is that by extending the httpapi framework you may break the original use-cases without the ability to test.

So the easiest path is everybody does their own implementation, but even for Cisco only there's a benefit of having a single framework.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests