<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>Hi Sten,<br></div>
<div> </div>
<div>On Mon, Jun 1, 2015, at 02:19 PM, Jim Campbell wrote:<br></div>
<blockquote type="cite"><div>Hi All,<br></div>
<div> </div>
<div>On Mon, Jun 1, 2015, at 02:10 PM, sten wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><p dir="ltr"><br>
On Jun 1, 2015 11:25 AM, "Jim Campbell" <<a href="mailto:jcampbell@gnome.org">jcampbell@gnome.org</a>> wrote:<br>
><br>
><br>
><br>
> On Sun, May 31, 2015, at 11:32 PM, Joseph Wegner wrote:<br>
> > On 05/31/2015 09:37 PM, Peter Baumgarten wrote:<br>
> > > I would be interested in participating in a hackfest. As a puppet<br>
> > > <<a href="https://puppetlabs.com/">https://puppetlabs.com/</a>> user myself I have been meaning to try out<br>
> > > either ansible <<a href="http://www.ansible.com">http://www.ansible.com</a>> or salt <<a href="http://saltstack.com">http://saltstack.com</a>>.<br>
> > ><br>
> > > On Fri, May 29, 2015 at 2:02 PM, sten <<a href="mailto:me@sud0.com">me@sud0.com</a> <mailto:<a href="mailto:me@sud0.com">me@sud0.com</a>>><br>
> > > wrote:<br>
> > ><br>
> > ><br>
> > > On May 29, 2015 07:07, "Jim Campbell" <<a href="mailto:jcampbell@gnome.org">jcampbell@gnome.org</a><br>
> > > <mailto:<a href="mailto:jcampbell@gnome.org">jcampbell@gnome.org</a>>> wrote:<br>
> > ><br>
> > > __<br>
> > ><br>
> > > On Fri, May 29, 2015, at 06:42 AM, meg ford wrote:<br>
> > >> Hi Sten,<br>
> > >> On Fri, May 29, 2015 at 6:41 AM, meg ford <<a href="mailto:meg387@gmail.com">meg387@gmail.com</a><br>
> > >> <mailto:<a href="mailto:meg387@gmail.com">meg387@gmail.com</a>>> wrote:<br>
> > >><br>
> > >> Forwarding from the old list:<br>
> > >> On Thu, May 28, 2015 at 10:32 AM, sten <<a href="mailto:me@sud0.com">me@sud0.com</a><br>
> > >> <mailto:<a href="mailto:me@sud0.com">me@sud0.com</a>>> wrote:<br>
> > >><br>
> > >><br>
> > >> Hi, all,<br>
> > >><br>
> > >> I've been talking with Jim offline about this, but we<br>
> > >> wanted to talk about it on-list before making any<br>
> > >> changes.<br>
> > >><br>
> > >> Jim can correct me here, but I understand everything<br>
> > >> under <a href="http://chicagolug.org">chicagolug.org</a> <<a href="http://chicagolug.org">http://chicagolug.org</a>> runs on a<br>
> > >> single Ubuntu instance on Rackspace. Since Rackspace<br>
> > >> is being so generous to the LUG, I'd like to split<br>
> > >> that out into multiple hosts, and do some HA and<br>
> > >> redundancy, and add at least one new service.<br>
> > >><br>
> > >> I'd also like to build it with Ansible, so it can be<br>
> > >> rebuilt from scratch easily if needed.<br>
> > >><br>
> > >> I've been thinking I'd like to do an Ansible<br>
> > >> presentation for the LUG, since I've been doing a lot<br>
> > >> with Ansible at work, particularly for OpenShift V3<br>
> > >> (v3 is all built and managed with ansible, see<br>
> > >> <a href="https://github.com/openshift/openshift-ansible/">https://github.com/openshift/openshift-ansible/</a>), but<br>
> > >> if we re-build <a href="http://chicagolug.org">chicagolug.org</a> <<a href="http://chicagolug.org">http://chicagolug.org</a>><br>
> > >> with Ansible, we can do something more collaborative<br>
> > >> and do it via the email list and pull requests.<br>
> > >><br>
> > >> What if we started with 1 new service, I'm thinking<br>
> > >> <a href="http://getkaiwa.com/">http://getkaiwa.com/</a> - this would run on a new<br>
> > >> Rackspace instance and point to the existing Prosody<br>
> > >> server.<br>
> > >><br>
> > >> I'd work with Jim and Meg to put together a new repo<br>
> > >> under the chicagolug github account, and we could do<br>
> > >> PRs to put together an Ansible role for Kaiwa and a<br>
> > >> playbook to create the Rackspace instance.<br>
> > >><br>
> > >> From there, we could add more roles and more playbooks<br>
> > >> and eventually get all the chicagolug services managed<br>
> > >> in Git.<br>
> > >><br>
> > >> Any interest? Any thoughts?<br>
> > >><br>
> > >><br>
> > >><br>
> > >><br>
> > >> Thanks for offering to help out with this! Is there any<br>
> > >> interest in the LUG having a hackfest around it? I know that<br>
> > >> your free time is currently somewhat limited, but if you do<br>
> > >> have time it might be cool to have a basic demo for those who<br>
> > >> haven't used Ansible before, followed by a few hours of<br>
> > >> collaborative work time. How do other people feel about it?<br>
> > ><br>
> > ><br>
> > ><br>
> > > I'd be happy to do that. Maybe I'll put together a quick<br>
> > > presentation on the basics and some examples. From there, we can<br>
> > > work on building out a working set of services.<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > Jim<br>
> > ><br>
> > ><br>
> ><br>
> > I would definitely be interested in attending a hackfest. We're working<br>
> > on making some Ansible playbooks at work for provisioning RHEL 7 VMs, so<br>
> > it would be great to see an example of how others are using these tools.<br>
> ><br>
> > -Joe<br>
><br>
><br>
> Would June 29th work for this? Sten, would you be free then and able to<br>
> give a talk on this?</p><p dir="ltr"><br></p><p dir="ltr">The 29th is a Monday, which might actually work for me, but I'm assuming that's not what you meant.. I can't do the 27th. I'm not sure about the 21st yet. <br></p><p dir="ltr"><br></p><p>If people want to get a head start, the Ansible documentation is great. There's an intro here: <a href="http://docs.ansible.com/intro.html">http://docs.ansible.com/intro.html</a> <br></p><p><br></p><p>When I learned Ansible, I basically took an evening and went through that intro, and after that evening felt like I had a good handle on how to work with the tool. <br></p><p dir="ltr"><br></p><p dir="ltr">Others? (If anyone won't be free then, but still<br>
> wants to participate, please let us know an alternate date).<br>
><br>
> What I'm thinking is that, for this month, we could use our monthly<br>
> meeting time to have a demo / discussion of how Ansible works, and then<br>
> use our remaining time to actually work on LUG infrastructure + Ansible.<br>
> Having a meeting later in the month would give us time to plan things<br>
> out on the list, review Ansible docs / tutorials, get started on things,<br>
> etc.<br>
><br>
> Does this sound good?<br>
><br>
> Jim<br>
><br>
><br>
> _______________________________________________<br>
> discuss mailing list<br>
> <a href="mailto:discuss@lists.chicagolug.org">discuss@lists.chicagolug.org</a><br>
> <a href="https://lists.chicagolug.org/mailman/listinfo/discuss">https://lists.chicagolug.org/mailman/listinfo/discuss</a></p></div>
</blockquote><div> </div>
<div>Sorry, I meant to type the 27th. The 20th could work for me, as well.<br></div>
<div> </div>
<div>Jim<br></div>
</blockquote><div> </div>
<div>Do you think you'd be free on the 20th, or would it be better to push things back to July? No worries either way. I personally think that moving things back to July would be fine for this meeting.<br></div>
<div> </div>
<div>As a note to the group, we had some good interactions with the Free Geek Chicago folks this weekend. Two of their members made it out to our Programming Tonight event on Friday (which had about 6-7 people there), and I made it over to their standing Saturday hackfest. They had a good bunch of people working on changing their website over to Jekyll. Joining them for those kinds of Saturday Hackings could make for good "Linux Office Hours", if people are interested. What do folks think about that?<br></div>
<div> </div>
<div>Looking ahead to the future, we're likely going to have our August meeting on August 15th. Jorge Castro from the Canonical Server team is free to give a talk on JuJu that weekend.<br></div>
<div> </div>
<div>Jim<br></div>
</body>
</html>