diff options
author | Marcello Stanisci <marcello.stanisci@inria.fr> | 2017-04-23 10:56:02 +0200 |
---|---|---|
committer | Marcello Stanisci <marcello.stanisci@inria.fr> | 2017-04-23 10:57:09 +0200 |
commit | 337b99bf555b47246113a616b9e5eccf7cc17cb6 (patch) | |
tree | b4c3acb9265b2b3c9394dd869314b023f6ab4dc5 /tripwire_sysadmin.txt | |
parent | 0d63d56577e5ffdbf8e41e829a714191d1ee6d80 (diff) | |
download | deployment-337b99bf555b47246113a616b9e5eccf7cc17cb6.tar.gz deployment-337b99bf555b47246113a616b9e5eccf7cc17cb6.tar.bz2 deployment-337b99bf555b47246113a616b9e5eccf7cc17cb6.zip |
Beginning documentation of tripwire's guide.
Diffstat (limited to 'tripwire_sysadmin.txt')
-rw-r--r-- | tripwire_sysadmin.txt | 100 |
1 files changed, 100 insertions, 0 deletions
diff --git a/tripwire_sysadmin.txt b/tripwire_sysadmin.txt new file mode 100644 index 0000000..ee24dd3 --- /dev/null +++ b/tripwire_sysadmin.txt @@ -0,0 +1,100 @@ +This document explains how to manage services running at +tripwire. + +== BUILDBOT == + +(Note, 'worker' and 'slave' are the same thing) + +The user running the buildbot master is 'containers'. + +-- Master -- + +To start the master, log in as 'containers', and run: +$ ~/buildbot/start.sh +To stop it, run: +$ ~/buildbot/stop.sh + +There is also a "restart" script, runnable as follows: +$ ~/buildbot/restart.sh + +-- Selenium worker -- + +The 'containers' user is also responsible for running the +selenium buildbot worker. + +Start it with: +$ buildbot-worker start ~/buildbot/selenium_worker/ + +stop it with: +$ buildbot-worker stop ~/buildbot/selenium_worker/ + +-- Lcov worker -- + +The worker is implemented by the 'lcovslave' user. + +To start the worker, log in as 'lcovslave' and run: + +$ source ~/activate +$ taler-deployment-bbstart + +# To stop it: +# taler-deployment-bbstop + +-- Switcher worker -- + +This worker is responsible for switching the blue/green user +upon every push in the whole Taler codebase. The switch occurs +after a successful compilation. + +The worker is implemented by the 'testswitcher' user. This user +has some additional "sudo" rights, since it has to act as "test-blue", +"test-green" and "test" user in order to accompish its task. +Note that the "sudo file" is tracked in this ('deployment') +repository, under the 'sudoers' directory. + +To start the worker, log in as 'lcovslave' and run: + +$ source ~/activate +$ taler-deployment-bbstart + +# To stop it: +# taler-deployment-bbstop + + +== SELENIUM TESTS == + +Selenium test can be run manually by logging in as 'containers' and just +invoking the script: + +$ launch_selenium_test + +Please note that there is NO DOCKER involved in this activity. + +== LCOV == + +Lcov data cab be generated manually by logging in as 'lcovslave', +and issuing the following commands: + +$ source ~/activate +$ taler-deployment-build --coverage + +The lcov.taler.net Web site takes its content from 'lcovslave', by +symlinking to its codebases, see below. + +root@tripwire:~# ls -l /var/www/lcov.taler.net/ +total 0 +lrwxrwxrwx 1 root root 38 Nov 13 20:23 exchange -> /home/lcovslave/exchange/doc/coverage/ +lrwxrwxrwx 1 root root 38 Nov 13 20:24 merchant -> /home/lcovslave/merchant/doc/coverage/ + +== TUTORIALS BUILD == + +The taler.net Web site links to tutorials/manuals, +both in pdf and html format. To manually build those +linked tutorials, do: + +$ /var/www/update_manual.sh +$ /var/www/update_tutorials.sh + +== Link to per-user Taler set-up == + +== OTHERS ? == |