Difference between revisions of "Ansible"
From RiceFamily Wiki
(→Documentation) |
|||
| Line 1: | Line 1: | ||
| + | = Overview = | ||
| + | The Linux Group started using Ansible when an Automation Initiative was started at work. They initially used it to automate a Server Build process for new Linux hosts. After a time, it was extended to the Windows Server Build process. | ||
| + | |||
| + | We are now looking at it to allow the Networking team to automate the upgrade processes on some of the network devices that are not supported by DNA-C. | ||
| + | |||
| + | While we are at it, my manager wants me to look at how Ansible can be used to replace BigFix since HCL has been playing games with our Licenses and it looks like we might be moving off BigFix in the near future. | ||
| + | |||
= Tutorials = | = Tutorials = | ||
* [https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-ansible-on-ubuntu-16-04 How to Install and Configure Ansible on Ubuntu 16-04] | * [https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-ansible-on-ubuntu-16-04 How to Install and Configure Ansible on Ubuntu 16-04] | ||
Revision as of 14:42, 23 September 2020
Contents
Overview
The Linux Group started using Ansible when an Automation Initiative was started at work. They initially used it to automate a Server Build process for new Linux hosts. After a time, it was extended to the Windows Server Build process.
We are now looking at it to allow the Networking team to automate the upgrade processes on some of the network devices that are not supported by DNA-C.
While we are at it, my manager wants me to look at how Ansible can be used to replace BigFix since HCL has been playing games with our Licenses and it looks like we might be moving off BigFix in the near future.
