Back from the Juno summit Ceph integration into OpenStack

Six months have passed since Hong Kong and it is always really exciting to see all the folks from the community gathered all-together in a (bit chilly) convention center. As far I saw from the submitted and accepted talks, Ceph continues its road to the top. There is still a huge growing interest about Ceph. On Tuesday May 13th, Josh and I led a (3 hours long) session to discuss the next steps of the integration of Ceph into OpenStack. To be honest, back when we were in Hong Kong, I believe that we were too optimistic about our roadmap. So this time we decided to be a little more realistic and took a more step-by-step approach rather than “let’s add everything we can”. However, this does not mean that the Icehouse cycle was limited in terms of features, not at all! Indeed the Icehouse cycle has seen some tremendous improvements. I don’t know if you remember my last year article right after the Icehouse summit, there was a feature that I wanted so much: RADOS as a backend for Swift. And yes, we made it, so if you want more details you’d better continue the reading :).

Read On...

Ceph maintenance with Ansible

Following up this article.

This playbook was made to automate Ceph servers maintenance. The typical use case is an hardware change. By running this playbook you will set the noout flag on your cluster, which means that OSD can’t be marked as out of the CRUSH map, but they will be marked as down. Thus the OSD will not receive any data. Basically we tell the cluster to do not move any data since the operation will not last for too long.

Read On...

Don't burn down your OpenStack cloud

t burn down your OpenStack cloud

Managing an OpenStack public cloud can be tough and building it properly is even harder. You can not predict the workload of your platform, customers do what they want (yes they pay for this!). So yes, cloud performance are often unpredictable! Recent studies showed that while running a long-standing benchmark on several cloud platforms, they experienced a performance drop-down of 40% (crazy isn’t it?). However, there are some simple facilities in OpenStack that allow you to have a better control of the resources that you offer to your customers/users. This is what I am going to briefly explore in this article.

Read On...