VRE Manager

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. For a detailed explanation about what is a scope and what is in scope, check the Scope Management section of the gCore Developer Guide.

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.

The test-suite

The VREManager comes with a test-suite package allowing to test its functionalities. The package is composed by a set of classes, sample configuration files and scripts ready to be executed. Each script allows to test one service's operation or a group of operations logically related. In the following each script and its usage are explained.

AddResource