| 2017-04-24 12:40:39 |
suzhengwei |
bug |
|
|
added bug |
| 2017-04-24 12:42:55 |
suzhengwei |
description |
I create a continus audit used vm_workload_consolidation strategy, and find some problems.
1.First audit, self._compute_model is none, and it will build self._compute_model use watcher_cluster_data_model_collectors. The next audit, the self._compute_model is still none, which make me confused.
2.Once a compute node is set disabled, it will never be removed from self._compute_model, because scoped_model only return enable node. There may be some problem with ServerConsolidation Strategy. If all the enabled compute nodes are overloaded, but the instance can't migrate to disabled nodes. |
I create a continus audit used vm_workload_consolidation strategy, and find some problems.
1.First audit, self._compute_model is none, and it will build self._compute_model use watcher_cluster_data_model_collectors. The next audit, the self._compute_model is still none, which make me confused.
2.Once a compute node is set disabled, it will be removed from self._compute_model, because scoped_model only return enable node. There may be some problem with ServerConsolidation Strategy. If all the enabled compute nodes are overloaded, but the instance can't migrate to disabled nodes. |
|
| 2017-04-25 03:30:18 |
suzhengwei |
watcher: assignee |
|
sue (sue.sam) |
|
| 2017-05-22 07:34:28 |
suzhengwei |
watcher: status |
New |
Invalid |
|
| 2017-05-22 07:34:28 |
suzhengwei |
converted to question |
|
633533 |
|
| 2017-05-22 09:57:19 |
suzhengwei |
summary |
compute_model problem |
compute_CDM problem |
|
| 2017-05-22 09:57:28 |
suzhengwei |
summary |
compute_CDM problem |
compute CDM problem |
|
| 2017-05-22 10:00:30 |
suzhengwei |
description |
I create a continus audit used vm_workload_consolidation strategy, and find some problems.
1.First audit, self._compute_model is none, and it will build self._compute_model use watcher_cluster_data_model_collectors. The next audit, the self._compute_model is still none, which make me confused.
2.Once a compute node is set disabled, it will be removed from self._compute_model, because scoped_model only return enable node. There may be some problem with ServerConsolidation Strategy. If all the enabled compute nodes are overloaded, but the instance can't migrate to disabled nodes. |
I create a continus audit used vm_workload_consolidation strategy, and find one problem.
Once a compute node is set disabled, it will be removed from self._compute_model, because scoped_model only return enable node. There may be some problem with vm_workload_consolidation strategy. If all enabled compute nodes are overloaded, the instance can't migrate to disabled nodes. |
|
| 2017-05-25 06:12:42 |
suzhengwei |
description |
I create a continus audit used vm_workload_consolidation strategy, and find one problem.
Once a compute node is set disabled, it will be removed from self._compute_model, because scoped_model only return enable node. There may be some problem with vm_workload_consolidation strategy. If all enabled compute nodes are overloaded, the instance can't migrate to disabled nodes. |
I create a continus audit used vm_workload_consolidation strategy, and find one problem.
Once a compute node is set disabled, it will be removed from self._compute_model, because scoped_model only return enable node. There may be some problem with vm_workload_consolidation strategy. If all enabled compute nodes are overloaded, the instance can't migrate to disabled nodes.
The disabled compute nodes in one availability zone is useful to watcher's strategies. But limited to nova api, we only can get the active compute nodes in the availability zone, so we build an imprecise compute CDM(without disabled compute nodes) in watcher. |
|
| 2017-05-25 09:05:14 |
suzhengwei |
watcher: status |
Invalid |
New |
|
| 2017-08-07 10:23:49 |
OpenStack Infra |
watcher: status |
New |
Fix Released |
|
