Description for Elektron Architecture
This commit is contained in:
parent
a5425874c2
commit
219eecc8cf
1 changed files with 5 additions and 0 deletions
|
@ -8,6 +8,11 @@ However, in addition to being a scheduler, Elektron also takes advantage of tool
|
|||
## Architecture
|
||||

|
||||
|
||||
_Elektron_ is comprised of three main components: _Task Queue_, _Scheduler_ and _Power Capper_.
|
||||
* **Task Queue** - Maintains tasks that are yet to be scheduled.
|
||||
* **Scheduler** - Matches tasks' resource requirements with Mesos resource offers. Tasks that matched offers are then launched on the corresponding nodes.
|
||||
* **Power Capper** - The Power Capper monitors the power consumption of the nodes in the cluster through the use of [Performance Co-Pilot](http://pcp.io/). A power capping policy uses this information and decides to power cap or power uncap one or more nodes in the cluster using [RAPL](https://01.org/blogs/2014/running-average-power-limit--rapl).
|
||||
|
||||
## Usage
|
||||
* [Pluggable Scheduling Policies](docs/SchedulingPolicies.md)
|
||||
* [Power-Capping strategies](docs/PowerCappingStrategies.md)
|
||||
|
|
Reference in a new issue