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

Network:Core roadmap 2.5

John R Barker edited this page Nov 2, 2017 · 27 revisions

Status: DRAFT

This is an uncommitted roadmap for 2.5

Feedback welcome in #ansible-network

Follow the our progress

GitHub Project

Note: To see which cards in our project pertain to a specific roadmap item, use the filter cards feature and filter using the keyword associated with each roadmap item e.g. [NET_CONN].

Convert existing non-DI NXOS modules into Declarative Intent [DI_NXOS]

Add missing declarative modules for supported platforms [DI_MISSING]

Network connection plugin work as part of core effort [NET_CONN]

Refactor common platform libraries to using CliConf plugin [CLI_CONF]

Refactor common platform libraries to using NetConf plugin [NETCONF]

Parse xml filter for network use case to return a json object [XML_FILTER]

Implement more flexible action handler plugin [ACTION_HANDLER]

Continuous Integration and Testing [CI] [TESTING]

Documentation [DOCS]

Create documentation for new users (getting started) and advanced users (such as how to authentication) to reduce confusion on how to best use Ansible to manage network devices. This will include creating a new landing page (which all network modules will link to); documenting various use-cases. Also where relevant existing Core (not network-specific) documentation will be reviewed and improved, this will be an ongoing process over the next few Ansible releases.

Refactor network common libraries into module_utils/network packaging [COMMON_LIB]

The rapid pace of module development for network modules has amassed a significant amount of technical debt related to the network shared code found in ansible/module_utils. This proposal is designed to provide details on creating a stable network package in ansible/module_utils/network and move the current shared network libraries into the new package. The ansible.module_utils.network package will only contain shared code that is common for all network modules to implement and will be maintained in a stable way moving forward.

(ARchived) Working groups

Working groups are now in the Ansible forum

Ansible project:
Community, Contributor Experience, Docs, News, Outreach, RelEng, Testing

Cloud:
AWS, Azure, CloudStack, Container, DigitalOcean, Docker, hcloud, Kubernetes, Linode, OpenStack, oVirt, Virt, VMware

Networking:
ACI, AVI, F5, Meraki, Network, NXOS

Ansible Developer Tools:
Ansible-developer-tools

Software:
Crypto, Foreman, GDrive, GitLab, Grafana, IPA, JBoss, MongoDB, MySQL, PostgreSQL, RabbitMQ, Zabbix

System:
AIX, BSD, HP-UX, macOS, Remote Management, Solaris, Windows

Security:
Security-Automation, Lockdown

Tooling:
AWX, Galaxy, Molecule

Communities

Modules:
unarchive, xml

Plugins:
httpapi

Wiki

Roles, Communication, Reviewing, Checklist, TODO

Clone this wiki locally