I'm not crazy about this approach of making changes throughout the
project; updating all of the projects and then removing the wrapper in
oslo, then updating the libs in all of the projects again is really
something that should not be a top priority.
I do however think that the usage should be allowed to fall off
naturally as other efforts are made to update to using mock, once that's
done we should eventually just find that this wrapper is no longer
needed and remove it from oslo at that time.
** Changed in: cinder
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1266962
Title:
Remove set_time_override in timeutils
Status in OpenStack Telemetry (Ceilometer):
New
Status in Cinder:
Invalid
Status in Gantt:
New
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Status in Ironic (Bare Metal Provisioning):
New
Status in OpenStack Identity (Keystone):
New
Status in Manila:
New
Status in OpenStack Message Queuing Service (Marconi):
New
Status in OpenStack Compute (Nova):
New
Status in Oslo - a Library of Common OpenStack Code:
New
Status in Messaging API for OpenStack:
New
Status in Python client library for Keystone:
New
Status in Python client library for Nova:
New
Status in Tuskar:
New
Bug description:
set_time_override was written as a helper function to mock utcnow in
unittests.
However we now use mock or fixture to mock our objects so
set_time_override has become obsolete.
We should first remove all usage of set_time_override from downstream
projects before deleting it from oslo.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1266962/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
