64b6c9261e
Current folder name New folder name Book title ---------------------------------------------------------- basic-install DELETE cli-guide DELETE common common NEW admin-guide-cloud Cloud Administrators Guide docbkx-example DELETE openstack-block-storage-admin DELETE openstack-compute-admin DELETE openstack-config config-reference OpenStack Configuration Reference openstack-ha high-availability-guide OpenStack High Availabilty Guide openstack-image image-guide OpenStack Virtual Machine Image Guide openstack-install install-guide OpenStack Installation Guide openstack-network-connectivity-admin admin-guide-network OpenStack Networking Administration Guide openstack-object-storage-admin DELETE openstack-security security-guide OpenStack Security Guide openstack-training training-guide OpenStack Training Guide openstack-user user-guide OpenStack End User Guide openstack-user-admin user-guide-admin OpenStack Admin User Guide glossary NEW OpenStack Glossary bug: #1220407 Change-Id: Id5ffc774b966ba7b9a591743a877aa10ab3094c7 author: diane fleming
37 lines
2.2 KiB
XML
37 lines
2.2 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<section xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
version="5.0"
|
|
xml:id="section_conductor">
|
|
<title>Conductor</title>
|
|
<para>The <systemitem class="service">nova-conductor</systemitem>
|
|
service enables OpenStack to function without compute nodes
|
|
accessing the database. Conceptually, it implements a new
|
|
layer on top of <systemitem class="service"
|
|
>nova-compute</systemitem>. It should not be deployed on
|
|
compute nodes, or else the security benefits of removing
|
|
database access from <systemitem class="service"
|
|
>nova-compute</systemitem> are negated. Just like
|
|
other nova services such as <systemitem class="service"
|
|
>nova-api</systemitem> or nova-scheduler, it can be scaled
|
|
horizontally. You can run multiple instances of <systemitem
|
|
class="service">nova-conductor</systemitem> on different
|
|
machines as needed for scaling purposes.</para>
|
|
<para>
|
|
In the Grizzly release, the methods exposed by <systemitem class="service">nova-conductor</systemitem> are relatively simple methods used by <systemitem class="service">nova-compute</systemitem> to offload its
|
|
database operations.
|
|
Places where <systemitem class="service">nova-compute</systemitem> previously performed database access are now
|
|
talking to <systemitem class="service">nova-conductor</systemitem>. However, we have plans in the medium to
|
|
long term to move more and more of what is currently in <systemitem class="service">nova-compute</systemitem>
|
|
up to the <systemitem class="service">nova-conductor</systemitem> layer. The compute service will start to
|
|
look like a less intelligent slave service to <systemitem class="service">nova-conductor</systemitem>. The
|
|
conductor service will implement long running complex operations,
|
|
ensuring forward progress and graceful error handling.
|
|
This will be especially beneficial for operations that cross multiple
|
|
compute nodes, such as migrations or resizes
|
|
</para>
|
|
<xi:include href="../../common/tables/nova-conductor.xml"/>
|
|
</section>
|
|
|