<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ceph on System Administration, Hosting, Cloud and technologies in between</title>
    <link>https://dmsimard.com/categories/ceph/</link>
    <description>Recent content in ceph on System Administration, Hosting, Cloud and technologies in between</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 27 Mar 2015 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://dmsimard.com/categories/ceph/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Ceph erasure coding overhead in a nutshell</title>
      <link>https://dmsimard.com/2015/03/27/ceph-erasure-coding-overhead-in-a-nutshell/</link>
      <pubDate>Fri, 27 Mar 2015 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2015/03/27/ceph-erasure-coding-overhead-in-a-nutshell/</guid>
      <description>Calculating the storage overhead of a replicated pool in Ceph is easy. You divide the amount of space you have by the &amp;ldquo;size&amp;rdquo; (amount of replicas) parameter of your storage pool.
Let&amp;rsquo;s work with some rough numbers: 64 OSDs of 4TB each.
Raw size: 64 * 4 = 256TB Size 2 : 128 / 2 = 128TB Size 3 : 128 / 3 = 85.33TB  Replicated pools are expensive in terms of overhead: Size 2 provides the same resilience and overhead as RAID-1.</description>
    </item>
    
    <item>
      <title>New release of python-cephclient: 0.1.0.5</title>
      <link>https://dmsimard.com/2015/03/11/new-release-of-python-cephclient/</link>
      <pubDate>Wed, 11 Mar 2015 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2015/03/11/new-release-of-python-cephclient/</guid>
      <description>I&amp;rsquo;ve just drafted a new release of python-cephclient on PyPi: v0.1.0.5.
After learning about the ceph-rest-api I just had to do something fun with it.
In fact, it&amp;rsquo;s going to become very handy for me as I might start to develop with it for things like nagios monitoring scripts.
The changelog:
dmsimard:
 Add missing dependency on the requests library Some PEP8 and code standardization cleanup Add root &amp;ldquo;PUT&amp;rdquo; methods Add mon &amp;ldquo;PUT&amp;rdquo; methods Add mds &amp;ldquo;PUT&amp;rdquo; methods Add auth &amp;ldquo;PUT&amp;rdquo; methods  Donald Talton:</description>
    </item>
    
    <item>
      <title>A new Ceph mirror on the east coast</title>
      <link>https://dmsimard.com/2014/08/09/a-new-ceph-mirror-on-the-east-coast/</link>
      <pubDate>Sat, 09 Aug 2014 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2014/08/09/a-new-ceph-mirror-on-the-east-coast/</guid>
      <description>I’m glad to announce that Ceph is now part of the mirrors iWeb provides.
It is available in both IPv4 and IPv6 by:
  http on http://mirror.iweb.ca/ or directly on http://ceph.mirror.iweb.ca/
  rsync on ceph.mirror.iweb.ca::ceph
  The mirror provides 4 Gbps of connectivity and is located on the eastern coast of Canada, more precisely in Montreal, Quebec.
We feel this complements very well the principal ceph mirror at ceph.</description>
    </item>
    
    <item>
      <title>A use case of Tengine, a drop-in replacement and fork of nginx</title>
      <link>https://dmsimard.com/2014/06/21/a-use-case-of-tengine-a-drop-in-replacement-and-fork-of-nginx/</link>
      <pubDate>Sat, 21 Jun 2014 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2014/06/21/a-use-case-of-tengine-a-drop-in-replacement-and-fork-of-nginx/</guid>
      <description>I&amp;rsquo;ve always been a fan of nginx, it was love at first sight.
I tend to use nginx first and foremost as a reverse proxy server for web content and applications. This means that nginx sends your request to backend servers and forwards you their response.
Some examples of backend servers I use:
 php5-fpm for PHP gunicorn or wsgi for Python PSGI/Plack or fastcgi for Perl  Now, the cool thing is that these backend servers are good at what they do: serve code and applications written in specific languages.</description>
    </item>
    
    <item>
      <title>Inktank and Redhat to open source Calamari, the Ceph web interface</title>
      <link>https://dmsimard.com/2014/05/03/inktank-redhat-to-open-source-calamari-the-ceph-web-interface/</link>
      <pubDate>Sat, 03 May 2014 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2014/05/03/inktank-redhat-to-open-source-calamari-the-ceph-web-interface/</guid>
      <description>You might have heard this already but Redhat made an annoucement last week that they will be acquiring Inktank, the company behind Ceph.
Inktank steered Ceph&amp;rsquo;s development, offered training and provided support through an entreprise package which included Calamari: a web interface to have insight on what is going on inside your cluster.
You can have a peek at what Calamari looks like here - in a session from Portland&amp;rsquo;s Openstack Summit.</description>
    </item>
    
    <item>
      <title>Openstack, Swift and Ceph @ Openstack Montreal</title>
      <link>https://dmsimard.com/2014/03/15/openstack-swift-ceph-openstack-montreal/</link>
      <pubDate>Sat, 15 Mar 2014 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2014/03/15/openstack-swift-ceph-openstack-montreal/</guid>
      <description>The second meetup of Openstack Montreal, in collaboration with iWeb, Enovance and Savoir-faire Linux, will happen at the Université du Québec à Montréal (UQAM) monday march 17th.
It&amp;rsquo;s with great pleasure that I accepted an invitation from my colleague Rafael Rosa (@rafaelrosafu) to talk about Ceph in the context of Openstack.
Our friends at Enovance will be talking about Swift, the object storage project in Openstack.
Should definitely be fun, it will in fact be my first public speech ever :D</description>
    </item>
    
    <item>
      <title>python-cephclient now on PyPi</title>
      <link>https://dmsimard.com/2014/01/18/python-cephclient-now-on-pypi/</link>
      <pubDate>Sat, 18 Jan 2014 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2014/01/18/python-cephclient-now-on-pypi/</guid>
      <description>Back on January 1st, I wrote about my initiative regarding a client for the Ceph REST API made in python.
I&amp;rsquo;m glad to announce that the client is now available on PyPi and I have just drafted the second release: v0.1.0.2.
Check it out and let me know what you think !</description>
    </item>
    
    <item>
      <title>A python client for ceph-rest-api</title>
      <link>https://dmsimard.com/2014/01/01/a-python-client-for-ceph-rest-api/</link>
      <pubDate>Wed, 01 Jan 2014 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2014/01/01/a-python-client-for-ceph-rest-api/</guid>
      <description>After learning there was an API for Ceph, it was clear to me that I was going to write a client to wrap around it and use it for various purposes.
It is still a work in progress and I feel it is not complete and clean enough to publish on pypi yet but I invite you to take a look and tell me what you think !
The client is available on Github under the Apache v2 license here: https://github.</description>
    </item>
    
    <item>
      <title>Documentation for ceph-rest-api</title>
      <link>https://dmsimard.com/2014/01/01/documentation-for-ceph-rest-api/</link>
      <pubDate>Wed, 01 Jan 2014 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2014/01/01/documentation-for-ceph-rest-api/</guid>
      <description>I learned that there was a Ceph REST API and I experimented with it a bit.
I said the documentation was lacking and I take that back, I didn&amp;rsquo;t catch on that the API documentation was built into the application. I opened a pull request to make the documentation a bit more explicit about that: https://github.com/ceph/ceph/pull/1026
Here&amp;rsquo;s what the API documentation currently looks like:
Enjoy !</description>
    </item>
    
    <item>
      <title>Experimenting with the Ceph REST API</title>
      <link>https://dmsimard.com/2013/12/21/experimenting-with-the-ceph-rest-api/</link>
      <pubDate>Sat, 21 Dec 2013 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2013/12/21/experimenting-with-the-ceph-rest-api/</guid>
      <description>Like I mentioned in my previous post, Ceph has a REST API now. That opens a lot of possibilities.
The Ceph REST API is a WSGI application and it listens on port 5000 by default.
This means you can query it directly but you probably want to put a webserver/proxy such a Apache or nginx in front of it.
For high availability, you could run ceph-rest-api on several servers and have redundant load balancers pointing to the API endpoints.</description>
    </item>
    
    <item>
      <title>Ceph has a REST API!</title>
      <link>https://dmsimard.com/2013/12/06/ceph-has-a-rest-api/</link>
      <pubDate>Fri, 06 Dec 2013 00:00:00 +0000</pubDate>
      
      <guid>https://dmsimard.com/2013/12/06/ceph-has-a-rest-api/</guid>
      <description>Ceph is a distributed object store and file system designed to provide excellent performance, reliability and scalability.
It&amp;rsquo;s a technology I&amp;rsquo;ve been following and working with for the past couple months, especially around deploying it with puppet, I really have a feeling it is going to revolutionize the world of storage.
I just realized Ceph has a REST API since the Dumpling (0.67) release.
This API essentially wraps around the command line tools allowing you to monitor and manage your cluster.</description>
    </item>
    
  </channel>
</rss>