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 30: | Line 30: | ||
* 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; | ||
| − | + | All the steps above assume that a [[New_D4Science_Portal_Installation|Portal]] has been already installed, it is running at infrastructure level and can be configured to join the new VO. | |
The last two parts of this section describe how to monitor and manage the Virtual Organization. | The last two parts of this section describe how to monitor and manage the Virtual Organization. | ||
Revision as of 18:32, 23 November 2011
This section describes a step-by-step process for creating a new Virtual Organization (VO) 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;
All the steps above assume that a Portal has been already installed, it is running at infrastructure level and can be configured to join the new VO.
The last two parts of this section describe how to monitor and manage the Virtual Organization.
