Alexander Roos, one of our Cloud Infrastructure Specialists on Getting Started with Cloud Automation. A basic overview of automation in general – how to use and when as well as examples of tools to use and a short demo.
For those of you that couldn’t make the live class, here is the replay.
Questions answered during the class
Q: Why do you use Ansible – better than Chef or Puppet?
A: Ansible is the easier of the three in my opinion. Chef and puppet is more code based and have been in the game longer than Ansible.
YAML is a very neat language and easy to understand. Also Ansible is client free while the others rely on installed clients.
Q: Whats a stack?
A: The Heat Wiki defines it as: A collection of instantiated resources that are defined in a single template. A much simpler way of putting it though is: A list of created and/or used resources in your infrastructure (i.e. Cores, ram, storage, network etc)
Q: Are they examples like this yaml-code online?
A: Here is a few examples of ansible playbooks writen in yaml: https://github.com/ansible/ansible-examples
Q: Could you show examples that we can use directly in City Cloud. Maybe the example You used in this demo?
Keith Tenzer from Red Hat has made an excellent example with heat, ansible and ansible tower. This is the one I used in the demo: https://keithtenzer.com/2016/05/09/openstack-heat-and-ansible-automation-born-in-the-cloud/
Q: Can you show some examples of juju or any solution more complex and complete?
A: Unfortunately this is not covered in this class. More in-depth classes about full automation is something we plan for the future. The next Master Class will cover the basics of Heat, and show you how to spin up complex application environments in no time.
Q: Where does Hashicorp’s Terraform fit?
A: Terraform is an infrastructure SKD same as Heat so referring to my presentation, that would fit in with the “Deployment SDK´s”