Changes between Version 76 and Version 77 of ESGFNodeInstallation


Ignore:
Timestamp:
Nov 19, 2013 7:36:26 PM (8 years ago)
Author:
carlos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ESGFNodeInstallation

    v76 v77  
    620620}}}
    621621
    622 
    623 First, obtain a digital certificate from an ESGF trusted !MyProxy server, and rename it to whatever path you have defined in esg.ini.
    624 
    625 [[NoteBox(warn, Remember\, you have to log in a Federation to do it.)]]
    626 
    627 {{{
    628 #!sh
    629 $ /usr/local/globus/bin/myproxy-logon -s vesgint-idx.ipsl.jussieu.fr -l blancojc -o ~/.globus/certificate-file
    630 }}}
    631 
    632 
    633 
    634 Finally, run the commands below to parse the cordex project on the local Data Node, ingest it in the local Postgres database, and send it for harvesting to the configured Index Node.
    635 {{{
    636 #!sh
    637 $ cd /usr/local/uvcdat/1.4.0/bin
    638 $ ./esgscan_directory -i /esg/config/esgcet/esg.ini --project cordex -o ~/cordex.txt /datasets/CORDEX/output/EUR-22
    639 $ ./esgpublish -i /esg/config/esgcet/esg.ini --project cordex --map ~/cordex.txt --service fileservice
     622In order to check that the datasets were entered correctly into the database, list the datasets for cordex project:
     623
     624{{{
     625#!sh
    640626$ ./esglist_datasets -i /esg/config/esgcet/esg.ini cordex
    641627+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
     
    664650+------------------------------------------------------------------------------------------------------------------------------------------------
    665651
     652}}}
     653
     654
     655First, obtain a digital certificate from an ESGF trusted !MyProxy server, and rename it to whatever path you have defined in esg.ini.
     656
     657[[NoteBox(warn, Remember\, you have to log in a Federation to do it.)]]
     658
     659{{{
     660#!sh
     661$ /usr/local/globus/bin/myproxy-logon -s vesgint-idx.ipsl.jussieu.fr -l blancojc -o ~/.globus/certificate-file
     662}}}
     663
     664
     665
     666Finally, run the commands below to parse the cordex project on the local Data Node, ingest it in the local Postgres database, and send it for harvesting to the configured Index Node.
     667{{{
     668#!sh
     669$ cd /usr/local/uvcdat/1.4.0/bin
     670$ ./esgscan_directory -i /esg/config/esgcet/esg.ini --project cordex -o ~/cordex.txt /datasets/CORDEX/output/EUR-22
     671$ ./esgpublish -i /esg/config/esgcet/esg.ini --project cordex --map ~/cordex.txt --service fileservice
     672
    666673$ ./esgpublish -i /esg/config/esgcet/esg.ini --project cordex --map ~/cordex.txt --noscan --publish --thredds --service fileservice
    667674}}}