7.3
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- Updated Information
- Foundations and Concepts
- 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
You can create and publish blueprints for a single machine deployment, or a single custom XaaS
resource, but you can also combine machine blueprints and XaaS blueprints with other building blocks to
design elaborate application blueprints that include multiple machines, networking and security, software
with full life cycle support, and custom XaaS functionality. You can also control deployment settings by
using a parameterized blueprint, which allows you to specify pre-configured size and image settings at
request time. Because all published blueprints and blueprint components are reusable, you can create a
library of these components and combine them in new nested blueprints to deliver increasingly complex
on-demand services.
Published blueprints become catalog items that your service catalog administrators can deliver to your
users. The service catalog provides a unified self-service portal for consuming IT services. Service
catalog administrators can manage user access to catalog services, items, and actions by using
entitlements and approvals, and users can browse the catalog to request items they need, track their
requests, and manage their provisioned items.
Foundations and Concepts
VMware, Inc. 9