<commit_before># Successfully automating your machines in the cloud using Ansible


## Videos of Talk

* 26-June, 2014 ([Bay Area Python Interest Group (BayPIGgies)/Silicon Valley Python MeetUp Video](https://plus.google.com/hangouts/onair/watch?hid=hoaevent%2Fcf7vrv1f9q5e8bojpslfjjen8gk&ytl=ptzruazbRXY&hl=en)


## Practice Sessions

* http://www.meetup.com/silicon-valley-python/events/191582452/


## Talk description
As we have seen with the previous talk, "Red Pill, Blue Pill Virtual Machines
and Virtual Environments"
( [GitHub](https://github.com/glenjarvis/red-pill-blue-pill) /
  [YouTube](https://www.youtube.com/watch?v=xZb3cr1JrMg) ), we can create
virtual machines in the cloud.

But, how do you "stamp" those machines differently? If you need to build a web
server, mail server, DNS server, and load balancer, each machine may have the
same base image but needs to be configured differently.

If you manually configure those machines, what happens when you suddenly have a
surge in traffic and need four more web servers? Or, what if one finds a
vulnerability in a library like
[Heartbleed](http://en.wikipedia.org/wiki/Heartbleed) in OpenSSL as we recently
encountered. A very safe option would be to rebuild these machines from<commit_msg>Add more Level 0 and Level 1 practice sessions<commit_after># Successfully automating your machines in the cloud using Ansible


## Videos of Talk

* 26-June, 2014 ([Bay Area Python Interest Group (BayPIGgies)/Silicon Valley Python MeetUp Video](https://plus.google.com/hangouts/onair/watch?hid=hoaevent%2Fcf7vrv1f9q5e8bojpslfjjen8gk&ytl=ptzruazbRXY&hl=en)


## Practice Sessions

* Hands-On Training: Level 0: Successful Ansible
  - Session 01:
    - 28-June, 2014
    - http://www.meetup.com/silicon-valley-python/events/191582452/
  - Session 02:
    - 28-June, 2014
    - http://www.meetup.com/silicon-valley-python/events/191818442/
  - Session 03:
    - 12-July, 2014
    -  http://www.meetup.com/silicon-valley-python/events/191819732/
* Hands-On Training: Level 1: Successful Ansible
  - Session 01:
    - 28-June, 2014
    - http://www.meetup.com/silicon-valley-python/events/191635482/
  - Session 02:
    - 12-July, 2014
    - http://www.meetup.com/silicon-valley-python/events/191822302/
  - Session 03:
    - 19-July, 2014
    - http://www.meetup.com/silicon-valley-python/events/191822552/
* Hands-On Training: Level 2: Successful Ansible
  - Not yet scheduled
* Hands-On Training: Level 3: Successful Ansible
  - Not yet scheduled
* Hands-On Training: Level 4: Successful Ansible
  - Not yet scheduled


## Talk description
As we have seen with the previous talk, "Red Pill, Blue Pill Virtual Machines
and Virtual Environments"
( [GitHub](https://github.com/glenjarvis/red-pill-blue-pill) /
  [YouTube](https://www.youtube.com/watch?v=xZb3cr1JrMg) ), we can create
virtual machines in the cloud.

But, how do you "stamp" those machines differently? If you need to build a web
server, mail server, DNS server, and load balancer, each machine may have the
same base image but needs to be configured differently.

If you manually configure those machines, what happens when you suddenly have a
surge in traffic and need four more web servers? Or, what if one finds a
vulnerability in a library like
[Heartbleed](http://en.wikipedia.org/wiki/Heartbleed) in OpenSSL as we recently
encountered. A very safe option would be to rebuild these machines from
{'fraction_non_alphanumeric': 0.09505703422053231, 'fraction_numerical': 0.043287510968119336, 'mean_word_length': 4.158371040723982, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 6, 'lorem ipsum': 0, 'www.': 9, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2509572', 'n_tokens_mistral': 1247, 'n_tokens_neox': 1081, 'n_words': 365}