D4Science Infrastructure

I'm going to create two tasks:

• One that changes the defaults for the root user
• One that changes the limits for the application user (tomcat/gcube/life/whatever), with 16000 for both soft and hard limit. The value will be configurable by setting a variable.

We now have two tasks.

One sets the root defaults and it will be executed on all our provisioned hosts.

The second one is run by the library/roles/d4s_user_services_perms role and sets the files limits for the d4science user (gcube on the smartgears nodes, life on the portals). The default for this one is 16000 and it can be changed setting the variable

limits_nofile_value

If a more complex setup is needed, an array of variables must be set. The default is:

security_limits:
  - { domain: '{{ d4science_user }}', l_item: 'nofile', type: 'soft', value: '{{ limits_nofile_value }}' }
  - { domain: '{{ d4science_user }}', item: 'nofile', type: 'hard', value: '{{ limits_nofile_value }}' }

Note: the services managed by upstart need the limits to be set inside the upstart file under /etc/init. This is the case of liferay (already managed).