From 99735fa39ab3feab44a49b2acf06cb079da64e94 Mon Sep 17 00:00:00 2001 From: zte-hanrong Date: Fri, 18 Nov 2016 14:57:06 +0800 Subject: [PATCH] Solve some spelling mistakes. Change-Id: Id7e8c4efbfc4203e63583b68c87be75f4a195b66 --- releasenotes/notes/add-scoring-module-fa00d013ed2d614e.yaml | 2 +- releasenotes/notes/get-goal-from-strategy-396c9b13a38bb650.yaml | 2 +- .../decision_engine/strategy/strategies/basic_consolidation.py | 2 +- .../strategy/strategies/vm_workload_consolidation.py | 2 +- watcher/objects/audit.py | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/releasenotes/notes/add-scoring-module-fa00d013ed2d614e.yaml b/releasenotes/notes/add-scoring-module-fa00d013ed2d614e.yaml index bd9dd3f45..1255b7131 100644 --- a/releasenotes/notes/add-scoring-module-fa00d013ed2d614e.yaml +++ b/releasenotes/notes/add-scoring-module-fa00d013ed2d614e.yaml @@ -1,7 +1,7 @@ --- features: - Added a generic scoring engine module, which - will standarize interactions with scoring engines + will standardize interactions with scoring engines through the common API. It is possible to use the scoring engine by different Strategies, which improve the code and data model re-use. diff --git a/releasenotes/notes/get-goal-from-strategy-396c9b13a38bb650.yaml b/releasenotes/notes/get-goal-from-strategy-396c9b13a38bb650.yaml index fa077846a..9732b1527 100644 --- a/releasenotes/notes/get-goal-from-strategy-396c9b13a38bb650.yaml +++ b/releasenotes/notes/get-goal-from-strategy-396c9b13a38bb650.yaml @@ -2,4 +2,4 @@ features: - Added a way to return the of available goals depending on which strategies have been deployed on the node - where the decison engine is running. + where the decision engine is running. diff --git a/watcher/decision_engine/strategy/strategies/basic_consolidation.py b/watcher/decision_engine/strategy/strategies/basic_consolidation.py index 58b0d9884..e51815ded 100644 --- a/watcher/decision_engine/strategy/strategies/basic_consolidation.py +++ b/watcher/decision_engine/strategy/strategies/basic_consolidation.py @@ -30,7 +30,7 @@ This algorithm not only minimizes the overall number of used servers, but also minimizes the number of migrations. It has been developed only for tests. You must have at least 2 physical compute -nodes to run it, so you can easilly run it on DevStack. It assumes that live +nodes to run it, so you can easily run it on DevStack. It assumes that live migration is possible on your OpenStack cluster. """ diff --git a/watcher/decision_engine/strategy/strategies/vm_workload_consolidation.py b/watcher/decision_engine/strategy/strategies/vm_workload_consolidation.py index 247a9c3be..75069edd8 100644 --- a/watcher/decision_engine/strategy/strategies/vm_workload_consolidation.py +++ b/watcher/decision_engine/strategy/strategies/vm_workload_consolidation.py @@ -129,7 +129,7 @@ class VMWorkloadConsolidation(base.ServerConsolidationBaseStrategy): self.number_of_released_nodes -= 1 def add_action_disable_node(self, node): - """Add an action for node disablity into the solution. + """Add an action for node disability into the solution. :param node: node object :return: None diff --git a/watcher/objects/audit.py b/watcher/objects/audit.py index 7a73f5f92..57c6f35e7 100644 --- a/watcher/objects/audit.py +++ b/watcher/objects/audit.py @@ -108,7 +108,7 @@ class Audit(base.WatcherPersistentObject, base.WatcherObject, _old_state = None # NOTE(v-francoise): The way oslo.versionedobjects works is by using a - # __new__ that will automagically create the attributes referenced in + # __new__ that will automatically create the attributes referenced in # fields. These attributes are properties that raise an exception if no # value has been assigned, which means that they store the actual field # value in an "_obj_%(field)s" attribute. So because we want to proxify a