<table cellspacing="0" cellpadding="0" border="0"><tr><td valign="top"><p dir="ltr"><font size ="2"><font size ="2">Reminder that RSVPs close on Meetup today around 5pm. Or you can just RSVP through me. Please spread the word to anyone who might be interested in LUG or Ansible.</font></font></p>
<p dir="ltr"><font size ="2"><font size ="2">We eat & socialize at 6pm. The talk will start around 7pm. Let's try to finish up by 9pm so our OpenX host doesn't have to stay too late to close up</font></font></p>
<p dir="ltr"><font size ="2"><font size ="2">The June Meetup will be on Docker so we will likely do that at OpenX again if they are agreeable.</font></font></p>
<p dir="ltr"><font size ="2"><font size ="2">I am hoping to go back to Du-Pars for July to feel out the larger dining room & </font></font><u><font size ="2"><font size ="2">s</font></font></u><font size ="2"><font size ="2">ee how that would work for our meeting format.</font></font></p>
</td></tr></table> <div id="_origMsg_">
<div>
<br />
<div>
<div style="font-size:0.9em">
<hr size="1">
<b>
<span style="font-weight:bold">From:</span>
</b>
James McDuffie <mcduffie@pitfall.org>; <br>
<b>
<span style="font-weight:bold">To:</span>
</b>
SGVLUG Discussion List. <sgvlug@sgvlug.net>; <br>
<b>
<span style="font-weight:bold">Subject:</span>
</b>
[SGVLUG] Reminder: May meeting: Ansible talk @ OpenX on May 14th *NOTE* Earlier start time: 6pm <br>
<b>
<span style="font-weight:bold">Sent:</span>
</b>
Fri, May 8, 2015 7:33:09 PM <br>
</div>
<br>
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td valign="top">A reminder that our May meeting will be OpenX (Lake and Walnut) this<BR>month and start an hour earlier at 6pm. (Sorry Ubuntu Hour folks!). We<BR>are probably going to be at OpenX again in June, and then, we'll<BR>probably go back to Du-Pars.<BR><BR>Due to the building security at OpenX, we need to get them a list of<BR>names 48 hours in advance. This can be first name and last initial. <BR>Bobby M., who is the OpenX employee arranging this for us, will be<BR>checking in people.<BR><BR>Please, please RSVP via Meetup by 5pm on Tuesday, May 12th. If you<BR>don't like Meetup, RSVP to Lan (<a ymailto="mailto:l.dang@ymail.com" href="javascript:return">l.dang@ymail.com</a>).<BR>We have 41 people currently RSVPed. The cap on Meetup is 70. The real<BR>maximum is 80 people. (We checked with facilities.)<BR><BR><a
href="http://www.meetup.com/SGVTech/events/221742845/" target=_blank >http://www.meetup.com/SGVTech/events/221742845/</a><BR><BR><BR>TOPIC<BR><BR>Andrew Hamilton will go over the basics of Ansible and discuss why it's<BR>a great tool for running simple commands, complex tasks and workflows<BR>across a group of systems.<BR><BR>Ansible is a powerful but simple automation tool. Ansible is simple<BR>enough that most developers and administrators will be able to<BR>understand the scripts without much trouble. With this simplicity,<BR>Ansible is great for organizations looking for a tool that both dev and<BR>ops can use together. The YAML based syntax of Ansible is also much<BR>easier to understand than the DSL that some other tools use.<BR><BR>BIO<BR><BR>Andrew is currently a Systems Architect at Prevoty where he focuses on<BR>automation and infrastructure. Previously he was an SRE for Search<BR>@Twitter and a system administrator for Eucalyptus. Andrew is
passionate<BR>about cloud computing and automation. <BR><BR>DIRECTIONS<BR><BR>OpenX is located in the One West Bank building @ 888 E Walnut St. <BR>Pasadena CA, 91101. Entrances to the building are eastbound on Walnut,<BR>right hand side before the Lake St. intersection or southbound on Lake<BR>St. right hand side after the Walnut St. intersection. Once through the<BR>driveway, please park in the 888 Lot that has the OpenX logo displayed<BR>out front. Pull a ticket and bring it with you to the Meet-Up, we will<BR>validate your parking.<BR><BR><BR><BR>MORE ON ANSIBLE:<BR><BR>Ansible has many features common to configuration management systems<BR>such as Puppet and Chef. Ansible uses a simple execution model compared<BR>to Puppet and Chef that is much easier for new users to understand. The<BR>majority of the modules it provides are indepotent so a playbook can be<BR>run multiple times without causing problems by running a change multiple<BR>times if it
isn't needed. The use of YAML to describe your playbooks<BR>also makes creating and editing Ansible playbooks much easier.<BR><BR><BR>Interacting directly with services such as AWS, GCE, Azure or OpenStack<BR>is easy through a set of provided modules. Ansible allows you to create<BR>an entire deployment framework with one tool that can provision hosts,<BR>configure and install software, add and remove servers from a load<BR>balancer and finally terminate the old instances. Ansible can also use<BR>dynamically generated lists of hosts making it easy to work in highly<BR>dynamic environments.<BR><BR>One of the most powerful features of Ansible is that hosts are accessed<BR>over SSH. There is no need to install additional daemons or to open up<BR>additional ports. You can simply write a playbook, give it a set of<BR>hosts to run against, provide a set of credentials and watch Ansible do<BR>what you've told it to do.<BR><BR><BR>You also don't need to give
Ansible access to root unless it is required<BR>for the playbook. Ansible can use either sudo or su to escalate<BR>privileges for single tasks or entire playbooks.<BR><BR><BR>Ansible core is written in Python so it's easy to run and extend. If<BR>Python is your language of choice, Ansible provides you with a set of<BR>modules that make writing your own modules easy. If you're not a Python<BR>developer, Ansible allows modules to be written in any language that can<BR>accept JSON through STDIN and then return JSON back to through STDOUT.<BR>Ansible can also be used as a library in Python that allows you to<BR>easily take advantage of some of its features in custom scripts. Ansible<BR>is a flexible tool that allows users to easily perform both adhoc remote<BR>command execution and configuration management across a group of hosts.<BR>Getting started with Ansible is easy and has relatively low overhead.<BR>Ansible playbooks are simple enough that they can be
compared with shell<BR>scripts. We'll go over the basics of Ansible and discuss why it's a<BR>great tool for running simple commands, complex tasks and workflows<BR>across a group of systems. <BR><BR></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>