<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Trotter Cashion</title>
    <description/>
    <link>https://speakerdeck.com/trotter</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/trotter.rss"/>
    <lastBuildDate>2013-05-05 13:55:24 -0400</lastBuildDate>
    <item>
      <title>Chef and the Cloud</title>
      <description>Over the past year, we've been using Chef to both configure instances in EC2 and build AMIs. Chef is an integral part of our workflow, but it doesn't always play perfectly in a world of auto scaling groups and ephemeral instances. In this talk, I cover what's worked and what's failed and explain how to best utilize Chef in the world of Amazon Web Services. It's better with audio: http://www.youtube.com/watch?v=KSScdObVdCM&amp;feature=youtu.be</description>
      <media:content url="https://files.speakerdeck.com/presentations/9ab2d90097da01306f0f6ea8a59f5346/preview_slide_0.jpg?1420727" type="image/jpeg" medium="image"/>
      <content:encoded>Over the past year, we've been using Chef to both configure instances in EC2 and build AMIs. Chef is an integral part of our workflow, but it doesn't always play perfectly in a world of auto scaling groups and ephemeral instances. In this talk, I cover what's worked and what's failed and explain how to best utilize Chef in the world of Amazon Web Services. It's better with audio: http://www.youtube.com/watch?v=KSScdObVdCM&amp;feature=youtu.be</content:encoded>
      <pubDate>Thu, 25 Apr 2013 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/trotter/chef-and-the-cloud</link>
      <guid>https://speakerdeck.com/trotter/chef-and-the-cloud</guid>
    </item>
  </channel>
</rss>
