Add recipe for source install

[clofresh]

No description provided.

[alq666]

Should we just disable the end-of-run checks of the source install script? @remh

[asiegman]

I had to write my own cookbook to do a source install because we use supervisor ourselves and datadog's packaging interferes with that, and since we use deb packages for deployment I can't have apt errors sitting out there.

Here's what I did to create a user and run the install script. Support added a "do not start agent" flag to be set in the environment, worked out well:

  0 user "dd-agent" do
  1   action :create
  2   home "/opt/datadog"
  3   system true
  4   shell "/bin/bash"
  5   supports :manage_home => true
  6 end
  7
  8 bash "install_datadog" do
  9   user "dd-agent"
 10   cwd "/opt/datadog/"
 11   environment "DD_API_KEY" => "YOUR_API_KEY", "DD_HOME" => "/opt/datadog/", "DD_START_AGENT" => "0"
 12   code <<-EOH
 13     sh -c "$(curl -L http://dtdg.co/dd-agent-source)"
 14   EOH
 15   creates "/opt/datadog/venv"
 16 end

Then a quick upstart script if you're on ubuntu and you're good to go.

  0 description "start and stop the datadog-agent provided by their install from source script"
  1
  2 respawn
  3 respawn limit 15 5
  4
  5 start on runlevel [2345]
  6 stop on runlevel [06]
  7
  8 script
  9   chdir /opt/datadog
 10   exec start-stop-daemon --start -c dd-agent --exec /opt/datadog/bin/agent
 11 end script

Obviously this is all very rough draft, it should be using attributes for all the paths and variables, but, I wrote it quick just to test out the software trial.

[miketheman]

@asiegman Since the opening of this issue, we have released version 5.x of the Datadog Agent, which bundles a self-contained supervisor which no longer conflicts with any other installed supervisor.
With that, you'd likely no longer need the source install method.

[miketheman]

Closing out this issue, as there's packagers for systems that no longer interfere with other supervisors.