Rudder

It should be able to manage the webapp with minimal dependencies from other system techniques.
Minimum requirements:

Jetty¶

• Restart rudder-jetty if the API is down in 2 consecutives runs
• Reload the technique library if the file /opt/rudder/etc/force_technique_reload exists, and remove it afterward
• Compress webapp logs
• Verify that the /var/rudder/configuration-repository exists and is not locked for more thant 5 minutes
• Insert disclaimer in:
  • /opt/rudder/etc/rudder-web.properties
• Force 600 root root on:
  • /opt/rudder/etc/rudder-web.properties
  • /opt/rudder/etc/rudder-passwords.conf
  • /opt/rudder/etc/rudder-users.xml
• Force postgres password from /opt/rudder/etc/rudder-passwords.conf in:
  • /opt/rudder/etc/rudder-web.properties
• Force ldap password from /opt/rudder/etc/rudder-passwords.conf in:
  • /opt/rudder/etc/rudder-web.properties
• Force webdav login/password from /opt/rudder/etc/rudder-passwords.conf in:
  • /opt/rudder/etc/rudder-web.properties
• Symlink the ppkey of the root server from ${sys.workdir}/ppkeys/localhost.pub to ${sys.workdir}/ppkeys/root-${sys.key_digest}.pub
• Force service to be started and enabled
• Restart jetty if needed

common¶

• Configure the file /etc/logrotate.d/rudder from the template ${sys.workdir}/inputs/server-roles/logrotate.conf/rudder
• Define the roles classes