From 86fb45c0724ae0afd39a0e44314b74b31327ea63 Mon Sep 17 00:00:00 2001 From: Dan Smith Date: Thu, 28 Jan 2016 02:43:06 -0800 Subject: [PATCH] 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 --- .../notes/compute_upgrade_levels_auto-97acebc7b45b76df.yaml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/releasenotes/notes/compute_upgrade_levels_auto-97acebc7b45b76df.yaml b/releasenotes/notes/compute_upgrade_levels_auto-97acebc7b45b76df.yaml index 3ae902c51f74..6db301315ddd 100644 --- a/releasenotes/notes/compute_upgrade_levels_auto-97acebc7b45b76df.yaml +++ b/releasenotes/notes/compute_upgrade_levels_auto-97acebc7b45b76df.yaml @@ -5,4 +5,8 @@ features: ``upgrade_levels.compute`` is accepted, that allows automatic determination 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 - 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.