This begins the catalog of team vision reflection documents by putting a
list of links at the end of the vision document itself; more should
be added as they come.
Change-Id: I1b1c1ad6a7f113a9e4ebc0f24896be56e20a46cb
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
As discussed at the Technical Vision session at the OpenStack Forum
in Berlin, make sure the interoperability guidance in the vision
calls out avoiding leakage of backend implementation details and
configuration choices into the end user experience (particularly
when it comes to altering API methods and their behaviors).
Change-Id: Ib15f7c20b4fc3f85dd90172373175b2b179d492e
Set out a vision for OpenStack clouds that clarifies, in long form, the
meaning of the mission statement at a technical level. Define what we
mean by 'cloud', describe how OpenStack must be different from other
cloud offerings, and list the design goals that we hope the OpenStack
system as a whole will achieve.
Change-Id: Ie988d87365cd2e190f2c6c13ee178f1590e4642d
Hongbin Lu