3f7995f586
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
94 lines
2.4 KiB
ReStructuredText
94 lines
2.4 KiB
ReStructuredText
..
|
|
Copyright 2010-2011 United States Government as represented by the
|
|
Administrator of the National Aeronautics and Space Administration.
|
|
All Rights Reserved.
|
|
|
|
Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
not use this file except in compliance with the License. You may obtain
|
|
a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
License for the specific language governing permissions and limitations
|
|
under the License.
|
|
|
|
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.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
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.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
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.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
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.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
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.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
nova-cells
|
|
nova-dhcpbridge
|
|
nova-network
|