The new Ceph container demo is super dope!

Title

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.

Read On...

Disabling scenarios in ceph-docker

Title

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.

Read On...

Test Ceph Luminous pre-release with ceph-docker

Title

/!\ 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:

  • tag-build-master-luminous-centos-7
  • tag-build-master-luminous-ubuntu-16.04

And you will get a running Ceph cluster on Luminous.

Read On...

No more privileged containers for Ceph OSDs

Title

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.

Read On...

Devstack Ceph supports containerized Ceph

Devstack Ceph supports containerized Ceph

Yes people, I’m still alive :). As you might noticed, I’ve been having a hard time to keep up the pace with blogging. It’s mainly due to me traveling a lot these days and preparing conferences. It’s a really busy end of the year for me :).

Fortunately, I’m still finding the time to work on some new features to projects I like. As you might know, I’ve been busy working on ceph-ansible and ceph-docker, trying conciliate both and making sure they work well together. In ceph-docker, we have an interesting container image, that I already presented here. I was recently thinking we could use it to simplify the Ceph bootstrapping process in DevStack. The patch I recently merge doesn’t get ride of the “old” way to bootstrap, the path is just a new addition, a new deployment method.

In practice, this doesn’t change anything for me, but at some point it allows us to validate that a containerized Ceph doesn’t have any problem and bring the same functionality as a non-containerized Ceph. Without further ado, let’s jump into this!

Read On...

Ceph zap device container

Title

Some use cases might require to zap a device (destroy partition tables) prior to run your Ceph OSD container with a dedicated disk. While running development environment this is particularly interesting as this allows us to quickly bootstrap and tear down sandboxes.

Read On...