Difference between revisions of "GHN Manager"

From Gcube Wiki
Jump to: navigation, search
(Architecture)
Line 1: Line 1:
 +
==== Introduction ====
 
The gHNManager is a gCube Local Service deployed together with the gCore package. Its main role is to provide an interface (mainly exploited by the ''[[VRE Manager[['' service) for managing the node as well as publishing node information. The service is responsible for a correct management and changes of the scope of the GHN and RI resources representing the node and the locally deployed service instances.
 
The gHNManager is a gCube Local Service deployed together with the gCore package. Its main role is to provide an interface (mainly exploited by the ''[[VRE Manager[['' service) for managing the node as well as publishing node information. The service is responsible for a correct management and changes of the scope of the GHN and RI resources representing the node and the locally deployed service instances.
  

Revision as of 16:51, 11 September 2008

Introduction

The gHNManager is a gCube Local Service deployed together with the gCore package. Its main role is to provide an interface (mainly exploited by the [[VRE Manager[[ service) for managing the node as well as publishing node information. The service is responsible for a correct management and changes of the scope of the GHN and RI resources representing the node and the locally deployed service instances.

Implementation overview

The gHNManager is a stateless service since it manages the state of local GCUBE Resources (node and instances). The service has one port-type providing the operations to manipulate such a state.

Operations

The main functions supported by gHNManager (thanks to the support of the gCube Application Framework and its scope management, cf. Section ) are:

  • addScope() – takes as input a valid scope expression; the scope is assigned to the node, if it is compliant with the scope rules of the infrastructure.
  • removeScope()
  • addRItoScope()
  • removeRIScope()