E-grid live-CD

User Interface Configuration





After booting up the system with the eGrid live-CD you can open up a terminal, just as shown.




Use ``sudo -s`` to open a ``root shell``. In general you can use ``sudo command`` to run ``command`` as root, but some programs are not on the default ``PATH``, so this won't work.




Start the ``egrid-conf`` program.




It should come up like this.




You can configure the current machine for several different roles. In order to understand the terminology used here, refer e.g. to the LCG documentation. Familiarity with this terminology is assumed in the rest of the document.

The rest of this document deals with setting up a ``User Interface'' on the host. Select that option.




Set up the configuration parameters ...




... manually ...




This is the meat of the configutation. You need to obtain this information from whoever is managing the grid at your site. If you are that person, you should know this data. If you don't, go back to reading the LCG documentation... or use Google... or go for a coffee. If your First Impression of the situation is not as positive as you had expected, put some Second Thoughts into it. If that doesn't help, resort to Third Thoughts (or find yourself a bunch of pictsies).


Description:

CLOSE_SE: This is the closest Storage Element to this host
CATALOG_TYPE: Which type of catalog are you using? (note that this option is prefilled with text that \emph{won't work}, you have to provide a valid answer.
DEF_VO_NAME: What's your default virtual organization's name?
BDII_HN: Your BDII's hostname
BDII_PORT: The port where your BDII is listening at
MAIN_SE_FQH: The fully qualified hostname for your main storage element.
REPLICA_SERVER: Your replica server
MYPROXY_SERVER: Your MyProxy server (no, not mine, yours!)
RB_SERVER: Your resource broker








Once you are done go ``Back`` and select ``Build configuration files'' and say ``Yes``.




It might spit out one or two error messages... it's probably not the end of the world. If it says it's done, it's fine.




And exit.




Now this is important: open a new shell. Some environment variables should be set with the correct values.





The file hostcert.pem and hostkey.pem is necessary only if you want to install a Grid Element CE SE or SN, is not necessary for a User Interface.

In /etc/skel/.globus is the DEMO user's certificate. Create a directory ``.globus`` in the home directory and copy those files there. If you have a Certificate coming from a CA you instead can copy this certificate







You should be able to initialize your proxy now. The passphrase for the certificate is shown above. Verify that the proxy is working.




At this point you should be able to connect to the resource broker and BDII and extract some information from it. Make sure these services are already running before you try this!