openstack/cinder
Code Issues Proposed changes

Modify some spelling mistakes in cinder

Browse Source 
While I am reading this code, I found some spelling mistakes
in the comments and corrected them here.

Change-Id: If76bac8b763257edb5ebb106a8d4ae74dfa2a710
This commit is contained in:
zhangbailin 2017-08-25 04:15:33 -07:00
parent 7c7b95780a
commit 67a1b5a224
6 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
cinder/image/image_utils.py
View File

@ -408,7 +408,7 @@ def fetch_to_volume_format(context, image_service,
% {'fmt': fmt, 'backing_file': backing_file, }) % {'fmt': fmt, 'backing_file': backing_file, })
# NOTE(e0ne): check for free space in destination directory before # NOTE(e0ne): check for free space in destination directory before
# image convertion. # image conversion.
check_available_space(dest, virt_size, image_id) check_available_space(dest, virt_size, image_id)
# NOTE(jdg): I'm using qemu-img convert to write # NOTE(jdg): I'm using qemu-img convert to write

2
cinder/scheduler/filters/capacity_filter.py
View File

@ -156,7 +156,7 @@ class CapacityFilter(filters.BaseBackendFilter):
"grouping": grouping, "grouping": grouping,
"grouping_name": backend_state.backend_id} "grouping_name": backend_state.backend_id}
LOG.warning("Insufficient free virtual space " LOG.warning("Insufficient free virtual space "
"(%(available)sGB) to accomodate thin " "(%(available)sGB) to accommodate thin "
"provisioned %(size)sGB volume on %(grouping)s" "provisioned %(size)sGB volume on %(grouping)s"
" %(grouping_name)s.", msg_args) " %(grouping_name)s.", msg_args)
return res return res

2
cinder/volume/api.py
View File

@ -1951,7 +1951,7 @@ class API(base.Base):
# FIXME(JDG): We want to be able to do things here like reserve a # FIXME(JDG): We want to be able to do things here like reserve a
# volume for Nova to do BFV WHILE the volume may be in the process of # volume for Nova to do BFV WHILE the volume may be in the process of
# downloading image, we add downloading here; that's easy enough but # downloading image, we add downloading here; that's easy enough but
# we've got a race inbetween with the attaching/detaching that we do # we've got a race between with the attaching/detaching that we do
# locally on the Cinder node. Just come up with an easy way to # locally on the Cinder node. Just come up with an easy way to
# determine if we're attaching to the Cinder host for some work or if # determine if we're attaching to the Cinder host for some work or if
# we're being used by the outside world. # we're being used by the outside world.

2
cinder/volume/drivers/nimble.py
View File

@ -1397,7 +1397,7 @@ class NimbleRestAPIExecutor(object):
filter = {'id': snap_id} filter = {'id': snap_id}
r = self.get_query(api, filter) r = self.get_query(api, filter)
if not r.json()['data']: if not r.json()['data']:
raise NimbleAPIException(_("Snapshot: %s doesnt exist") % snap_id) raise NimbleAPIException(_("Snapshot: %s doesn't exist") % snap_id)
return r.json()['data'][0] return r.json()['data'][0]
@utils.retry(NimbleAPIException, 2, 3) @utils.retry(NimbleAPIException, 2, 3)

2
cinder/volume/drivers/qnap.py
View File

@ -751,7 +751,7 @@ class QnapISCSIDriver(san.SanISCSIDriver):
_metadata = self._get_volume_metadata(new_volume) _metadata = self._get_volume_metadata(new_volume)
# metadata will not be swap after migration wiht liberty version # metadata will not be swap after migration with liberty version
# , and the metadata of new volume is diifferent with the metadata # , and the metadata of new volume is diifferent with the metadata
# of original volume. Therefore, we need to update the migrated volume # of original volume. Therefore, we need to update the migrated volume
if not hasattr(new_volume, '_orig_metadata'): if not hasattr(new_volume, '_orig_metadata'):

4
cinder/volume/manager.py
View File

@ -2149,7 +2149,7 @@ class VolumeManager(manager.CleanableManager,
# NOTE(jdg): Things get a little hairy in here and we do a lot of # NOTE(jdg): Things get a little hairy in here and we do a lot of
# things based on volume previous-status and current-status. At some # things based on volume previous-status and current-status. At some
# point this should all be reworked but for now we need to maintain # point this should all be reworked but for now we need to maintain
# backward compatability and NOT change the API so we're going to try # backward compatibility and NOT change the API so we're going to try
# and make this work best we can # and make this work best we can
LOG.debug("migrate_volume_completion: completing migration for " LOG.debug("migrate_volume_completion: completing migration for "
@ -2266,7 +2266,7 @@ class VolumeManager(manager.CleanableManager,
'vol %(vol)s: %(err)s', 'vol %(vol)s: %(err)s',
{'vol': volume.id, 'err': ex}) {'vol': volume.id, 'err': ex})
# For the new flow this is realy the key part. We just use the # For the new flow this is really the key part. We just use the
# attachments to the worker/destination volumes that we created and # attachments to the worker/destination volumes that we created and
# used for the libvirt migration and we'll just swap their volume_id # used for the libvirt migration and we'll just swap their volume_id
# entries to coorespond with the volume.id swap we did # entries to coorespond with the volume.id swap we did