Versions Compared

Old Version 12

changes.mady.by.user Thomas Amsler

Saved on

compared with

New Version 13

changes.mady.by.user Thomas Amsler

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

The following information describes a Sakai Clustered TEST setup. Once the test is completed, this information will be updated with PRODUCTION relevant information.

Panel
titleTasks and Issues
  • Create smartsite-test.ucdavis.edu dns entry, which points at load balancer
  • Use IP based balancing
    • Does this mean that a given client IP will always connect to the same node or is there some timeout?
      If there is a timeout, what is the TTL?
  • On a node, we need to find a common location for tomcat. Each node will retrieve a "ready to run" tomcat
    instance from AFS space and put it on local disk. Right now, tomcat is located in "/ucd/pkg/". Can we
    use that location? If not what is the location where the sakai user has "rw" access to?
  • What is the best way get a copy of the "ready to run" tomcat instance from AFS onto each node's local disk?
    • rsync, cp, ..?
  • We need to configure sakai.properties for each node. What tools do you recommend for doing this?
    • e.g. preprocessors such as M4 or some other configuration manager tool

Load Balancer

...

Load Balancer

  • IP: 169.237.104.20
  • Test Name: smartsite-test.ucdavis.edu pointing at the load balancerSetup:
  • Sticky session
    • WebDAV problem:
  • Can we also have IP based balancing?
    • Can balancer detect WebDAV requests and only forward them to Head Node?

Nodes

  • littlejohn (Head Node: For possible WebDAV workaround)
  • walton
  • braddock

System (Node) User

...