Sylvain Bauza 9666894b46 Strip internal _nova-prefixed scheduler hints on create
User-supplied scheduler hints can include internal keys like
"_nova_check_type" which cause the scheduler to bypass Placement
candidate selection, request pre-filters, and resource claims.
This can lead to instances being created without proper resource
accounting.

Rather than rejecting the request, silently strip any _nova-prefixed
hints before they reach the scheduler. This is consistent with the
existing hints behavior of ignoring unknown ones and ensures the
probe attempt still costs the attacker money.

Assisted-By: Cursor

Change-Id: Iac4fef93bef0bab3060d40a9ea3e0ebd69a38c37
Closes-Bug: #2151252
Signed-off-by: Sylvain Bauza <[email protected]>
2026-06-16 15:21:37 +02:00
2025-09-02 18:06:31 +05:30
2025-09-08 09:35:47 -07:00
2019-04-19 19:45:52 +00:00
2014-05-07 12:14:26 -07:00
2026-01-21 10:56:13 +00:00
2017-11-24 16:51:12 -05:00
2026-05-29 15:53:09 +01:00
2026-01-20 23:14:18 +09:00
2026-04-29 14:37:53 +00:00
2010-05-27 23:05:26 -07:00
2017-09-07 15:42:31 +02:00
2025-03-19 12:30:41 +00:00
2024-01-12 17:47:49 +09:00

OpenStack Nova

OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), VMware and OpenStack Ironic.

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.

To understand better the processes that the team is using, please refer to the Process document.

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:

S
Description
OpenStack Compute (Nova)
Readme 1.7 GiB
Languages
Python 97.5%
Go Template 2.3%
Shell 0.2%