Archived

This repository has been archived on 2024-04-10. You can view files and clone it, but you cannot make any changes to it's state, such as pushing and creating new issues, pull requests or comments.

History

Renan DelValle 5e4ba5a933 capping funciton now returns which zones were sucessfully capped and which zones could not be capped. This information is now returned to the caller of the HTTP api.		2020-01-18 20:11:44 -08:00
..
main.go	capping funciton now returns which zones were sucessfully capped and which zones could not be capped. This information is now returned to the caller of the HTTP api.	2020-01-18 20:11:44 -08:00
README.md	capping funciton now returns which zones were sucessfully capped and which zones could not be capped. This information is now returned to the caller of the HTTP api.	2020-01-18 20:11:44 -08:00
util.go	capping funciton now returns which zones were sucessfully capped and which zones could not be capped. This information is now returned to the caller of the HTTP api.	2020-01-18 20:11:44 -08:00
util_test.go	capping funciton now returns which zones were sucessfully capped and which zones could not be capped. This information is now returned to the caller of the HTTP api.	2020-01-18 20:11:44 -08:00

README.md

RAPL Daemon

This runs a server that is capable of changing the percentage at which a node is being throttled to using RAPL. This daemon should be installed on all worker nodes.

Sample payload for testing:

 curl --header "Content-Type: application/json" \
  --request POST \
  --data '{"percentage":75}' \
  http://localhost:9090/powercap

Payload

{
    "percentage":75
}

Response

The daemon will respond with a json payload containing zones that were successfully capped as well as the zones that were not capped.

{
    "cappedZones": null,
    "failedZones": [
        "intel-rapl:0",
        "intel-rapl:1"
    ],
    "error": "some zones were not able to be powercapped"
}

Field error will not exist if failed zones is empty.