Comment 2 for bug 1257053

Reviewed: https://review.openstack.org/59892
Committed: http://github.com/openstack/cinder/commit/a347b99c261dc1c761a8bc51c2aee99d20161ca6
Submitter: Jenkins
Branch: master

commit a347b99c261dc1c761a8bc51c2aee99d20161ca6
Author: Jay S. Bryant <email address hidden>
Date: Tue Dec 3 21:31:17 2013 -0600

    delete.start/delete.end notification for hostless

    Third party GUIs may rely on notifications to track the
    progress of volume creation and deletion. In the case that
    a volume is being deleted after a failed attempt to create
    (the volume is listed in the database but is not actually
    resident in a backing store) the path that is taken in
    volume.api.delete() makes no notifications of deletion
    occurring.

    This patch adds a volume_utils.notify_about_volume_usage
    call to the beginning and end of the delete with a
    delete.start and delete.end respectively. The notifications
    serve as triggers for GUIs to refresh the state of the
    volume. This change makes the hostless delete path's
    functionality more consistent with the other paths through
    the delete code.

    Change-Id: I091b9d277834b341105569d41a48ef5c1fc105ce
    Closes-Bug: 1257053