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

Linode: destroy communitty plan

Jump to bottom
back edited this page Nov 8, 2020 · 3 revisions

Schemes / Rants / Plans

Existing thoughts on Linode Modules

Pick apart the thoughts laid out in this issue by a previous maintainer about improving the Linode modules overall.

Implement new modules based on linode-api4 functionality

See feature set provided by http://linode-api4.readthedocs.io/ and https://developers.linode.com/api/v4

Implement modules for Linode's core infrastructure primitives:

  • Implement Linode Domains (DNS)
  • Implement NodeBalancers
  • Implement Images
  • Implement Block Storage Volumes
  • Implement StackScripts

Triaging

We can always, of course, be useful somewhere in Ansible world:

https://github.com/ansible/ansible/labels/Linode

This Wiki is used for quick notes, not for support or documentation.

(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