openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
54,769 Commits 9 Branches 85 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Eric Fried 45026cb5c1 Get rid of args to RBDDriver.__init__() 
While reviewing [1] I noticed an annoying and unnecessary
coupling/duplication of references to the CONF variables for RBD. This
commit consolidates them down to a single source, the guts of
RBDDriver.__init__().

As part of this a workaround is also removed concerning the passing of
conffile=None to RADOS via python-rbd. The following change merged in
2014 so we can now return None when ``[libvirt]/images_rbd_ceph_conf``
is not set:

Make python rados.Rados accept conffile=None
https://github.com/ceph/ceph/pull/1787

[1] https://review.opendev.org/667421

Co-Authored-By: Lee Yarwood <lyarwood@redhat.com>
Change-Id: I361af845d6a733618ecd056aa7df973191184ae9
 		2019-07-29 08:02:19 +00:00
api-guide/source Update api-ref location 2019-07-22 19:17:28 +02:00
api-ref/source Merge "api-ref: touch up the os-services docs" 2019-07-25 19:25:27 +00:00
devstack Merge "Add nova-multi-cell job" 2019-04-30 21:18:42 +00:00
doc Merge "Remove 'nova.virt.driver.ComputeDriver.estimate_instance_overhead'" 2019-07-25 18:16:39 +00:00
etc/nova Merge "Summarize output of sample configuration generator" 2019-06-16 07:30:03 +00:00
gate Convert nova-next to a zuul v3 job 2019-07-23 11:32:35 -04:00
nova Get rid of args to RBDDriver.__init__() 2019-07-29 08:02:19 +00:00
playbooks Merge "Convert nova-next to a zuul v3 job" 2019-07-26 18:02:40 +00:00
releasenotes Use a less chipper title for release notes 2019-07-26 20:19:05 +00:00
roles/run-post-test-hook Convert nova-next to a zuul v3 job 2019-07-23 11:32:35 -04:00
tools Replace git.openstack.org URLs with opendev.org URLs 2019-04-24 13:59:57 +08:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Delete the placement code 2019-04-28 20:06:15 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:45:52 +00:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Disable cinder-backup service in nova-next job 2019-07-24 14:05:44 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Hacking N362: Don't abbrev/alias privsep import 2019-04-04 20:42:43 +00:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
README.rst Update api-ref location 2019-07-22 19:17:28 +02:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt bindep: Remove dead markers 2019-07-18 11:27:13 +01:00
lower-constraints.txt Use Adapter global_request_id kwarg 2019-07-15 14:30:35 -05:00
requirements.txt Use Adapter global_request_id kwarg 2019-07-15 14:30:35 -05:00
setup.cfg Remove nova-consoleauth 2019-07-05 15:04:47 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Merge "Exclude broken ironicclient versions 2.7.1" 2019-06-03 19:44:11 +00:00
tox.ini Update api-ref location 2019-07-22 19:17:28 +02:00

README.rst

Team and repository tags

image

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, OpenStack Ironic and PowerVM.

Use the following resources to learn more.

API

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

For more information on OpenStack APIs, SDKs and CLIs in general, refer to:

Operators

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

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

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:

Other Information

During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: