openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
55,927 Commits 9 Branches 80 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Thierry Carrez a12fde0e68 Start README.rst with a better title 
Now that we are using gitea the contents of our README.rst are
more prominently displayed. Starting it with a "Team and repository
tags" title is a bit confusing. This change makes it start with the
name of the project instead.

Change-Id: I8cefd1bd206520cd83d20807a07a3d55b8ce4d86
 		2019-11-19 17:29:28 +01:00
api-guide/source docs: update SUSPENDED server status wrt supported drivers 2019-11-14 10:25:06 -05:00
api-ref/source Merge "Block deleting compute services with in-progress migrations" 2019-11-16 08:28:41 +00:00
devstack Merge "Find instance in another cell during floating IP re-association" 2019-09-13 15:19:55 +00:00
doc Merge "Remove service_uuids_online_data_migration" 2019-11-18 21:01:45 +00:00
etc/nova Deprecate [api]auth_strategy and noauth2 2019-10-09 15:16:07 -05:00
gate Convert legacy nova-live-migration and nova-multinode-grenade to py3 2019-11-14 16:06:02 +00:00
nova functional: Make '_wait_for_state_change' behave consistently 2019-11-19 09:09:29 +00:00
playbooks Convert legacy nova-live-migration and nova-multinode-grenade to py3 2019-11-14 16:06:02 +00:00
releasenotes Merge "Stop testing Python 2" 2019-11-18 21:38:48 +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 Stop testing Python 2 2019-11-18 10:31:06 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Remove descriptions of nonexistent hacking rules 2019-08-26 14:55:51 +09: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 Start README.rst with a better title 2019-11-19 17:29:28 +01:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Added openssh-client into bindep 2019-10-23 07:21:23 +00:00
lower-constraints.txt Merge "Remove fixed sqlalchemy-migrate deprecation warning filters" 2019-11-15 23:11:07 +00:00
requirements.txt Merge "Stop testing Python 2" 2019-11-18 21:38:48 +00:00
setup.cfg Stop testing Python 2 2019-11-18 10:31:06 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Stop testing Python 2 2019-11-18 10:31:06 +00:00
tox.ini Stop testing Python 2 2019-11-18 10:31:06 +00:00

README.rst

OpenStack Nova

image

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: