Difference between revisions of "Data e-Infrastructure Management Facilities"
Manuele.simi (Talk | contribs) (→Subsystems) |
Manuele.simi (Talk | contribs) (→Overview) |
||
Line 8: | Line 8: | ||
meaning that the requirements posed to resources (even independent resources) to be managed are minimal, close to zero in some cases. All the implemented solutions are prioritized in order to pursue this goal. | meaning that the requirements posed to resources (even independent resources) to be managed are minimal, close to zero in some cases. All the implemented solutions are prioritized in order to pursue this goal. | ||
+ | |||
+ | Towards new directions of openness and interoperability called by our growing community, management facilities move along: | ||
+ | * the adoption of standards | ||
+ | * a [Resource_Model_(2nd_generation) second generation] of its Resource Model | ||
== Key Features == | == Key Features == |
Revision as of 17:52, 29 February 2012
Overview
Data e-Infrastructure management facilities promote the optimal exploitation of the resources available in the e-Infrastructure and the integration of technology external to the e-Infrastructure. They insulate as much as possible the management of the e-Infrastructure from the data and the data management services that are hosted in or accessible through the infrastructure itself.
The motto at the heart of the management facilities is
less dependencies for more management
meaning that the requirements posed to resources (even independent resources) to be managed are minimal, close to zero in some cases. All the implemented solutions are prioritized in order to pursue this goal.
Towards new directions of openness and interoperability called by our growing community, management facilities move along:
- the adoption of standards
- a [Resource_Model_(2nd_generation) second generation] of its Resource Model
Key Features
- Extensible notion of resource
- a resource model which is open to modular extensions at runtime by arbitrary third parties
- Transparent software resource management
- management facilities requesting nearly zero-dependency to managed resources
- Dynamic Deployment and Optimal Resource (re)Allocation
- ...
- Resource lifetime management
- ...
- Resource publication, discovery and access
- ...
- More self-elastic management for less constraints
- ...
- Interoperability, openness and integration at software level
- third-parties software can be added to the Data e-Infrastructure at runtime, other initiatives can exploit gCube in a standard way
- Support to standards
- crucial functionalities are accessible via recognized standards in order to enhance interoperability
Subsystems
Data e-Infrastructure Management facilities are collectively delivered by the following set of software subsystems:
Resource Management Specification