From 1c6d25290df612099725a83b4a2057ea1104f029 Mon Sep 17 00:00:00 2001 From: Sarafraj Singh Date: Tue, 13 Dec 2016 15:04:33 -0600 Subject: [PATCH] Add service_token for nova-neutron interaction Service token will be passed along with user token to communicate with services when dealing with long running tasks like live migration. This change addresses adding service_token to the request when nova requests neutron session. Implements: blueprint use-service-tokens Change-Id: I5e6d6dfeda3673d38bab0bc692c50ca74eb90fc1 --- nova/conf/service_token.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nova/conf/service_token.py b/nova/conf/service_token.py index 9c4d75959..482c0581f 100644 --- a/nova/conf/service_token.py +++ b/nova/conf/service_token.py @@ -32,7 +32,7 @@ service_user_opts = [ When True, if sending a user token to an REST API, also send a service token. Nova often reuses the user token provided to the nova-api to talk to other -REST APIs, such as Cinder. It is possible that while the +REST APIs, such as Cinder and Neutron. It is possible that while the user token was valid when the request was made to Nova, the token may expire before it reaches the other service. To avoid any failures, and to make it clear it is Nova calling the service on the users behalf, we include