Matt Riedemann
9ca2a51ec4
There are two changes here: 1. Removes the mention of the message queue since the cell0 mapping has a transport_url but it's effectively none meaning we don't use RPC for accessing cell0 objects. 2. Adds boilerplate wording on the config option used to determine the database connection if the --database_connection argument is not specified. This was particularly confusing at one point because it originally started out as the CONF.api_database.connection but we changed that mid-cycle in Ocata since the schema for cell0 is the cell (nova) DB, not the nova_api DB. Change-Id: Ie869f8565460600da767d99e9e397abc5e8bf0e0
========================
Team and repository tags
========================
.. image:: http://governance.openstack.org/badges/nova.svg
:target: http://governance.openstack.org/reference/tags/index.html
.. Change things from this point on
OpenStack Nova
==============
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
and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache
License, Version 2.0. The full terms and conditions of this
license are detailed in the LICENSE file.
API
---
To learn how to use Nova's API, consult the documentation
available online at:
http://developer.openstack.org/api-guide/compute/
http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs,
please see:
http://www.openstack.org/appdev/
http://developer.openstack.org/
Operators
---------
To learn how to deploy and configure OpenStack Nova, consult the
documentation available online at:
http://docs.openstack.org
For information about the different compute (hypervisor) drivers
supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
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:
http://bugs.launchpad.net/nova
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:
http://docs.openstack.org/developer/nova/