I did it mostly to learn about docker (and because i wanted a 'cluster in the office' like Loic had :-)). Not incredibly pretty though. Usually i go with vagrant to deploy ceph in a box (1 mon, 2 osds) in an lxc container, with file loopback mounts and using the puppet module to deploy/config (which has good vagrant integration, and mimics our production env). We use a similar setup for the openstack bits, and it's also the basis of our continuous integration. On Tue, Feb 25, 2014 at 3:11 PM, Hunter Nield <hunter@xxxxxxxx> wrote: > The packer solution sounds sensible to me as it also would allow the > creation of Docker images. > > A basic Docker image has already been started > (https://index.docker.io/u/rochaporto/cephbox/) but it would be quite > useful to have a version that comes from an official maintained > source. > > On Tue, Feb 25, 2014 at 7:06 AM, Kyle Bader <kyle.bader@xxxxxxxxx> wrote: >>> so that's great. It's already almost done. Let us know when you have managed updating it. >>> >>> I suppose it would be best if we could offer one image each of the last 3 Ceph versions (dumpling, emperor and firefly) so people can then play with the expected level they are looking for in either test environment or production environment. >>> >>> Each of the images would be maintained up to date for the last stable code base of each version only to reduce time consuming. >> >> This is screaming for us to use packer [1], that way we can easily >> create vbox/kvm/ec2 images from a file that we can stash in git >> >> [1] http://www.packer.io/ >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
