Difference between revisions of "Administrator's Guide:Setting up a gCube infrastructure"

Revision as of 12:10, 4 December 2007

A gCube infrastructure is a set of working nodes (so-called DHNs, DILIGENT Hosting Nodes) glued by the gCube enabling services and able to host gCube services. When creating a new infrastructure, there are two kinds of configuration: secure configuration and non-secure configuration The setup of the latter is easier than the former, since the secure infrastructures require some additional steps. In order to setup a non-secure infrastructure, the following steps have to be performed:

1. decide the VOs hierarchy configuration: at least one root VO and a subVO are required to be there
2. identify a set of machines to turn on as DHNs (their number may vary depending on the infrastructure needs)
3. prepare a VO Map XML file for each VO
4. setup the root VO
   1. identify two machines to dedicate to the VO management
   2. install the DHN 1.0 bundle in the two machines and copy the VO Map files under the $GLOBUS_LOCATION/etc/org_diligentproject_keeperservice_hnm/VOmaps folder
   3. configure one DHN (named DIS root DHN) as root, join it to the root VO as default VO and install there the DIS core services (DIS-IC, DIS-Registry, DIS-Broker) dedicated to the management of the root VO
   4. configure one DHN (named DLMan root DHN) to join it to the root VO as default VO and
      • install and populate a Package Repository there (named PR DHN)
      • install and configure a DL Management Service there (named DLMan root DHN)
   5. start the container on the DIS root DHN, then on the DLMan root DHN and then on the PR DHN and verify that they work properly
5. setup the subVO
   1. identify two machines to dedicate to the subVO management
   2. install the DHN 1.0 bundle in the two machines and copy the VO Map files under the $GLOBUS_LOCATION/etc/org_diligentproject_keeperservice_hnm/VOmaps folder
   3. configure one DHN as root, join it to the subVO as default VO and install there the DIS core services (DIS-IC, DIS-Registry, DIS-Broker) dedicated to the subVO (named DIS subVO DHN)
   4. configure one DHN (named DLMan subVO DHN) to join it to the subVO as default VO and install and configure a DL Management Service there (named DLMan root DHN)
6. configure and start generic DHNs
   1. install the DHN 1.0 bundle in each machine and copy the VO Map files under the $GLOBUS_LOCATION/etc/org_diligentproject_keeperservice_hnm/VOmaps folder
   2. configure the DHNs to join the appropriate VO:
      • they can be configured to directly join the subVO
      • or they can be configure to joing the root VO and then dynamically added to the

Manuelesimi 12:10, 4 December 2007 (EET)