<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Forwarder management:  deployment server vs Chef in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-management-deployment-server-vs-Chef/m-p/294299#M55918</link>
    <description>&lt;P&gt;If the client is already using Chef then they should continue to do so.  Chef can do much more than a deployment server can.  Even if they use a DS, they'll still need Chef to update the forwarder executable itself (something a DS can't do).&lt;/P&gt;</description>
    <pubDate>Wed, 11 Oct 2017 21:13:09 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2017-10-11T21:13:09Z</dc:date>
    <item>
      <title>Forwarder management:  deployment server vs Chef</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-management-deployment-server-vs-Chef/m-p/294298#M55917</link>
      <description>&lt;P&gt;I have very little experience with chef.  I have a client with very high security requirements.  I was wondering if anyone in the community can explain the costs and benefits of using the deployment server vs chef.  I'm assuming the customer would want to use client certs with the deployment server.&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Oct 2017 18:59:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-management-deployment-server-vs-Chef/m-p/294298#M55917</guid>
      <dc:creator>responsys_cm</dc:creator>
      <dc:date>2017-10-11T18:59:31Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder management:  deployment server vs Chef</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-management-deployment-server-vs-Chef/m-p/294299#M55918</link>
      <description>&lt;P&gt;If the client is already using Chef then they should continue to do so.  Chef can do much more than a deployment server can.  Even if they use a DS, they'll still need Chef to update the forwarder executable itself (something a DS can't do).&lt;/P&gt;</description>
      <pubDate>Wed, 11 Oct 2017 21:13:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-management-deployment-server-vs-Chef/m-p/294299#M55918</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2017-10-11T21:13:09Z</dc:date>
    </item>
  </channel>
</rss>

