Security and Delegation with Ansible Tower, Part 1
This is part of a series of posts about how Ansible and Ansible Tower enable you to manage your infrastructure simply, securely, and efficiently.
When we talk about Tower, we often talk in terms of control, knowledge, and delegation. But what does that mean? In previous posts in this series, we've talked about the concept of 'control', as it relates to both managing your infrastructure and managing your automation. Today we're going to explain delegation, and the security aspects that go into that.
DELEGATION - THE BASICS
Ansible Playbooks, out of the box, are pretty simple - you run Ansible as a particular user, you pass it whatever inventory you want to manage, and it uses whatever credentials the executing user happens to have on hand. This is great for getting automating quickly, but what if you want to delegate automation to someone else to run as needed? You need to provide an inventory file for Ansible and Playbook to them (hopefully they don't edit them), and give them credentials (hopefully they won't use them for something else).That's where the control, knowledge, and delegation features of Ansible Tower come into play.
In the move to the telco cloud, there are some crucial considerations in NFVI components selection.
It only deployed a single instance of the virtual router as proof of its viability.
There is also a security aspect to this new capability.