Difference between revisions of "Administrator's Guide:Setting up a gCube infrastructure"
From Gcube Wiki
Manuelesimi (Talk | contribs) |
Manuelesimi (Talk | contribs) |
||
| Line 4: | Line 4: | ||
#decide the VOs hierarchy configuration: at least one root VO and a subVO are required to be there | #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) | #identify a set of machines to turn on as DHNs (their number may vary depending on the infrastructure needs) | ||
| + | |||
#setup the root VO | #setup the root VO | ||
| − | ##identify | + | ##identify two machines to dedicate to the VO management |
| − | ##install the DHN 1.0 bundle in the | + | ##install the DHN 1.0 bundle in the two machines |
| − | ##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 ( | + | ##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 |
| − | + | ##configure one DHN (''DLMan and PR 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'') | ||
##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 | ##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 | ||
| + | |||
#setup the subVO | #setup the subVO | ||
##identify two machines to dedicate to the subVO management | ##identify two machines to dedicate to the subVO management | ||
Revision as of 10:25, 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:
- 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)
- setup the root VO
- identify two machines to dedicate to the VO management
- install the DHN 1.0 bundle in the two machines
- 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
- configure one DHN (DLMan and PR 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)
- 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
- setup the subVO
- identify two machines to dedicate to the subVO management
- install the DHN 1.0 bundle in the two machines
- 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)
- ...
- configure and start generic DHNs
- install the DHN 1.0 bundle in each machine
- ...
