Dan Smith c8e3cbc4d1 Prevent us from sleeping during DB retry tests
Unit tests should never *actually* sleep. Some of the DB API tests
that poke the retry wrapper in oslo.db trigger situations that would
call time.sleep(). This is part of a desirable exponential backoff
timer in oslo.db, but there's no reason to actually wait to call
the next mock in a unit test. So, mock out sleep for those tests.
Before this, the single-thread time to run test_db_api was 289s,
and afterwards it is 133s.

Change-Id: I0492b497000585f079691ae863b2b2ebf078795d
2016-09-30 11:49:17 -07:00
2014-05-07 12:14:26 -07:00
2012-02-08 19:30:39 -08:00
2010-05-27 23:05:26 -07:00
2015-05-23 03:22:07 +10:00
2016-08-08 10:26:08 +01:00
2016-09-01 17:56:56 +00:00
2015-09-17 16:41:48 +00:00

OpenStack Nova
==============

OpenStack Nova provides a cloud computing fabric controller,
supporting a wide variety of compute technologies, including:
libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer
and OpenStack Ironic.

OpenStack Nova is distributed under the terms of the Apache
License, Version 2.0. The full terms and conditions of this
license are detailed in the LICENSE file.

API
---

To learn how to use Nova's API, consult the documentation
available online at:

    http://developer.openstack.org/api-guide/compute/
    http://developer.openstack.org/api-ref/compute/

For more information on OpenStack APIs, SDKs and CLIs,
please see:

    http://www.openstack.org/appdev/
    http://developer.openstack.org/

Operators
---------

To learn how to deploy and configure OpenStack Nova, consult the
documentation available online at:

    http://docs.openstack.org

For information about the different compute (hypervisor) drivers
supported by Nova, please read:

   http://docs.openstack.org/developer/nova/feature_classification.html

In the unfortunate event that bugs are discovered, they should
be reported to the appropriate bug tracker. If you obtained
the software from a 3rd party operating system vendor, it is
often wise to use their own bug tracker for reporting problems.
In all other cases use the master OpenStack bug tracker,
available at:

   http://bugs.launchpad.net/nova

Developers
----------

For information on how to contribute to Nova, please see the
contents of the CONTRIBUTING.rst.

Any new code must follow the development guidelines detailed
in the HACKING.rst file, and pass all unit tests.

Further developer focused documentation is available at:

   http://docs.openstack.org/developer/nova/
S
Description
No description provided
Readme 258 MiB
Languages
Python 97.5%
Smarty 2.3%
Shell 0.2%