Difference between revisions of "GHN Manager"
From Gcube Wiki
(New page: The GHNManager is a gCube Service contributing to form the gHN. Its main role is to provide the ''[[VRE Manager[['' service with an entry point for managing the node, e.g. installing the m...) |
Manuele.simi (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | The | + | 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. |
| − | ==== | + | ==== Architecture ==== |
| − | The | + | 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: | The main functions supported by GHNManager (thanks to the support of the gCube Application Framework and its scope management, cf. Section ) are: | ||
| − | * '''addScope()''' – | + | * '''addScope()''' – takes as input the new scope the GHNManager; the scope is assigned to the node, if it is compliant with the scope rules of the infrastructure. |
| − | * '''addRItoScope()''' – | + | * '''removeScope()''' – |
| + | * '''addRItoScope()''' – takes as input parameter a message containing a list of pairs Running Instance identifiers and scope for each of such bindings and notes this new GHN operational context; | ||
| + | * '''removeRIScope()''' – | ||
[[Category:VRE Management]] | [[Category:VRE Management]] | ||
Revision as of 15:45, 11 September 2008
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.
Architecture
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 the new scope the GHNManager; the scope is assigned to the node, if it is compliant with the scope rules of the infrastructure.
- removeScope() –
- addRItoScope() – takes as input parameter a message containing a list of pairs Running Instance identifiers and scope for each of such bindings and notes this new GHN operational context;
- removeRIScope() –
