I’m excited to announce that just right for Cephalocon and KubeCon Europe, Rook has landed on operatorhub.io. It has been quite a challenge to have it merged, but in the end my pull request got merged :). If you want to know what this means for upstream you should look at this article.
It has been a long time since I’ve been giving updates or even blogging. Let’s take some time here (while being on the plane) to update you on what I’m doing these days.
I’m simply relaying an article I reviewed and helped writting. It is reflecting my talk from the last OpenStack Summit in Berlin.
You can read it here Thanks to the author for capturing the essence of the talk.
I have been recently working on refactoring our Ceph container images.
We used to have two separate images for daemon and demo.
Recently, for Luminous, I decided to merge the demo container into daemon.
It makes everything easier, code is in a single place, we only have a single image to test with the CI and users have a single image to play with.
I have been extensively working on ceph-docker for the last few months and it’s getting better. With the upcoming arrival of Ceph Luminous (next LTS), Bluestore will be the default backend to store objects. Thus, I had to spend some time working on improving the support for Bluestore.
I recently completed a full resync from Kraken to Jewel in ceph-docker in which I introduced a new feature to disable scenarios. Running an application on bleeding edge technology can be tough and challenging for individuals and also for companies. Even me, as a developer and for bleeding edge testers I’m tempted to release unstable features (understand not recommended for production). So sometimes it’s handy to have the ability to restrict the use of a software by disabling some of its functionality. This is exactly what I did for ceph-docker, in this article I’ll explain how that works.
/!\ DISCLAIMER /!\
/!\ DO NOT GET TOO EXCITED, AT THE TIME OF THE WRITTING LUMINOUS IS NOT OFFICIALLY RELEASE IN STABLE YET /!\
/!\ USE AT YOUR OWN RISK, DO NOT PUT PRODUCTION DATA ON THIS /!\
Luminous is just around the corner but we have been having packages available for a couple of weeks already. That’s why I recently thought: “how come don’t we have any Ceph container image for Luminous then?”. And I know a lot of you are eager to test the latest developments of Bluestore (the new method to store objects, directly on a raw device).
Now it’s done, you can fetch the ceph/daemon image using one of these two tags:
And you will get a running Ceph cluster on Luminous.
For the last couple of weeks, Erwan Velu and I have been busy refactoring the entire ceph-docker code base. Through these cosmetic changes, we implemented new mechanisms to finely grained debug containers at run time. This article was co-written with Erwan Velu and will explain what we worked on.
During the last CDM (Ceph Developer Monthly), I presented a blueprint that will help Ceph playing nicely when it’s being containerized.
I’m really sorry for being so quiet lately, I know I promised to release articles more regularly and I clearly failed… Many things are going on and where motivation is key to write articles, I’ve been having a hard time to find the right motivation to write :/
However, I am not giving up and I finally found the time to write a little bit on the things we improved in ceph-docker, our Ceph in container project.