There's no reason to create these files and cleaning them up takes precious time during each test run. Don't do it. The benefits of this can be seen in running both the full test suite and part of the test suite. For the former case - running the full test suite: $ time ( tox -e py27 ) Without this change: real 12m48.003s user 38m27.039s sys 1m2.786s With this change: real 11m53.921s user 39m33.360s sys 1m1.686s For the latter case - running part of the full test suite: $ time ( tox -e py27 -- nova.tests.unit.test_configdrive2 ) Without this change: real 2m0.686s user 1m3.080s sys 0m12.950s With this change: real 1m37.098s user 1m16.559s sys 0m11.846s The actual results can vary massively, but this change is always faster. Change-Id: Iffd759e368878f39c015258935d8b37de09d9745
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
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.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
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:
Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast