tpiccioli
/
ansible-roles
forked from ISTI-ansible-roles/ansible-roles
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
ansible-roles/d4s_user_services_perms
History
Andrea Dell'Amico 44c7857c8f library/roles/d4s_user_services_perms: Manage the basic gcore case, where we only create a user. 
d4science-ghn-cluster: Playbook to provision access.d4science.org.
 		2016-03-01 14:14:12 +01:00
..
defaults library/roles/d4s_user_services_perms: Manage the basic gcore case, where we only create a user. 2016-03-01 14:14:12 +01:00
tasks library/roles/d4s_user_services_perms: Manage the basic gcore case, where we only create a user. 2016-03-01 14:14:12 +01:00
templates library/roles/d4s_user_services_perms: Install a README file inside the gcube home directory. Set up acls so that the gcube user can read/write the tomcat options files. 2015-07-24 12:00:37 +02:00
README.md library/roles/d4s_user_services_perms: Install a README file inside the gcube home directory. Set up acls so that the gcube user can read/write the tomcat options files. 2015-07-24 12:00:37 +02:00

README.md

This role assumes that only one tomcat instance is defined and running on the system.

Important note: the variable ‘http_port’ needs to be defined earlier in the calling playbook.

What the role does:

  • Install the sudoers config that permits the tomcat user to restart the service
  • Install the script that allows the tomcat user to start and stop the service without using the full path
  • Install the README file that explains where the options files are placed and how start/stop the service