Jump to: navigation, search

OpenStack Personas 2015

Revision as of 19:36, 17 November 2015 by Stan Li (talk | contribs)

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

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.


Cloud EcoSystem

Cloud Eco System


Cloud Roles

Below is a list of existing cloud roles we have identified from the persona workshop, you can find their

#Infrastructure Architect

Service Admin

#Cloud Ops

#Domain Ops

#Dev Ops