openstack-manuals/doc/config-reference/source/tables/nova-upgrade_levels.rst
KATO Tomoyuki 467eb1431a [config-ref] update compute config options for Newton
Change-Id: I4b7f182daf7bc101a59ddfdb98055ffcd719e3bd
2016-09-30 09:47:45 +00:00

4.3 KiB

Description of upgrade levels configuration options
Configuration option = Default value Description
[cells]

scheduler = nova.cells.scheduler.CellsScheduler

(String) Cells scheduler

The class of the driver used by the cells scheduler. This should be the full Python path to the class to be used. If nothing is specified in this option, the CellsScheduler is used.

[upgrade_levels]
baseapi = None (String) Set a version cap for messages sent to the base api in any service

cells = None

(String) Cells version

Cells client-side RPC API version. Use this option to set a version cap for messages sent to local cells services.

Possible values:

  • None: This is the default value.
  • grizzly: message version 1.6.
  • havana: message version 1.24.
  • icehouse: message version 1.27.
  • juno: message version 1.29.
  • kilo: message version 1.34.
  • liberty: message version 1.37.

Services which consume this:

  • nova-cells

Related options:

  • None

cert = None

(String) Specifies the maximum version for messages sent from cert services. This should be the minimum value that is supported by all of the deployed cert services.

Possible values:

Any valid OpenStack release name, in lower case, such as 'mitaka' or 'liberty'. Alternatively, it can be any string representing a version number in the format 'N.N'; for example, possible values might be '1.12' or '2.0'.

Services which consume this:

  • nova-cert

Related options:

  • None
compute = None (String) Set a version cap for messages sent to compute services. Set this option to "auto" if you want to let the compute RPC module automatically determine what version to use based on the service versions in the deployment. Otherwise, you can set this to a specific version to pin this service to messages at a particular level. All services of a single type (i.e. compute) should be configured to use the same version, and it should be set to the minimum commonly-supported version of all those services in the deployment.
conductor = None (String) Set a version cap for messages sent to conductor services
console = None (String) Set a version cap for messages sent to console services
consoleauth = None (String) Set a version cap for messages sent to consoleauth services

intercell = None

(String) Intercell version

Intercell RPC API is the client side of the Cell<->Cell RPC API. Use this option to set a version cap for messages sent between cells services.

Possible values:

  • None: This is the default value.
  • grizzly: message version 1.0.

Services which consume this:

  • nova-cells

Related options:

  • None
network = None (String) Set a version cap for messages sent to network services

scheduler = None

(String) Sets a version cap (limit) for messages sent to scheduler services. In the situation where there were multiple scheduler services running, and they were not being upgraded together, you would set this to the lowest deployed version to guarantee that other services never send messages that any of your running schedulers cannot understand.

This is rarely needed in practice as most deployments run a single scheduler. It exists mainly for design compatibility with the other services, such as compute, which are routinely upgraded in a rolling fashion.

Services that use this:

  • nova-compute, nova-conductor

Related options:

  • None