Merge "Fix typos in persona descriptions."

This commit is contained in:
Jenkins 2016-11-14 23:32:39 +00:00 committed by Gerrit Code Review
commit 23fd3fc4b9
2 changed files with 21 additions and 21 deletions

View File

@ -21,7 +21,7 @@ Rey performs the following tasks very frequently:
including backup, disaster recovery, and platform services.
* Usage tracking: Tracks the use that App Developers, Project Owners, and
Domain operators make of the cloud and optimizes the services accordingly.
Domain Operators make of the cloud and optimizes the services accordingly.
* Update: Performs updates and verification of the OpenStack cloud.
@ -75,30 +75,30 @@ and updating the OpenStack cloud. The following pain point examples
highlight the cases where progress can be impeded. This enables you to
anticipate and compensate when preparing a project:
Rey has trouble finding information to help triage issues that can
prevent the cloud from running:
* Rey has trouble finding information to help triage issues that can
prevent the cloud from running:
"New users do not have the flexibility to spend weeks delving into
source code to figure out how to do common tasks, especially in the
areas of orchestration. Were it not for `ask.openstack.org <https://ask.openstack.org/en/questions/>`_
and the hard work of many bloggers in the community, I would have a
significantly more difficult time trying to understand practical
uses of OpenStack functionality."
"New users do not have the flexibility to spend weeks delving into
source code to figure out how to do common tasks, especially in the
areas of orchestration. Were it not for `ask.openstack.org <https://ask.openstack.org/en/questions/>`_
and the hard work of many bloggers in the community, I would have a
significantly more difficult time trying to understand practical
uses of OpenStack functionality."
Consistency between projects slows down progress:
* Inconsistency between projects slows down progress:
"All projects should strive to use the same standards—in code,
libraries used, file formats, and documentation. [We need] consistency
between different OpenStack projects and releases."
"All projects should strive to use the same standards—in code,
libraries used, file formats, and documentation. [We need] consistency
between different OpenStack projects and releases."
"It really boils down to having OpenStack act more like a single
initiative, versus a collection of projects."
"It really boils down to having OpenStack act more like a single
initiative, versus a collection of projects."
Building a community that listens and takes on feedback is also a goal:
* Building a community that listens and takes on feedback is also a goal:
"Theres still a bit of a gap between developers and operators.
Although that is narrowing, understanding operators pains in
certain areas is key in developing a better product as a whole."
"Theres still a bit of a gap between developers and operators.
Although that is narrowing, understanding operators pains in
certain areas is key in developing a better product as a whole."
The scale of quotas presents significant obstacles for operators. Consider
that Rey may need to manage over one thousand projects in a deployment.

View File

@ -28,7 +28,7 @@ Adrian performs the following tasks very frequently:
processes, and the end users when recommending and installing cloud
instances.
* Cloud planing: Defines and plans the cloud while considering hardware,
* Cloud planning: Defines and plans the cloud while considering hardware,
platform choices, services, and scale.
Key information
@ -49,7 +49,7 @@ important for the usability of your OpenStack development. Within a small
organization, such as Rifkom or Nikishi University, Adrian might be required
to assume some roles and responsibilities of a Cloud Operator or, more
rarely, a Domain Operator. Within a larger organization, like CNBB
Securities, Adrian's tasks are performed by the team planing and implementing
Securities, Adrian's tasks are performed by the team planning and implementing
the cloud instances.
Your development