a6abc94946
This change modifies the previous names with gender-neutral versions. The filenames, references, pronouns, and in text instances were all changed as well. Change-Id: I3c30704b7b97e7758afbc57cbb32a116b5d04b55 Closes-Bug: #1618130 Signed-off-by: Rodrigo Caballero <rodrigo.caballero.abraham@intel.com>
66 lines
2.6 KiB
ReStructuredText
66 lines
2.6 KiB
ReStructuredText
.. _infrastructure-arch:
|
|
|
|
=================================
|
|
Adrian - infrastructure architect
|
|
=================================
|
|
|
|
Adrian is responsible for the strategy and road-map for his company's cloud
|
|
and identifies reasons to compel management to adopt OpenStack for production
|
|
environments. The reasons that would deter Adrian from recommending OpenStack
|
|
are frequent instabilities, non-deterministic errors, the inability to create
|
|
an environment, and missing documentation. Similarly to the domain operator,
|
|
Adrian needs to know about any outage conditions that may occur on both
|
|
testing and production environments.
|
|
|
|
Key tasks
|
|
~~~~~~~~~
|
|
|
|
Adrian performs the following tasks very frequently:
|
|
|
|
* Decision making: Considers adoption of OpenStack based on financial,
|
|
strategic, architecture, and security advantages.
|
|
|
|
* Hardware configurations: Determines if a hardware configuration
|
|
suits the requirements of a cloud instance and if an OpenStack solution
|
|
running on such hardware is the best possible option.
|
|
|
|
* User experience: Considers application developers, the development
|
|
processes, and the end users when recommending and installing cloud
|
|
instances.
|
|
|
|
* Cloud planing: Defines and plans the cloud while considering hardware,
|
|
platform choices, services, and scale.
|
|
|
|
Key information
|
|
~~~~~~~~~~~~~~~
|
|
|
|
Adrian spends a lot of time reading and researching information about
|
|
OpenStack and other cloud technologies. Adrian has attended more than one
|
|
OpenStack summit and contributes solutions to the community regularly. Adrian
|
|
values OpenStack and is committed to drive adoption. Adrian's priority,
|
|
however, is a fully functional and stable cloud that fulfills all of his
|
|
requirements.
|
|
|
|
The organizational models
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
The tasks that the persona performs within a certain organizational model are
|
|
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
|
|
the cloud instances.
|
|
|
|
Your development
|
|
~~~~~~~~~~~~~~~~
|
|
|
|
Adrian's main concern is the cloud's architecture. Adrian interacts directly
|
|
with OpenStack and has probably developed any pieces that were needed. Your
|
|
development targets Adrian if it makes any changes to the way clouds are
|
|
implemented and deployed. Any new features, fixes, and limitations are
|
|
important to Adrian.
|
|
|
|
If your development modifies the scope, implementation, and usage of
|
|
OpenStack ensure to take Adrian into consideration.
|