Skip to content
Browse files

Import bluepill version 1.0.4

  • Loading branch information...
1 parent 3533ef8 commit ef6fda2183e8af8ee401863f190f61929c282dd5 @phunehehe committed Jul 12, 2012
View
22 bluepill/CHANGELOG.md
@@ -0,0 +1,22 @@
+## 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
View
29 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.
View
201 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.
View
80 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.
View
34 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
View
30 bluepill/metadata.json
@@ -0,0 +1,30 @@
+{
+ "name": "bluepill",
+ "description": "Installs bluepill gem and configures to manage services, includes bluepill_service LWRP",
+ "long_description": "Description\n===========\n\nInstalls bluepill RubyGem and configures it to manage services. Also includes a LWRP.\n\nRequirements\n============\n\nBluepill 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.\n\nAttributes\n==========\n\nDefault locations for bluepill are in \"FHS compliant\" locations.\n\n* `node[\"bluepill\"][\"bin\"]` - Path to bluepill program, default is 'bluepill' in the RubyGems binary directory.\n* `node[\"bluepill\"][\"logfile\"]` - Location of the bluepill log file, default \"/var/log/bluepill.log\".\n* `node[\"bluepill\"][\"conf_dir\"]` - Location of service config files (pills), default \"/etc/bluepill\".\n* `node[\"bluepill\"][\"pid_dir\"]` - Location of pidfiles, default \"/var/run/bluepill\"\n* `node[\"bluepill\"][\"state_dir\"]` - Location of state directory, default \"/var/lib/bluepill\"\n* `node[\"bluepill\"][\"init_dir\"]` - Location of init script directory, default selected by platform.\n\nResources/Providers\n===================\n\nThis 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.\n\n service \"my_app\" do\n provider bluepill_service\n action [:enable, :load, :start]\n end\n\n bluepill_service \"my_app\" do\n action [:enable, :load, :start]\n end\n\nThe load action should probably always be specified, to ensure that if bluepill isn't running already it gets started. The\n\nThe 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.\n\nUsage\n=====\n\nBe 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.\n\nIf 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.\n\nExample pill template resource and .erb file:\n\n template \"/etc/bluepill/my_app\" do\n source \"my_app.pill.erb\"\n end\n\n Bluepill.application(\"my_app\") do |app|\n app.process(\"my_app\") do |process|\n process.pid_file = \"/var/run/my_app.pid\"\n process.start_command = \"/usr/bin/my_app\"\n end\n end\n\nSee bluepill's documentation for more information on creating pill templates.\n\nLicense and Author\n==================\n\nAuthor:: Joshua Timberman (<joshua@opscode.com>)\n\nCopyright 2010, Opscode, Inc.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n http://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n",
+ "maintainer": "Opscode, Inc.",
+ "maintainer_email": "cookbooks@opscode.com",
+ "license": "Apache 2.0",
+ "platforms": {
+ },
+ "dependencies": {
+ },
+ "recommendations": {
+ },
+ "suggestions": {
+ },
+ "conflicting": {
+ },
+ "providing": {
+ },
+ "replacing": {
+ },
+ "attributes": {
+ },
+ "groupings": {
+ },
+ "recipes": {
+ "bluepill::default": "Installs bluepill rubygem and set up management directories"
+ },
+ "version": "1.0.4"
+}
View
7 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.0.4"
+recipe "bluepill::default", "Installs bluepill rubygem and set up management directories"
View
109 bluepill/providers/service.rb
@@ -0,0 +1,109 @@
+#
+# Cookbook Name:: bluepill
+# Provider:: service
+#
+# 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.
+#
+
+require 'chef/mixin/command'
+require 'chef/mixin/language'
+include Chef::Mixin::Command
+
+action :enable do
+ config_file = "#{node['bluepill']['conf_dir']}/#{new_resource.service_name}.pill"
+
+ unless @bp.enabled
+ link "#{node['bluepill']['init_dir']}/#{new_resource.service_name}" do
+ to node['bluepill']['bin']
+ only_if { ::File.exists?(config_file) }
+ end
+ end
+
+ case node['platform']
+ when "centos", "redhat", "freebsd"
+ 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
+end
+
+action :load do
+ unless @bp.running
+ execute "#{node['bluepill']['bin']} load #{node['bluepill']['conf_dir']}/#{new_resource.service_name}.pill"
+ end
+end
+
+action :start do
+ unless @bp.running
+ execute "#{node['bluepill']['bin']} #{new_resource.service_name} start"
+ end
+end
+
+action :disable do
+ if @bp.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
+ end
+end
+
+action :stop do
+ if @bp.running
+ execute "#{node['bluepill']['bin']} #{new_resource.service_name} stop"
+ end
+end
+
+action :restart do
+ if @bp.running
+ execute "#{node['bluepill']['bin']} #{new_resource.service_name} restart"
+ end
+end
+
+def load_current_resource
+ @bp = Chef::Resource::BluepillService.new(new_resource.name)
+ @bp.service_name(new_resource.service_name)
+
+ Chef::Log.debug("Checking status of service #{new_resource.service_name}")
+
+ begin
+ if run_command_with_systems_locale(:command => "#{node['bluepill']['bin']} #{new_resource.service_name} status") == 0
+ @bp.running(true)
+ end
+ rescue Chef::Exceptions::Exec
+ @bp.running(false)
+ nil
+ end
+
+ if ::File.exists?("#{node['bluepill']['conf_dir']}/#{new_resource.service_name}.pill") && ::File.symlink?("#{node['bluepill']['init_dir']}/#{new_resource.service_name}")
+ @bp.enabled(true)
+ else
+ @bp.enabled(false)
+ end
+end
View
33 bluepill/recipes/default.rb
@@ -0,0 +1,33 @@
+#
+# Cookbook Name:: bluepill
+# Recipe:: 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.
+#
+
+gem_package "i18n"
+gem_package "bluepill"
+
+[
+ node["bluepill"]["conf_dir"],
+ node["bluepill"]["pid_dir"],
+ node["bluepill"]["state_dir"]
+].each do |dir|
+ directory dir do
+ recursive true
+ owner "root"
+ group node["bluepill"]["group"]
+ end
+end
View
26 bluepill/resources/service.rb
@@ -0,0 +1,26 @@
+#
+# Cookbook Name:: bluepill
+# Resource:: service
+#
+# 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.
+#
+
+actions :start, :stop, :enable, :disable, :load, :restart
+
+attribute :service_name, :name_attribute => true
+attribute :enabled, :default => false
+attribute :running, :default => false
+attribute :variables, :kind_of => Hash
+attribute :supports, :default => { :restart => true, :status => true }
View
32 bluepill/templates/centos/bluepill_init.erb
@@ -0,0 +1,32 @@
+#!/bin/sh
+#
+# Author: Jamie Winsor (<jamie@vialstudios.com>)
+#
+# chkconfig: 345 99 1
+# Description: Bluepill loader for <%= @service_name %>
+# Provides: <%= @service_name %>
+# Default-Start: 3 4 5
+# Default-Stop: 0 1 2 6
+
+BLUEPILL_BIN=<%= node['bluepill']['bin'] %>
+BLUEPILL_CONFIG=<%= @config_file %>
+SERVICE_NAME=<%= @service_name %>
+
+case "$1" in
+ start)
+ echo "Loading bluepill configuration for $SERVICE_NAME "
+ $BLUEPILL_BIN load $BLUEPILL_CONFIG
+ ;;
+ stop)
+ $BLUEPILL_BIN $SERVICE_NAME stop
+ $BLUEPILL_BIN $SERVICE_NAME quit
+ ;;
+ restart)
+ $0 stop
+ $0 start
+ ;;
+ *)
+ echo "Usage: $0 {start|stop|restart}"
+ exit 1
+ ;;
+esac
View
31 bluepill/templates/freebsd/bluepill_init.erb
@@ -0,0 +1,31 @@
+#!/bin/sh
+##
+# PROVIDE: named
+# REQUIRE: SERVERS cleanvar
+# KEYWORD: shutdown
+#
+
+. /etc/rc.subr
+
+name="<%= @service_name %>"
+rcvar=`set_rcvar`
+
+# Set some defaults
+<%= @service_name %>_enable=${<%= @service_name %>_enable:-"NO"}
+
+pidfile="/var/run/<%= @service_name %>.pid"
+command="/usr/local/bin/bluepill"
+
+start_precmd="${command} load <%= node['bluepill']['conf_dir'] %>/<%= @service_name %>.pill"
+start_cmd="${command} ${name} start"
+
+status_cmd="${command} ${name} status"
+
+stop_cmd="${command} ${name} stop"
+stop_postcmd="${command} ${name} quit"
+
+load_rc_config ${name}
+
+PATH="${PATH}:/usr/local/bin"
+
+run_rc_command "$1"

0 comments on commit ef6fda2

Please sign in to comment.
Something went wrong with that request. Please try again.