Difference between revisions of "Administrator's Guide: How to create a Virtual Organization"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) |
||
| Line 6: | Line 6: | ||
* deploy and configure the [[VO_installation|VO enabling services]] on 3 gHNs. These are the mandatory services needed to glue together the VO nodes; | * deploy and configure the [[VO_installation|VO enabling services]] on 3 gHNs. These are the mandatory services needed to glue together the VO nodes; | ||
* [[VO_configuration|configure]] the VO; | * [[VO_configuration|configure]] the VO; | ||
| − | * [Verifying_the_Virtual_Organization_correctness|verify]] the VO correctness; | + | * [[Verifying_the_Virtual_Organization_correctness|verify]] the VO correctness; |
* [[VO_Resources|create and register]] the VO Resources; | * [[VO_Resources|create and register]] the VO Resources; | ||
* deploy and configure the [[VO_Services_Deployment_and_Configuration|VO-level services]] on 5 gHNs (eventually, other VO specific services). These services are deployed at VO level to support a specific deployment scenario; | * deploy and configure the [[VO_Services_Deployment_and_Configuration|VO-level services]] on 5 gHNs (eventually, other VO specific services). These services are deployed at VO level to support a specific deployment scenario; | ||
Revision as of 19:25, 18 December 2009
This section describes a step-by-step process for creating a new Virtual Organization within an existing gCube infrastructure.
The creation of a VO requires to:
- identify at least 8 machines to turn as gHNs (more machines could be needed, depending on the VO needs);
- deploy and configure the VO enabling services on 3 gHNs. These are the mandatory services needed to glue together the VO nodes;
- configure the VO;
- verify the VO correctness;
- create and register the VO Resources;
- deploy and configure the VO-level services on 5 gHNs (eventually, other VO specific services). These services are deployed at VO level to support a specific deployment scenario;
These steps assume that a Portal has been already deployed and running at infrastructure level and can be configure to join the new VO.
