Users Guide

Scaledown service
This workow scales down the service by removing the selected Service Component (prompted during the workow run). This
workow tracks the status of the target Service, and it completes its run when the service status is no longer in in_progress status.
Scaleup service
There are two sample synchronous scaleup service workows:
• Scaleup service – Server: Scale up the service by adding more server components or resources. This workow tracks the
status of the target Service, and it completes its run when the Service status is no longer in in_progress.
• Scaleup service – Storage: Scale up the service by adding more storage components or resources. This workow tracks the
status of the target Service, and it completes its run when the Service status is no longer in in_progress.
Teardown service
There are two sample synchronous teardown service workows:
• Teardown service – All: Delete the service selected (prompted during the workow run) and remove all its resources. This
workow tracks the existence of the target Service, and it completes its run when the Service no longer exists.
• Teardown service – Selectively: Removes the Service and all its resources selected by their type. This workow tracks the
existence of the target Service, and it completes its run when the Service no longer exists. The SERVER and VIRTUALMACHINE
type components are automatically set for removal.
XaaS
The workows described in this section are designed for the vRA Integration, but they can be run in the vRO as well. They are
benecial for use cases that require single point of input entry. However, the selectable options for this type of workows are read
from the cache unlike the synchronous workows.
NOTE: : Unlike the other types of workows, the XaaS workows do not lter the selectable options. Instead an
inventory window prompting user input is displayed. Ensure that the selected items have relationship with other
selections, that is, you cannot select an ASM:: Service or ASM:Template object if it is not in the target ASM:Appliance.
You must also ensure that the ASM:ServiceComponent is selected from the target ASM: Service.
Deploy Service
This workow allows you to deploy a new service based on the template conguration selected. Inputs such as ASM: Appliance,
ASM: Template, service name, and description to determine the conguration must be entered in the rst stage of the workow run.
This workow tracks the status of the new service, and is complete its run when the service status is no longer displaying as
in_progress.
NOTE: You may change the interval between the status checks—delay and initDelay attributes.
Scaledown service
This workow scales down the service by removing the selected Service Component—which is selected in the rst stage of the
workow run. This workow tracks the status of the target service, and is completes its run when the service status is no longer
displaying as in_progress status.
Scaleup service
There are two sample synchronous scaleup service workows:
• Scaleup service - Server—Scale up the service by adding more server components or resources. This workow tracks the
status of the target service, and is completes its run when the service status is no longer displaying as in_progress.
• Scaleup service - Storage—Scale up the service by adding more Storage components or resources. This workow tracks the
status of the target service, and is completes its run when the service status is no longer displaying as in_progress.
Teardown service
22