7.2
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- Updated Information
- Using Scenarios
- Using the Goal Navigator
- Introducing vRealize Automation
- Tenancy and User Roles
- Service Catalog
- Infrastructure as a Service
- XaaS Blueprints and Resource Actions
- Common Components
- Life Cycle Extensibility
- vRealize Automation Extensibility Options
- Leveraging Existing and Future Infrastructure
- Configuring Business-Relevant Services
- Extending vRealize Automation with Event-Based Workflows
- Integrating with Third-Party Management Systems
- Adding New IT Services and Creating New Actions
- Calling vRealize Automation Services from External Applications
- Distributed Execution
- Index
Containers User Roles and Access Privileges
You can use container-specic roles to control who can create and congure containers by using options in
the vRealize Automation Containers tab and who can add and congure container components in
blueprints by using options in the Design tab.
When you enable Containers, two container-specic roles appear in the list of roles that a
vRealize Automation tenant administrator can assign to users and groups.
User Role Description
Container
Administrator
Users and groups with this role can see the Containers tab in vRealize Automation. They can use
all theContainers options, such as conguring hosts, placements, and registries. They can also
create templates and provision containers and applications for conguration and validation
purposes.
Container Architect Users and groups with this role can use containers as components when creating and editing
blueprints in vRealize Automation. They have permission to see the Design tab in
vRealize Automation and to work with blueprints.
For information about vRealize Automation administrator and user roles, see User Roles Overview in the
vRealize Automation Information Center.
Tenant administrators can assign one or both of these roles to users or groups in their tenant at any time by
using options on the vRealize Automation Administration tab.
IaaS administrators automatically inherit the container administrator permissions to perform Containers
administrative tasks.
Consumers of catalog items that involve containers inherit the necessary privileges to access the resources
provided by the Containers. They can open and see the details of their container-related items and perform
day-two operations on them.
vRealize Automation users authenticated through VMware Identity Manager (vIDM) have access to
Containers.
vRealize Automation multi-tenancy and business group membership is implemented in Containers.
Service Catalog
The service catalog provides a common interface for consumers of IT services to use to request and manage
the services and resources they need.
Foundations and Concepts
22 VMware, Inc.