Kepler Documentation about kepler

[williamcaban]

I guess you mean using the Sphinx theme. That's fine with me. I'm happy with anything that can use markdown-type files for quick iteration and easier collaboration on docs.

[gpgn]

Hi, checking out this project after Kubecon EU, looks like an interesting project. Im currently using Scaphandre, and scanning for alternatives.

I was looking for documentation on what exactly it is you're monitoring, and how you are calculating that, similar to:
https://github.com/hubblo-org/scaphandre/blob/main/docs_src/explanations/how-scaph-computes-per-process-power-consumption.md. Then I noticed this issue, so I would recommend having a section like that in your docs. As a user this is the first thing Im looking for.

[rootfs]

@geertpingen slack invite sent. The coefficients are hardcoded at the moment. They will be learned via online training by the model server (still under construction). If you are excited about building a model of your own, it is a place for collaboration

[husky-parul]

We can use one of these as a reference
Volsync
Microshift

[husky-parul]

@rootfs Please assign the issue to me. For some reason I still can't assign issues to myself.

[husky-parul]

@rootfs @nikimanoledaki @williamcaban I would appreciate your inputs on which doc would look good for Kepler. I have mentioned two references above. My preference is VolSync. It looks simple, intuitive and easy to navigate.

[rootfs]

Please use this repo for documentation. Ideally we have doc to serve the following purposes:

• For developers: an deep dive into the development environment, architecture, methodology, enhancement.
• For end users: Environment requirement, deployment process, dashboard setup and customization.
• For integrators: Packaging, API, and extensions.

[husky-parul]

I am going to follow the this flow

Contents

Overview

Installation

Kubernetes

OpenShift

Usage

Developers

End Users

Integratiors

[husky-parul]

Thanks @geertpingen for your suggestions. We are still in early stages but to give some context, we calculate power consumption of running containers in Kubernetes env based on cpu cycles/instruction/time/cache misses etc. Incorporating the details on how it is calculated is still WIP and will be available at our docs page here

[rootfs]

@geertpingen thanks for the pointer, alternative is good for consumers :D

Kepler and Scaphandre both want to give users an answer on how much energy spent by a workload (process, container, or VM).

The difference is that, Scaphandre spends a good deal on breaking down the processes' CPU time to attribute the energy to the workloads. Kepler uses CPU time as well as CPU spends time on doing. At the end of the day, not all CPU instruction consumes the same amount of energy.

[gpgn]

@husky-parul @rootfs Thanks for the quick replies! Again very interesting project. Perhaps this is a question best asked in another setting (forgive me for the clutter here, are you active on Slack or a similar platform?), but I was wondering how you obtain the coefficients here:

kepler/pkg/model/model.go

Line 47 in a71dce9

BareMetalCoeff = Coeff{

(used at

kepler/pkg/collector/reader.go

Line 321 in 79055d7

cpuTimeRatio = float64(float64(v.CurrCPUTime)/aggCPUTime) * coreDelta * model.RunTimeCoeff.CPUTime

)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.