server_maint 0.0.1 → 0.0.2

data/.gitmodules

@@ -4,3 +4,15 @@
 [submodule "lib/cookbooks/nginx"]
 	path = lib/cookbooks/nginx
 	url = git://github.com/opscode-cookbooks/nginx.git
+[submodule "lib/cookbooks/build-essential"]
+	path = lib/cookbooks/build-essential
+	url = git://github.com/opscode-cookbooks/build-essential.git
+[submodule "lib/cookbooks/runit"]
+	path = lib/cookbooks/runit
+	url = git://github.com/opscode-cookbooks/runit.git
+[submodule "lib/cookbooks/bluepill"]
+	path = lib/cookbooks/bluepill
+	url = git://github.com/opscode-cookbooks/bluepill.git
+[submodule "lib/cookbooks/ohai"]
+	path = lib/cookbooks/ohai
+	url = git://github.com/opscode-cookbooks/ohai.git

data/lib/cookbooks/bluepill/.gitignore

@@ -0,0 +1,4 @@
+.bundle
+.cache
+.kitchen
+bin

data/lib/cookbooks/bluepill/CHANGELOG.md

@@ -0,0 +1,31 @@
+## v1.1.0:
+
+* [COOK-1592] - use mixlib-shellout instead of execute, add test-kitchen
+
+## v1.0.6:
+
+* [COOK-1304] - support amazon linux
+* [COOK-1427] - resolve foodcritic warnings
+
+## v1.0.4:
+
+* [COOK-1106] - fix chkconfig loader for CentOS 5
+* [COOK-1107] - use integer for GID instead of string
+
+## v1.0.2:
+
+* [COOK-1043] - Bluepill cookbook fails on OS X because it tries to
+  use root group
+
+## v1.0.0:
+
+* [COOK-943] - add init script for freebsd
+
+## v0.3.0:
+
+* [COOK-867] - enable bluepill service on RHEL family
+* [COOK-550] - add freebsd support
+
+## v0.2.2:
+
+* Fixes COOK-524, COOK-632

data/lib/cookbooks/bluepill/CONTRIBUTING

@@ -0,0 +1,29 @@
+If you would like to contribute, please open a ticket in JIRA:
+
+* http://tickets.opscode.com
+
+Create the ticket in the COOK project and use the cookbook name as the
+component.
+
+For all code contributions, we ask that contributors sign a
+contributor license agreement (CLA). Instructions may be found here:
+
+* http://wiki.opscode.com/display/chef/How+to+Contribute
+
+When contributing changes to individual cookbooks, please do not
+modify the version number in the metadata.rb. Also please do not
+update the CHANGELOG.md for a new version. Not all changes to a
+cookbook may be merged and released in the same versions. Opscode will
+handle the version updates during the release process. You are welcome
+to correct typos or otherwise make updates to documentation in the
+README.
+
+If a contribution adds new platforms or platform versions, indicate
+such in the body of the commit message(s), and update the relevant
+COOK ticket. When writing commit messages, it is helpful for others if
+you indicate the COOK ticket. For example:
+
+    git commit -m '[COOK-1041] Updated pool resource to correctly delete.'
+
+In the ticket itself, it is also helpful if you include log output of
+a successful Chef run, but this is not absolutely required.

data/lib/cookbooks/bluepill/Gemfile

@@ -0,0 +1,5 @@
+source "https://rubygems.org"
+
+group :test do
+  gem "test-kitchen"
+end

data/lib/cookbooks/bluepill/Gemfile.lock

@@ -0,0 +1,115 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    archive-tar-minitar (0.5.2)
+    bunny (0.7.9)
+    chef (10.14.4)
+      bunny (>= 0.6.0, < 0.8.0)
+      erubis
+      highline (>= 1.6.9)
+      json (>= 1.4.4, <= 1.6.1)
+      mixlib-authentication (>= 1.3.0)
+      mixlib-cli (>= 1.1.0)
+      mixlib-config (>= 1.1.2)
+      mixlib-log (>= 1.3.0)
+      mixlib-shellout
+      moneta
+      net-ssh (~> 2.2.2)
+      net-ssh-multi (~> 1.1.0)
+      ohai (>= 0.6.0)
+      rest-client (>= 1.0.4, < 1.7.0)
+      treetop (~> 1.4.9)
+      uuidtools
+      yajl-ruby (~> 1.1)
+    childprocess (0.3.5)
+      ffi (~> 1.0, >= 1.0.6)
+    coderay (1.0.7)
+    erubis (2.7.0)
+    ffi (1.1.5)
+    foodcritic (1.6.1)
+      erubis
+      gherkin (~> 2.11.1)
+      gist (~> 3.1.0)
+      nokogiri (= 1.5.0)
+      pry (~> 0.9.8.4)
+      rak (~> 1.4)
+      treetop (~> 1.4.10)
+      yajl-ruby (~> 1.1.0)
+    gherkin (2.11.2)
+      json (>= 1.4.6)
+    gist (3.1.0)
+    hashr (0.0.22)
+    highline (1.6.15)
+    i18n (0.6.1)
+    ipaddress (0.8.0)
+    json (1.5.4)
+    librarian (0.0.24)
+      archive-tar-minitar (>= 0.5.2)
+      chef (>= 0.10)
+      highline
+      thor (~> 0.15)
+    log4r (1.1.10)
+    method_source (0.7.1)
+    mime-types (1.19)
+    mixlib-authentication (1.3.0)
+      mixlib-log
+    mixlib-cli (1.2.2)
+    mixlib-config (1.1.2)
+    mixlib-log (1.4.1)
+    mixlib-shellout (1.1.0)
+    moneta (0.6.0)
+    net-scp (1.0.4)
+      net-ssh (>= 1.99.1)
+    net-ssh (2.2.2)
+    net-ssh-gateway (1.1.0)
+      net-ssh (>= 1.99.1)
+    net-ssh-multi (1.1)
+      net-ssh (>= 2.1.4)
+      net-ssh-gateway (>= 0.99.0)
+    nokogiri (1.5.0)
+    ohai (6.14.1)
+      ipaddress
+      mixlib-cli
+      mixlib-config
+      mixlib-log
+      systemu
+      yajl-ruby
+    polyglot (0.3.3)
+    pry (0.9.8.4)
+      coderay (~> 1.0.5)
+      method_source (~> 0.7.1)
+      slop (>= 2.4.4, < 3)
+    rak (1.4)
+    rest-client (1.6.7)
+      mime-types (>= 1.16)
+    slop (2.4.4)
+    systemu (2.5.2)
+    test-kitchen (0.6.0)
+      foodcritic (~> 1.4)
+      hashr (~> 0.0.20)
+      highline (>= 1.6.9)
+      librarian (~> 0.0.20)
+      mixlib-cli (~> 1.2.2)
+      vagrant (~> 1.0.2)
+      yajl-ruby (~> 1.1.0)
+    thor (0.16.0)
+    treetop (1.4.10)
+      polyglot
+      polyglot (>= 0.3.1)
+    uuidtools (2.1.3)
+    vagrant (1.0.5)
+      archive-tar-minitar (= 0.5.2)
+      childprocess (~> 0.3.1)
+      erubis (~> 2.7.0)
+      i18n (~> 0.6.0)
+      json (~> 1.5.1)
+      log4r (~> 1.1.9)
+      net-scp (~> 1.0.4)
+      net-ssh (~> 2.2.2)
+    yajl-ruby (1.1.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  test-kitchen

data/lib/cookbooks/bluepill/LICENSE

@@ -0,0 +1,201 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/lib/cookbooks/bluepill/README.md

@@ -0,0 +1,80 @@
+Description
+===========
+
+Installs bluepill RubyGem and configures it to manage services. Also includes a LWRP.
+
+Requirements
+============
+
+Bluepill is a pure Ruby service management tool/library, so this cookbook should work on any system. The attributes do set up paths based on FHS locations, see below.
+
+Attributes
+==========
+
+Default locations for bluepill are in "FHS compliant" locations.
+
+* `node["bluepill"]["bin"]` - Path to bluepill program, default is 'bluepill' in the RubyGems binary directory.
+* `node["bluepill"]["logfile"]` - Location of the bluepill log file, default "/var/log/bluepill.log".
+* `node["bluepill"]["conf_dir"]` - Location of service config files (pills), default "/etc/bluepill".
+* `node["bluepill"]["pid_dir"]` - Location of pidfiles, default "/var/run/bluepill"
+* `node["bluepill"]["state_dir"]` - Location of state directory, default "/var/lib/bluepill"
+* `node["bluepill"]["init_dir"]` - Location of init script directory, default selected by platform.
+
+Resources/Providers
+===================
+
+This cookbook contains an LWRP, `bluepill_service`. This can be used with the normal Chef service resource, by using the `provider` parameter, or by specifying the `bluepill_service` shortcut. These two resources are equivalent.
+
+    service "my_app" do
+      provider bluepill_service
+      action [:enable, :load, :start]
+    end
+
+    bluepill_service "my_app" do
+      action [:enable, :load, :start]
+    end
+
+The load action should probably always be specified, to ensure that if bluepill isn't running already it gets started. The
+
+The recipe using the service must contain a template resource for the pill and it must be named `my_app.pill.erb`, where `my_app` is the service name passed to the bluepill service resource.
+
+Usage
+=====
+
+Be sure to include the bluepill recipe in the run list to ensure that the gem and bluepill-related directories are created. This will also make the cookbook available on the system and other cookbooks won't need to explicitly depend on it in the metadata.
+
+If the default directory locations in the attributes/default.rb aren't what you want, change them by setting them either in the attributes file itself, or create attributes in a role applied to any systems that will use bluepill.
+
+Example pill template resource and .erb file:
+
+    template "/etc/bluepill/my_app" do
+      source "my_app.pill.erb"
+    end
+
+    Bluepill.application("my_app") do |app|
+      app.process("my_app") do |process|
+        process.pid_file = "/var/run/my_app.pid"
+        process.start_command = "/usr/bin/my_app"
+      end
+    end
+
+See bluepill's documentation for more information on creating pill templates.
+
+License and Author
+==================
+
+Author:: Joshua Timberman (<joshua@opscode.com>)
+
+Copyright 2010, Opscode, Inc.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/lib/cookbooks/bluepill/attributes/default.rb

@@ -0,0 +1,34 @@
+# Cookbook Name:: bluepill
+# Attributes:: default
+# 
+# Copyright 2010, Opscode, Inc.
+# 
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+# 
+#     http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+default["bluepill"]["bin"] = "#{languages[:ruby][:bin_dir]}/bluepill"
+default["bluepill"]["logfile"] = "/var/log/bluepill.log"
+default["bluepill"]["pid_dir"] = "/var/run/bluepill"
+default["bluepill"]["state_dir"] = "/var/lib/bluepill"
+default["bluepill"]["group"] = 0
+
+case platform
+when "arch"
+  default["bluepill"]["init_dir"] = "/etc/rc.d"
+  default["bluepill"]["conf_dir"] = "/etc/bluepill"
+when "freebsd"
+  default["bluepill"]["init_dir"] = "/usr/local/etc/rc.d"
+  default["bluepill"]["conf_dir"] = "/usr/local/etc/bluepill"
+else
+  default["bluepill"]["init_dir"] = "/etc/init.d"
+  default["bluepill"]["conf_dir"] = "/etc/bluepill"
+end

data/lib/cookbooks/bluepill/metadata.rb

@@ -0,0 +1,7 @@
+maintainer       "Opscode, Inc."
+maintainer_email "cookbooks@opscode.com"
+license          "Apache 2.0"
+description      "Installs bluepill gem and configures to manage services, includes bluepill_service LWRP"
+long_description IO.read(File.join(File.dirname(__FILE__), 'README.md'))
+version          "1.1.1"
+recipe "bluepill::default", "Installs bluepill rubygem and set up management directories"

data/lib/cookbooks/bluepill/providers/service.rb

@@ -0,0 +1,155 @@
+#
+# Cookbook Name:: bluepill
+# Provider:: service
+#
+# Copyright 2010, Opscode, Inc.
+# Copyright 2012, Heavy Water Operations, LLC
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+require 'chef/mixin/shell_out'
+require 'chef/mixin/language'
+
+include Chef::Mixin::ShellOut
+
+action :enable do
+  config_file = ::File.join(node['bluepill']['conf_dir'],
+                            "#{new_resource.service_name}.pill")
+  unless @current_resource.enabled
+    link "#{node['bluepill']['init_dir']}/#{new_resource.service_name}" do
+      to node['bluepill']['bin']
+      only_if { ::File.exists?(config_file) }
+    end
+    case node['platform']
+    when "centos", "redhat", "freebsd", "amazon", "scientific", "fedora"
+      template "#{node['bluepill']['init_dir']}/bluepill-#{new_resource.service_name}" do
+        source "bluepill_init.erb"
+        cookbook "bluepill"
+        owner "root"
+        group node['bluepill']['group']
+        mode "0755"
+        variables(
+                  :service_name => new_resource.service_name,
+                  :config_file => config_file
+                  )
+      end
+
+      service "bluepill-#{new_resource.service_name}" do
+        action [ :enable ]
+      end
+    end
+    new_resource.updated_by_last_action(true)
+  end
+end
+
+action :load do
+  unless @current_resource.running
+    shell_out!(load_command)
+    new_resource.updated_by_last_action(true)
+  end
+end
+
+action :start do
+  unless @current_resource.running
+    shell_out!(start_command)
+    new_resource.updated_by_last_action(true)
+  end
+end
+
+action :disable do
+  if @current_resource.enabled
+    file "#{node['bluepill']['conf_dir']}/#{new_resource.service_name}.pill" do
+      action :delete
+    end
+    link "#{node['bluepill']['init_dir']}/#{new_resource.service_name}" do
+      action :delete
+    end
+    new_resource.updated_by_last_action(true)
+  end
+end
+
+action :stop do
+  if @current_resource.running
+    shell_out!(stop_command)
+    new_resource.updated_by_last_action(true)
+  end
+end
+
+action :restart do
+  if @current_resource.running
+    Chef::Log.debug "Restarting #{new_resource.service_name}"
+    shell_out!(restart_command)
+    new_resource.updated_by_last_action(true)
+    Chef::Log.debug "Restarted #{new_resource.service_name}"
+  end
+end
+
+def load_current_resource
+  @current_resource = Chef::Resource::BluepillService.new(new_resource.name)
+  @current_resource.service_name(new_resource.service_name)
+
+  Chef::Log.debug("Checking status of service #{new_resource.service_name}")
+
+  determine_current_status!
+
+  @current_resource
+end
+
+protected
+
+def status_command
+  "#{node['bluepill']['bin']} #{new_resource.service_name} status"
+end
+
+def load_command
+  "#{node['bluepill']['bin']} load #{node['bluepill']['conf_dir']}/#{new_resource.service_name}.pill"
+end
+
+def start_command
+  "#{node['bluepill']['bin']} #{new_resource.service_name} start"
+end
+
+def stop_command
+  "#{node['bluepill']['bin']} #{new_resource.service_name} stop"
+end
+
+def restart_command
+  "#{node['bluepill']['bin']} #{new_resource.service_name} restart"
+end
+
+def determine_current_status!
+  service_running?
+  service_enabled?
+end
+
+def service_running?
+  begin
+    if shell_out(status_command).exitstatus == 0
+      @current_resource.running true
+      Chef::Log.debug("#{new_resource} is running")
+    end
+  rescue Mixlib::ShellOut::ShellCommandFailed, SystemCallError
+    @current_resource.running false
+    nil
+  end
+end
+
+def service_enabled?
+  if ::File.exists?("#{node['bluepill']['conf_dir']}/#{new_resource.service_name}.pill") &&
+      ::File.symlink?("#{node['bluepill']['init_dir']}/#{new_resource.service_name}")
+    @current_resource.enabled true
+  else
+    @current_resource.enabled false
+  end
+end