Difference between revisions of "Data e-Infrastructure Management Facilities"

From Gcube Wiki
Jump to: navigation, search
(Key Features)
(Key Features)
Line 6: Line 6:
 
== Key Features ==
 
== Key Features ==
  
;More management for less dependencies
+
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.
: lesser intrusive than in the past, management facilities requests nearly zero-dependencies to managed services by offering more high level control
+
  
;More self-elastic management for less constraints
+
;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 request nearly zero-dependency to managed resources with lightweight integration mechanisms with existing technologies
 +
 
 +
;Dynamic Deployment and Optimal Resource (re)Allocation
 
:...
 
:...
  
;Feature 3
+
;Resource Lifetime Management
 
:...
 
:...
 +
 +
;More self-elastic management for less constraints
 +
:...
 +
 +
...
  
 
== Subsystems ==
 
== Subsystems ==

Revision as of 23:10, 22 February 2012

This is the template for Facilities Specifications.

Overview

Few lines with a promotional 'flavour', e.g. "gCube xxx facilities offer scalable, high-performance, reliable, open source instruments for ..."

Key Features

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.

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 request nearly zero-dependency to managed resources with lightweight integration mechanisms with existing technologies
Dynamic Deployment and Optimal Resource (re)Allocation
...
Resource Lifetime Management
...
More self-elastic management for less constraints
...

...

Subsystems

Because

  1. the identified facilities might be quite extent / "fat" from the functional point of view and
  2. the information introduced so far is very generic from a technical point of view

one or more 'subsystem' pages should be created.

Each subsystem page is expected to provide the reader with a description capturing design and deployment aspects as well as supported use cases. The following template is proposed:

Subsystem Specification Template

Next step will be the identification of the subsystems for each facility.