Version 4 (modified by sdonegan, 12 years ago) (diff)


Triton Configuration

This page is to describe the configuration of Triton - the machine for deployment of NDG3 services in an operational environment. Triton will replace proglue for ndg "production" services.

The basics : ( ports 80 and 443 have been enabled for the site firewall. Port 5432 (postgres) enabled for internal machines

Deployment Grid

Please fill in your relevant areas as your services are deployed.

Developer Service Deployment status Documentation Version Notes Tested?
Steve D NDG Redirection Service Installed 18/11/09 n/a n/a Installed /usr/local/ndg-redirect Awaiting proper configuration n/a
Steve D Discovery Postgres Database installed 13/10/09 n/a n/a Clone of Neptune (AJH) n/a
Steve D Discovery Service ingestion stack Installed 18/11/09 n/a n/a Installed /usr/local/ndg-discovery-ingest (needs to be connected to triton cronjob) standard ingest NO/ ceda feed YES
Steve D Discovery Service OAI info editor Installed 18/11/09 n/a n/a Installed /usr/local/ndg-oai-info-editor - awaiting configuration and update of Security certs etc n/a
Steve D Discovery Service API Installed 11/11/09 n/a n/a Runs in axis war file - compile locally and load to axis using ant buildfile n/a
Steve D Discovery Service front end (milk stack) Installed 17/11/09 n/a n/a Installed and operational in new triton buildout environment ( - connects to Triton API (works). Needs properly configuring -i.e. get view working n/a
Steve D Discovery service logging framework n/a n/a n/a n/a n/a
Steve D Discovery Service usage stats API n/a n/a n/a n/a n/a
Steve D DLESE OAI Harvester Installed 18/11/09:DEPLOYED n/a n/a Installed as WAR file in tomcat - same usernames etc as Neptune. Loaded all Provider info n/a
Steve D CEDA ATOM Discovery XML pipeline Installed 18/11/09 n/a n/a Installed in /home/badc/buildouts/atomFeedDocumentIngester - not strictly MSi service but running on Triton! Awiating connection to cron wrapper scripts n/a
* * * * * * *
Phil K Security stuff
* * * * * * *
Dom L COWS stuff
* * * * * * *
Stephen P COWS stuff

Python Configuration

System default is Python 2.5 in /usr/bin. Under SuSE, the site package location is customised to /usr/local/lib64/python2.5/site-packages with /usr/lib64/python2.5/distutils/distutils.cfg.

Application packages will be installed separately to avoid version conflicts and maintenance problems with a single package area. virtualenv or zc.buildout could achieve this. virtualenv is easy to set-up with mod_wsgi - see Apache Configuration. zc.buildout enables overriding control over package versions to define a package and version combination to make a stable deployment. zc.buildout  collective.recipe.modwsgi enables integration with mod_wsgi. zc.buildout is currently the preferred means of configuration (17/06/2009).