Admin Portal Maintenance

From UGP-Wiki

Jump to: navigation, search

Contents

[edit] I. Portal Maintenance

[edit] A. General Maintenance

[edit] Backup

We highly recommend that you perform incremental backup every night on your Grid Portal and MyProxy Server machines. On the MyProxy Server, the user's proxy certificates are stored in the directory: 

   GT4/var/myproxy

At the minimum, you should backup that directory every night.

[edit] Monitoring

At UCLA we run periodic cron jobs to monitor the state of the system. These cron jobs send email messages to appropriate administrators if they determine that something is amiss.

Scripts used to monitor the state of the Grid Portal can be found in the Scripts subdirectory. They are organized in 6 subdirectories for the machine on which they may be installed: 


   forClusterAppliance/
   forClusterHeadnode/
   forGridPortal/
   forGridPortalAux/
   forMyproxy/
   forStorage/

The README file in the Scripts directory gives an overview of the purpose of each machine's scripts, and provides an index to all the scripts.

[edit] B. MySQL

[edit] How to Change the SQL you are using with UGP

UGP uses Hibernate as its interface to its databases. Hibernate is a portable SQL extension for Java that talks to a number of SQL databases. While we have used UGP only with MySQL at UCLA, it should work with any other database that Hibernate works with.

Follow these instructions if you download a new release of MySQL or if you want to change databases. 


1. Login to the Grid Portal machine as globus.

2. Edit the following properties files for your new SQL Database:

       INSTALL/gridsphere/webapps/gridsphere/WEB-INF/CustomPortal/database/
       hibern
       UCLAGridPortal/Portal/webapp/WEB-INF/persistence/
       hibernate.properties.template

   Where INSTALL is the directory in which you have installed UGP, including
   tomcat, GridSphere, UGP, etc.

3. Reinstall GridSphere and UGP:

       cd INSTALL/gridsphere; ant install
       cd UCLAGridPortal/Portal; ant install

[edit] How to Backup and Restore MySQL Data

We highly recommend that you backup your MySQL database every night. The script that we use to accomplish this at UCLA is included in the Scripts subdirectory. Alternatively, you can login to your Grid Portal machine as user globus and use the following command to dump the MySQL database to a file: 

   mysqldump -a gridsphere -u dbadmin -p -r ugp.file

Replace ugp.file with the file name of the file into which the database will be dumped.

To restore the MySQL data: 

   mysql gridsphere -u dbadmin -p
   When prompted, enter the MySQL password for dbadmin.
   mysql>\. ugp.file

Replace ugp.file with the name of the file into which you dumped the MySQL database. You must either be in the same directory as the file or code the complete path. For more information about the MySQL user dbadmin, see the section titled Prerequisites in the UGP Installation Guide (UGP_INSTALL).

[edit] C. MyProxy Server

[edit] How to add a MyProxy Server to a Grid Portal that is Currently not using one

Currently UGP can only work with a single MyProxy Server. If you have no MyProxy Server now, you can add one. If you are currently using a MyProxy Server you can switch to another one, but you will have to migrate all the user proxy certificates.

Follow the instructions given in UGP_INSTALL to install MyProxy on a separate MyProxy Server machine and install a signed host certificate there. Then edit the portal.properties file and fill in the information about your new MyProxy Server by completing the myProxyHost, myProxyPort, etc. tags. Then redeploy UGP by entering: 

   cd UCLAGridPortal/Portal
   ant deploy

[edit] D. Adding a Cluster to the Grid

To add a cluster to the Grid: 

1. Prepare a Grid Appliance machine. Install Linux Fedora Core on it.

2. Follow the instructions in UGP_INSTALL to make the Appliance work with the
   scheduler the cluster is using, cross-mount user home directories, set up
   the firewall, install UGP, and install a signed (trusted) host certificate.

3. Open a web browser and go to the Grid Portal's URL. Login with the Grid
   Admin Username and Password.

4. Select TrustedClusterList under the Grid Admin tab. The TrustedClusterList
   includes every cluster that is connected to the Grid Portal. Click on Add.
   You will be presented with a table. Fill in the information about the
   cluster that will be connected to the Grid Portal via this Grid Appliance.
   In the table, fill in the email address of the Cluster Admin for that
   cluster under the heading SupportEmail. Cluster Name is the name (alpha
   address) of the Grid Appliance. True Name is the plain English name of the
   cluster. This name will appear in the Grid Portal as the name of the
   cluster so it should be the name users know it by. Examples at UCLA are:
   Hoffman cluster, hydro cluster, CNSI cluster, etc. Cluster Head Node is the
   name (alpha address) the Cluster head node.

5. To populate the Grid Appliance with users from the Cluster head node, see
   Scripts/forClusterApplicance/rootbin/gridusers.pl and gridusers.README

[edit] E. Adding a Grid Admin

Each Grid Portal can have one or more Grid Admin. Only the GridSphere Super User can designate a Grid Admin. To designate someone who is already a user of the Grid Portal as a Grid Admin, login to the Grid Portal as the GridSphere Super User and: 


1. Under the Administration tab click on Users. Each user in the user list
   will either have User or Admin to the right of his/her name. The proposed
   Grid Admin should have User next to his/her name. Clicking on User will
   cause another page to appear. On that page, under uclagridportal change
   User to Admin and click on Save.

2. Under the Administration tab click on Groups. Then click on Edit Users to
   the right of uclagridportal. On the next page add the proposed Grid Admin
   to Admin.
Retrieved from "http://www.ucgrid.org/wiki/index.php/Admin_Portal_Maintenance"
Personal tools