MLCR Deployment » History » Revision 20

« Previous | Revision 20/42 (diff) | Next »
Rogers, Chris, 06 June 2013 09:30

MLCR Deployment

There are three installations of MAUS in the MICE Local Control Room:

  • The current version .maus_release (bound to lp:maus)
  • The previous version .maus_release_old (bound to lp:maus)
  • A development copy .maus_control-room (bound to lp:~maus-mlcr/maus/control-room/)

The current and previous version are updated by leapfrogging; at the moment only the control-room version is used for online reconstruction, the control room stuff was never merged into the trunk. Note that versions are in hidden folders (prefixed by '.'). To see them do

ls -h
There is a soft link that points to the "default" version (for use by shifters). This should usually point at the current version .maus_release.

New version of main MAUS release

To update to a new version:

  1. Let MOM know what you are doing
  2. First move the current MAUS install onto the fall back release
    1. mv .maus_release_old .maus_release_old_
    2. mv .maus_release .maus_release_old
    3. Reconfigure the old install
      • cd .maus_release_old; ./configure; source
    4. Check it is okay
      • bash tests/unit_tests.bash; bash tests/application_tests.bash
  3. Next get the current MAUS release copy (or a version as specified by MAUS experts)
    1. Do bzr checkout lp:maus .maus_release or bzr checkout lp:maus -rMAUS-vx.y.z .maus_release
    2. Build the code cd .maus_release; ./install_build_test.bash
    3. Run the integration tests bash tests/application_tests.bash >& test.log
    4. Check that the online libraries are running okay python python tests/integration/test_distributed_processing/
    5. Run tests/integration/test_analyze_data_online/ Bring up a browser and look at pretty plots.
    6. Check that the integration tests passed; check that analyze_data_online and test_multi_vs_single_threaded tests did not skip.
  4. Check for changes in power cycle procedure Onrec_power_cycle_procedure or shifter instructions
  5. Check the updated installation functions correctly by following the shifter instructions
    • A cosmics run is ideal
  6. Remove the old old release rm -rf .maus_release_old_
  7. Add a note in the ELog
  8. Email MOGUL head and MOM to let them know that something changed

New version of control room branch

To update the control room branch

  1. Let MOM know what you are doing and MAUS online person.
  2. cd MAUS/.maus_control_room
  3. bzr update
  4. ./install_build_test.bash
  5. Run whatever tests you want

Apache server (Not used)

If you want to use the Apache web server, then:

  • Configure the web server,
    cd /home/mice/
    rm -rf media/thumbs/*
    rm -rf media/raw/*
  • As super user, restart Apache,
    /usr/local/apache2/bin/apachectl restart
  • Check the logs,
    more /usr/local/apache2/logs/error_log 
  • You should see something like,
    [Mon Mar 12 12:41:16 2012] [notice] Apache/2.2.22 (Unix) mod_wsgi/3.3 
     Python/2.7.2 configured -- resuming normal operations
  • If you get a warning like,
    httpd: Syntax error on line 55 of /usr/local/apache2/conf/httpd.conf: 
    Cannot load /usr/local/apache2/modules/ into server: 
    cannot open shared object file: No such file or directory
    • Then unset MAUS_ROOT_DIR and try again:
      unset MAUS_ROOT_DIR
      /usr/local/apache2/bin/apachectl restart

Updated by Rogers, Chris over 8 years ago · 20 revisions