Plosone Systems

This document will describe the various topaz installations that plos runs.

journals

we'll have a separate vhost per virtual journals. substitute the following to get correct hostnames:

  • plosone
  • clinicaltrials
  • plosntds

http://<journal>-dev.plos.org

this is the dev install. it is a single box install with a webhead.

<journal>-dev lives at the PLoS office. you'll need to be on the PLoS PPTP VPN to access plosone-dev.

* <journal>-dev.plos.org 10.135.1.19

http://<journal>-stage.plos.org

<journal>-stage is a single-box stage install hosted at united layer.

some cron jobs against the production servers are run from plosone-stage.

plosone-stage is also known as plosstage01.plos.org. stage sites for most other plos web sites are hosted here as well.

all articles are ingested, QC'd and published on stage before going live.

* plosstage01.plos.org 209.237.227.199

http://<journal>-mirrorXX.plos.org

also hosted on plosstage01, <journal>-mirror01 and <journal>-mirror02 are vhosts that connects to one of the production plosone servers.

if a single stack goes down, we'll point the production web heads at the remaining good stack, and then use <journal>-mirrorXX to test the bad stack.

topaz staff can login to plosstage01 as topazdev.

http://<journal>-webXX.plos.org

the production servers hosted at united layer.

like the dev stack, most servers have private IPs. only webhead and cas servers have public ips.

  • ploskow01.localdomain 192.168.66.20 (mulgara)
  • plofed01.localdomain 192.168.66.19 (fedora)
  • plostopaz01.localdomain 192.168.66.17 (plosone) currently, all external traffic is going through web02 and topaz02
  • plostopaz02.localdomain 192.168.66.18 (plosone)
  • plosauth01.localdomain 192.168.66.12, register.plos.org 209.237.233.102 (cas)
  • plosweb01.localdomain 192.168.66.13, plosweb01.plos.org 209.237.233.100 currently, all external traffic is going through web02 and topaz02
  • plosweb02.localdomain 192.168.66.14, plosweb02.plos.org 209.237.233.101

http://www.plosone.org and http://clinicaltrials.ploshubs.org go through a load balancer.

the individual web heads have vhosts that can be used to access them:

  • http://<journal>-web01.plos.org = plosweb01
  • http://<journal>-web02.plos.org = plosweb02

you'll have to set up your hosts file to use these vhosts (you could also use a hosts file to map www.plosone.org to either webhead, or to mirror, if you like)

topaz staff can login to the production servers as topazdev.