Versions Compared

Key

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

...

Web ServerIISTomcatMigration StatusComments
glast-ground.slac.stanford.eduglast-win01,glast-win02multipleMigrated (11/16/2015) 
web08.slac.stanford.eduweb08   
aida.freehep.orgweb08scalnx-v03  
aidatld.freehep.orgweb08scalnx-v03 Up
exo-data.slac.stanford.eduweb08exolnx-v01  
forum.freehep.orgweb08N/A fudform application Page is up, but forum may be down, returns a blank page (was fhforum.slac.stanford.edu)
heprep.freehep.orgweb08scalnx-v03 Up
jas.freehep.orgweb08scalnx-v03  
java.freehep.orgweb08scalnx-v03  

lcsim.org, www.lcsim.org

lcsim.freehep.org

web08scalnx-v03 lcsim.freehep.org exists as a host name, but the application appears to actually be www.lcsim.org
lelaps.freehep.orgweb08scalnx-v03 Up
lp99.freehep.orgweb08  Down, no DNS record- but IIS is still aware of the Application (checked via telnet web08 80: GET / HTTP/1.1\nHost: lp99.freehep.org\n\n)
lsst-camera.slac.stanford.eduweb08

lsstlnx-v01

 Up
pingerlod.slac.stanford.eduweb08

scalnx-v06

 Up

portal.lsst-desc.org

portal.lsstdesc.org

web08  Up
sid.slac.stanford.eduweb08  Points to exo portal?
srs.slac.stanford.eduweb08  Up
wired1.freehep.orgweb08N/A (on web08) Up
www.freehep.orgweb08N/A (on web08) Up

www-sld.slac.stanford.edu

www-bes.slac.stanford.edu

www-midas.slac.stanford.edu

web08N/A (on web08) Up. Also has www-bes and www-midas, but they all serve the same page.
www-sldnt.slac.stanford.eduweb08scalnx-v03/Also on web08? scalnx-v03, just a blank page
xrdmon.slac.stanford.eduweb08  Worker defined to be xrootd-mon, Not sure if this is on web08 or some other server?

wired4.freehep.org

wired.freehep.org

web08scalnx-v03  
wired2.freehep.orgweb08  Points to web08. No record in IIS. Not sure how this one works? There is a directory on scalnx-v03
forum.linearcollider.orgweb08N/A (web08  

 

nginx configuration workbook

Note: See SCA NGINX Configuration for information on actual configuration.

SSL Configuration

http://nginx.com/resources/admin-guide/nginx-ssl-termination/

...

http://fudforum.org/doc/d/manual.html#admin.dump

Keepalived

keepalived is to be configured on both machines.

keepalived seems to support HTTP status checks.

The following is roughly the configuration for sca-nginx01. The configuration for sca-nginx02, which will be the failover machine, will be nearly identical, but the priority on the vrrp_instance MUST BE LOWER than the priority on the master. The password will be different.

The configuration is located in /etc/keepalived/keepalived.conf

Code Block
global_defs {
   notification_email {
     bvan@slac.stanford.edu
   }
   notification_email_from bvan@slac.stanford.edu
   smtp_server smtp.slac.stanford.edu  # Not sure if this works
   smtp_connect_timeout 30
   router_id SCA_WWW  # Not sure if this is used
}
 
# This is a health check script. Right now it just checks to see
# if nginx is up.
#
# Note on the weight: If the weight isn't enough to break a tie between
# the priority difference between sca-nginx01 and sca-nginx02, and
# nginx is down but sca-nginx01 is up, then requests
# may still go to sca-nginx01.
vrrp_script chk_nginx {
      script "killall -0 nginx"
      interval 2 # seconds
      weight 2 # points
}
vrrp_instance VI_1 {
    state MASTER
    interface eth0
    virtual_router_id 85 # Random ID. We shouldn't have the same router id on the same subnet
    priority 100  # See note on weight above
    advert_int 1 # Advertisement interval (i.e. heartbeat seconds)
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        134.79.129.86
    }
    track_script {
         chk_nginx
    }
   unicast_src_ip 134.79.129.92   # Unicast specific option, this is the IP of the interface keepalived listens on
   unicast_peer {                 # Unicast specific option, this is the IP of the peer instance 
     134.79.129.91
   }
}