Hopefully, by this point things are getting a bit easier to follow. You will notice that the steps to complete the playbooks/roles are similar despite the tasks themselves being different. Ansible is the key to simplifying those repeated steps. Just like in the last chapter, you can use this role in combination with others, as many times as you want. This is why you want to design your roles to be the base generic task, as much as possible.

Some of the things that we covered in this chapter were to define what a quota within OpenStack is. We then took that knowledge and learned how to update a quota for a tenant/user using the OpenStack CLI. We applied some base principles as to why you will use the default cloud quotas and how to update them appropriately. Next we reviewed how to reset any of the custom quotas created. Lastly, we developed our very own Ansible playbook and a role to automate the updating of custom tenant/user quotas.

Let's now move on to the next chapter, where we...