Michael Still 3f7995f586 Move the idmapshift binary into privsep.

I can't see any evidence that anyone else uses our nova-idmapshift
binary, and it adds a lot of complexity (flags we never call for
example). Move the code we do actually use into the privsep
directory and simplify our calls to it. Remove the extra binary
from our install and documentation.

Change-Id: Ibce28d20d166da154833376cf51f1877b829925e
blueprint: hurrah-for-privsep

2017-10-24 18:50:23 +11:00

2.4 KiB

Raw Blame History

Command-line Utilities

In this section you will find information on Nova's command line utilities.

Nova Management Commands

These commands are used to manage existing installations. They are designed to be run by operators in an environment where they have direct access to the nova database.

nova-manage nova-status

Service Daemons

The service daemons make up a functioning nova environment. All of these are expected to be started by an init system, expect to read a nova.conf file, and daemonize correctly after starting up.

nova-api nova-compute nova-conductor nova-console nova-consoleauth nova-novncproxy nova-scheduler nova-serialproxy nova-spicehtml5proxy nova-xvpvncproxy

WSGI Services

Starting in the Pike release, the preferred way to deploy the nova api is in a wsgi container (uwsgi or apache/mod_wsgi). These are the wsgi entry points to do that.

nova-api-metadata nova-api-os-compute

Additional Tools

There are a few additional cli tools which nova services call when appropriate. This should not need to be called directly by operators, but they are documented for completeness and debugging if something goes wrong.

nova-rootwrap

Deprecated Services

The following services are deprecated in nova. They should not be used in new deployments, but are documented for existing ones.

nova-cells nova-dhcpbridge nova-network

2.4 KiB Raw Blame History