openstack
/
fuel-specs
Code Issues Proposed changes

Fix typos in fuel-library-modularization.rst & fuel-with-existed-ldap.rst 

TrivialFix:
"automaticly" should be  "automatically"
"similiar" should be  "similar"

Change-Id: I235e385e0f17db7c2185606dfe0cae162cdeffca
This commit is contained in:
zhangyanxian 2016-12-19 07:48:12 +00:00
parent 2f026c8b24
commit ef7b668bd6
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
specs/6.1/fuel-library-modularization.rst
View File

@ -574,12 +574,12 @@ task during the deployment process and even during production deployment if we
decide to invent a method to run them.
There is olso another popular rspec framework for acceptace testing
https://github.com/puppetlabs/beaker that look similiar to serverspec but is
https://github.com/puppetlabs/beaker that look similar to serverspec but is
more popular in the OpenStack community. It uses either KVM or Docker
environment to test the manifests and includes means to apply tests automaticly
so it’s fit for both local developer testing and centralized CI Gate testing.
Unfortunately, it cannot work with local environments and cannot be used for
production system testing without modifications.
environment to test the manifests and includes means to apply tests
automatically so it’s fit for both local developer testing and centralized
CI Gate testing.Unfortunately, it cannot work with local environments and
cannot be used for production system testing without modifications.

2
specs/6.1/fuel-with-existed-ldap.rst
View File

@ -207,7 +207,7 @@ Documentation Impact
accounts(eg their passwords should nerver expire).
* The documentation should warn user to make sure LDAP/AD read connection
available from openstack keystone service and no futher authorize granted.
available from openstack keystone service and no further authorize granted.
References

2
specs/8.0/openstack-config-change.rst
View File

@ -447,7 +447,7 @@ Acceptance criteria
options after cloud is deployed
* User is provided with interface (CLI + API calls) to modify OpenStack
options before cloud is deployed
* New test cases are executed succesfully
* New test cases are executed successfully
* The testing report is provided
----------