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
n
Containers Overview on page 11
You can use containers to gain access to additional instrumentation for developing and deploying
applications in vRealize Automation.
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 specication 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 conguration and extensibility features also make IaaS
a highly exible means of customizing machine congurations and integrating machine provisioning and
management with other enterprise-critical systems such as load balancers, conguration management
databases (CMDBs), ticketing systems, IP address management systems, or Domain Name System (DNS)
servers.
Software Components Overview
Software components automate the installation, conguration, and life cycle management of middleware
and application deployments in dynamic cloud environments. Applications can range from simple Web
applications to complex and even packaged applications.
By using a congurable scriptable engine, software architects fully control how middleware and application
deployment components are installed, congured, updated, and uninstalled on machines. Through the use
of Software properties, software architects can require or allow blueprint architects and end-users to specify
conguration elements such as environment variables. For repeated deployments, these blueprints
standardize the structure of the application, including machine blueprints, software components,
dependencies, and congurations, but can allow environment variables and property binding to be
recongured if necessary.
Deploying Any Application and Middleware Service
You can deploy Software components on Windows or Linux operating systems on vSphere,
vCloud Director, vCloud Air, and Amazon AWS machines.
n
IaaS architects create reusable machine blueprints based on templates, snapshots, or Amazon machine
images that contain the guest agent and Software bootstrap agent to support Software components.
n
Software architects create reusable software components that specify exactly how the software is
installed, congured, updated during deployment scale operations, and uninstalled on machines.
n
Software architects, IaaS architects, and application architects use a graphical interface to model
application deployment topologies. Architects recongure Software properties and bindings as
required by the software architect, and publish application blueprints that combine Software
components and machine blueprints.
n
Catalog administrators add the published blueprints to a catalog service, and entitle users to request the
catalog item.
n
Entitled users request the catalog item and provide any conguration values designed to be editable.
vRealize Automation deploys the requested application, provisioning any machine(s), networking and
security components, and Software component(s) dened in the application blueprint.
n
Entitled users request the scale in or scale out actions to adjust their deployments to changing workload
demands. vRealize Automation installs or uninstalls Software components on machines for scale, and
runs update scripts for dependent Software components.
Foundations and Concepts
VMware, Inc. 9