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

From Gcube Wiki
Jump to: navigation, search
(New page: A ''gCube infrastructure'' is a set of working nodes (so-called DHN, DILIGENT Hossting Node) glued by the gCube enabling services and able to host gCube services. There are two kinds of in...)
 
Line 1: Line 1:
 
A ''gCube infrastructure'' is a set of working nodes (so-called DHN, DILIGENT Hossting Node) glued by the gCube enabling services and able to host gCube services. There are two kinds of infrastructure: secure infrastructures and non-secure infrastructures. The setup of the latter is easier than the former, since the secure infrastructures require some additional steps.
 
A ''gCube infrastructure'' is a set of working nodes (so-called DHN, DILIGENT Hossting Node) glued by the gCube enabling services and able to host gCube services. There are two kinds of infrastructure: secure infrastructures and non-secure infrastructures. 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:
 
In order to setup a non-secure infrastructure, the following steps have to be performed:
−
#decide the VOs hierarchy configuration: at least one root VO and a subVO are required to be there
+
 
−
#identify a set of machines to turn on as DHNs   
+
#decide the VOs hierarchy configuration: at least one root VO and a subVO are required to be there
−
#setup the root VO
+
#identify a set of machines to turn on as DHNs   
−
##identify three machines to dedicate to the VO management
+
#setup the root VO
−
##install the DHN 1.0 bundle in the three machines
+
##identify three machines to dedicate to the VO management
−
##configure one 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 root VO (named ''DIS root DHN'')
+
##install the DHN 1.0 bundle in the three machines
−
##configure one DHN to join the root VO and install and populate a Package Repository there (named ''PR DHN'')
+
##configure one 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 root VO (named ''DIS root DHN'')
−
##configure one DHN to join the root VO install and configure a DL Management Service there (named ''DLMan root DHN'')
+
##configure one DHN to join the root VO and install and populate a Package Repository there (named ''PR DHN'')
−
##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
+
##configure one DHN to join the root VO install and configure a DL Management Service there (named ''DLMan root DHN'')
−
#setup the subVO
+
##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
−
##identify two machines to dedicate to the subVO management
+
#setup the subVO
−
##install the DHN 1.0 bundle in the two machines
+
##identify two machines to dedicate to the subVO management
−
##configure one DHN as root, join it to the subVO as default VO and there the DIS core services (DIS-IC, DIS-Registry, DIS-Broker) dedicated to the subVO (named ''DIS subVO DHN'')
+
##install the DHN 1.0 bundle in the two machines
−
##...
+
##configure one DHN as root, join it to the subVO as default VO and there the DIS core services (DIS-IC, DIS-Registry, DIS-Broker) dedicated to the subVO (named ''DIS subVO DHN'')
−
#configure and start generic DHNs
+
##...
−
##install the DHN 1.0 bundle in each machine
+
#configure and start generic DHNs
−
##...
+
##install the DHN 1.0 bundle in each machine
 +
##...

Revision as of 10:55, 4 December 2007

A gCube infrastructure is a set of working nodes (so-called DHN, DILIGENT Hossting Node) glued by the gCube enabling services and able to host gCube services. There are two kinds of infrastructure: secure infrastructures and non-secure infrastructures. 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
  3. setup the root VO
    1. identify three machines to dedicate to the VO management
    2. install the DHN 1.0 bundle in the three machines
    3. configure one 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 root VO (named DIS root DHN)
    4. configure one DHN to join the root VO and install and populate a Package Repository there (named PR DHN)
    5. configure one DHN to join the root VO install and configure a DL Management Service there (named DLMan root DHN)
    6. 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
  4. setup the subVO
    1. identify two machines to dedicate to the subVO management
    2. install the DHN 1.0 bundle in the two machines
    3. configure one DHN as root, join it to the subVO as default VO and there the DIS core services (DIS-IC, DIS-Registry, DIS-Broker) dedicated to the subVO (named DIS subVO DHN)
    4. ...
  5. configure and start generic DHNs
    1. install the DHN 1.0 bundle in each machine
    2. ...
Retrieved from "https://wiki.gcube-system.org/index.php?title=Administrator%27s_Guide:Setting_up_a_gCube_infrastructure&oldid=3146"