make timeouts datastore specific

[Amrith Kumar]

Timeouts like resize timeout and restart timeout are currently configurable but are common for all datastores. In restarting some datastores, it has been observed that these timeouts are sufficient but for some others they are not. It would be preferable to make the timeouts datastore specific.

VOLUME_TIME_OUT = CONF.volume_time_out # seconds.
DNS_TIME_OUT = CONF.dns_time_out # seconds.
RESIZE_TIME_OUT = CONF.resize_time_out # seconds.
REVERT_TIME_OUT = CONF.revert_time_out # seconds.
HEAT_TIME_OUT = CONF.heat_time_out # seconds.
USAGE_SLEEP_TIME = CONF.usage_sleep_time # seconds.

from taskmanager/models.py

[Amrith Kumar (amrith)]

Thank you William

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by William Criswell (<email address hidden>) on branch: master
Review: https://review.openstack.org/303671
Reason: Incorrect commit to master

[OpenStack Infra (hudson-openstack)]

Change abandoned by William Criswell (<email address hidden>) on branch: master
Review: https://review.openstack.org/303671
Reason: I am unable to resolve the testing failures in functional-dsvm-mysql, so I hope that someone can complete the change.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Nikhil Manchanda (<email address hidden>) on branch: master
Review: https://review.openstack.org/303671
Reason: Abandoning due to inactivity as per the discussion in the Trove Weekly meeting on 11/9. Please feel free to restore this patch if this is still work in progress. Thanks!

[Trevor McCasland (twm2016)]

Removing low-hanging-fruit tag as this wasn't as easy as we thought.