953f1eef19139a6b7b47d56802f211008ca72e7c
Go to file
Balazs Gibizer 953f1eef19 Basics for PCI Placement reporting
A new PCI resource handler is added to the update_available_resources
code path update the ProviderTree with PCI device RPs, inventories and
traits.
It is a bit different than the other Placement inventory reporter. It
does not run in the virt driver level as PCI is tracked in a generic way
in the PCI tracker in the resource tracker. So the virt specific
information is already parsed and abstracted by the resource tracker.
Another difference is that to support rolling upgrade the PCI handler
code needs to be prepared for situations where the scheduler does not
create PCI allocations even after some of the compute already started
reporting inventories and started healing PCI allocations. So the code
is not prepared to do a single, one shot, reshape at startup, but
instead to do a continuous healing of the allocations. We can remove
this continuous healing after the PCI prefilter will be made mandatory
in a future release.
The whole PCI placement reporting behavior is disabled by default while
it is incomplete. When it is functionally complete a new
[pci]report_in_placement config option will be added to allow enabling
the feature. This config is intentionally not added by this patch as we
don't want to allow enabling this logic yet.
blueprint: pci-device-tracking-in-placement
Change-Id: If975c3ec09ffa95f647eb4419874aa8417a59721
2022年08月25日 10:00:10 +02:00
2021年04月09日 16:06:10 +00:00
2022年08月25日 10:00:10 +02:00
2022年03月04日 03:42:14 +00:00
2022年08月25日 10:00:10 +02:00
2016年10月12日 16:20:49 -04:00
2019年04月19日 19:45:52 +00:00
2014年05月07日 12:14:26 -07:00
2017年11月24日 16:51:12 -05:00
2022年05月06日 08:51:15 +02:00
2021年09月01日 12:26:52 +01:00
2010年05月27日 23:05:26 -07:00
2017年09月07日 15:42:31 +02:00
2022年08月25日 10:00:10 +02:00
2022年08月02日 15:31:19 +02:00
2022年08月02日 15:31:19 +02:00
2022年08月02日 15:31:19 +02:00
2017年03月02日 11:50:48 +00:00
2022年08月02日 15:31:19 +02:00
2022年08月22日 14:57:21 +01:00

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 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.

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:

Description
OpenStack Compute (Nova)
Readme 1.7 GiB
Languages
Python 97.6%
Smarty 2.3%
Shell 0.1%