-
Notifications
You must be signed in to change notification settings - Fork 144
Network Working Group Meeting Agenda 3 #363
Comments
|
commenting on top of @dagwieers 's comment here For F5 specific stuff, we have a special token that is generated (and required to be re-used) after we auth with a user/pass. we need to put that token in a Header which we send with future requests. This token needs to be deleted at the "end of the session" too otherwise we'll eventually run out of available tokens. So right now we establish a connection (non-httpapi) make all our calls with the token, and then delete the token upon success/fail. We have a couple modules that also check to see if the box is online to begin with. Today this isnt a problem because we handle the connection in the module. If the connection is moved out of the module, then the httpapi connection will need to know how to deal with this. In our case, it's technically equivalent of wait_for and some other custom checks. I imagine this would be a little ugly to bake into the httpapi (or equivalent) code. Finally, we have several modules that reboot the device and wait for it to come back online. This rebooting invalidates the token as well. We would need to be able to mimic this in httpapi (or equivalent). |
I have started a new Wiki page to share requirements from each of the potential httpapi shareholders. Feel free to add more information there. |
That's pretty standard. In an httpapi plugin, you can set
This is one I haven't given a whole lot of thought to. I'm not entirely sure what this means, to be honest. I'm not really sure what this needs that
Additionally, (and especially as a lot of the above points were requested by them), if you want to see how someone who is not me wrote an httpapi plugin to work with something that does not look anything like NX-API/eAPI (read: REST), take a look at plugins/httpapi/ftd.py. If you want to know what is expected of an httpapi plugin, the interface is described in plugins/httpapi/__init__.py, and if something still doesn't seem clear, bring it up and I'll be happy to talk about how to make it better. @dagwieers I think this covers most of your needs as well. The major sticking point I know you still have is cluster support, and I haven't the faintest idea how to make that work in a way that doesn't ruin all the niceties that making connections look like real connection plugins. My only idea is to add a |
Proposal: Interface manager role ansible-network/network-proposals#1 The interface manager role provides a platform agnostic implementation to declaratively manage the aggregate set of network interfaces on a remote device. This role is designed to effectively replace the |
Proposal: VRF definitions role ansible-network/network-proposals#3 This proposal describe the implementation of a new resource role for managing VRF definitions in network device active configurations. This role would replace the current net_vrf agnostic module that currently resides in Ansible core. |
Proposal: VLANs role ansible-network/network-proposals#2 This proposal describes the implementation of a VLANs role to replace the current platform agnostic implementation ofnet_vlan currently in Ansible core. |
Please review and merge PR ansible/ansible#46623 Thanks & Regards |
2018-10-10Team status and updates
Actions
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2018-10-10/ansible_network_working_group.2018-10-10-16.00.html |
Can we discuss this please on 10/17- ansible/ansible#46185 |
2018-10-17Team status and updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2018-10-17/ansible_network_working_group.2018-10-17-16.02.html |
Hi, Best Regards, |
2018-10-24Team status and updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2018-10-24/ansible_network_working_group.2018-10-24-16.03.html |
2018-10-31Team status and updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2018-10-31/ansible_network_working_group.2018-10-31-15.57.html |
2018-11-07Team status and updates
Logs
|
Need the following PR Merged:
|
2018-11-14Team status and updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2018-11-14/ansible_network_working_group.2018-11-14-16.00.html |
Need the following PR Merged: |
2018-11-28Team status and updates
Minutes: https://meetbot.fedoraproject.org/ansible-network/2018-11-28/ansible_network_working_group.2018-11-28-16.06.html |
Please merge |
Please cherry-pick the following bug fix PR's into ansible/ansible#49479 |
2018-12-05Action items -- |
2018-12-12Team status and updates
Actions
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2018-12-12/ansible_network_working_group.2018-12-12-16.01.html |
Please merge PR |
New IOS NTP module.
|
2018-12-19Team status and updates
Actions
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2018-12-19/ansible_network_working_group.2018-12-19-16.00.html |
Please merge PR |
@FedericoOlivieri Thanks for raising the PR, but as the |
Need review for ansible/ansible#66633. |
Need review for ansible/ansible#66248 - A module to manage guest virtual machines on EXOS devices. |
2020-01-22Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-01-22/ansible_network_working_group.2020-01-22-16.00.html |
2020-01-29Core Updates
Zuul CI improvements
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-01-29/ansible_network_working_group.2020-01-29-16.00.html |
2020-02-05Core Updates
Resource Module Documentation Feedback
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-02-05/ansible_network_working_group.2020-02-05-16.00.html |
2020-02-19Collections Update
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-02-19/ansible_network_working_group.2020-02-19-16.00.html |
For more detail on the collections migration who/what/when/where/how and sometimes why, see https://groups.google.com/forum/#!msg/ansible-devel/oKqgCeYTs-M/cHrOgMw8CAAJ and https://github.com/ansible-collections/overview/blob/master/README.rst |
Ansible Contributors Summit EUROPEWhatAnsible Contributor Summit is a one day event especially for community contributors to meet with each other, as well as Ansible development teams (Core, AWX/Tower, Galaxy) in person, to discuss important issues in the community and help shape the future of Ansible. For those unable to make it to Gothenburg, we welcome you to join virtually for part/all of the day. Online participation and streaming details to follow closer to the summit. When
How
Agenda
|
Is still possible to review and marge ansible/ansible#67958 or new modules already redirected to collections? |
@FedericoOlivieri no, ansible/ansible devel is feature freeze. The new location for the PR would be: https://github.com/ansible-collections/eos |
@pabelanger thanks! I raised new PR: ansible-collections/arista.eos#9 and closed the old. Is the weekly call still good for PR review? |
2020-03-04Core Updates
New arista module
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-03-04/ansible_network_working_group.2020-03-04-16.05.html |
2020-03-18Not much to report at this stage. Collections are becoming available at https://github.com/ansible-collections LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-03-18/ansible_network_working_group.2020-03-18-15.59.html |
2020-03-25Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-03-25/ansible_network_working_group.2020-03-25-16.00.html |
2020-04-01Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-04-01/ansible_network_working_group.2020-04-01-16.00.html |
2020-04-08Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-04-08/ansible_network_working_group.2020-04-08-16.00.html |
2020-04-15Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-04-15/ansible_network_working_group.2020-04-15-16.00.html |
2020-04-22Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-04-22/ansible_network_working_group.2020-04-22-16.00.html |
2020-04-29Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-04-29/ansible_network_working_group.2020-04-29-16.08.html |
2020-05-06Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-05-06/ansible_network_working_group.2020-05-06-16.01.html |
2020-05-13Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-05-13/ansible_network_working_group.2020-05-13-16.00.html |
2020-05-20Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-05-20/ansible_network_working_group.2020-05-20-15.59.html |
2020-05-27Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-05-27/ansible_network_working_group.2020-05-27-16.00.html |
2020-06-03Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-06-03/ansible_network_working_group.2020-06-03-16.10.html |
Hi ansible-collections/junipernetworks.junos#55 Thank you |
2020-06-17Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-06-17/ansible_network_working_group.2020-06-17-16.03.html |
2020-06-24Core Updates
LogsMinutes: https://meetbot.fedoraproject.org/ansible-network/2020-06-24/ansible_network_working_group.2020-06-24-16.00.html |
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
The text was updated successfully, but these errors were encountered: