Changeset d720895 in flex_extract.git for Documentation/html/_sources/Installation/remote.rst.txt
- Timestamp:
- Dec 19, 2019, 8:12:11 PM (4 years ago)
- Branches:
- master, ctbto, dev
- Children:
- e70c85f
- Parents:
- 76c37a9
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
Documentation/html/_sources/Installation/remote.rst.txt
r30f7911 rd720895 42 42 .. _ref-req-remote: 43 43 44 Remote environment requirements45 ========================== =====44 Remote mode - dependencies 45 ========================== 46 46 47 The environment for ``flex_extract`` on ECMWF servers has to provide these 48 software packages and libraries: 47 The following software is required, and already available at the ECMWF servers: 49 48 50 49 +---------------------------+-----------------+ … … 63 62 ========================== 64 63 65 The environment on the ECMWF server (such as *ecgate* or *cca*) is already 66 prepared. ECMWF server provide all libraries via a module system which is 67 going to be selected by ``flex_extract`` automatically. 64 ECMWF servers provide all libraries via a module system. Loading the required modules is already built into ``flex_extract`` and no user action is needed. 68 65 69 66 … … 73 70 =================== 74 71 75 First, log in on one of the ECMWF Linux server, such as *ecgate* or *cca/ccb*.72 First, log in on one of the ECMWF servers, such as *ecgate* or *cca/ccb*. 76 73 Substitute *<ecuid>* with your ECMWF user name: 77 74 … … 101 98 *************************************************************** 102 99 103 <ecuid>@ 131.130.157.5's password: ***100 <ecuid>@<ipname/address>'s password: *** 104 101 Select hostname (ecgate, cca, ccb) [ecgate]: ecgate 105 102 106 103 [<ecuid>@ecgb11 ~]$ 107 104 105 Substitute the *<localuser>* and *<localmachine.tld>* placeholders with your local user name and the IP name or address of your local machine. 106 Untar the file and change into the ``flex_extract`` root directory. 108 107 109 Then, copy the ``flex_extract`` tar ball (from section :ref:`ref-download`)110 to the ``$HOME`` directory of the ECMWF Linux server via ``scp``.111 Substitute the *<localuser>* and *<server.edu>* placeholders with your credentials.112 Untar the file and change into the ``flex_extract`` root directory.113 114 108 .. code-block:: bash 115 109 116 scp <localuser>@< server.edu>:/path/to/tarfile/flex_extract_vX.X.tar.gz $HOME/110 scp <localuser>@<localmachine.tld>:</path/to/tarfile/>flex_extract_vX.X.tar.gz $HOME/ 117 111 cd $HOME 118 112 tar xvf flex_extract_vX.X.tar.gz … … 120 114 121 115 122 On these ECMWF servers, it is not necessary to prepare the environment or the 123 ``Makefile`` for the Fortran program (``CONVERT2``) as described above. 124 All third party libraries are available from a module system. The ``Makefile`` 125 is optimized for ECMWF servers and the compilation 126 script ``compilejob.ksh``, which will be submitted by ``flex_extract`` to the 127 batch job queue at ECMWF, does load all relevant modules from the ECMWF's module system. 128 129 So there is just the need to execute the ``setup.sh`` script from the 130 ``flex_extract`` root directory for installation. 116 117 Execute the ``setup.sh`` script from the ``flex_extract``'s root directory. 131 118 Before executing it, it is necessary to adapt some parameters from ``setup.sh`` 132 119 described in :doc:`Documentation/Input/setup`. 133 120 134 Open ``setup.sh`` with your editorand adapt the values:135 121 Open ``setup.sh`` with your preferred editor (e.g., ``nano'') and adapt the values: 122 136 123 +----------------------------------------------+----------------------------------------------+ 137 | Take this for target = **ectrans** | Take this for target = **cca** |124 | Use this for target = **ectrans** | Use this for target = **cca** | 138 125 +----------------------------------------------+----------------------------------------------+ 139 126 | .. code-block:: bash | .. code-block:: bash | … … 158 145 159 146 :underline:`Please substitute the values of ECUID and ECGID 160 with your own credentials and settings.`147 with your own ones (look at any of your files with ``ls -l'' to see uid and gid).` 161 148 162 149 .. note:: 163 150 164 If a local gateway server is available the transfer of files could be done 165 via the ``ECaccess`` commands. Therefore a valid *GATEWAY* and *DESTINATION* 166 have to be present and should be set in the ``setup.sh`` file. 167 151 If a local gateway server is available, files can be transferred with ``ECaccess`` commands. In that case, a valid *GATEWAY* and *DESTINATION* have to be present in the ``setup.sh`` file (even if not used, the lines must not be deleted). 168 152 169 153 Afterwards, type: … … 174 158 ./setup.sh 175 159 176 to start the installation. You should see the following o utput at the command line.160 to start the installation. You should see the following on standard output. 177 161 178 162 … … 185 169 186 170 187 The email content should look like this with a "SUCCESS" statement in the last line:171 ``Flex_extract`` uses the email address connectd to the user account on ECMWF servers. The email content should look like this with a "SUCCESS" statement in the last line: 188 172 189 173 .. code-block:: bash
Note: See TracChangeset
for help on using the changeset viewer.