blueprint sphinx-doc-cleanup bug 944385 - Fix formatting and markup issues that produce error messages - Update TOC lists for missing/new files - Fix a few links - Update instructions with dependencies for building the documentation - Updated base on review comments from oubiwann to fix trailing whitespace in modified files Change-Id: I589152bfab9c543d2b11fa8bed2344259aa90675
3.5 KiB
Running Nova
This guide describes the basics of running and managing Nova. This site is intended to provide developer documentation. For more administrator's documentation, refer to docs.openstack.org.
Running the Cloud
The fastest way to get a test cloud running is by following the
directions in the ../quickstart
.
Nova's cloud works via the interaction of a series of daemon
processes that reside persistently on the host machine(s). Fortunately,
the ../quickstart
process launches sample versions of all these daemons for you. Once you
are familiar with basic Nova usage, you can learn more about daemons by
reading ../service.architecture
and binaries
.
Administration Utilities
There are two main tools that a system administrator will find useful to manage their Nova cloud:
nova.manage euca2ools
The nova-manage command may only be run by users with admin
privileges. Commands for euca2ools can be used by all users, though
specific commands may be restricted by Role Based Access Control. You
can read more about creating and managing users in managing.users
User and Resource Management
The nova-manage and euca2ools commands provide the basic interface to perform a broad range of administration functions. In this section, you can read more about how to accomplish specific administration tasks.
For background on the core objects referenced in this section, see
../object.model
managing.users managing.projects managing.instances managing.instance.types managing.images managing.networks managingsecurity
Deployment
For a starting multi-node architecture, you would start with two nodes - a cloud controller node and a compute node. The cloud controller node contains the nova- services plus the Nova database. The compute node installs all the nova-services but then refers to the database installation, which is hosted by the cloud controller node. Ensure that the nova.conf file is identical on each node. If you find performance issues not related to database reads or writes, but due to the messaging queue backing up, you could add additional messaging services (rabbitmq). For instructions on multi-server installations, refer to Installing and Configuring OpenStack Compute.
binaries
Networking
network.vlan.rst network.flat.rst
Advanced Topics
flags monitoring vncconsole