openstack/openstack-manuals
Code Issues Proposed changes

Clarify "Limit cloud feature set" para in Methodology

Browse Source 
Rework paragraph to avoid duplicate phrase
"recreate the entire OpenStack tool suite" contained in the
"Limit Cloud Feature Set" section in Methodology.

Change-Id: I706b6b09ca1c98fa542a22eefdb577c222a6f186
Closes-Bug: #1398335
This commit is contained in:
Diego de Lima Pereira
2015-02-02 16:54:43 -03:00
committed by Andreas Jaeger
parent 89d46d7e7e
commit 65100ee65c
1 changed files with 8 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
doc/arch-design/introduction/section_methodology.xml
View File

@@ -103,15 +103,14 @@
<formalpara>
<title>Limit cloud feature set</title>
<para>
Create requirements that address the pain points, but do not
recreate the entire OpenStack tool suite. The requirement to
build OpenStack, only better, is self-defeating. It is
important to limit scope creep by concentrating on developing
a platform that will address tool limitations for the
requirements, but not recreating the entire suite of
tools. Work with technical product owners to establish
critical features that are needed for a successful cloud
deployment.
Create requirements that address the pain points but keep the
core design of OpenStack. The requirement to build OpenStack,
only better, is self-defeating. It is important to limit scope
creep by concentrating on developing a platform that will
address tool limitations for the requirements, but not
recreating the entire suite of tools. Work with technical
product owners to establish critical features that are needed
for a successful cloud deployment.
</para>
</formalpara>
<section xml:id="application-cloud-readiness-methods">