nova.conf - az configuration options in Configuration Reference

Bug #1668542 reported by Dr. Jens Harbott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Stephen Finucane

Bug Description

This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:

- [X] This doc is inaccurate in this way: __see below____
- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output.

If you have a troubleshooting or support issue, use the following resources:

 - Ask OpenStack: http://ask.openstack.org
 - The mailing list: http://lists.openstack.org
 - IRC: 'openstack' channel on Freenode

----

The descriptions of default_availability_zone and default_schedule_zone are confusing, they seem to serve the same purpose and it is not clear how they differ.

Looking at the code a bit, the text for default_schedule_zone is even wrong, it does not affect the scheduler (at least not directly), but is being used in the "create server" call in the API in case that the original request did not specify an availability_zone.

The default_availability_zone in contrast seems to be used to evaluate what the az for a compute host will be if it is not being set by other means.

It would be nice if someone from Nova team could confirm this before we start updating the docs.

-----------------------------------
Release: 0.9 on 2017-02-28 05:45
SHA: f8b8c1c2f797d927274c6b005dffb4acb18b3a6e
Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/config-reference/source/compute/config-options.rst
URL: https://docs.openstack.org/draft/config-reference/compute/config-options.html

Revision history for this message
John Garbutt (johngarbutt) wrote :

Yeah, lets make that clearer, I think default_availability_zone is about where the host defaults to, and the scheduler one is about where instances go.

Changed in nova:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
John Garbutt (johngarbutt) wrote :

Note, once the patch lands in Nova, the docs need rebuilding to get the updated description, so its quite correct to impact both Nova and the manuals here.

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

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

Changed in nova:
assignee: nobody → John Garbutt (johngarbutt)
status: Confirmed → In Progress
Changed in nova:
assignee: John Garbutt (johngarbutt) → Sylvain Bauza (sylvain-bauza)
Darren Chan (dazzachan)
Changed in openstack-manuals:
status: New → Triaged
importance: Undecided → Medium
milestone: none → pike
Changed in nova:
assignee: Sylvain Bauza (sylvain-bauza) → Stephen Finucane (stephenfinucane)
Changed in openstack-manuals:
assignee: nobody → foundjem (foundjem-devops)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/438887
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4814cfb9daeb7c66d9b2701faa506f42a593ba94
Submitter: Jenkins
Branch: master

commit 4814cfb9daeb7c66d9b2701faa506f42a593ba94
Author: John Garbutt <email address hidden>
Date: Tue Feb 28 09:54:21 2017 +0000

    Fix default_availability_zone docs

    The default_availability_zone description incorrectly mentioned about
    the VM that is being booted.

    To save confusion in the future between default_availability_zone and
    default_schedule_zone, I have moved them into the same file.

    default_schedule_zone didn't previous define what None meant, that has
    also been corrected in this change.

    Change-Id: I370e1309f7b2e01ad76d5345c6fe5d0443942fec
    Closes-Bug: #1668542
    Co-Authored-By: Stephen Finucane <email address hidden>

Changed in nova:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 16.0.0.0b2

This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.

Revision history for this message
Stephen Finucane (stephenfinucane) wrote :

Removing openstack-manuals as docs are maintained in the nova tree since Pike and this is fixed there

Changed in openstack-manuals:
assignee: foundjem (foundjem-devops) → nobody
status: Triaged → Invalid
no longer affects: openstack-manuals
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.