Thierry Carrez 909d0de68e Remove unused rootwrap filters
Thanks to mikal, nova was fully transitioned to using privsep over
the past cycles. However the old rootwrap filter definitions have been
left behind, which basically means that there is limited security
benefit right now (code gone rogue could still call rootwrap to execute
some code as root).

As far as I can tell, those can be removed now. os-brick calls in
compute.filters should be covered by the os_brick.privileged.default
context.

Rootwrap is now only used to launch the two privileged privsep contexts.
Since those are one-shot at the start of the service, there is little
point in using rootwrap-daemon on nova nodes.

network.filters and api-metadata.filters are being removed in
https://review.opendev.org/#/c/696518 as part of the nova-net cleanup.

Change-Id: Ie5e5ab17dabad713d4ad1261ab8b5d62b017f31e
2019-12-04 12:32:49 +01:00
2019-12-04 12:32:49 +01:00
2019-04-28 20:06:15 +00: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
2012-02-08 19:30:39 -08:00
2019-10-23 07:21:23 +00:00
2018-01-12 17:05:11 +08:00
2010-05-27 23:05:26 -07:00
2017-09-07 15:42:31 +02:00
2017-03-02 11:50:48 +00:00
2019-11-18 10:31:06 +00: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, 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:

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