diff options
| author | Chris Behrens <cbehrens@codestud.com> | 2012-02-17 00:42:10 +0000 |
|---|---|---|
| committer | Chris Behrens <cbehrens@codestud.com> | 2012-02-22 23:36:50 +0000 |
| commit | 08fa534a0d28fa1be48aef927584161becb936c7 (patch) | |
| tree | d872447d9d266df831c0f077afd09a3bd5e90d32 /bin/stack | |
| parent | 9196e1c7b07be8d3f9dbe7947cace9fd4e862f9c (diff) | |
| download | nova-08fa534a0d28fa1be48aef927584161becb936c7.tar.gz nova-08fa534a0d28fa1be48aef927584161becb936c7.tar.xz nova-08fa534a0d28fa1be48aef927584161becb936c7.zip | |
Remove network_api fallback for info_cache from APIs
Fixes bug 932395
OS API and EC2 would query the network API when instance['info_cache']
had no network info.. or network info was an empty list. The ideal was
to fall back to querying the network IP in case the cache was busted.
However, reality says this case is extremely common as it is the case
when instances are freshly built and haven't had network info assigned
yet. The calls to network API are expensive and goes against the whole
idea of this "cache".
So, this patch removes the fallback to querying the network API. In its
place, it adds a periodic task to the compute manager to periodically
sync the cache entry.
Since I had to fix a number of tests, I consolidated some things there
as well with regards to instance stubbing.
Change-Id: I493f811bcba4e99ac6a5756bcab473557d5c0104
Diffstat (limited to 'bin/stack')
0 files changed, 0 insertions, 0 deletions