Page Comparison

...

• (01:55 Thomas/Emily) Backup all configuration files on production staging area
  • /afs/.ucdavis.edu/app/sakai/staging/config/*

    • Code Block
      mkdir /afs/.ucdavis.edu/app/sakai/staging/config/config-2-4-x.bak cp /afs/.ucdavis.edu/app/sakai/staging/config/* /afs/.ucdavis.edu/app/sakai/staging/config/config-2-4-x.bak/

• (02:10 Thomas/Emily) Start process of preparing Sakai v2.4.x source on the head node (stubing).
• ** Getting the source code:

  • • Code Block
      cd ~/src svn co https://mware.ucdavis.edu/svn/ucd-sakai/sakai/tags/sakai_2-4-x-prod-001

  • Setting up the build environment:
  • ~/build.properties

    • Code Block
      maven.repo.remote=http://source.sakaiproject.org/maven/,http://svn.ucdavis.edu/maven/,http://www.ibiblio.org/maven2/ maven.tomcat.home=/ucd/opt/sakai/tomcat-staging/ maven.compile.source = 1.5 maven.compile.target = 1.5

  • ~/.bash_profile

    • Code Block

      PATH=/ucd/opt/java5/bin:/ucd/opt/maven/bin:$PATH MAVEN_HOME=/ucd/opt/maven CATALINA_HOME=/ucd/pkg/apache-tomcat JAVA_HOME=/ucd/opt/java5 JAVA_OPTS=" -d64 -server -Xmx6144m -Xms6144m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:PermSize=256m -XX:MaxPermSize=512m -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Dsakai.home=/ucd/opt/sakai/sakai-home/" CATALINA_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9000 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false" MAVEN_OPTS="-Xmx1024m -Xms1024m" export PATH MAVEN_HOME CATALINA_HOME JAVA_HOME JAVA_OPTS CATALINA_OPTS MAVEN_OPTS

  • Delete old tomcat content

    • Code Block
      rm -fr /ucd/pkg/apache-tomcat/*

  • Delete old tomcat staging build

    • Code Block
      cd ~/bin ./tomcatclean.sh

  • Build the source code

    • Code Block
      cd ~/src/sakai_2-4-x-prod-001 maven sakai

  • Copy staged tomcat

    • Code Block
      cd /ucd/pkg/apache-tomcat/ cp -R /afs/.ucdavis.edu/app/sakai/staging/tomcat/apache-tomcat-5.5.23/* .

• (03:00 Thomas/Emily) Making sure all the configuration files are in place for v2.3.x such as sakai.properties etc.
  • Configure JAVA_OPTS to allow JMX access via JConsole
  • Synchronize all configuration files on the head node (stubing) with the AFS configuration stating area
    • /afs/.ucdavis.edu/app/sakai/staging/config
  • Start-up head node (stubing) and check catalina.out for any errors
    • Make sure that "auto.ddl=true" for first time startup on head node
    • Check catalina.out for DB errors
  • Once the head node started up without any errors, shut it down again
  • Start-up head node (stubing) again but this time "auto.ddl=false"
    • Make sure that there are no errors in catalina.out
  • Access head node and perform any appropriate testing
  • If there are no errors/problems, perform installation on second node (walton)
  • Start-up walton and perform any appropriate testing
• (04:00 Kirk, Sandra, ...) Release SmartSite for initial testing to determine "successful upgrade"
  • Access it via:
    • https://smartsite.ucdavis.edu:8443/portal
      • https://stubing.ucdavis.edu:8443/portal
      • https://walton.ucdavis.edu:8443/portal
• (07:00 Joncarlo) Adjust iptables on all nodes (stubing, walton) to give public access again
• (07:05) System ready for public access

Fallback Procedure (If needed)

• In case anything goes wrong that cannot be fixed within the allocated maintenance window we perform the following tasks
• (08:00 Thomas/Emily) Shutdown all application servers
• (08:10 Prabhu) Restore Sakai internal production database on caje
• (08:40 Thomas/Emily) Install latest sakai-core-2-3-x-prod snapshot on all application nodes (stubing, walton)
  • Restore v2.3.x configuration files
• (09:30 Thomas/Emily) Start nodes and test
• (09:40 Kirk, Sandra, ...) Start testing
• (10:00 Joncarlo) Adjust iptables
• (10:05) System ready for public access

Post Upgrade TODOs:

• ...