OpenStack Summit Berlin: Distributed Hyperconvergence Pushing Openstack and Ceph to the Edge
Date: 13/11/18
Date: 13/11/18
My latest presentation of cn
(ceph nano) that I gave at the French Ceph Meetup in Paris.
Date: 22/05/18
Next week is the OpenStack Summit conference. I will attend and will be giving a talk How to Survive an OpenStack Cloud Meltdown with Ceph.
See you there!
I will be attending the Red Hat summit as I’m co-presenting a lab. This goal of the lab is to deploy an OpenStack Hyperconverged environment (HCI) with Ceph. See you in San Francisco!
With its two latest versions (v1.3.0 and v1.4.0) Ceph Nano brought some nifty new functionalities that I’d like to highlight in the article.
Following our recent initiative on writing more Ceph modules for Ceph Ansible, I’d like to introduce one that I recently wrote: ceph_key.
A year ago, I was describing how we were debugging our ceph containers; today I’m back with yet another great thing we wrote :). Sometimes, when a process receives a signal and if that process runs within a container, you might want to do something before or after its termination. That’s what we are going to discuss.
Tomorrow, the first conference fully dedicated to Ceph will start in Beijing, China. I’m attending and super excited. I will see you there!
A massive refactor done a week ago on ceph-container.
And yes, I’m saying ceph-container, not ceph-docker anymore.
We don’t have anything against Docker, we believe it’s excellent and we use it extensively.
However, having the ceph-docker name does not reflect the content of the repository.
Docker is only the Dockerfile
, the rest is either entrypoints or examples.
In the end, we believe ceph-container is a better match for the repository name.