TEST: Setup Sakai Cluster
The following information describes a Sakai Clustered TEST setup. Once the test is completed, this information will be updated with PRODUCTION relevant information.
JIRA: SAK-130
Load Balancer
- IP: 169.237.104.20
- DNS: smartsite-test.ucdavis.edu
Nodes
- littlejohn
- walton
- braddock
Sakai system user on each node
- User name: sakai
- Home: /ucd/opt/sakai
AFS staging volume
- /afs/.ucdavis.edu/app/sakai-test/staging
- /afs/.ucdavis.edu/app/sakai-test/staging/tomcat
- /afs/.ucdavis.edu/app/sakai-test/staging/config
- /afs/.ucdavis.edu/app/sakai-test/staging/src
AFS content links
- The following soft links need to be created on each node
/var/sakai/content --> /afs/.ucdavis.edu/app/sakai-test/misc/content/smartsite /var/sakai/archive --> /afs/.ucdavis.edu/app/sakai-test/misc/archive/smartsite /var/sakai/ucd-data --> /afs/.ucdavis.edu/app/sakai-test/misc/ucd-data/smartsite /var/melete --> /afs/.ucdavis.edu/app/sakai-test/misc/melete/smartsite/melete /var/meleteDocs --> /afs/.ucdavis.edu/app/sakai-test/misc/melete/smartsite/meleteDocs /var/uploads --> /afs/.ucdavis.edu/app/sakai-test/misc/melete/smartsite/uploads /var/samigo --> /afs/.ucdavis.edu/app/sakai-test/misc/samigo/smartsite
Environment setup
- /ucd/pkg/jdk1.5.0_09
- Create soft-link: /ucd/opt/java5 --> /ucd/pkg/jdk1.5.0_09
- /ucd/pkg/1.4.2_12
- Create soft-link: /ucd/opt/java --> /ucd/pkg/1.4.2_12
- /ucd/pkg/maven-1.0.2
- Create soft-link: /ucd/opt/maven --> /ucd/pkg/maven-1.0.2
Common files in staging area
- /afs/.ucdavis.edu/app/sakai-test/staging/tomcat/..
- apache-tomcat-5.5.17
- /afs/.ucdavis.edu/app/sakai-test/staging/config/..
- bash_profile
- sakai.properties
- start.sh
- stop.sh
- tomcatclean.sh
- sakai.properties
- local.properties
- build.properties
- keystore NOTE: We use this for testing only
- /afs/.ucdavis.edu/app/sakai-test/staging/src/..
- sakai-core-2-1-x-prod-005 NOTE: This changes
Directory setup on each node
- /ucd/opt/sakai
- build.properties NOTE: In case we need to build the source
- /ucd/opt/sakai/bin
- start.sh
- stop.sh
- tomcatclean.sh
- /ucd/opt/sakai/sakai-home
- sakai.properties
- local.properties
- /ucd/opt/sakai/tomcat-node
- Ready to run tomcat instance
- /ucd/opt/sakai/etc NOTE: We use this for testing only
- keystore
Detailed file descriptions and content
- bash_profile
PATH=/ucd/opt/java/bin:/ucd/opt/maven/bin:$PATH MAVEN_HOME=/ucd/opt/maven CATALINA_HOME=/ucd/opt/sakai/tomcat-node JAVA_HOME=/ucd/opt/java JAVA_OPTS=" -d64 -Xmx6144m -Xms6144m -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSParallelRemarkEnabled -XX:+UseAdaptiveSizePolicy -XX:NewSize=512m -XX:MaxPermSize=200m -XX:PermSize=64m -XX:MaxTenuringThreshold=3 -XX:CMSInitiatingOccupancyFraction=75 -XX:MinHeapFreeRatio=18 -Dsakai.home=/ucd/opt/sakai/sakai-home/" export PATH MAVEN_HOME CATALINA_HOME JAVA_HOME JAVA_OPTS
- start.sh
#!/bin/sh JAVA_HOME=/ucd/opt/java5 CATALINA_HOME=/ucd/opt/sakai/tomcat-node export JAVA_HOME CATALINA_HOME $CATALINA_HOME/bin/startup.sh
- stop.sh
#!/bin/sh JAVA_HOME=/ucd/opt/java5 CATALINA_HOME=/ucd/opt/sakai/tomcat-node export JAVA_HOME CATALINA_HOME $CATALINA_HOME/bin/shutdown.sh
- local.properties NOTE: The serverId field is different for each node
# Local server name serverId=littlejohn
FAQ
- Q: How do I know which node I am connected to?
- A: Look at the bottom of the page, where you will see a filed called Server
- e.g. Server littlejohn