Changes between Initial Version and Version 1 of Software/MSI/ConfigurationTriton


Ignore:
Timestamp:
14/10/09 14:41:37 (12 years ago)
Author:
sdonegan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Software/MSI/ConfigurationTriton

    v1 v1  
     1= Triton Configuration = 
     2 
     3This 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. 
     4 
     5 
     6== Deployment Grid == 
     7 
     8Please fill in your relevant areas as your services are deployed. 
     9 
     10|| '''Developer''' || '''Service''' || '''Deployment status''' || '''Documentation''' || '''Version''' || '''Notes''' || 
     11|| Steve D || NDG Redirection Service || n/a || n/a || n/a || n/a || 
     12|| Steve D || Discovery Postgres Database || installed 13/10/09 || n/a || n/a || Clone of Neptune (AJH) || 
     13|| Steve D || Discovery Service ingestion stack || n/a || n/a || n/a || n/a || 
     14|| Steve D || Discovery Service OAI info editor || n/a || n/a || n/a || n/a || 
     15|| Steve D || Discovery Service API || n/a || n/a || n/a || n/a || 
     16|| Steve D || Discovery Service front end (milk stack) || n/a || n/a || n/a || n/a || 
     17|| Steve D || Discovery service logging framework || n/a || n/a || n/a || n/a || 
     18|| Steve D || Discovery Service usage stats API || n/a || n/a || n/a || n/a || 
     19|| * || * || * || * || * || * ||  
     20|| Phil K || Security stuff ||  ||  ||  ||  ||  
     21|| * || * || * || * || * || * ||  
     22|| Dom L || COWS stuff ||  ||  ||  ||  || 
     23|| * || * || * || * || * || * ||  
     24|| Stephen P || COWS stuff ||  ||  ||  ||  || 
     25 
     26 
     27 
     28 
     29== Python Configuration == 
     30System 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`. 
     31 
     32Application 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 [wiki:Software/MSI/ConfigurationNeptune/ApacheConfiguration Apache Configuration].  `zc.buildout` enables overriding control over package versions to define a package and version combination to make a stable deployment.  `zc.buildout` [http://pypi.python.org/pypi/collective.recipe.modwsgi collective.recipe.modwsgi] enables integration with `mod_wsgi`.  `zc.buildout` is currently the preferred means of configuration (17/06/2009). 
     33