cDOT driver should use loopingcall for autosupport report timing

[Clinton Knight]

The Manila cDOT driver uses its own timing code called from get_share_stats() to do ASUP logging. The periodic ASUP task should instead be controlled by an independent looping call task.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/163067
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=1c223f6a997e8fb947a03238388551bdd375d09c
Submitter: Jenkins
Branch: master

commit 1c223f6a997e8fb947a03238388551bdd375d09c
Author: Clinton Knight <email address hidden>
Date: Mon Mar 9 17:13:26 2015 -0400

    Manila cDOT driver should use loopingcall for ASUP report timing

    The Manila cDOT driver uses its own timing code called from
    get_share_stats() to do ASUP logging. The periodic ASUP task
    should instead be controlled by an independent loopingcall task.
    This simplifies the driver and better separates code paths that
    are unrelated and should run separately.

    Change-Id: Ia3deda9415ecb2c026d4e91d047c8611b8432674
    Closes-Bug: #1429972