Introduction to Ansible Transcripts
Chapter: What's Next
Lecture: Course Recap
0:00 We've covered a lot of ground together over the past few hours. Now that you know how to configure servers and deploy applications with Ansible
0:07 you've got a strong foundation to be able to do almost anything you want with the tool. Let's recap a little bit where we've been.
0:12 We talked about why Ansible is such a great tool for configuration management how it's made configuration management much easier
0:18 than alternative tools that came before it. We worked through the initial concepts like modules, tasks, roles, playbooks
0:24 and the inventory files as the core pieces that we needed to know about to use Ansible. As we started our first playbook and expanded upon it
0:30 we learned to write our playbooks and then run them against the server and perform useful tasks like creating deployer users
0:36 instead of logging in as a root so that we could perform any step that we wanted to take on a remote server. Most of our playbooks consist of YAML
0:42 and we wrote a bunch of it together. Got our top-level playbook.yml file and then the individual tasks combined together under roles
0:49 like common, or web server, or database server. As we got comfortable with writing simple playbooks like this, we learned about working with data
0:55 adding variables, reading environment variables using templates as our input data and encrypting data as well.
1:00 We added a group_vars file and learned how to encrypt it and we learned how to use templates to configure services such as Nginx.
1:07 We combined the variables with the templates executed by tasks and Ansible to create our configuration on remote servers.
1:13 Encrypting files consist of using Ansible Vault the encrypt and decrypt command and passing in the vault password whenever we run our playbook
1:20 that contains sensitive information so that Vault could decrypt the data before it is run and then re-encrypt it once the playbook is over
1:26 so that the information stays secret. With all of our concepts in place, we work through building
1:31 a good size Ansible playbook to configure multiple servers. We had a bunch of common operations we wanted to apply to all servers in our common role.
1:39 Then, we separated out the web server and database server roles to differentiate our server types.
1:44 You can try to extend this model with your own caching load balancing, and other server roles when necessary for your application.
1:51 Finally, we took a simple prototype application combined it with the playbook we built in Chapter Six added enhanced tasks within our roles
2:00 to deploy the application, to ansibledeploymentexample.com. You should now be able to use Ansible playbooks as a base
2:07 for automating deployments of your own applications. You may need to look through Ansible's documentation for some additional modules
2:13 depending on what you're trying to do but you're well on your way towards using Ansible for its intended purpose as a configuration management tool.
2:20 Remember, take a look at the https://github.com/fullstackPython/book-and-video-code-examples so you can take the Ansible playbook
2:26 modify it for your own purposes and use it within your own projects.