2c389ccc8c
There was a substantial amount of code in the image cache devoted to checksumming images. However, these checksums were never used beyond the generation of a log message during the image cache manager's periodic task of the form: Corrupt base files: ... This code was expensive to run, added significant complexity to the image cache manager, and not actually used by anything. This patch removes it. The only functional change should be that the above log message is no longer generated. We can't remove it completely in this pass because the image cache may be on shared storage with an old compute host which expects these files to exist. Consequently we retain the code to delete the image metadata file when deleting an entry from the cache, and we don't delete these files automatically when we find them. These vestiges can be removed in Ocata. Additional context can be found here: http://lists.openstack.org/pipermail/openstack-dev/2016-May/095751.html Change-Id: I3d84117809d5058cb2c779754523913347d5374b
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