Revise the compute_upgrade_levels_auto release note

This revises that compute node release note to describe the SIGHUP
service behavior impacts.

Related to blueprint service-version-behavior

Change-Id: I5030cba5e12d3cdfbb563258358c2e43e66bcc08
This commit is contained in:
Dan Smith 2016-01-28 02:43:06 -08:00
parent 70775d1783
commit 86fb45c072

View File

@ -5,4 +5,8 @@ features:
``upgrade_levels.compute`` is accepted, that allows automatic determination ``upgrade_levels.compute`` is accepted, that allows automatic determination
of the compute service version to use for RPC communication. By default, we of the compute service version to use for RPC communication. By default, we
still use the newest version if not set in the config, a specific version still use the newest version if not set in the config, a specific version
if asked, and only do this automatic behavior if 'auto' is configured. if asked, and only do this automatic behavior if 'auto' is
configured. When 'auto' is used, sending a SIGHUP to the service
will cause the value to be re-calculated. Thus, after an upgrade
is complete, sending SIGHUP to all services will cause them to
start sending messages compliant with the newer RPC version.