ansible-roles/d4s_user_services_perms
Andrea Dell'Amico 29c3b9357a d4s_user_services_perms: More scenarios that involve nfs (so no ACLs) and common main group between users. 2017-10-24 13:46:32 +02:00
..
defaults library/roles/d4s_user_services_perms: Add a script that recursively sets the ACLs. 2017-08-13 20:11:38 +02:00
tasks d4s_user_services_perms: More scenarios that involve nfs (so no ACLs) and common main group between users. 2017-10-24 13:46:32 +02:00
templates d4s_user_services_perms: More scenarios that involve nfs (so no ACLs) and common main group between users. 2017-10-24 13:46:32 +02:00
README.md library/roles/d4s_user_services_perms: Now it's possible to create additional users on smartgears nodes too. 2017-07-03 16:51:41 +02:00

README.md

Several different scenarios are covered.

  1. One smartgears tomcat instance, installed inside the users home
  2. One or more tomcat instances, each instance installed inside its users home
  3. One service, not tomcat based, installed inside the users home
  4. One service, installed inside the users home, not managed by other ansible playbooks (only the user is created)
  5. ACLs are used if more than one user must be able to read/write some common directories or files. This works both with the gcore and the smartgears cases

Important note: the variable http_port(s) needs to be defined earlier in the calling playbook.

What the role does:

  • Installs the sudoers config that permits the user to restart the service
  • Installs the script that allows the user to start and stop the service without using the full path
  • Installs the README file that explains where the options files are placed and how start/stop the service
  • The default open files limits are increased
  • Creates additional users if needed, and adds ACLS to allow them access shared directories