The auth plugin specified by auth knows that it got this from a user token and will not attempt to reauthenticate.
Similarly for problem 2, the auth plugin sorts this out, there is a token within the plugin that is used for requests. This negates the need for all those horrible cinderclient context hacks.
Retries are a known problem throughout all of OpenStack, however we can't pass a user_id and password to cinder from nova because this is the user's data - and nova never knows the user's password.
The code mentioned has been replaced. Looking at master calling client looks like:
return cinder_ client. Client( version,
session= _SESSION,
auth= auth,
endpoint_ override= endpoint_ override,
connect_ retries= CONF.cinder. http_retries,
**service_ parameters)
The auth plugin specified by auth knows that it got this from a user token and will not attempt to reauthenticate.
Similarly for problem 2, the auth plugin sorts this out, there is a token within the plugin that is used for requests. This negates the need for all those horrible cinderclient context hacks.
Retries are a known problem throughout all of OpenStack, however we can't pass a user_id and password to cinder from nova because this is the user's data - and nova never knows the user's password.