Skip to content

Ceph Appliance

Cornelius Schumacher edited this page · 13 revisions
Clone this wiki locally

Description

When Florian Haas and I presented our Ceph Tutorial at linux.conf.au 2013, we used Debian VM images, mostly because Florian already had them, and they worked. I'd like to replicate this, but as a Studio Appliance, so people can go download it, deploy it, and play with Ceph on openSUSE and/or SLES.

People

Tim Serong originated this idea.

Status

I plan to work on this project.

Initially unclear on:

  • how best to handle ease of configuration, storage/HW prerequisites, network config, etc. (or just say "this is hard coded for N nodes on this network range, live with it)
  • possible intersection with OpenStack & SUSE Cloud projects.

2013-04-09 Update:

2013-04-11 Update:

  • https://github.com/ceph/ceph-cookbooks now looks markedly newer than the SUSE-Cloud cookbooks (which were originally forked from wonko/ceph-cookbook, because apparently at the time of that fork, the original ceph cookbook wasn't usable). Naturally the two cookbooks look like they work differently, require different attributes, etc...
  • blog post with notes on an attempt to actually use the above cookbooks: http://ourobengr.com/2013/04/the-ceph-chef-experiment/

2013-04-12 Update:

2013-04-15 Update:

Final Status / Impact

  • @Ceph noticed and tweeted about the initial studio appliance image / blog post.
  • That appliance image has been cloned once and downloaded three times, so at least some minor interest :)
  • Blog posts documenting progress (Hackweek 9: Ceph Appliance Odyssey, The Ceph Chef Experiment and One More chef-client Run) provide reasonably thorough/useful information (had a comment that The Ceph Chef Experiment helped to elucidate "the capabilities and complexities of ceph and chef together")
  • Came to the conclusion that in future we should switch to using the upstream ceph chef cookbooks in SUSE Cloud (depending on timing, what version of ceph we're using, etc., but in any case that's the direction we should go in).
  • Next steps for an easy-to-deploy appliance (i.e. TBD at some point in future when I have time):
    • Add csync2 to appliance image for syncing /etc/ceph/ across the cluster
    • Document deployment method, and possibly write a couple of wrapper scripts, similar to the way sleha-boostrap works in SLE HA; it should hopefully come down to: decide on IP address(es) of initial mons, use ceph CLI tools to create mons, osds on each node, then just keep adding nodes.

Categories: storage,cloud Tags: idea,helpwanted,ceph,openstack,inprogress

Related material

Comments

by Tim Serong: Obvious irritation/problem for ad-hoc appliance deployment is injecting hostname & ip address into ceph config. This should be mitigated by deploying in the same way the upstream chef cookbooks do it, i.e. minimal config file with just initial mons specified, then create mons and osds on each node using the ceph CLI tools and rely on the init script in Ceph >= 0.58 to do the right thing with what it finds.

Something went wrong with that request. Please try again.