7.1
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
- Index
Scale Up or Scale Down By Using Reconfigure
After you provision a vSphere, vCloud Air, or vCloud Director virtual or cloud machine you can adjust to
changing workload demands by requesting a machine recongure to increase (scale up) or decrease (scale
down) machine resource specications for CPU, memory, storage, or networks. You can also add, edit, or
remove custom properties and change descriptions. You can request to recongure machines that are in the
On or O state.
When you recongure a virtual or cloud machine for scale up, vRealize Automation allocates the requested
resources on the current reservation before proceeding. If the resources are not available, the machine
recongure fails. If a machine recongure request fails, any resources allocated for scale up are deallocated
and available for new requests. When you recongure a virtual or cloud machine for scale down, resources
are not made available to new requests unless the recongure nishes successfully.
Table 10. Required Entitlements for Machine Reconfigure Scenarios ( vSphere , vCloud Air , and
vCloud Director only)
Virtual or Cloud Machine Owner wants to... Required Entitlements
Run the recongure immediately after any required
approvals are given.
Recongure
Specify a date and time to run the reconguration. Recongure
Reschedule a recongure because the request was not
approved until after the scheduled time.
Recongure
Retry a failed recongure request. Execute recongure
Cancel a failed recongure request. Cancel recongure
Cancel a scheduled recongure request. Cancel recongure
XaaS Blueprints and Resource Actions
XaaS architects can use the XaaS options to create blueprints and publish them to the service catalog. They
can also create and publish post-provisioning operations that the consumers can perform on provisioned
items.
Creating XaaS Blueprints and Actions
By using the XaaS blueprints and resource actions, you dene new provisioning, request, or action oerings
and publish them to the common catalog as catalog items.
You can create XaaS blueprints and actions for either requesting or provisioning. The XaaS blueprints for
requesting do not provision items and provide no options for post-provisioning operations. Examples of
XaaS blueprints for requesting include blueprints for sending emails, generating reports, performing
complex calculations, and so on. For an XaaS blueprint, the result is a provisioned item. You can create a
custom resource so that you can access and manage the items on the Items tab.
To dene the XaaS specication, you create a blueprint and publish it as a catalog item. After you publish a
catalog item, you must include it in a service category. You can use an existing service or create one. A
tenant administrator or business group manager can entitle the whole service or only the catalog item to
specic users.
If you created a custom resource for a provisioned item, you can create resource actions to dene the post-
provisioning operations that the consumers can perform. You can also create resource actions for an item
that is provisioned by a source dierent from the XaaS blueprints, for example by IaaS. For this purpose,
rst you must create a resource mapping to dene the type of the catalog item.
Foundations and Concepts
VMware, Inc. 31