| Home | About | Software | Documentation | Support | Outreach | Ecosystem | Blog | Dev | Awards | Team & Sponsors |
This shows you the differences between two versions of the page.
|
documentation:release_5.6:ig [ - 2010/01/21, 13:00 - ] Alejandro Lorca |
documentation:release_5.6:ig [ - 2010/01/21, 19:00 - ] (current) Alejandro Lorca |
||
|---|---|---|---|
| Line 83: | Line 83: | ||
| Login as your user account and follow these steps: | Login as your user account and follow these steps: | ||
| * 1. Download the distribution file to the installation directory, for example your ''$HOME'' directory | * 1. Download the distribution file to the installation directory, for example your ''$HOME'' directory | ||
| - | * 2. Unpack the distribution file and change to the ''gridway_5.6.0'' directory:<xterm>$ tar xzf gridway_5.6.0.tgz | + | * 2. Unpack the distribution file and change to the ''gridway_5.6.1'' directory:<xterm>$ tar xzf gridway_5.6.1.tgz |
| - | $ cd gridway_5.6.0</xterm> | + | $ cd gridway_5.6.1</xterm> |
| * 3. Set up Globus development environment:<xterm>$ source $GLOBUS_LOCATION/etc/globus-devel-env.sh</xterm>or<xterm>$ . $GLOBUS_LOCATION/etc/globus-devel-env.csh</xterm>depending on the shell you are using. | * 3. Set up Globus development environment:<xterm>$ source $GLOBUS_LOCATION/etc/globus-devel-env.sh</xterm>or<xterm>$ . $GLOBUS_LOCATION/etc/globus-devel-env.csh</xterm>depending on the shell you are using. | ||
| * 4. Run configure to set up GridWay installation.<xterm>./configure OPTIONS</xterm> Possible options for configure are: | * 4. Run configure to set up GridWay installation.<xterm>./configure OPTIONS</xterm> Possible options for configure are: | ||
| Line 134: | Line 134: | ||
| ^ Important ^ | ^ Important ^ | ||
| - | | The instructions here described assumes that you are going to install GridWay in its own directory (''$GW_LOCATION'', e.g. ''/opt/gridway/5.6.0''). Also it is assumed that the installation, configuration and service execution will be performed by an special account (''gwadmin'').GridWay can be also installed within the Globus Toolkit tree. To do this you have to use the flag ''<nowiki>--enable-globus-scheme<nowiki>'' when calling configure script and set the prefix to ''$GLOBUS_LOCATION''. In this case, the ''gwadmin'' user will be the user account that performed the Globus Toolkit installation. When you install it this way you also have to note that ''$GW_LOCATION/var'' and ''$GW_LOCATION/etc'' directories will be ''$GLOBUS_LOCATION/var/gridway'' and ''$GLOBUS_LOCATION/etc/gridway''. | | + | | The instructions here described assumes that you are going to install GridWay in its own directory (''$GW_LOCATION'', e.g. ''/opt/gridway/5.6.1''). Also it is assumed that the installation, configuration and service execution will be performed by an special account (''gwadmin'').GridWay can be also installed within the Globus Toolkit tree. To do this you have to use the flag ''<nowiki>--enable-globus-scheme<nowiki>'' when calling configure script and set the prefix to ''$GLOBUS_LOCATION''. In this case, the ''gwadmin'' user will be the user account that performed the Globus Toolkit installation. When you install it this way you also have to note that ''$GW_LOCATION/var'' and ''$GW_LOCATION/etc'' directories will be ''$GLOBUS_LOCATION/var/gridway'' and ''$GLOBUS_LOCATION/etc/gridway''. | |
| | Note that GridWay daemon **SHOULD NOT** be run as root. Only part of the installation will require privileged access. | | | Note that GridWay daemon **SHOULD NOT** be run as root. Only part of the installation will require privileged access. | | ||
| Line 142: | Line 142: | ||
| - The GridWay administrator account, ''<adminuser>'', can be an existing administrative login or a new login. We recommend creating a new account for the GridWay administration user (call ''gwadmin'', for example). This account will own all of the files in the GridWay installation, all of the daemons in the GridWay execution and it can be used to configure GridWay once it is installed. Primary group of ''<adminuser>'' should be ''<gwgroup>''.\\ DO NOT use root account for the GridWay administrator account. | - The GridWay administrator account, ''<adminuser>'', can be an existing administrative login or a new login. We recommend creating a new account for the GridWay administration user (call ''gwadmin'', for example). This account will own all of the files in the GridWay installation, all of the daemons in the GridWay execution and it can be used to configure GridWay once it is installed. Primary group of ''<adminuser>'' should be ''<gwgroup>''.\\ DO NOT use root account for the GridWay administrator account. | ||
| - Download the distribution file to the installation directory, for example your ''/opt/gridway'' directory | - Download the distribution file to the installation directory, for example your ''/opt/gridway'' directory | ||
| - | - Unpack the distribution file and change ownership:<xterm># tar xzf gridway_5.6.0.tgz | + | - Unpack the distribution file and change ownership:<xterm># tar xzf gridway_5.6.1.tgz |
| # chown -R gwadmin:gwusers /opt/gridway | # chown -R gwadmin:gwusers /opt/gridway | ||
| - | # chmod 755 /opt/gridway</xterm>Become GridWay administrator user, and change to ''gridway_5.6.0'' directory:<xterm># su gwadmin | + | # chmod 755 /opt/gridway</xterm>Become GridWay administrator user, and change to ''gridway_5.6.1'' directory:<xterm># su gwadmin |
| - | $ cd gridway_5.6.0</xterm> | + | $ cd gridway_5.6.1</xterm> |
| - Set up Globus development environment:<xterm>$ source $GLOBUS_LOCATION/etc/globus-devel-env.sh</xterm>or<xterm>$ . $GLOBUS_LOCATION/etc/globus-devel-env.csh</xterm>depending on the shell you are using. | - Set up Globus development environment:<xterm>$ source $GLOBUS_LOCATION/etc/globus-devel-env.sh</xterm>or<xterm>$ . $GLOBUS_LOCATION/etc/globus-devel-env.csh</xterm>depending on the shell you are using. | ||
| - Run configure to set up GridWay installation. Check above for possible options or just type<xterm>./configure OPTIONS</xterm> | - Run configure to set up GridWay installation. Check above for possible options or just type<xterm>./configure OPTIONS</xterm> | ||
| Line 174: | Line 174: | ||
| Runas_Alias GWUSERS = %gwusers | Runas_Alias GWUSERS = %gwusers | ||
| # GridWay entries | # GridWay entries | ||
| - | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.0/bin/gw_em_mad_prews * | + | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.1/bin/gw_em_mad_prews * |
| - | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.0/bin/gw_em_mad_ws * | + | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.1/bin/gw_em_mad_ws * |
| - | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.0/bin/gw_em_mad_ssh * | + | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.1/bin/gw_em_mad_ssh * |
| - | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.0/bin/gw_tm_mad_ftp * | + | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.1/bin/gw_tm_mad_ftp * |
| - | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.0/bin/gw_tm_mad_dummy * | + | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.1/bin/gw_tm_mad_dummy * |
| - | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.0/bin/gw_tm_mad_ssh * | + | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/gridway/5.6.1/bin/gw_tm_mad_ssh * |
| gwadmin ALL=(GWUSERS) NOPASSWD: /opt/globus/4.2.1/bin/grid-proxy-info *</file> | gwadmin ALL=(GWUSERS) NOPASSWD: /opt/globus/4.2.1/bin/grid-proxy-info *</file> | ||
| Usually **sudo** clears all environment variables for security reasons. However MADs need the **GW_LOCATION** and **GLOBUS_LOCATION** (and **GLOBUS_TCP_PORT_RANGE** if existing) variables to be set. To preserve those variables in the MAD environment, add the following line to your "sudoers" file:<file>Defaults>GW_USERS env_keep="GW_LOCATION GLOBUS_LOCATION GLOBUS_TCP_PORT_RANGE"</file>The following line //shouldn't// be in the sudoers file, otherwise gridway could not use sudo as it will ask for a tty:\\ | Usually **sudo** clears all environment variables for security reasons. However MADs need the **GW_LOCATION** and **GLOBUS_LOCATION** (and **GLOBUS_TCP_PORT_RANGE** if existing) variables to be set. To preserve those variables in the MAD environment, add the following line to your "sudoers" file:<file>Defaults>GW_USERS env_keep="GW_LOCATION GLOBUS_LOCATION GLOBUS_TCP_PORT_RANGE"</file>The following line //shouldn't// be in the sudoers file, otherwise gridway could not use sudo as it will ask for a tty:\\ | ||
| <del>Defaults requiretty</del> | <del>Defaults requiretty</del> | ||
| - | Please refer to the **sudo** manual page for more information. Additionally you can configure your drivers environment by using the ''gwrc'' interface (see Section “MAD Environment Configuration”). To test the **sudo** command configuration try to execute a MAD as a user in the ''gwusers'' group, for example:<xterm>$ sudo -u gwuser /opt/gridway/5.6.0/bin/gw_em_mad_prews</xterm>Following previous steps, the end-users must login to the GridWay server host to be able to execute GridWay commands and use the DRMAA libraries. | + | Please refer to the **sudo** manual page for more information. Additionally you can configure your drivers environment by using the ''gwrc'' interface (see Section “MAD Environment Configuration”). To test the **sudo** command configuration try to execute a MAD as a user in the ''gwusers'' group, for example:<xterm>$ sudo -u gwuser /opt/gridway/5.6.1/bin/gw_em_mad_prews</xterm>Following previous steps, the end-users must login to the GridWay server host to be able to execute GridWay commands and use the DRMAA libraries. |
| Additionally, client hosts, that are not required to have GridWay/Globus installed, could be deployed to remotely interface to the GridWay server host. In such a case, user accounts and home directories must be shared between the GridWay server and the client hosts, via for example NIS and NFS; and ''$GW_LOCATION'' directory should be readable on all client hosts. The ''$GW_LOCATION'' directory may be available via for example NFS by exporting ''$GW_LOCATION'' from GridWay server, creating the directory in the client hosts, changing its ownership to ''gwadmin:gwusers'' and mounting the ''$GW_LOCATION'' directory exported by the GridWay server on the ''$GW_LOCATION'' of the client hosts. | Additionally, client hosts, that are not required to have GridWay/Globus installed, could be deployed to remotely interface to the GridWay server host. In such a case, user accounts and home directories must be shared between the GridWay server and the client hosts, via for example NIS and NFS; and ''$GW_LOCATION'' directory should be readable on all client hosts. The ''$GW_LOCATION'' directory may be available via for example NFS by exporting ''$GW_LOCATION'' from GridWay server, creating the directory in the client hosts, changing its ownership to ''gwadmin:gwusers'' and mounting the ''$GW_LOCATION'' directory exported by the GridWay server on the ''$GW_LOCATION'' of the client hosts. | ||