Difference between revisions of "Resource Management Specification"
Manuele.simi (Talk | contribs) (→Dynamic Deployment) |
Manuele.simi (Talk | contribs) |
||
| Line 16: | Line 16: | ||
;Maven Integration | ;Maven Integration | ||
| + | :... | ||
| + | |||
| + | ;Node management and Monitoring | ||
:... | :... | ||
| Line 35: | Line 38: | ||
The main software components forming the subsystem should be identified and roughly described. An architecture diagram has to be added here. A template for the representation of the architecture diagram will be proposed together with an opensource tool required to produce it. | The main software components forming the subsystem should be identified and roughly described. An architecture diagram has to be added here. A template for the representation of the architecture diagram will be proposed together with an opensource tool required to produce it. | ||
| − | |||
| − | |||
== Deployment == | == Deployment == | ||
| Line 54: | Line 55: | ||
=== Well suited Use Cases === | === Well suited Use Cases === | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Less well suited Use Cases === | === Less well suited Use Cases === | ||
| − | |||
| − | |||
Revision as of 19:37, 24 February 2012
Overview
A brief overview of the subsystem should be here. It should include the key features.
Key features
- Dynamic Deployment
- ...
- Optimal Resource Allocation
- ...
- Maven Integration
- ...
- Node management and Monitoring
- ...
- Scalability
- ...
- Coordination and Elastic Management
- ...
- Extensible Bridging over Virtual Platforms
- ...
Design
Philosophy
This is the rationale behind the design. An example will be provided.
Architecture
The main software components forming the subsystem should be identified and roughly described. An architecture diagram has to be added here. A template for the representation of the architecture diagram will be proposed together with an opensource tool required to produce it.
Deployment
Usually, a subsystem consists of a number of number of components. This section describes the setting governing components deployment, e.g. the hardware components where software components are expected to be deployed. In particular, two deployment scenarios should be discussed, i.e. Large deployment and Small deployment if appropriate. If it not appropriate, one deployment diagram has to be produced.
Large deployment
A deployment diagram suggesting the deployment schema that maximizes scalability should be described here.
Small deployment
A deployment diagram suggesting the "minimal" deployment schema should be described here.
Use Cases
The subsystem has been conceived to support a number of use cases moreover it will be used to serve a number of scenarios. This area will collect these "success stories".
