openstack
/
magnum
Code Issues Proposed changes

Merge "Corrected some misspellings in magnum"

This commit is contained in:
Zuul 2018-02-23 10:17:18 +00:00 committed by Gerrit Code Review
parent 21b50f6d8d 7142ba7d61
commit 742014d8ea
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/admin/index.rst
View File

@ -1,5 +1,5 @@
Adminstrator's Guide Administrator's Guide
==================== =====================
Installation & Operations Installation & Operations
------------------------- -------------------------

4
magnum/tests/functional/common/models.py
View File

@ -43,7 +43,7 @@ class BaseModel(object):
class EntityModel(BaseModel): class EntityModel(BaseModel):
"""Superclass resposible from converting dict to instance of model""" """Superclass responsible from converting dict to instance of model"""
@classmethod @classmethod
def from_dict(cls, data): def from_dict(cls, data):
@ -55,7 +55,7 @@ class EntityModel(BaseModel):
class CollectionModel(BaseModel): class CollectionModel(BaseModel):
"""Superclass resposible from converting dict to list of models""" """Superclass responsible from converting dict to list of models"""
@classmethod @classmethod
def from_dict(cls, data): def from_dict(cls, data):

2
magnum/tests/unit/conductor/handlers/test_cluster_conductor.py
View File

@ -199,7 +199,7 @@ class TestHandler(db_base.DbTestCase):
# again, this so bad because we have already called it in setUp # again, this so bad because we have already called it in setUp
# since other test case will share the codes in setUp() # since other test case will share the codes in setUp()
# But in self.handler.cluster_create, we update cluster.uuid and # But in self.handler.cluster_create, we update cluster.uuid and
# cluster.stack_id so cluster.create will create a new recored with # cluster.stack_id so cluster.create will create a new record with
# clustermodel_id None, this is bad because we load clusterModel # clustermodel_id None, this is bad because we load clusterModel
# object in cluster object by clustermodel_id. Here update # object in cluster object by clustermodel_id. Here update
# self.cluster.clustermodel_id so cluster.obj_get_changes will get # self.cluster.clustermodel_id so cluster.obj_get_changes will get