Difference between revisions of "VRE Manager"
Manuele.simi (Talk | contribs) (→Sample Report) |
Manuele.simi (Talk | contribs) (→Configuration) |
||
Line 77: | Line 77: | ||
==== Configuration ==== | ==== Configuration ==== | ||
− | The only configuration parameter is the Scope to operate in. This can be specified in two ways: | + | The only configuration parameter is the Scope in which the instance has to operate in. This can be specified in two ways: |
* as static start Scope of the RI (see the releate section on the [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] for details); | * as static start Scope of the RI (see the releate section on the [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] for details); | ||
* as deployment parameter, in case the VREManager itself is dynamically deployed trough the [[Deployer|Deployer]] facilities. | * as deployment parameter, in case the VREManager itself is dynamically deployed trough the [[Deployer|Deployer]] facilities. |
Revision as of 03:06, 26 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.
Contents
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, ....
Resources Report
After each resource management request, a report is produced by the service.
Possible service states:
- ...
- ...
Possible resource states:
- ...
- ...
Sample Report
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?> <Report> <Type>DEPLOY</Type> <LastUpdate>2008-09-25T16:54:35+02:00</LastUpdate> <Packages> <Package> <ServiceClass>InformationSystem</ServiceClass> <ServiceName>IS-Notifier</ServiceName> <ServiceVersion>1.00.00</ServiceVersion> <PackageName>Notifier-stubs<PackageName> <PackageVersion>1.00.00</PackageVersion> <Status>DEPLOYED</Status> <Host>dlib33.isti.cnr.it:8002</Host> <GHN>a938b7d0-88ce-11dd-a38a-f9b09f00a04e</GHN> </Package> <Package> <ServiceClass>DVOS</ServiceClass> <ServiceName>AuthorizationService</ServiceName> <ServiceVersion>1.00.00</ServiceVersion> <PackageName>Stubs</PackageName> <PackageVersion>0.00.00</PackageVersion> <Status>DEPLOYED</Status> <Host>dlib33.isti.cnr.it:8002</Host> <GHN>a938b7d0-88ce-11dd-a38a-f9b09f00a04e</GHN> </Package> <Package> <ServiceClass>InformationSystem</ServiceClass> <ServiceName>IS-Notifier</ServiceName> <ServiceVersion>1.00.00</ServiceVersion> <PackageName>Notifier-service</PackageName> <PackageVersion>1.00.00</PackageVersion> <Status>DEPLOYED</Status> <Host>dlib33.isti.cnr.it:8002</Host> <GHN>a938b7d0-88ce-11dd-a38a-f9b09f00a04e</GHN> </Package> <Package> <ServiceClass>DVOS</ServiceClass> <ServiceName>AuthorizationService</ServiceName> <ServiceVersion>1.00.00</ServiceVersion> <PackageName>Main</PackageName> <PackageVersion>0.00.00</PackageVersion> <Status>DEPLOYED</Status> <Host>dlib33.isti.cnr.it:8002</Host> <GHN>a938b7d0-88ce-11dd-a38a-f9b09f00a04e</GHN> </Package> </Packages> </Report>
Configuration
The only configuration parameter is the Scope in which the instance has to operate in. This can be specified in two ways:
- as static start Scope of the RI (see the releate section on the gCore Developer Guide for details);
- as deployment parameter, in case the VREManager itself is dynamically deployed trough the Deployer facilities.