Changes between Version 2 and Version 3 of I2B2BackgroundInstallDetails


Ignore:
Timestamp:
11/08/10 21:37:00 (14 years ago)
Author:
Dave Morris
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • I2B2BackgroundInstallDetails

    v2 v3  
    44
    55=== The Install Artifacts ===
    6 My feeling (Jeff) is that the install packages should be in a well-known place within the available BRICCS network/resources, eg: in a repo on briccs-2. We could use wget "locally" to download known versions of software within the automated procedures. Or could we just script automated sftp's? Having known versions of software in our own location would be reassuring, quick and easy to script.
     6My feeling (Jeff) is that the [=#datarepo] install packages should be in a well-known place within the available BRICCS network/resources, eg: in a repo on briccs-2. We could use wget "locally" to download known versions of software within the automated procedures. Or could we just script automated sftp's? Having known versions of software in our own location would be reassuring, quick and easy to script.
    77
    88This may have to be a private facility to avoid licence implications, so perhaps sftp would be easier for this. Any thoughts?
     
    1111Within a Linux environment, the question of owner and group needs thinking through.
    1212
    13 I'm not in favour of running software as root. Should we have specific owners and groups (eg: catissue, jboss) or have a generic group (eg: briccs)? These could be set up during the install process if they did not already exist.
     13I'm not in favour of running software as root. Should we have [=#usergroups] specific owners and groups (eg: catissue, jboss) or have a generic group (eg: briccs)? These could be set up during the install process if they did not already exist.
    1414   
    1515NB: The Oracle-XE install creates user oracle and group dba
    1616
    1717=== Start and Restart ===
    18 * Should the database and JBoss be started at boot?     
    19 * Should they routinely be restarted each day overnight to reclaim any errant resources?
     18* [=#startonboot] Should the database and JBoss be started at boot?     
     19* [=#dailyrestart] Should they routinely be restarted each day overnight to reclaim any errant resources?
    2020
    2121=== Order of Installation ===
     
    3737* There is a degree of ambiguity when you read the docs for the Data and the PM install. Complete the Data install before going to the PM install.
    3838* The PM install is the first cell install. As such it also bundles the i2b2 common package install and the web client install.
     39
     40----
     41
     42Comments from DaveMorris
     43
     44 * +1 to the [#datarepo data repository].
     45I have already set up a location store public files, see : http://data.briccs.org.uk/
     46I have already uploaded the files needed by the CaTissue install scripts.
     47
     48The data site has a robots.txt file that prevents it from being indexed by search engines.
     49
     50If we need to we can add a protected area which is only accessible via sftp.
     51
     52 * +1 to using standard [#usergroups users and groups].
     53
     54None of our services should be run as root, or using one of our own user accounts.
     55Each service should have its own user acount and group associated with it.
     56
     57The install scripts I have in svn define separate users and groups for each of the services.
     58We may need to negotiate with RCS to reserve user identifiers for these.
     59
     60* +1 to having the services [#startonboot start automatically] when the machine is booted
     61
     62Our install scripts should add fully functional system init scripts enabling our services
     63to behave in the same way that the system services do.
     64
     65* -1 to having the service [#dailyrestart restart every day] unless it is absolutely necessary.
     66
     67This is at best a temporary fix, and just means that resource problems don't show up
     68in development and only begin to show up once the service is under heavy use.
     69
     70However, we should have test systems that are left running under stress for extended periods of time
     71and we should also have test systems that are repeatedly restarted to identify any resource problems
     72as early as possible.
     73 
     74----
     75
     76