Difference between revisions of "OpenStack Personas 2015"
(→CLOUD ECOSYSTEM) |
(→CLOUD ECOSYSTEM) |
||
Line 4: | Line 4: | ||
===CLOUD ECOSYSTEM=== | ===CLOUD ECOSYSTEM=== | ||
− | [[File:Https://wiki.openstack.org/w/images/ | + | [[File:Https://wiki.openstack.org/w/images/3/3e/CloudEcoSystem.png|frameless]] |
=== INFRASTRUCTURE ARCHITECT === | === INFRASTRUCTURE ARCHITECT === |
Revision as of 22:59, 10 November 2015
Contents
INTRODUCTION
CLOUD ADOPTION STAGE
CLOUD ECOSYSTEM
File:Https://wiki.openstack.org/w/images/3/3e/CloudEcoSystem.png
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 |