Changes between Version 3 and Version 4 of installation_QCG_BES_AR
- Timestamp:
- 05/16/11 12:33:57 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
installation_QCG_BES_AR
v3 v4 1 [[PageOutline]] 2 1 3 = Introduction = 2 4 The SMOA Computing (the successor of the OpenDSP project) is an open source service acting as a computing provider exposing on demand access to computing resources and jobs over the HPC Basic Profile compliant Web Services interface. In addition the SMOA Computing offers remote interface for Advance Reservations management. … … 32 34 * Instead of ARES library a Python module (installed by default with SMOA Computing) is used. Thus to make Advance Reservation capabilities accessible via SMOA Computing you will need Python interpreter (version 2.4 at least) together with the python library for XML processing (''lxml'' or ''elementtree''). 33 35 34 if Torque with Maui scheduler:36 If Torque with Maui scheduler: 35 37 * DRMAA library can be obtained from the [http://sourceforge.net/projects/pbspro-drmaa/ PBS DRMAA sourceforge project]. After installation, as described in the library README file, you need either to: 36 38 * configure Torque to keep information about completed jobs (e.g.: by setting: qmgr -c 'set server keep_completed = 60'). … … 66 68 }}} 67 69 68 '''Note ":''' You may need to pass some additional options to `./configure` script, if some of the dependencies are installed in non-standard locations (type `./configure --help` for more info)70 '''Note:''' You may need to pass some additional options to `./configure` script, if some of the dependencies are installed in non-standard locations (type `./configure --help` for more info) 69 71 70 72 == SMOA Computing service == … … 83 85 }}} 84 86 85 86 =Configuration= 87 Before you start create a new system user (e.g. <code>smoa_comp</code>) that will be used by the service (and only the SMOA Computing service) to run in unprivileged mode: 88 # useradd -d /opt/QCG/smoa/var/log/smoa-comp/ -M smoa_comp 87 = Configuration = 88 Before you start create a new system user (e.g. `smoa_comp`) that will be used by the service (and only the SMOA Computing service) to run in unprivileged mode: 89 90 {{{ 91 #!div style="font-size: 90%" 92 {{{#!sh 93 # useradd -d /opt/QCG/smoa/var/log/smoa-comp/ -M smoa_comp 94 }}} 95 }}} 89 96 90 97 == Database setup == 91 You need to create a database for SMOA Computing and appropriate tables using the provided <tt>smoa-comp-psql.sql</tt> script. It can be found in <tt>PREFIX/share/smoa-comp/db/</tt>. Currently only PostgreSQL is supported. 92 93 * Create new database user (e.g. smoa_comp) authenticated via password (you will later provide this password in the SMOA Computing configuration file). This user must be allowed to create new databases. 98 You need to create a database for SMOA Computing and appropriate tables using the provided `smoa-comp-psql.sql` script. It can be found in `PREFIX/share/smoa-comp/db/`. Currently only PostgreSQL is supported. 99 100 * Create new database user (e.g. `smoa_comp`) authenticated via password (you will later provide this password in the SMOA Computing configuration file). This user must be allowed to create new databases. 101 {{{ 102 #!div style="font-size: 90%" 103 {{{#!sh 94 104 # su - postgres 95 105 $ createuser -P smoa_comp 96 106 $ exit 97 98 * Create new database (e.g. smoa_comp) owned by the smoa_comp user: 107 }}} 108 }}} 109 110 * Create new database (e.g. `smoa_comp`) owned by the `smoa_comp` user: 111 {{{ 112 #!div style="font-size: 90%" 113 {{{#!sh 99 114 # su - smoa_comp 100 115 $ createdb -U smoa_comp smoa_comp 101 116 $ exit 102 103 104 * Depending on the local PostgreSQL configuration you may need to edit the <code>pg_hba.conf</code> file (''host based authentication'' configuration file) and add the following lines as the two top rules: 117 }}} 118 }}} 119 120 * Depending on the local PostgreSQL configuration you may need to edit the `pg_hba.conf` file (''host based authentication'' configuration file) and add the following lines as the two top rules: 121 {{{ 122 #!div style="font-size: 90%" 123 {{{#!default 105 124 local smoa_comp smoa_comp md5 106 125 host smoa_comp smoa_comp 127.0.0.1/32 md5 107 : in order to enable password authentication for the user <code>smoa_comp</code> 108 109 {{Note|}} You must reload the PostgreSQL server in order to make the changes visible e.g: 110 126 }}} 127 }}} 128 in order to enable password authentication for the user `smoa_comp`. 129 130 '''Note:''' You must reload the PostgreSQL server in order to make the changes visible e.g: 131 132 {{{ 133 #!div style="font-size: 90%" 134 {{{#!sh 111 135 # /etc/init.d/postgresql reload 112 113 * Create database schema using provided script (<code>smoa-comp-psql.sq</code>) : 114 136 }}} 137 }}} 138 139 * Create database schema using provided script (1smoa-comp-psql.sql`) : 140 141 {{{ 142 #!div style="font-size: 90%" 143 {{{#!default 115 144 $ psql -f /opt/QCG/smoa/share/smoa-comp/db/smoa-comp-psql.sql -U smoa_comp 116 145 psql:/opt/QCG/smoa/share/smoa-comp/db/smoa-comp-psql.sql:3: ERROR: table "states" does not exist … … 149 178 CREATE TABLE 150 179 CREATE INDEX 180 }}} 181 }}} 151 182 152 183 * You need to create ODBC Data Source Name. You can do this by editing system-wide, i.e. /etc/odbc.ini, configuration file and adding new section. In this example we assume that the DSN (Database Source Name) will be smoa_comp, real database name is also smoa_comp and appropriate drivers for PostgreSQL database (i.e. the <code>libodbcpsql.so</code> and <code>libodbcpsqlS.so</code> files) are located in /usr/local/lib:
