Glance and glanceclient have patches up for a no auth
option in glance. In order for that to happen, nova needs to
send in additional information in its headers to glanceclient.
More details:
Some deployments have everything in the same network. And
for long running snapshots this may cause 401s because
token expires. In these cases the reauth is not required
cause nova has already authenticated the user.
This patch does not convert it to no auth. It only makes
it optional for glance users who do want to use that option.
Related patches: https://review.openstack.org/#/c/37062/ https://review.openstack.org/#/c/36563/
Reviewed: https:/ /review. openstack. org/37070 github. com/openstack/ nova/commit/ 5bb1803cfd82ece ec09765fb3c41e9 e571364a94
Committed: http://
Submitter: Jenkins
Branch: master
commit 5bb1803cfd82ece ec09765fb3c41e9 e571364a94
Author: iccha.sethi <email address hidden>
Date: Fri Jul 12 20:23:19 2013 +0000
Add identity headers while calling glanceclient
Glance and glanceclient have patches up for a no auth /review. openstack. org/#/c/ 37062/ /review. openstack. org/#/c/ 36563/
option in glance. In order for that to happen, nova needs to
send in additional information in its headers to glanceclient.
More details:
Some deployments have everything in the same network. And
for long running snapshots this may cause 401s because
token expires. In these cases the reauth is not required
cause nova has already authenticated the user.
This patch does not convert it to no auth. It only makes
it optional for glance users who do want to use that option.
Related patches:
https:/
https:/
Resolves bug 1200761
Change-Id: Ife02059abbdce7 920f1f408b71e97 45d777fa770