-
Notifications
You must be signed in to change notification settings - Fork 144
Network: F5
THIS PAGE IS OLD and no longer maintained. For questions, please use the Ansible forum.
- Tim Rupp (@caphrim007)
Ideas and issues should be filed at the f5-ansible
repo first
And in the Ansible core issues page secondarily.
Note:
If you do file in Ansible core though, @caphrim007 is usually called out in the issue, so it will come to the F5 developer's attention. The standard procedure is,
- Clone the Ansible issue into the F5Networks repository
- Make mention of the F5Networks issue in the Ansible issue
- Close the Ansible issue
- Ongoing development continues in F5Networks repository
- Once complete, code is upstreamed into Ansible core
Refer to the upstream
tag of each project in the projects list here
Additionally, please reference the Todo
column of the f5-ansible
project for each release of Ansible. Those projects are found here
Any functionality that is missing from the above modules can be implemented using the bigip_command module which gives access to anything available in tmsh
.
If you feel up to it, you can implement your own F5 modules by looking at the existing ones.
This Wiki is used for quick notes, not for support or documentation.
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
Plugins:
httpapi