Workload Characterization and QoS
As we run several workloads in a cloud, we should be able to characterize such workloads as input to watcher for ensuring Application QoS, placements and consolidation. An example of workload characterization is a weighted combination of CPU, Memory or any other resource attributes like High IOPs, Network latency etc.
We should be able to map such workload characters to applications (group of VMs) and build strategies for optimization.
Currently watcher doesn't have the concept of workload characterization. In short, we should provide the following capabilities -
1. Specify Workload characteristics
2. Map the Workload characteristics to Applications
3. Build optimization strategies based on these characteristics
Or we may also want watcher to pack a host with VMs of different characterizations together, before adding more of the same type.
Definition of QoS in this context:
Based on the defined workload characteristics we should be able to apply Quality of Services to applications. An example would be leveraging technologies like Intel RDT (http://
This opens up several application optimization possibilities (use cases like NFV etc.) and also ensures efficient use of cloud resources.
Scope of this blueprint is to build a QoS strategy using Intel RDT and workload grammar.
Dependent on https:/
Blueprint information
- Status:
- Not started
- Approver:
- Antoine Cabot
- Priority:
- Undefined
- Drafter:
- Susanne Balle
- Direction:
- Approved
- Assignee:
- Susanne Balle
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Work Items
Dependency tree
* Blueprints in grey have been implemented.