openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
59,769 Commits 9 Branches 80 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Sylvain Bauza a755e5d9f2 api: Drop generating a keypair and add special chars to naming 
As agreed in the spec, we will both drop the generation support for a keypair
but we'll also accept @ (at) and . (dot) chars in the keyname, all of them in
the same API microversion.

Rebased the work from I5de15935e83823afa545a250cf84f6a7a37036b4

APIImpact

Implements: blueprint keypair-generation-removal
Co-Authored-By: Nicolas Parquet <nicolas.parquet@gandi.net>

Change-Id: I6a7c71fb4385348c87067543d0454f302907395e
 		2022-07-28 11:05:50 +02:00
api-guide/source [doc] port-resource-request-groups not landed in Xena 2021-09-06 13:03:22 +02:00
api-ref/source api: Drop generating a keypair and add special chars to naming 2022-07-28 11:05:50 +02:00
devstack Switch to new rolevar for run-tempest role 2021-04-09 16:06:10 +00:00
doc api: Drop generating a keypair and add special chars to naming 2022-07-28 11:05:50 +02:00
etc/nova etc: Highlight absence of packages from config gen 2022-07-14 09:53:52 +01:00
gate Enable unified limits in the nova-next job 2022-03-04 03:42:14 +00:00
nova api: Drop generating a keypair and add special chars to naming 2022-07-28 11:05:50 +02:00
playbooks zuul-job for Adds Pick guest CPU architecture based on host arch 2022-02-25 16:55:43 -05:00
releasenotes api: Drop generating a keypair and add special chars to naming 2022-07-28 11:05:50 +02:00
roles [OVN] Adapt the live-migration job scripts to work with OVN 2021-03-15 09:41:03 +00:00
tools tools: Ignore bot-generated branch creation patches 2021-09-27 10:20:34 +01:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore db: Enable auto-generation of API DB migrations 2021-10-18 20:26:18 +01: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
.pre-commit-config.yaml pre-commit: Sync hacking version, bump plugins 2022-04-05 13:02:18 +01:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml zuul: Put Centos9 Stream job periodic-weekly and experimental 2022-07-12 09:58:39 +02:00
CONTRIBUTING.rst [Community goal] Update contributor documentation 2020-03-25 12:01:37 +00:00
HACKING.rst Add two new hacking rules 2021-09-01 12:26:52 +01: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 docs: Remove references to XenAPI driver 2020-08-31 15:53:31 +01:00
bindep.txt Adapt bindep ubuntu-jammy 2022-05-06 08:51:15 +02:00
mypy-files.txt Follow up for unified limits 2022-03-04 03:42:58 +00:00
requirements.txt Fix compatibility with jsonschema 4.x 2022-07-18 12:30:25 +01:00
setup.cfg Update python testing as per zed cycle teting runtime 2022-04-21 22:06:22 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Move optional build dependencies to 'extras' 2022-01-28 12:27:06 +00:00
tox.ini Merge "Drop lower-constraints.txt and its testing" 2022-05-17 00:01:41 +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, 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: