USECASES.md is unclear on what works and what is WIP

[David Gurtner]

Only one of the usecases is clearly marked as not working in this form, while in reality they do not work.
This can lead to confusion for prospective users of the module or worse turn them away from using the module.

As the current puppet recipes are proven via CI to actually support most of these usecases on Ubuntu Precise and RedHat 6.4 family, instead of adding a header about them not being expected to work, they should instead be adapted to working examples.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/98730

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/98730
Committed: https://git.openstack.org/cgit/stackforge/puppet-ceph/commit/?id=4db0825273bd39f392605a90a72acd9d82285878
Submitter: Jenkins
Branch: master

commit 4db0825273bd39f392605a90a72acd9d82285878
Author: David Gurtner <email address hidden>
Date: Sun Jun 8 18:15:44 2014 +0200

    Rewrite the usecases to actually working scenarios

    Only one of the usecases was clearly marked as not working in this form,
    while in reality all but the first do not work.
    This could have led to confusion for prospective users of the module or
    worse turn them away from using the module.

    As the current puppet recipes are proven via CI to actually support these
    usecases on Ubuntu Precise and RedHat 6.4 family, instead of adding a
    header about them not being expected to work, they were instead adapted
    to working examples (with minor adaptions to user specific setups as a
    caveat).

    Change-Id: Id30d339ef1295bb50dcf017eefc996edfc8dbe60
    Closes-Bug: #1327785