Difference between revisions of "Data e-Infrastructure Management Facilities"
From Gcube Wiki
Manuele.simi (Talk | contribs) (Created page with 'This is the template for Facilities Specifications. == Overview == Few lines with a promotional 'flavour', e.g. ''"gCube xxx facilities offer scalable, high-performance, reliab…') |
Manuele.simi (Talk | contribs) (→Key Features) |
||
| Line 5: | Line 5: | ||
== Key Features == | == Key Features == | ||
| − | |||
| − | ; | + | ;More management for less dependencies |
| − | : | + | : 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 |
| − | : | + | :... |
| − | ; | + | ;Feature 3 |
| − | : | + | :... |
| − | + | ||
| − | + | ||
| − | + | ||
== Subsystems == | == Subsystems == | ||
Revision as of 22:52, 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
- More management for less dependencies
- 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
- ...
- Feature 3
- ...
Subsystems
Because
- the identified facilities might be quite extent / "fat" from the functional point of view and
- 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.
