ocaml / ocaml/infrastructure

energy monitoring of the ocaml.org cluster

Open
#25 5 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
42
Forks
11
PR merge metrics
No merged PRs in 30d

Description

As part of the process to reduce our emissions resulting from the ocaml.org infrastructure, we need to first systematically track and measure each service. This issue tracks progress towards determining our current energy expenditure, and we will then have initiatives to reduce and consolidate as appropriate.

  • have a machine readable list of physical/virtual machines we are operating, and their locations. We almost have this now with the information in this repository, @mtelvers?
  • obtain more specific information about energy usage of the various data centres we use.
    • @patricoferris and @avsm have requested access to the University of Cambridge's energy monitoring platform, for all the cluster nodes hosted there (~12 or so)
    • we use Scaleway's Paris2 datacentre which has some statistics here
    • Equinix Metal and Works on ARM have sustainability reports but need to find more specific information.
  • deploy Clarke against the Prometheus instance so we are tracking each machine's energy. @patricoferris and @mtelvers are handling this. As an aside, do we have an ocaml.org-specific instance of Grafana/Prometheus, or is it still running on status.ci.ocamllabs.io?
  • publish the data on ocaml.org, and link to it from https://ocaml.org/policies/carbon-footprint
  • publish blog post https://github.com/ocaml/infrastructure/pull/45 and cross post to discuss.ocaml.org

Once this is done, we can have a review of the actual services and determine how to reduce the footprint.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.