Difference between revisions of "Data e-Infrastructure Management Facilities"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Key Features) |
(→Subsystems) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <!-- CATEGORIES --> | |
| + | [[Category: gCube Features]] | ||
| + | <!-- CATEGORIES --> | ||
== Overview == | == 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. | 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. | ||
| Line 10: | Line 12: | ||
Towards new directions of openness and interoperability called by our growing community, management facilities move along: | Towards new directions of openness and interoperability called by our growing community, management facilities move along: | ||
| − | * | + | * adoption of standards |
| − | * a [[Resource_Model_(2nd_generation)| second generation]] of its Resource Model | + | * support for new software platforms by implementing a zero-dependency approach to [[Software_Management_Functions|software management]] |
| + | * a [[Resource_Model_(2nd_generation)|second generation]] of its Resource Model | ||
== Key Features == | == Key Features == | ||
| Line 19: | Line 22: | ||
;Transparent software resource management | ;Transparent software resource management | ||
| − | : nearly zero-dependency requested to managed resources | + | :nearly zero-dependency requested to managed resources for being part of the infrastructure |
| + | |||
| + | ;Environment propagation | ||
| + | :operational information among services are transparently propagated over a range of protocols (SOAP, HTTP/S, and more) | ||
;Dynamic Deployment and Optimal Resource (re)Allocation | ;Dynamic Deployment and Optimal Resource (re)Allocation | ||
| − | : remote deployment and (re-)configuration of resources across the infrastructure | + | :remote deployment and (re-)configuration of resources across the infrastructure |
;Resource lifetime management | ;Resource lifetime management | ||
| − | : complete | + | :complete running of the entire lifetime of resources ranging from creation and publication to discovery, access and consumption |
| − | ; | + | ;Self-elastic management |
| − | : | + | :dynamic resource provisioning to meet peaks and lows in demand |
;Interoperability, openness and integration at software level | ;Interoperability, openness and integration at software level | ||
| Line 35: | Line 41: | ||
;Support to standards | ;Support to standards | ||
:crucial functionalities are accessible via recognized standards in order to enhance interoperability | :crucial functionalities are accessible via recognized standards in order to enhance interoperability | ||
| + | |||
| + | ;Multi-platforms | ||
| + | : not only gCore (our ''in-house'' platform), but also Tomcat6, external infrastructures, and a framework for bridging potentially any software hosting platform | ||
== Subsystems == | == Subsystems == | ||
| Line 41: | Line 50: | ||
[[Resource Management Specification]] | [[Resource Management Specification]] | ||
| − | [[Information System Specification]] | + | [[Information System | SmartGears Based Information System Specification]] |
| + | |||
| + | [[gCore Based Information System Specification]] | ||
[[Common Libraries Specification]] | [[Common Libraries Specification]] | ||
Latest revision as of 18:15, 13 December 2016
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:
- adoption of standards
- support for new software platforms by implementing a zero-dependency approach to software management
- a 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
- nearly zero-dependency requested to managed resources for being part of the infrastructure
- Environment propagation
- operational information among services are transparently propagated over a range of protocols (SOAP, HTTP/S, and more)
- Dynamic Deployment and Optimal Resource (re)Allocation
- remote deployment and (re-)configuration of resources across the infrastructure
- Resource lifetime management
- complete running of the entire lifetime of resources ranging from creation and publication to discovery, access and consumption
- Self-elastic management
- dynamic resource provisioning to meet peaks and lows in demand
- 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
- Multi-platforms
- not only gCore (our in-house platform), but also Tomcat6, external infrastructures, and a framework for bridging potentially any software hosting platform
Subsystems
Data e-Infrastructure Management facilities are collectively delivered by the following set of software subsystems:
Resource Management Specification
SmartGears Based Information System Specification
