The installation of the nova-consoleauth service was erroneously removed from the docs prematurely. The nova-consoleauth service is still being used in Rocky, with the removal being possible in Stein. This should have been fixed as part of change Ibbdc7c50c312da2acc59dfe64de95a519f87f123 but was missed. This is also related to the release note update in Rocky under change Ie637b4871df8b870193b5bc07eece15c03860c06. Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com> Closes-Bug: #1793255 Related-Bug: #1798188 Change-Id: Ied268da9e70bd2807c2dfe7a479181fbec52979d
91 lines
3.1 KiB
ReStructuredText
91 lines
3.1 KiB
ReStructuredText
.. _compute-trusted-pools.rst:
|
|
|
|
=====================
|
|
System administration
|
|
=====================
|
|
|
|
.. toctree::
|
|
:maxdepth: 2
|
|
|
|
manage-users.rst
|
|
manage-volumes.rst
|
|
flavors.rst
|
|
default-ports.rst
|
|
admin-password-injection.rst
|
|
manage-the-cloud.rst
|
|
manage-logs.rst
|
|
root-wrap-reference.rst
|
|
configuring-migrations.rst
|
|
live-migration-usage.rst
|
|
remote-console-access.rst
|
|
service-groups.rst
|
|
node-down.rst
|
|
adv-config.rst
|
|
|
|
To effectively administer compute, you must understand how the different
|
|
installed nodes interact with each other. Compute can be installed in many
|
|
different ways using multiple servers, but generally multiple compute nodes
|
|
control the virtual servers and a cloud controller node contains the remaining
|
|
Compute services.
|
|
|
|
The Compute cloud works using a series of daemon processes named ``nova-*``
|
|
that exist persistently on the host machine. These binaries can all run on the
|
|
same machine or be spread out on multiple boxes in a large deployment. The
|
|
responsibilities of services and drivers are:
|
|
|
|
**Services**
|
|
|
|
``nova-api``
|
|
Receives XML requests and sends them to the rest of the system. A WSGI app
|
|
routes and authenticates requests. Supports the OpenStack Compute APIs. A
|
|
``nova.conf`` configuration file is created when Compute is installed.
|
|
|
|
``nova-compute``
|
|
Manages virtual machines. Loads a Service object, and exposes the public
|
|
methods on ComputeManager through a Remote Procedure Call (RPC).
|
|
|
|
``nova-conductor``
|
|
Provides database-access support for compute nodes (thereby reducing security
|
|
risks).
|
|
|
|
``nova-consoleauth``
|
|
Manages console authentication.
|
|
|
|
.. deprecated:: 18.0.0
|
|
|
|
``nova-consoleauth`` is deprecated since 18.0.0 (Rocky) and will be removed
|
|
in an upcoming release. See
|
|
:oslo.config:option:`workarounds.enable_consoleauth` for details.
|
|
|
|
``nova-objectstore``
|
|
A simple file-based storage system for images that replicates most of the S3
|
|
API. It can be replaced with OpenStack Image service and either a simple
|
|
image manager or OpenStack Object Storage as the virtual machine image
|
|
storage facility. It must exist on the same node as ``nova-compute``.
|
|
|
|
``nova-network``
|
|
Manages floating and fixed IPs, DHCP, bridging and VLANs. Loads a Service
|
|
object which exposes the public methods on one of the subclasses of
|
|
NetworkManager. Different networking strategies are available by changing the
|
|
``network_manager`` configuration option to ``FlatManager``,
|
|
``FlatDHCPManager``, or ``VLANManager`` (defaults to ``VLANManager`` if
|
|
nothing is specified).
|
|
|
|
.. deprecated:: 14.0.0
|
|
|
|
``nova-network`` was deprecated in the OpenStack Newton release.
|
|
|
|
``nova-scheduler``
|
|
Dispatches requests for new virtual machines to the correct node.
|
|
|
|
``nova-novncproxy``
|
|
Provides a VNC proxy for browsers, allowing VNC consoles to access virtual
|
|
machines.
|
|
|
|
.. note::
|
|
|
|
Some services have drivers that change how the service implements its core
|
|
functionality. For example, the ``nova-compute`` service supports drivers
|
|
that let you choose which hypervisor type it can use. ``nova-network`` and
|
|
``nova-scheduler`` also have drivers.
|