c05b338f16
Only use PyCrypto/PyCryptodome work-around with Paramiko 1.x and use straight-forward Paramiko interface with 2.x. TODO: Revert this and PyCrypto/PyCryptodome work-around when Paramiko is upgraded to 2.x (ie replace `generate_keys(bits)` call with `paramiko.RSAKey.generate(bits)`). Change If88beeb3983705621fe736995939ac20b2daf1f3 added a work-around for the partially-PyCrypto-compatible PyCryptodome causing Paramiko, which has a dependency on PyCrypto, to break. This work-around entails implementing Paramiko internals (ie how to generate a key) in Nova in a way compatible with both PyCrypto and PyCryptodom. This work-around is itself a source of failure with Paramiko 2 which has replaced the PyCrypto requirement with the cryptography Python package. As Paramiko no longer depends on PyCrypto, Nova doesn't have an explicit PyCrypto requirement, and there's no implicit dependency on PyCrypto, when Nova tries to import PyCrypto it fails. Even if PyCrypto was installed, the work-around would still fail because the Paramiko interface that Nova is using as part of the work-around changed with the major version change (ie 1.x => 2.x). Change-Id: I5d6543e690a3b4495476027fd8a4894ff8c42bf6 Related-Bug: #1483132 |
||
|---|---|---|
| api-guide/source | ||
| api-ref | ||
| 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 | ||
| 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