Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Unified Diff: manifests/issuesserver.pp

Issue 5735669590654976: #753 - set up an order system to let eyeo employees file order requests (Closed)
Patch Set: #753 - set up an order system to let eyeo employees file order requests Created Aug. 1, 2014, 4:25 p.m.
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | modules/trac/files/eyeo_logo.png » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: manifests/issuesserver.pp
===================================================================
--- a/manifests/issuesserver.pp
+++ b/manifests/issuesserver.pp
@@ -1,5 +1,6 @@
node 'issues1' {
- include base
+
+ include base, private::trac
class {'trac':
domain => 'issues.adblockplus.org',
@@ -8,6 +9,91 @@
is_default => true,
}
+ trac::instance {'issues':
+ config => 'trac/trac.ini.erb',
+ description => 'Adblock Plus Issue Tracker',
+ location => '/',
+ logo => 'puppet:///modules/trac/adblockplus_logo.png',
+ database => 'trac',
+ permissions => "puppet:///modules/trac/permissions.csv",
+ }
+
+ trac::instance {'orders':
+ config => 'trac/orders.ini.erb',
+ description => 'Eyeo Order System',
+ location => '/orders',
+ logo => 'puppet:///modules/trac/eyeo_logo.png',
+ database => 'trac_orders',
+ permissions => "puppet:///modules/trac/order-permissions.csv",
+ }
+
+ # Transforming the auth_cookie table of the "new" Trac project into an
+ # insertable view for the "old" project's table of the same name avoids
+ # the need to convert the entire auth to htpasswd-file handling, which
+ # would be the official way to go for achieving a shared authentication.
+ exec { 'trac_auth_cookie_view':
+ command => "mysql -utrac -p'${private::trac::database_password}' trac_orders --execute '
+ DROP TABLE IF EXISTS auth_cookie;
+ CREATE VIEW auth_cookie AS SELECT * FROM trac.auth_cookie;'",
+ unless => "mysql -utrac -p'${private::trac::database_password}' trac_orders --execute '
+ SHOW CREATE VIEW auth_cookie'",
+ path => "/usr/bin:/usr/sbin:/bin:/usr/local/bin",
+ require => [
+ Exec["deploy_issues"],
+ Exec["deploy_orders"],
+ ],
+ }
+
+ # Synchronizing e-mail and password information between the project
+ # allows for logging in from any entry point - whilst maintaining a
+ # registration form (and process) in one project only.
+ cron {'trac_session_attribute_sync':
+ ensure => present,
+ user => trac,
+ minute => '*/30',
+ command => "mysql -utrac -p'${private::trac::database_password}' trac_orders --execute ' \
+ INSERT INTO session_attribute (sid, authenticated, name, value) SELECT sid, authenticated, name, value \
+ FROM trac.session_attribute WHERE authenticated = 1 AND name IN (\"email\", \"password\") \
+ ON DUPLICATE KEY UPDATE value=VALUES(value) ' >/dev/null
+ ",
+ require => Exec['trac_auth_cookie_view'],
+ }
+
+ # This directive is required due to legacy issues, where only one trac
+ # project was configured. Now we want to have more verbose names, e.g.
+ # tracd_issues and tracd_orders, but the spawn-fcgi module doesn't remove
+ # unmentioned former setups. So, in order to avoid conflicts or manual
+ # intervention during rollout, we must keep this statement here and never
+ # re-use the name again. Ugly, but neccessary.
+ spawn-fcgi::pool {"tracd":
+ ensure => absent,
+ require => Exec['tracd_kludge'],
+ }
+
+ # Unfortunately, the spawn-fcgi module is not capable of stopping the
+ # processes of pools that are changed to absent - simply because it removes
+ # the configuration file and the subsequent reload or restart does not
+ # recognize the pool any more. Thus, we have to ensure that the service is
+ # stopped before:
+ exec { 'tracd_kludge':
+ command => 'service spawn-fcgi stop',
+ onlyif => 'service spawn-fcgi status',
+ path => '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin',
+ }
+
+ # Pretty similar to the "tracd" pool issue above: The trac-admin initenv
+ # command would fail for environment-issues after creation of the directory
+ # structure, when it comes to the database setup (which already exists),
+ # if we do not handle the existing resources manually..
+ exec { 'trac_env_issues_kludge':
+ command => 'ln -s environment /home/trac/environment-issues',
+ before => Exec['trac_env_issues'],
+ path => "/usr/bin:/bin",
+ user => trac,
+ onlyif => 'test -d /home/trac/environment',
+ require => User['trac'],
+ }
+
class {'nagios::client':
server_address => 'monitoring.adblockplus.org'
}
« no previous file with comments | « no previous file | modules/trac/files/eyeo_logo.png » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld