Cloud Vision: clarify meaning of design goals
Feedback on this section from a couple of different sources reveals that the current description fails to make clear that the design goals represent capabilities that we want OpenStack to present to applications, and aren't necessarily descriptive of the OpenStack service implementations themselves. Tweak the wording to help readers interpret the goals in the correct context. Change-Id: I5e2fe12dca016f0e9039cdf4290060ed51bc10ce
This commit is contained in:
parent
b4041d896b
commit
d765da632c
|
@ -174,11 +174,12 @@ to avoid ascribing physical meanings to the groupings.
|
|||
Design Goals
|
||||
============
|
||||
|
||||
The following are design goals that we would like to see the OpenStack services
|
||||
as a whole fulfil. It is not expected that every service or feature would (or
|
||||
even could) conform to every category listed. Rather, any service that
|
||||
contributes to achieving one or more of the objectives below is likely to help
|
||||
further the mission of the OpenStack project.
|
||||
The following design goals represent the capabilities that we would like to see
|
||||
the OpenStack services as a whole provide to applications and users. It is not
|
||||
expected that every service or feature would (or even could) bear on every
|
||||
objective listed. Rather, any service that contributes to achieving one or more
|
||||
of the objectives below is likely to help further the mission of the OpenStack
|
||||
project.
|
||||
|
||||
Basic Physical Data Center Management
|
||||
-------------------------------------
|
||||
|
|
Loading…
Reference in New Issue