Difference between revisions of "OpenStack Personas 2015"
| Line 1: | Line 1: | ||
| − | + | ==INTRODUCTION== | |
| + | Below are the outcomes from the 2015 OpenStack Persona Workshop hosted at IBM Design's Austin studio. We have identified stages a company needs to go through in adopting cloud technologies; five cloud roles (or persona prototypes) that are most relevant to OpenStack; and how does these cloud roles fit into a cloud ecosystem. | ||
| + | |||
| + | As a community member for OpenStack, it's highly likely that you will resonate with one or more of these cloud roles. In order to finalize these cloud roles into personas that accurately represent OpenStack users, we would love your help! | ||
| + | |||
| + | We'd like you to scan through all the five cloud roles we identified, find the one(s) that you resonate the most, and fill out the related survey(s). But before you jump right into these roles, we'd encourage you to take a closer look at the Cloud Adoption Stages and the Cloud EcoSystem. | ||
| + | |||
| + | Thank you! | ||
| + | |||
| + | - OpenStack UX Project Team | ||
===CLOUD ADOPTION STAGE=== | ===CLOUD ADOPTION STAGE=== | ||
| Line 19: | Line 28: | ||
| USE || End-user consumption of the OpenStack cloud services. | | USE || End-user consumption of the OpenStack cloud services. | ||
|} | |} | ||
| + | |||
| + | ===Cloud Roles=== | ||
| + | [[# Infrastructure Architect ]] | ||
| + | |||
| + | |||
===CLOUD ECOSYSTEM=== | ===CLOUD ECOSYSTEM=== | ||
[[File:CloudEcoSystem.png|1000px|thumb|left|Cloud Eco System]] | [[File:CloudEcoSystem.png|1000px|thumb|left|Cloud Eco System]] | ||
| − | === | + | == Persona Prototypes == |
| + | |||
| + | <div id="InfraArchitect"></div> | ||
| + | |||
| + | === Infrastructure Architect === | ||
<blockquote>“I make sure the cloud is up and running and try to get things running again ASAP”</blockquote> | <blockquote>“I make sure the cloud is up and running and try to get things running again ASAP”</blockquote> | ||
Revision as of 17:26, 11 November 2015
Contents
INTRODUCTION
Below are the outcomes from the 2015 OpenStack Persona Workshop hosted at IBM Design's Austin studio. We have identified stages a company needs to go through in adopting cloud technologies; five cloud roles (or persona prototypes) that are most relevant to OpenStack; and how does these cloud roles fit into a cloud ecosystem.
As a community member for OpenStack, it's highly likely that you will resonate with one or more of these cloud roles. In order to finalize these cloud roles into personas that accurately represent OpenStack users, we would love your help!
We'd like you to scan through all the five cloud roles we identified, find the one(s) that you resonate the most, and fill out the related survey(s). But before you jump right into these roles, we'd encourage you to take a closer look at the Cloud Adoption Stages and the Cloud EcoSystem.
Thank you!
- OpenStack UX Project Team
CLOUD ADOPTION STAGE
| Stage | Description |
|---|---|
| DECIDE | Decision-making about adopting cloud and/or managed services while considering strategic,financial, architecture, security, applications, process, and users. |
| DEFINE | Define and plan the OpenStack cloud while considering hardware, compute, storage, network, infrastructure and platform choices, services, along with scale. |
| INSTALL | Install and configure the OpenStack cloud. |
| OPERATE | Day-to-day operation and administration of the OpenStack cloud including backup, disaster recovery, managing the infrastructure and platform services offered by the OpenStack cloud. |
| UPDATE | Perform updates and post-update verification to the OpenStack cloud. |
| USE | End-user consumption of the OpenStack cloud services. |
Cloud Roles
CLOUD ECOSYSTEM
Persona Prototypes
Infrastructure Architect
“I make sure the cloud is up and running and try to get things running again ASAP”
HIGH LEVEL TASKS/RESPONSIBILITIES
- New Services/Configuration
- Troubleshoot Issues from Cloud Ops (L3, L4)
- Producing KPIs
- Report Issues to Community/Vendor
CLOUD ADOPTION STAGE
| DECIDE | DEFINE | INSTALL | OPERATE | UPDATE | USE |
|---|---|---|---|---|---|
| Decision-making about adopting cloud and/or managed services while considering strategic,financial, architecture, security, applications, process, and users. | Define and plan the OpenStack cloud while considering hardware, compute, storage, network, infrastructure and platform choices, services, along with scale. | Install and configure the OpenStack cloud. | Day-to-day operation and administration of the OpenStack cloud including backup, disaster recovery, managing the infrastructure and platform services offered by the OpenStack cloud. | Perform updates and post-update verification to the OpenStack cloud. | End-user consumption of the OpenStack cloud services. |
| Example | Example | Example | Example | Example | Example |
| Example | Example | Example | Example | Example | Example |
