From 08d463d220cdd09778563e2da1a85708f3442d6a Mon Sep 17 00:00:00 2001 From: venkatamahesh Date: Thu, 4 Feb 2016 09:19:56 +0530 Subject: [PATCH] Fix misspellings Change-Id: I7f250d89efb204dc3e232e1e10c0382deb04eec8 --- doc/source/examples.rst | 2 +- doc/source/orchestration/entities.rst | 2 +- doc/source/resource.rst | 3 ++- solar/cli/resource.py | 2 +- solar/core/handlers/puppet.py | 2 +- solar/dblayer/locking.py | 2 +- utils/jenkins/README.md | 2 +- 7 files changed, 8 insertions(+), 7 deletions(-) diff --git a/doc/source/examples.rst b/doc/source/examples.rst index 19fe95fe..0615e0dc 100644 --- a/doc/source/examples.rst +++ b/doc/source/examples.rst @@ -116,7 +116,7 @@ Step 7: Think of the deployment composition +++++++++++++++++++++++++++++++++++++++++++ The deployment composition is which resources should be used and in which order -it should be executed to achive the expected result, which is a successfull +it should be executed to achieve the expected result, which is a successful :ref:`deploy-plan-term`. For the given example, the composition may be as following: diff --git a/doc/source/orchestration/entities.rst b/doc/source/orchestration/entities.rst index 18819e41..57ef0b23 100644 --- a/doc/source/orchestration/entities.rst +++ b/doc/source/orchestration/entities.rst @@ -37,7 +37,7 @@ Subscriptions Each public method of worker is subscribable, in current version 4 events are available to subscribers. -on_sucess +on_success Called in the case of successful execution, provides context, result and event arguments on_error diff --git a/doc/source/resource.rst b/doc/source/resource.rst index 93eebbf1..3b740451 100644 --- a/doc/source/resource.rst +++ b/doc/source/resource.rst @@ -113,7 +113,8 @@ has (connections etc), but you can set a function that will return final input value. .. note:: - Remeber, that you need to connect inputs to have it accessible in + + Remember, that you need to connect inputs to have it accessible in Computable Inputs logic. Currently you can write the functions using: diff --git a/solar/cli/resource.py b/solar/cli/resource.py index 824fc612..76fe49c0 100644 --- a/solar/cli/resource.py +++ b/solar/cli/resource.py @@ -200,7 +200,7 @@ def remove(name, tag, f): if f: msg = 'Resource %s removed from database' % res.name else: - msg = 'Resource %s will be removed after commiting changes.' % res.name # NOQA + msg = 'Resource %s will be removed after committing changes.' % res.name # NOQA click.echo(msg) diff --git a/solar/core/handlers/puppet.py b/solar/core/handlers/puppet.py index 611ad7b6..aec53ec2 100644 --- a/solar/core/handlers/puppet.py +++ b/solar/core/handlers/puppet.py @@ -59,7 +59,7 @@ class Puppet(TempFileHandler): ) rc, out, err = res.return_code, res.stdout, res.stderr log.debug('CMD %r RC %s OUT %s ERR %s', cmd_args, rc, out, err) - # 0 - no changes, 2 - successfull changes + # 0 - no changes, 2 - successful changes if rc not in [0, 2]: raise errors.SolarError( 'Puppet for {} failed with RC {}'.format( diff --git a/solar/dblayer/locking.py b/solar/dblayer/locking.py index 1e914bcf..2dbf9657 100644 --- a/solar/dblayer/locking.py +++ b/solar/dblayer/locking.py @@ -182,7 +182,7 @@ class RiakEnsembleLock(_Lock): lk.save(force=True) return lk except RiakError as exc: - # TODO object shouldnt be cached before successfull save + # TODO object shouldnt be cached before successful save del DBLock._c.obj_cache[lk.key] # check documentation for error message # http://docs.basho.com/riak/latest/dev/advanced/strong-consistency/#Error-Messages diff --git a/utils/jenkins/README.md b/utils/jenkins/README.md index 50c4505b..7fbdcd46 100644 --- a/utils/jenkins/README.md +++ b/utils/jenkins/README.md @@ -1,7 +1,7 @@ Examples testing ================ -To automaticly test examples install first fuel-devops framework. Installation process is described here https://github.com/openstack/fuel-devops. After installation run migrations scripts: +To automatically test examples install first fuel-devops framework. Installation process is described here https://github.com/openstack/fuel-devops. After installation run migrations scripts: ```bash export DJANGO_SETTINGS_MODULE=devops.settings