Tuesday Tech Tip - The Simplest Way to Build a Ceph Cluster
Vložit
- čas přidán 16. 08. 2021
- 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.
Visit our website: www.45drives.com/
Check out Ceph Deploy on our GitHub: github.com/45Drives/cockpit-c...
Check out Ansible: github.com/ceph/ceph-ansible
Check out our GitHub that includes our Ansible playbooks: github.com/45drives
Read our Knowledgebase for technical articles: knowledgebase.45drives.com/
Check out our blog: www.45drives.com/blog/
Have a discussion on our subreddit: / 45drives - Věda a technologie
Lol someone had fun editing this video.
Video editing quality is like a... LTT! XD.
Great editing
Love this style haha
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!
Don't care what this video is about but I see a mayhem shrit 🤘
I knew I made the right call wearing that shirt to work the day we shot this. 🤘
Nice Mayhem shirt!
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.
hii.. what happen if admin crash and need to re install from scratch?
Will this work on debian?
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.
Good call, I'll add that in.
I do you have Sam deployment for Ubuntu or Debian
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?
Thanks for the question! We are believers that Ceph should be standalone to the Kubernetes cluster. Ceph and Kubernetes are both complex systems so sticking with our theme of keeping it simple and having them work independently of each other is ideal.
You can consume ceph storage (external to kubernetes) through the use of the ceph-csi drivers (github.com/ceph/ceph-csi). Hope this helps!
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 minutes..... Am I too old ?
where the hell is the second part i want it
Whats the default password for the webinterface of cephdeploy?
I figured it out, you can ignore that post.
Wait though.... Building is one thing, adding on is another.... Maintain and repair , just in case, should be the priority, perhaps ?
Fuck the marketing team, this is YOUR studio now. Un-negociable.
Nice shirt
You get into the quantum matrix ¿ I'm going to stay retired
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 😉
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
does not seem to work, error: nothing provides python3-dataclasses needed by cockpit-ceph-deploy-1.0.2-2.el8.noarch
Hey Arthur, this looks like its just a dependency/repo issue. Which OS are you trying to run on? We only officially support Ubuntu and Rocky at this time. If you are using Rocky or Ubuntu, just make sure that your packages are all up to date. If you are still running into issues, feel free to reach out to us at info@45drives.com and we could get you in touch with support. Thanks!