tripleo-image-elements/elements/os-svc-install
Richard Su bd228e4b3a Fix /var/run SELinux file contexts
/var/run/<service> needs to be relabeled with the correct file
contexts. With systemd, these directories are created anew each
boot by /lib/systemd/system/<service>-create-dir.service.
os-svc-daemon was updated to correct the file contexts.

Change-Id: I6487d0726db08912eed3062dfee2552940eadcfb
Closes-Bug: 1346559
2014-08-01 17:12:31 -07:00
..
bin Fix /var/run SELinux file contexts 2014-08-01 17:12:31 -07:00
install.d Adds mysql-dev and mariadb-dev elements 2014-03-26 21:22:31 +01:00
tests Add unit tests for os-svc-daemon 2014-03-28 19:55:29 -05:00
upstart Add a service enable/disable mechanism for upstart 2013-12-10 20:55:31 -08:00
__init__.py Add unit tests for os-svc-daemon 2014-03-28 19:55:29 -05:00
element-deps Fix /var/run SELinux file contexts 2014-08-01 17:12:31 -07:00
README.md Add -i options to os-svc-install/os-svc-daemon... 2014-03-24 09:55:53 -04:00
source-repository-eventlet Pull in patched eventlet to fix Second Simultaneous errors 2014-07-28 10:07:01 -04:00

Command line utilities to simplify installation of OpenStack services.

os-svc-install

Given a git repo url, pip-install the repo and all of its python dependencies into a virtualenv. NOTE: By default the virtualenv is installed to /opt/stack/venvs/SERVICENAME but this can be customized. NOTE: By default services do not autostart until os-svc-enable is called.

os-svc-daemon

Given a system service command line and run-as user, generate and install system service start script. See output of os-svc-daemon -h for online help.

os-svc-enable

Enable the given service name so it starts on boot. This is typically called in an os-refresh-config/post-configure.d script to enable a service once it has been fully configured.

os-svc-enable-upstart (upstart distros only)

Given an upstart job and an action, acts on the enabled or disabled state of jobs produced by os-svc-daemon. This requires the os-svc-enable upstart job which is installed by this element as well. There is also an action, 'enabled', which allows checking whether or not a service is enabled; the command exits 0 if it is enabled, or 1 if it is not. A disabled service will not be started automatically nor can it be manually started.

example usage

# clone nova, and install it and its dependencies to /opt/stack/venvs/nova
os-svc-install -u nova -r git://git.openstack.org/openstack/nova.git

# install a system-start script for nova-api
os-svc-daemon -e 'foo=bar bar=baz' -n nova-api -u nova -c /opt/stack/venvs/nova/bin/nova-api -- --config-dir /etc/nova

# enable nova-api so that it starts on boot
os-svc-enable -n nova-api