Difference between revisions of "Administrator's Guide:Setting up a gCube infrastructure"
From Gcube Wiki
Manuelesimi (Talk | contribs) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:Administrator's Guide]][[Category:TO_BE_REMOVED]] | ||
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> | 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> | ||
| + | == Non-secure configuration == | ||
| + | ==== Minimal configuration ==== | ||
The setup a minimal configuration of a non-secure infrastructure requires the following steps: | The setup a minimal configuration of a non-secure infrastructure requires the following steps: | ||
| Line 23: | Line 26: | ||
##[[DHN_Installation#Post-installation_configuration|configure]] the DHNs to join the subVO as default VO: | ##[[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 | ##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> | ||
<br> | <br> | ||
| − | [[User:Manuelesimi|Manuelesimi]] 12: | + | [[User:Manuelesimi|Manuelesimi]] 12:49, 4 December 2007 (EET) |
Latest revision as of 17: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.
Contents
Non-secure configuration
Minimal configuration
The setup a minimal configuration of a non-secure infrastructure requires the following steps:
- 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 (their number may vary depending on the infrastructure needs)
- prepare a VO Map XML file for each VO
- setup the root VO
- identify two machines to dedicate to the VO management
- 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
- 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
- configure one DHN (named DLMan root DHN) to join it to the root VO as default VO and
- start the container on the DIS root DHN and then on the DLMan root DHN and verify that they work properly
- setup the subVO
- identify two machines to dedicate to the subVO management
- 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
- 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)
- 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
- 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
- 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
- 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
Manuelesimi 12:49, 4 December 2007 (EET)
