search

ansible / community

This repository is being archived. See https://github.com/ansible-community/presentations and https://github.com/ansible-community/meetings for the new locations
Apache License 2.0
489 stars 144 forks source link

Network Working Group Meeting Agenda 2 #247

Closed gundalow closed 6 years ago

gundalow commented 7 years ago

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

samerd commented 6 years ago

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 commented 6 years ago

Thanks a lot @samerd

Qalthos commented 6 years ago

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

Please subscribe to #363

dagwieers commented 6 years ago

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.