Skip to content
Snippets Groups Projects
Commit bb6a2a44 authored by Hironori Shiina's avatar Hironori Shiina
Browse files

Fix typos in developer documentation

Fix 4 typos in documentation 'Customize an OpenStack Deployment'.

Change-Id: I9da8e44e8281fef18a7a5e86f10464a296aa2d49
parent a48fb29f
No related branches found
No related tags found
No related merge requests found
......@@ -49,7 +49,7 @@ documentation is extremely mature and well-formulated.
As an example, consider running Kolla in a virtual machine. In order to
launch virtual machines from Nova in a virtual environment, it is necessary
to use the QEMU hypervisor, rather then the KVM hypervisor. To achieve this
to use the QEMU hypervisor, rather than the KVM hypervisor. To achieve this
result, simply modify the file `/etc/kolla/config/nova/nova-compute.conf` and
add the contents::
......@@ -57,14 +57,14 @@ add the contents::
virt_type=qemu
After this change Kolla will use an emulated hypervisor with lower performance.
Kolla could have templated this commonly modified configuraiton option. If
Kolla could have templated this commonly modified configuration option. If
Kolla starts down this path, the Kolla project could end with hundreds of
config options all of which would have to be subjectively evaluated for
inclusion or exclusion in the source tree.
Kolla's approach yields a solution which enables complete customization without
any upstream mainteance burden. Operators don't have to rely on a subjective
any upstream maintenance burden. Operators don't have to rely on a subjective
approval process for configuration options nor rely on a
developement/test/release cycle to obtain a desired customization. Instead
development/test/release cycle to obtain a desired customization. Instead
operators have ultimate freedom to make desired deployment choices immediately
without the approval of a third party.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment