This is a Chef cookbook for the remote administration tool Rundeck. It installs the Rundeck package (either on deb or rpm format) and configures various aspects of the software.
The latest and greatest revision of this cookbook will always be available at https://github.com/priestjim/chef-rundeck
The following cookbooks are direct dependencies because they're used for common "default" functionality.
- java
- apt
- yum
- logrotate
In order to install the Chef discovery service, you'll need the supervisor
cookbook.
In order to install the NGINX proxy site, you'll either need the openresty
or
nginx
cookbook.
The following platforms are supported and tested using Vagrant 1.2:
- Ubuntu 12.04
- CentOS 6.4
Other Debian and RHEL family distributions are assumed to work.
The cookbook converges best on Chef installations >= 10.18.2
Attributes are split in files semantically:
-
node['rundeck']['deb_version']
- The Rundeck version to be installed for Debian-based distributions. -
node['rundeck']['rpm_version']
- The Rundeck version to be installed for RPM-based distributions. -
node['rundeck']['node_name']
- The Rundeck node name. Defaults tonode.name
-
node['rundeck']['node_name']
- The port Rundeck HTTP server runs on. -
node['rundeck']['log4j_port']
- The Rundeck Log4J port. -
node['rundeck']['public_rss']
- Enables an unauthenticated RSS feed for jobs. -
node['rundeck']['logging_level']
- The default logging level for Rundeck. -
node['rundeck']['admin']['encrypted_data_bag']
- Enables loading the Rundeck administrator credentials using Chef encrypted data bags instead of simple ones. -
node['rundeck']['admin']['data_bag']
- The data bag name for the administrator credentials -
node['rundeck']['admin']['data_bag_id']
- The data bag item name for the administrator credentials -
node['rundeck']['admin']['username']
- Hardcoded administrator username in case data bags are not available (i.e. chef-solo runs) -
node['rundeck']['admin']['password']
- Hardcoded administrator password in case data bags are not available (i.e. chef-solo runs) -
node['rundeck']['admin']['ssh_key']
- Hardcoded administrator private SSH key in case data bags are not available (i.e. chef-solo runs) -
node['rundeck']['mail']
- Hash with various SMTP parameters used by Rundeck for notifications. -
node['rundeck']['mail']['recipients_data_bag']
- The name of the data bag to be searched for recipients of mails for administrative purposes. -
node['rundeck']['mail']['recipients_query']
- A standard Chef query to use for searching for administrative contacts. -
node['rundeck']['mail']['recipients_field']
- Field to use for the administrative e-mail. Must be in standard hash notation and will be eval'ed (i.e. "['email']")
-
node['rundeck']['chef']['port']
- TCP port to run the chef-rundeck discovery service -
node['rundeck']['chef']['client_key']
- Hardcoded Chef client key in case data bags are not available -
node['rundeck']['chef']['port']
- Hardcoded Chef client name in case data bags are not available
-
node['rundeck']['ssh']['user']
- Default SSH user with whom Rundeck will login to the servers. -
node['rundeck']['ssh']['timeout']
- SSH connection timeout in milliseconds. -
node['rundeck']['ssh']['port']
- Default SSH port to connect to.
-
node['rundeck']['java']['enable_jmx']
- Defines a set of flags in order to enable JMX monitoring on the Rundeck installation -
node['rundeck']['java']['allocated_memory']
- Defines the maximum heap memory available to Rundeck's JVM -
node['rundeck']['java']['thread_stack_size']
- Defines the default thread stack size for the Rundeck's JVM
-
node['rundeck']['proxy']['hostname']
- Defines the default hostname used in the NGINX proxy instance. -
node['rundeck']['proxy']['default']
- Set to true to enable the NGINX default server flags for the Rundeck proxy virtual host.
The default
recipe will install the official Rundeck package for your specific distribution and install various
configuration files needed for Rundeck to operate. If you need SSL support, it would be better to use a reverse proxy for
this (such us NGINX or Apache2) since Rundeck's SSL support requires various complicated steps (all hail Java).
Log rotation of Rundeck's and Chef-Rundeck's logs is managed by a logrotate
job.
The default
recipe will install and enable either a SYSV-standard service for Redhat and Debian based distributions
or an Upstart service for Ubuntu installations.
The cookbook also needs a custom Rundeck user that will be used to execute remote jobs. You need to create the user before installing Rundeck and then define a passwordless RSA SSH key for the user in this cookbook's properties.
All credentials used are retrieved from:
- An encrypted data bag if the
node['rundeck']['admin']['encrypted_data_bag']
attribute is enabled - A simple data bag otherwise
- In case there is no data bag defined, administrative attributes are retrieved from node attributes
The chef
recipe will install the chef-rundeck
gem using the Ruby bundled with the Chef omnibus package. That way, no
extra dependencies occur (i.e. rbenv or rvm or a packaged ruby).
Supervisor from the supervisor
cookbook is used to start and supervise the service.
As with default
, all credentials (Chef client key and client name) used are retrieved from:
- An encrypted data bag if the
node['rundeck']['admin']['encrypted_data_bag']
attribute is enabled - A simple data bag otherwise
- In case there is no data bag defined, administrative attributes are retrieved from node attributes
The proxy
recipe will install an NGINX configuration file that exposes Rundeck through a reverse proxy HTTP interface.
The Rundeck cookbook requires some data to be available in data bags. Depending on the value of
node['rundeck']['admin']['encrypted_data_bag']
, the data bag data will be loaded via encrypted data bag
methods or plain. You can select the data bag name and ID via the node['rundeck']['admin']['data_bag']
and node['rundeck']['admin']['data_bag_id']
attributes. The following attributes must be present in the
selected data bag:
username
: Used as the default administrator's username created during the initial installation of Rundeck.password
: Used the default administrator's password created during the initial installation of Rundeck.ssh_key
: Used in place of the Rundeck SSH user's RSA private key.
If you are using the rundeck::chef
recipe, the following must be present in the data bag too:
client_key
: The Chef client's private key in PEM format.client_name
: The Chef client's name.
In addition to administrative attributes, data bags are used in mail recipient search. The search query searches among the
node['rundeck']['mail']['recipients_data_bag']
data bag using a standard Chef query defined in
node['rundeck']['mail']['recipients_query']
and from the results retrieves the field
defined in node['rundeck']['mail']['recipients_field']
using standard Ruby eval.
So, if you are looking for the user['notifications']['email']
field in your data bags
for your mail recipients, you should define it as:
node['rundeck']['mail']['recipients_field'] = "['notifications']['email']"
The cookbook includes the rundeck_user
LWRP. The LWRP can be used to create users
in Rundeck (see http://rundeck.org/docs/administration/authentication.html#realm.properties) through the standard
realm.properties
file. Only MD5 and CRYPT encryption is supported as an encryption scheme, along with plain-text.
The following actions are supported:
create
- Creates a Rundeck user if it does not exist already.update
- Updates a Rundeck user.delete
- Removes a Rundeck user.
The following attributes are used in the LWRP:
name
- The actual Rundeck username.password
- The password in plain text.roles
- The Rundeck roles that this user is a member of.encryption
- One ofcrypt
,md5
,plain
.
The LWRP can be used like
rundeck_user 'ops' do
password '123abc'
encryption 'md5'
roles %w{ user admin architect deploy build }
action :create
end
Include the recipe on your node or role. Modify the attributes as required in a role cookbook to change how various configuration is applied per the attributes section above.
If you need to alter the location of various cookbook_file
directives, use chef_rewind
.
- Author:: Panagiotis Papadomitsos (pj@ezgr.net)
Copyright 2013, Panagiotis Papadomitsos
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.