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...)
 
 
(27 intermediate revisions by 2 users not shown)
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.
+
[[Category:Administrator's Guide]][[Category:TO_BE_REMOVED]]
−
In order to setup a non-secure infrastructure, the following steps have to be performed:
+
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.<br>
−
#decide the VOs hierarchy configuration: at least one root VO and a subVO are required to be there
+
== Non-secure configuration ==
−
#identify a set of machines to turn on as DHNs
+
==== Minimal configuration ====
−
#setup the root VO
+
The setup a minimal configuration of a non-secure infrastructure requires the following steps:
−
##identify three machines to dedicate to the VO management
+
 
−
##install the DHN 1.0 bundle in the three machines
+
#decide the VOs hierarchy configuration: at least one root VO and a subVO are required to be there
−
##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'')
+
#identify a set of machines to turn on as DHNs (their number may vary depending on the infrastructure needs)
−
##configure one DHN to join the root VO and install and populate a Package Repository there (named ''PR DHN'')
+
#prepare a VO Map XML file for each VO
−
##configure one DHN to join the root VO install and configure a DL Management Service there (named ''DLMan root DHN'')
+
#setup the root VO
−
##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 VO management
−
#setup the subVO
+
##[[DHN_Installation|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
−
##identify two machines to dedicate to the subVO management
+
##[[DHN_Installation#Post-installation_configuration|configure]] one DHN (named ''DIS root DHN'') as root, join it to the root VO as default VO and [[Core_Services_Installation#DILIGENT_Information_Service_.28DIS.29|install the DIS core services]] (DIS-IC, DIS-Registry, DIS-Broker) there dedicated to the management of the root VO
−
##install the DHN 1.0 bundle in the two machines
+
##[[DHN_Installation#Post-installation_configuration|configure]] one DHN (named ''DLMan root DHN'') to join it to the root VO as default VO and
−
##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'')
+
##*[[Core_Services_Installation#Package_Repository|install and populate a Package Repository]] there  
−
##...
+
##*[[Core_Services_Installation#DL_Management|install and configure a DL Management Service]] there
−
#configure and start generic DHNs
+
##start the container on the ''DIS root DHN'' and then on the ''DLMan root DHN'' and verify that they work properly
−
##install the DHN 1.0 bundle in each machine
+
#setup the subVO
−
##...
+
##identify two machines to dedicate to the subVO management
 +
##[[DHN_Installation|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
 +
##[[DHN_Installation#Post-installation_configuration|configure]] one DHN as root, join it to the subVO as default VO and [[Core_Services_Installation#DILIGENT_Information_Service_.28DIS.29|install the DIS core services]] (DIS-IC, DIS-Registry, DIS-Broker) there dedicated to the subVO (named ''DIS subVO DHN'')
 +
##[[DHN_Installation#Post-installation_configuration|configure]] one DHN (named ''DLMan subVO DHN'') to join it to the subVO as default VO and [[Core_Services_Installation#DL_Management|install and configure a DL Management Service]] there
 +
##start the container on the ''DIS subVO DHN'' and then on the ''DLMan subVO DHN'' and verify that they work properly
 +
#configure and start generic DHNs
 +
##[[DHN_Installation|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
 +
##[[DHN_Installation#Post-installation_configuration|configure]] the DHNs to join the subVO as default VO:
 +
##start the container on each machine and verify that the DHN is correctly published both in the root VO and in the subVO DIS
 +
==== Other possible configurations ====
 +
== Secure configuration ==
 +
==== Minimal configuration ====
 +
 
 +
==== Other possible configurations ====
 +
<br>
 +
<br>
 +
[[User:Manuelesimi|Manuelesimi]] 12:49, 4 December 2007 (EET)

Latest revision as of 18:49, 6 July 2016

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.

Non-secure configuration

Minimal configuration

The setup a minimal configuration of a non-secure infrastructure requires the following steps:

  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 the DIS core services (DIS-IC, DIS-Registry, DIS-Broker) there 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
    5. start the container on the DIS root DHN and then on the DLMan root 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 the DIS core services (DIS-IC, DIS-Registry, DIS-Broker) there 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
    5. start the container on the DIS subVO DHN and then on the DLMan subVO DHN and verify that they work properly
  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 subVO as default VO:
    3. start the container on each machine and verify that the DHN is correctly published both in the root VO and in the subVO DIS

Other possible configurations

Secure configuration

Minimal configuration

Other possible configurations



Manuelesimi 12:49, 4 December 2007 (EET)

Retrieved from "https://wiki.gcube-system.org/index.php?title=Administrator%27s_Guide:Setting_up_a_gCube_infrastructure&oldid=25195"