@korkenzieher OK, that was a really helpful RTFM. I now have a virtual IP up and running and can connect to the S3 endpoint via that vIP.

Sadly, the TLS settings seem to be a little less capably in the tentacle release. If I understand the documentation (https://docs.ceph.com/en/tentacle/cephadm/services/rgw/#high-availability-service-for-rgw) correctly, I can handover a TLS certificate and key.

In the `latest` documentation on can specify this should be a self-signed certificate provided by cephadm.

So until I get the Let's Encrypt certificate, I have HTTP traffic served on port 443, as just specifying `ssl: true` seems to do nothing in Tentacle...

#ceph #cephadm #rgw #radosgw #s3 #storage

RGW Service — Ceph Documentation

I found that there are two instances of the RGW service running, which are listening on port 80. I managed to put them behind a simple haproxy (that was already in my homelab) and it seems to work.

Having a virtual IP on all three nodes that hosts the loadbalancer, similar to how kolla-ansible is doing it for the OpenStack things, would be really nice. But I do not want to build and maintain that myself and was hoping for something out of the box...

#ceph #cephadm #storage #s3 #homelab #selfhosting #HellYeah

OK, I am officially confused by the ceph and cephadm documentation (mostly the fact that some things are in the cephadm one and others are in the "general" documentation)

I managed to get a three-node cluster with some old hardware running (as a demo, not productive). MGRs are running, MONs are running, OSDs are running. RGWs are running. The ceph dashboard is running.

Can anyone point me in the right direction / RTFM on how to supply proper certificates to a ceph cluster installed with cephadm? Mostly for the ceph dashboard and the S3 endpoints.

On a related note, do I need to setup haproxy / keepalived / ... myself to make the cluster "highly available" (in my case just surviving the reboot of a node, just to show the setup is "working")? Or can cephadm or similar do that for me, too?

#ceph #cephadm #selfhosting #homelab #storage #s3 #HellYeah

Welp, #cephadm on #Guix just fails with `No such file or directory: 'systemctl'`. Looking at a code search for systemctl apparently #ceph is quite intertwined with #systemd...

#DisDoncMastodon

Tu as une solution géniale pour gérer ton #cluster #ceph "by #state" depuis que #upstream a décidé (de manière inconditionnellement et très très intelligente 😏) de jeter #ceph-ansible à la poubelle ?

De ma fenêtre, #cephadm ne permet QUE de déployer et de prendre la main intelligemment sur les services...

Pas de #SpecsFiles, pas de #states...

Merci pour vos #boosts,

Je sais toi aussi ça t'intéresse 😘😘😘