Difference between revisions of "VRE Manager"
Manuele.simi (Talk | contribs) (→Functions) |
Manuele.simi (Talk | contribs) (→Architecture) |
||
| Line 2: | Line 2: | ||
==== Architecture ==== | ==== Architecture ==== | ||
| − | Within the gCube architecture, the VREManage is placed at the top of a stack of the VREManagement services, below only the [[VRE_Modeler|VRE Modeler]] service. | + | Within the gCube architecture, the VREManage is placed at the top of a stack of the VREManagement services, below only the [[VRE_Modeler|VRE Modeler]] service. Each instance of the service is devoted to manage one and only one specific Scope and, within such a scope, it is in charge of adding/updating/removing GCUBEResource. |
| − | + | ||
| + | ==== Design ==== | ||
| + | The VREManager adopts the Singleton pattern and it exposes a single port-type, <code>gcube/vremanagement/vremanager/VREManager</code>. Clients may manipulate GCUBEResources within the scope by using the operations of such a port-type. | ||
| + | |||
| + | Basically, .... | ||
| + | |||
| + | |||
| + | ==== Configuration ==== | ||
| + | The only configuration parameter is the Scope to operate in. This can be specified in two ways: | ||
| + | * as static start Scope of the RI, see [[https://wiki.gcore.research-infrastructures.eu/gCore-dev/index.php/Scope_Management#Static_scope_for_Running_Instances_.28RIs.29_of_gCube_services || gCore Developer Guide]] | ||
| + | * as deployment parameter, in case the VREManager itself is dynamically deployed trough the [[Deployer|Deployer]] facilities. | ||
| + | |||
| + | |||
| + | ==== The test-suite ==== | ||
==== Functions ==== | ==== Functions ==== | ||
Revision as of 17:34, 25 September 2008
The VRE Manager is a gCube Service grouping the facilities for managing the constituents of the VREs, namely the service instances. It is the service in charge to coordinate the overall deployment and operation of each VRE. Moreover, it takes care to interact with the Virtual Organisation Management to create the VO needed to support the operation of the VREs.
Architecture
Within the gCube architecture, the VREManage is placed at the top of a stack of the VREManagement services, below only the VRE Modeler service. Each instance of the service is devoted to manage one and only one specific Scope and, within such a scope, it is in charge of adding/updating/removing GCUBEResource.
Design
The VREManager adopts the Singleton pattern and it exposes a single port-type, gcube/vremanagement/vremanager/VREManager. Clients may manipulate GCUBEResources within the scope by using the operations of such a port-type.
Basically, ....
Configuration
The only configuration parameter is the Scope to operate in. This can be specified in two ways:
- as static start Scope of the RI, see [|| gCore Developer Guide]
- as deployment parameter, in case the VREManager itself is dynamically deployed trough the Deployer facilities.
