Start OSD during boot time

Prior to this patch OSD daemons were not started during the boot
sequence.

Closes bug: #41
Allow to enable ceph service in ceph::conf

This allows to have a central point to ensure the ceph services starts on
boot.
Start OSD during boot time

Prior to this patch OSD daemons were not started during the boot
sequence.

Closes bug: #41
Allow to enable ceph service in ceph::conf

This allows to have a central point to ensure the ceph services starts on
boot.
Merge pull request #42 from enovance/bug/leseb/41

Start OSD during boot time
Revert "Manage osd journal as a lvm"

This reverts commit ae66e2226aab65fd1a448866b6ac0a9661b5ac6e.

By default, ceph OSD stores its journal in a regular file at
"${osd_data}/journal". This file is created when the OSD is first launched.
With this commit, the "${osd_data}/journal" resource is now managed by Puppet
and replaced by a symlink to a non-existent (in our setup) LVM device.

Result is that the actual journal content gets deleted (and fortunately backed
up in Puppet's clientbucket) and a broken symlink is installed instead.

This is why I think that this commit should be either reverted or that the
File["${osd_data}/journal"] resource should depend on a new parameter which
defaults to false.
Merge pull request #43 from ctrlaltdel/master

Revert "Manage osd journal as a lvm"