Le Tian Ren 52947efccd Timing issue in remote-keystone deployment model ... This is actually timing issue between openstack service endpoints becoming active and powervc-driver's client initialization of those. 1. get_client() call with version_filter might runs into the 'None' client error mentioned in the bug, which means *currently* only glance sync is affected. When no version filtered, we do a rediscover for the svc_type. 2. get_client() call without version_filter or new_client() call just choose the latest avaiable version service, so no 'None' client error, although the chosen version might not be the real *latest* but the default hardcoded 'v1' version, due to the timing issue mentioned in the bug. For the latter case, unless there is an observation/notification mechanism or poll mechanism for service versions update, based on current design, there is no perfect solution as far as I can imagine. Change-Id: I9ca0f906c8954ecd621be22445c12fd6a55a1ae7 Closes-Bug: 1358215		2014-09-01 13:54:48 +08:00
..
etc	Add retry logic while initializing local keystone client	2014-06-26 13:53:41 +08:00
logrotate.d	Fix flake8 warning and error report	2014-07-22 14:35:24 +08:00
powervc	Timing issue in remote-keystone deployment model	2014-09-01 13:54:48 +08:00
test	Fix flake8 checking issue in powervc-driver and Unittest	2014-08-24 23:14:44 -04:00
.project	Initial code base commit.	2014-05-08 22:00:29 +08:00
.pydevproject	Initial code base commit.	2014-05-08 22:00:29 +08:00
run_tests.sh	Initial code base commit.	2014-05-08 22:00:29 +08:00