Page Comparison

...

• Preferably on Friday before the Tuesday maintenance but no later than 8:00 a.m. the Monday before activate (or have someone activate) the regular maintenance schedule MOTD and set at the bottom the date for the next maintenance time. Patch weekend MOTD should be posted 3-4 days before the weekend.
• On Monday send an email to: sakai-releasemgt@ucdavis.edu

  • No Format
    Email Subject: SmartSite Maintenance : May 06, 2008 : 05:30 to 07:00 Email Body: Hello, We are performing scheduled maintenance on SmartSite on May 06, 2008 from 05:30 to 07:00. For more information, please see: https://confluence.ucdavis.edu:8443/confluence/x/URM Best, <Your Name>

    
    
• On Tuesday, after you have finished maintenance, reply to the above email with the following message:

  • No Format
    Email Body: Hello, We have finished maintenance on SmartSite. Users will be able to access SmartSite after the maintenance window ends at 07:00. Best, <Your Name>

    
    

Setup of deployment

• If deploying a staging release, follow the instructions here instead of the ones in this section. Resume work in the Deployment section after the special instructions are complete.

• Prior to deployment, run as yourself (not sakai):

sudo /ucd/local/sbin/set_status.sh maintenance

• In ~sakai/src, make sure to clear the oldest tag before checkout/building. We only have space to support two tags(current and next most recent)
• Start the deployment by building the prod tag as follows on the headnode:

1. Code Block
   ~/config-staging/tomcatclean.sh

   
   

2. Code Block
   cd ~/src

   
   

3. Code Block
   svn co https://mware.ucdavis.edu/svn/ucd-sakai/sakai/tags/sakai_2-5-x-prod-XYZ

   
   

4. Code Block
   cd sakai_2-5-x-prod-XYZ

   
   

5. Code Block
   patches/scripts/apply-patches.pl

   
   

6. Code Block
   mvn clean install sakai:deploy -P with-jsmath

   
   

• Next step is to deploy the sakai.properties tag in the staging area

1. Code Block
   cd $HOME/config-staging

   
   
2. Delete any old sakai.properties

3. Code Block
   svn export https://mware.ucdavis.edu/svn/ucd-sakai/sakai-properties/tags/sakai-properties-2-5-x-prod-XYZ/sakai.properties svn export https://mware.ucdavis.edu/svn/ucd-sakai/sakai-properties/tags/sakai-properties-2-5-x-prod-XYZ/jameskiller_whitelist.dat

   
   

Deployment

• Stop all nodes in the cluster by ~/bin/stop.sh and make sure all tomcat processes are dead (eg ps -ef | grep java| grep sakai)

• On each node do(starting with the head node):

1. Code Block
   cd $HOME

   
   

2. Code Block
   ./config-staging/setup-sakai-node.sh

   
   

3. Code Block
   cd $CATALINA_HOME/logs

   
   

4. Code Block
   ~/bin/start.sh ; tail -f catalina.out

   
   
5. Once sakai is fully up, test login and continue with the next node

After Deployment

• Make sure all JIRAs associated with the tag have a fix rev of the tag, and that they are all in proper state.

• Place each server back into normal mode:

sudo /ucd/local/sbin/set_status.sh normal

...