commit | 793ca1b3b2c568d2165fefa1680247a1c72047d5 | [log] [tgz] |
---|---|---|
author | Serge Bazanski <q3k@hackerspace.pl> | Sun Mar 07 00:07:19 2021 +0000 |
committer | Serge Bazanski <q3k@hackerspace.pl> | Sun Mar 07 00:09:58 2021 +0000 |
tree | 13d8d1aefe9dcac3428768d742b0836d4fda71d1 | |
parent | 3ba5c1b59112905a7736405414fc8bf0447b1006 [diff] |
cluster/kube: limit OSDs in ceph-waw3 to 8GB RAM Each OSD is connected to a 6TB drive, and with the good ol' 1TB storage -> 1GB RAM rule of thumb for OSDs, we end up with 6GB. Or, to round up, 8GB. I'm doing this because over the past few weeks OSDs in ceph-waw3 have been using a _ton_ of RAM. This will probably not prevent that (and instead they wil OOM more often :/), but it at will prevent us from wasting resources (k0 started migrating pods to other nodes, and running full nodes like that without an underlying request makes for a terrible draining experience). We need to get to the bottom of why this is happening in the first place, though. Did this happen as we moved to containerd? Followup: b.hswaw.net/29 Already deployed to production. Change-Id: I98df63763c35017eb77595db7b9f2cce71756ed1
hscloud
is the main monorepo of the Warsaw Hackerspace infrastructure code.
Any time you see a //path/like/this
, it refers to the root of hscloud, ie. the path path/like/this
in this repository. Perforce and/or Bazel users should feel right at home.
For a pleaseant web viewing experience, see this documentation in hackdoc. This will allow you to read this markdown file (and others) in a pretty, linkable view.
See //doc/codelabs for tutorials on how to use hscloud.
If you want to browse the source of hscloud
in a web browser, use cs.hackerspace.pl.
If you want some other help, talk to q3k, informatic or your therapist.
Directories you should care about:
k0.hswaw.net
)Unless noted otherwise, code in hscloud is licensed under the BSD 0-clause license - see COPYING.