Tag: Aria Orchestrator Page 1 of 2

Lately, I was developing an Extensibility Subscription workflow in Orchestrator, which queries the Aria Automation CMX REST API.
While it was perfectly running when being executed manually within Orchestrator, it fails when invoked from Aria Automation Service Broker as part of an Extensibility subscription (here Kubernetes Supervisor Namespace Post Provision).
The resulting error message was:

Catalog Item Deployment NS Test failed for Supervisor Namespace: Extensibility error for topic kubernetes.sv.namespace.provision.post: [10040] SubscriberID: vro-gateway-elsAsEMn7yjjbAGz, RunnableID: 587ed41a-a51b-4cdc-a10d-7c705a57db39 and SubscriptionID: sub_1695305241572 failed with the following error: Workflow run [fd626a0a-0386-4778-b2ad-8e7ffd5f5e9f] completed with error [Error in worker: HTTP error 500 - {"timestamp":"2023-08-20T16:26:45.991+0000","path":"/cmx/api/resources/supervisor-namespaces","status":500,"error":"Internal Server Error","message":"No orgId in token for vro-gateway-elsAsEMn7yjjbAGz","requestId":"f7763022-202212","@type":"java.lang.IllegalStateException"} (Dynamic Script Module name : executeRestCall#11) (Workflow:Kubernetes Supervisor Namespace Post Provision / Control WF (item4)#5)]

Read More

Recently I was tasked to create some kind of instant auto-removal of failed Aria Automation deployments for a given Cloud template.

This can be achieved through leveraging a custom day 2 operation using the Aria Automation Deployment API request controller. For this particular use-case we execute the deployment resource “delete” action.

The required REST call for this resource action is: POST /deployment/api/requests/{requestId}
The JSON body must be specified as follows: { “actionId”: “Deployment.Delete”}

To execute this action every time a deployment fails, we use an Extensibility subscription to be automatically triggered if the status of the deployment is “FAILED” and the event type equals “CREATE_DEPLOYMENT”.

In this example we will use Aria Orchestrator to create the custom action.

Read More

Recently, I was asked by a customer to deploy a custom NSX-T firewalling solution for their virtual machines, where virtual machines owned by an Aria Automation user are allowed to communicate with virtual machines of the same user. The solution leverages NSX-T firewall rules based on groups, where the group membership is defined based on NSX-T tags attached to a virtual machine.

To achieve the custom tagging of virtual machines in NSX-T during the VM deployment phase in Aria Automation, I developed a Orchestrator workflow leveraging the capabilities of the NSX-T API.

In this blog post, I’ll demonstrate how to use the NSX-T API from Orchestrator.

Read More

vRealize Automation provides pre-defined application and services life cycles operations which require customizing this life cycle via extensibility. This lifecycle extensibility is applied through the Event Broker Service (EBS).

vRealize Automation 8.x provisioning event topics are designed with a set of high level topics calling deployment resources topics. Event topics trigger when particular events occur in vRealize automation; examples are:

• When a cloud template is deployed
• When the resources in a deployment are allocated
• During a life cycle state and entity change
• When an approval policy is triggered
• When Day-2 operations are requested

The following event topics are defined in vRA for the provision lifecycle phase (image taken from the official VMware documentation):

In this example we’re going to have a more detailed look on the lifecycle of a virtual machine during the provisioning.

Read More