Tuesday Tech Tip - The Simplest Way to Build a Ceph Cluster

preview_player
Показать описание
Each Tuesday, we will be releasing a tech tip video that will give users information on various topics relating to our Storinator storage servers.

This week, Mark from our R&D team is here to walk you through our latest Houston module, that will greatly simplify building your next Ceph cluster.

Along with our previous release of Houston modules, the on-going theme behind all of these new features is to get everyone out of the command line and make setting up and managing your storage infrastructure super simple. Still using Ansible underneath the hood, this new Ceph Deployment module will graphically take you through the steps of setting up your own Ceph storage cluster.

Рекомендации по теме
Комментарии
Автор

Lol someone had fun editing this video.

intheprettypink
Автор

Video editing quality is like a... LTT! XD.
Great editing

heechanlee
Автор

Don't care what this video is about but I see a mayhem shrit 🤘

benjaminl
Автор

hii.. what happen if admin crash and need to re install from scratch?

dwieztro
Автор

should we deploy ceph inside kubernetes cluster?
I mean, what if something happened to the cluster than we wouldn't have access to our PVs and PVCs.
Is it possible to integrate ceph with proxmox and than use it inside the kubernetes?
What is the best practice here?

UnleashingMayhem
Автор

where the hell is the second part i want it

whatwhat-
Автор

Whats the default password for the webinterface of cephdeploy?

TrifonKalchev
Автор

Can i suggest something, after each run is done and the done option is made available, would it not be best to Grey out the run option then otherwise you might get someone clicking run again by mistake.

lickerishstick
Автор

If the ansible inventory mgmt is such a tedious task for you why don't you investigate a little bit time into dynamic inventories or the add_host module. You can get rid of all this inventory management when you make the classification on the machines itself, using the daughter board or with some characteristics of the hardware. Also, I would ship this boring manual pinging as part of your playbook 😉

tekknokrat
Автор

does not seem to work, error: nothing provides python3-dataclasses needed by

ArthurOnline
Автор

You get into the quantum matrix ¿ I'm going to stay retired

johnhaight
Автор

I don’t get it why they make ceph so complicated. I mean come on, a rpm/deb package for each service (osd, mon…) and one simple config file in etc/ceph (osd.conf, mon.conf…) and that should be enough. But all this cephadm/cephdeploy madness is just unnecessary

steveo
Автор

Took me many nights to install 4 servers one by one by hand with Ceph. Now you do this in a video that takes not longer than 13 Am I too old ?

Carlos-Rodrigues
Автор

Hey, same question as others, can this work for other hardware than 45drives ? Stuck at the Device Alias playbook (core) step. Would love to ear about you. Huge work on your side guys, thanks a lot.

DaymauhGaming
Автор

Very cool video! Well made! I'm really impressed with the ansible playbooks and this nifty Cockpit module you guys have made! I've never explored cockpit modules, turns out I've been missing out big time!

TmanaokLine
Автор

Hey Guys! What do you think about running ceph on Kubernetes on git?

obtFusi
Автор

package broken now? fedora40 doesn't find dependencies. python3-dataclasses is part of python3 now, and the packages don't seem to have been updated to reflect current package state.

MidnightTech
Автор

Wait though.... Building is one thing, adding on is another.... Maintain and repair, just in case, should be the priority, perhaps ?

johnhaight
Автор

Fuck the marketing team, this is YOUR studio now. Un-negociable.

Varengard
Автор

I do you have Sam deployment for Ubuntu or Debian

alfarahat