49b0d1741c
If an exception is raised out of the _report_state call, we find that the service no longer reports any updates to the database, so the service is considered dead, thus creating a kind of zombie service. I55417a5b91282c69432bb2ab64441c5cea474d31 seems to introduce a regression, which leads to nova-* services marked as 'down', if an error happens in a remote nova-conductor while processing a state report: only Timeout errors are currently handled, but other errors are possible, e.g. a DBError (wrapped with RemoteError on RPC client side), if a DB temporarily goes away. This unhandled exception will effectively break the state reporting thread - service will be up again only after restart. While the intention of I55417a5b91282c69432bb2ab64441c5cea474d31 was to avoid cathing all the possible exceptions, but it looks like we must do that to avoid creating a zombie. The other part of that change was to ensure that during upgrade, we do not spam the log server about MessagingTimeouts while the nova-conductors are being restarted. This change ensures that still happens. Closes-Bug: #1517926 Change-Id: I44f118f82fbb811b790222face4c74d79795fe21 |
||
|---|---|---|
| api-guide/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| nova | ||
| plugins/xenserver | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bandit.yaml | ||
| openstack-common.conf | ||
| requirements.txt | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tests-py3.txt | ||
| tox.ini | ||
README.rst
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