grizzly: add docs for nova-conductor

Bug #1082689 reported by Lorin Hochstein
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
High
Tom Fifield

Bug Description

There is a new service called nova-conductor. It will provide services for nova-compute, such as completing database updates and handling long-running tasks.

See:
 * https://review.openstack.org/16135
 * https://review.openstack.org/16136

Tags: nova
Lorin Hochstein (lorinh)
tags: added: grizzly
description: updated
Revision history for this message
Tom Fifield (fifieldt) wrote :

patch was merged

Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → Medium
tags: added: nova
removed: grizzly
Revision history for this message
Ramkumar (na-ramkumar) wrote :
Revision history for this message
Anne Gentle (annegentle) wrote :

What types of additional information would be useful?

Revision history for this message
Ramkumar (na-ramkumar) wrote :

Additional information for?

Revision history for this message
Lorin Hochstein (lorinh) wrote :

I think it would be helpful if there was some text in the compute admin guide that discussed what the nova-conductor service does.

Changed in openstack-manuals:
status: Confirmed → Triaged
Revision history for this message
Ramkumar (na-ramkumar) wrote :

The nova-conductor service is key to completing no-db-compute. Conceptually, it implements a new layer on top of nova-compute. It should *not* be deployed on compute nodes, or else the security benefits of removing database access from nova-compute will be negated. Just like other nova services such as nova-api or nova-scheduler, it can be scaled horizontally. You can run multiple instances of nova-conductor on different machines as needed for scaling purposes.

The methods exposed by nova-conductor will initially be relatively simple methods used by nova-compute to offload its database operations. Places where nova-compute previously did database access will now be talking to nova-conductor. However, we have plans in the medium to long term to move more and more of what is currently in nova-compute up to the nova-conductor layer. The compute service will start to look like a less intelligent slave service to nova-conductor. 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

Revision history for this message
Tom Fifield (fifieldt) wrote :

Thanks Ramkumar!

Revision history for this message
Ramkumar (na-ramkumar) wrote :

No Problem Tom...

Tom Fifield (fifieldt)
Changed in openstack-manuals:
importance: Medium → High
milestone: none → grizzly
Tom Fifield (fifieldt)
Changed in openstack-manuals:
assignee: nobody → Tom Fifield (fifieldt)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (master)

Fix proposed to branch: master
Review: https://review.openstack.org/35025

Changed in openstack-manuals:
status: Triaged → In Progress
Revision history for this message
Tom Fifield (fifieldt) wrote :

patching to add nova-conductor description in the config guide:

https://review.openstack.org/35025

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/35025
Committed: http://github.com/openstack/openstack-manuals/commit/24293e8a2856813ab2460d04fa4c979d7ce92854
Submitter: Jenkins
Branch: master

commit 24293e8a2856813ab2460d04fa4c979d7ce92854
Author: Tom Fifield <email address hidden>
Date: Sun Jun 30 17:10:01 2013 +1000

    Add nova-conductor description to config guide

    Adds a chapter on nova-conductor to the configuration reference

    fixes bug 1082689

    Minor edits, rebase.

    Change-Id: If713e179706228fb5cb2e817a27efb0df81cfe0d

Changed in openstack-manuals:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.