Changes between Version 19 and Version 20 of Archive/SeattleGeniProductionHttp

Changes between Version 19 and Version 20 of Archive/SeattleGeniProductionHttp

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 19 and Version 20 of Archive/SeattleGeniProductionHttp

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 19 and Version 20 of Archive/SeattleGeniProductionHttp

Show
Ignore:
Timestamp:
07/05/12 19:06:06 (7 years ago)
Author:
leonwlaw
Comment:

Updated SeattleGENI references to SeattleClearinghouse?. Did not change instances in filenames nor links.

Legend:

Unmodified
Added
Removed
Modified
  • Archive/SeattleGeniProductionHttp

    v19 v20  
    1 = SeattleGENI in Production = 
     1= !SeattleClearinghouse in Production = 
    22 
    3 The SeattleGENI portal runs on Apache and uses mod_python to interface with django. 
    4 This page describes how to redeploy SeattleGENI from the current svn trunk as well 
    5 as some additional configuration information for using SeattleGENI in production. 
     3The !SeattleClearinghouse portal runs on Apache and uses mod_python to interface with django. 
     4This page describes how to redeploy !SeattleClearinghouse from the current svn trunk as well 
     5as some additional configuration information for using !SeattleClearinghouse in production. 
    66 
    7  * For info on installing the necessary software to run GENI, see [wiki:SeattleGeniInstallation]. 
     7 * For info on installing the necessary software to run GENI, see [wiki:!SeattleClearinghouseInstallation]. 
    88 
    99---- 
     
    1414---- 
    1515 
    16 The way we have things setup on seattlegeni and betabox, if you try to access the website before running the other service after you have just deployed then you are likely to get a permissions error of apache not being able to write files in /home/geni/live/seattle. However, this is not a problem if you use the start_seattlegeni_components.sh script because it will start the lockserver and backend before restarting apache, and the result will be that all of the '.repy' files that need to be turned into '_repy.py' will have already been processed, so the website (mod_python running under apache's user) won't try to do that. 
     16The way we have things setup on !SeattleClearinghouse and betabox, if you try to access the website before running the other service after you have just deployed then you are likely to get a permissions error of apache not being able to write files in /home/geni/live/seattle. However, this is not a problem if you use the start_seattlegeni_components.sh script because it will start the lockserver and backend before restarting apache, and the result will be that all of the '.repy' files that need to be turned into '_repy.py' will have already been processed, so the website (mod_python running under apache's user) won't try to do that. 
    1717 
    1818== Apache Settings == 
     
    2929---- 
    3030 
    31 The SeattleGENI website's log data goes to the apache error log. However, the log files of the 
     31The !SeattleClearinghouse website's log data goes to the apache error log. However, the log files of the 
    3232individual scripts (polling daemons, transition scripts, lockserver, and backend) go to file 
    3333in the /home/geni/logs directory. These need to be rotated by logrotate. 
     
    4242  missingok 
    4343  notifempty 
    44   # The seattlegeni scripts don't know how to start a new log file, so we have 
     44  # The !SeattleClearinghouse scripts don't know how to start a new log file, so we have 
    4545  # logrotate make a copy of the log files and truncate the original ones. 
    4646  copytruncate 
     
    5555 
    5656[[BR]] 
    57 == Redeploying SeattleGENI from SVN == 
     57== Redeploying !SeattleClearinghouse from SVN == 
    5858---- 
    5959 
    60 To deploy SeattleGENI code from SVN trunk into production: 
    61   1. Log in to either seattlegeni.cs or betabox.cs (depending on which installation you are updating). 
     60To deploy !SeattleClearinghouse code from SVN trunk into production: 
     61  1. Log in to either !SeattleClearinghouse.cs or betabox.cs (depending on which installation you are updating). 
    6262  1. Get a root shell: `sudo -i` 
    6363  1. Open the screen running as root: `screen -r` 
     
    7474All components started. Kill this process (CTRL-C or 'kill 24038') to stop all started components (except apache). 
    7575}}} 
    76   1. Press CTRL-C and wait for `start_seattlegeni_components.sh` to exit (you will see "Shutting down seattlegeni components." a few times, that's OK). 
     76  1. Press CTRL-C and wait for `start_seattlegeni_components.sh` to exit (you will see "Shutting down !SeattleClearinghouse components." a few times, that's OK). 
    7777  1. Run the command `/home/geni/update_seattlegeni_from_trunk.sh`. Answer "y" when it asks. It will look like this: 
    7878{{{