7.0
Table Of Contents
- Foundations and Concepts
- Contents
- 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
n
Service Catalog Overview
The service catalog provides a unified self-service portal for consuming IT services. Users can
browse the catalog to request items they need, track their requests, and manage their provisioned
items.
Infrastructure as a Service Overview
With Infrastructure as a Service (IaaS), you can rapidly model and provision servers and desktops across
virtual and physical, private and public, or hybrid cloud infrastructures.
Modeling is accomplished by creating a machine blueprint, which is a specification for a machine.
Blueprints are published as catalog items in the common service catalog, and are available for reuse as
components inside of application blueprints. When an entitled user requests a machine based on one of
these blueprints, IaaS provisions the machine.
With IaaS, you can manage the machine life cycle from a user request and administrative approval
through decommissioning and resource reclamation. Built-in configuration and extensibility features also
make IaaS a highly flexible means of customizing machine configurations and integrating machine
provisioning and management with other enterprise-critical systems such as load balancers, configuration
management databases (CMDBs), ticketing systems, IP address management systems, or Domain Name
System (DNS) servers.
Software Components Overview
Software automates the installation, configuration, and life cycle management of middleware and
application deployment components such as Oracle, MySQL, WAR, and DB Schemas.
Enterprise users can standardize, deploy, configure, update, and uninstall complex applications in
dynamic cloud environments. These applications can range from simple Web applications to complex
custom applications and packaged applications. Artifact management supports the use of logical names
for build files and other types of software artifacts, allowing users to deploy applications without regard for
the physical location or identifier of such files.
Software architects create reusable Software components, and IaaS architects create reusable machine
blueprints. Software and Application architects can use the drag-and-drop interface to create visual
application blueprints that combine Software components with vSphere, vCloud Air, or Amazon AWS
machine blueprints, and can bind Software properties to other properties in the application blueprint.
By using a configurable scriptable engine, software architect fully control how middleware and application
deployment components are installed, configured, and uninstalled on machines. Through the use of
Software properties, software architects can require or allow blueprint architects and end-users to specify
configuration elements such as environment variables. For repeated deployments, these blueprints
standardize the structure of the application, including machine blueprints, software components,
dependencies, and configurations, but can allow environment variables and property binding to be
reconfigured if necessary.
Foundations and Concepts
VMware, Inc. 9