Difference between revisions of "Resource Management for the gCube Model"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) |
||
| Line 7: | Line 7: | ||
'''This component is under development.''' | '''This component is under development.''' | ||
| − | == | + | == Role and Responsibilities == |
Resource Management refers to a set of software components revolving around the Resource Manager service. They are collectively responsible for delivering the following operations: | Resource Management refers to a set of software components revolving around the Resource Manager service. They are collectively responsible for delivering the following operations: | ||
| − | * creating '' | + | * creating ''contexts'' |
* moving, editing, merging, deleting contexts | * moving, editing, merging, deleting contexts | ||
* managing resources within a context according to the [[Facet_Based_Resource_Model#gCube_Model|'''gCube Resource Model''']]. | * managing resources within a context according to the [[Facet_Based_Resource_Model#gCube_Model|'''gCube Resource Model''']]. | ||
They work atop the [[Information_System_Resource_Registry | Resource Registry]] and its client libraries. | They work atop the [[Information_System_Resource_Registry | Resource Registry]] and its client libraries. | ||
| + | |||
| + | == Design requirements == | ||
| + | |||
| + | * The service has to be stateless. Multiple instances will be deployed behind a HAProxy. | ||
| + | * The service has to be able to manage more than one context (a.k.a. scope). In principle, we will deploy just one set of instances of the service (behind the proxy) to manage the infrastructure context, the VOs, and VREs. However, it should also be possible to deploy one instance for a specific VO. | ||
| + | * A new instance of the service can be added at any time to the set of instances already deployed without manual configuration of the new instance or changes to the configuration of the pre-existing ones. | ||
| + | |||
| + | == Related documentation == | ||
| + | |||
| + | * [[Facet_Based_Resource_Model#gCube_Model| gCube Resource Model]] | ||
| + | * [[Information_System_Resource_Registry | Resource Registry]] | ||
| + | * [[https://wiki.gcube-system.org/gcube/Interacting_with_Resource_Registry_Service_-_Context_and_Schema_Port_Type | Interacting with the Resource Registry]] | ||
Revision as of 06:24, 9 November 2017
This component is under development.
Role and Responsibilities
Resource Management refers to a set of software components revolving around the Resource Manager service. They are collectively responsible for delivering the following operations:
- creating contexts
- moving, editing, merging, deleting contexts
- managing resources within a context according to the gCube Resource Model.
They work atop the Resource Registry and its client libraries.
Design requirements
- The service has to be stateless. Multiple instances will be deployed behind a HAProxy.
- The service has to be able to manage more than one context (a.k.a. scope). In principle, we will deploy just one set of instances of the service (behind the proxy) to manage the infrastructure context, the VOs, and VREs. However, it should also be possible to deploy one instance for a specific VO.
- A new instance of the service can be added at any time to the set of instances already deployed without manual configuration of the new instance or changes to the configuration of the pre-existing ones.
