Red Hat OpenStack Administration I: Core Operations for Domain Operators
- SectionDescribing OpenStack Personas
- Quiz: Describing OpenStack Personas
- Launching an Instance
- Guided Exercise: Launching an Instance
- Describing Red Hat OpenStack Platform Services
- Guided Exercise: Describing Red Hat OpenStack Platform Services
- Describing a Single-site Overcloud Deployment
- Quiz: Describing a Single-site Overcloud Deployment
- Lab: Introducing Red Hat OpenStack Platform
- Summary
Abstract
| Goal | Describe OpenStack personas, launch an instance, and describe the OpenStack components and architecture. |
| Objectives |
|
| Sections |
|
| Lab |
Introducing Red Hat OpenStack Platform |
After completing this section, you should be able to describe the personas in the cloud ecosystem that characterize the use cases and tasks taught in this course.
Personas are user definitions created to represent user types in OpenStack cloud environments. Personas help you to understand user scenarios and goals by researching trends and use cases with Red Hat OpenStack Platform (RHOSP) organizations. Red Hat uses personas to focus training on relevant user tasks and behavior and not only features and tools.
Ten personas cover the common roles at most organizations using OpenStack. These were identified through OpenStack Foundation and Fedora cloud surveys, research on cloud roles from job boards, industry conferences, and Red Hat Certified Professionals.
Personas are built on information from real RHOSP users. Personas may describe multiple job titles, and your organization's job titles may map to multiple personas. The personas presented here embody the most common roles performed by RHOSP users. Roles may change depending on your organization's size and user ecosystem. This course uses the domain operator persona to define RHOSP operations and use cases.
This course focuses on the roles and responsibilities of the domain operator as the primary persona as shown in SectionFigure 1.1: OpenStack persona ecosystem. The domain operator supports other personas which are referenced in each use case.
Domain operators are responsible for creating projects, assigning user roles, and managing resources and other tasks within their domain. Domain operators use projects and subprojects to securely isolate deployed applications and their resources. Domain operators may delegate project, role, and resource management to project owners or experienced cloud users. Domain operators are typically the first level of support for a domain's cloud users.
The following list describes the OpenStack domain and the responsibilities of the domain operator:
A domain operator's scope is within one or more OpenStack identity service domains.
A domain contains the users, projects, and resources of an organization. OpenStack supports multiple domains in an overcloud, regardless of topology.
Domain operators do not install or configure OpenStack infrastructure. However, they must understand cloud project requirements to accurately manage cloud resources.
Domain operators support cloud users who deploy applications as instances or virtual machine stacks, and must therefore be experienced with deployment configuration and behavior.
Domain operators are subject matter experts on compute, storage, and network resources. They provide guidance on matching scenarios with specific resource attributes.
An OpenStack cloud user deploys applications as virtual machine instances or stacks. Cloud users could be the application developer or maintainer, a project manager who owns the application, or a DevOps engineer who specializes in application deployment, automation, or performance tuning.
Although the types and responsibilities of cloud users are diverse, they all share an ability to perform application deployments. Cloud users assign and configure project resources, and then launch application instances or stacks. Because a domain operator provides resources and support to cloud users, a domain operator must also be proficient in deploying applications.
To provide support, domain operators advise cloud users about OpenStack functionality and available resources. The following are examples of common cloud users that a domain operator could encounter in their organization.
- Application developer
An application developer may be an original coder, maintainer, or other cloud user responsible for the correct deployment and behavior of an application. A domain operator coordinates with the application developer to ensure that sufficient resources are available, quotas are set properly, and that the application and its project are properly secured.
- Project owner
A project owner manages an application project and technical team, in either development or production. The domain operator might delegate management rights for one or more OpenStack projects to the project owner. Project owners typically manage the user and role assignments for their projects.
Because staffing, skills, security, and sizing can vary in various organizations, personas and cloud roles might be implemented differently. Although personas sometimes match individuals, it is common for users to assume multiple roles depending on their workplace responsibilities.
At telecommunications service providers (telcos) and cloud service providers, the prevalent personas are domain and cloud operators, infrastructure architects, and cloud service developers. Other personas are handled by their customers, who obtain support using the provider's service ticketing system.
At a public cloud customer, personas include application developers, project owners, and domain operators, and use a provider's professional services for all other cloud needs.
At organizations requiring a secure, private, dedicated OpenStack infrastructure, such as in banking and finance, all roles are staffed internally. The cloud operator and infrastructure architect personas act as service providers and support all other personas.
At universities and smaller OpenStack implementations, cloud users can potentially assume all roles. The infrastructure architect and the cloud operator personas are commonly handled by a single individual. Similarly, project owner and application developer personas are merged for many students and researchers.
References
