Requirement Engineering with vRA

One does not simply, bring software developing processes to an infrastructure focused territory In this post I’ve tried to jot down one possible way with a highlevel view to have the activities between new ideas and delivery of new features sorted and organized in a requirement process, priorizied in a release management and developed in… Continue reading Requirement Engineering with vRA

vRA User Interactions hacks

A vRO / vRA “User Interaction” is a nice feature to have request data completed by several peers and / or gathering data which is not known during request time. To some extend this could also be used to approve a step during a provisioning or WF run. If a XaaS Blueprint or Resource Actions… Continue reading vRA User Interactions hacks

Categorized as vRA

Orphaned vRA User Interaction

Under followed circumstances an active vRA Manual User Interaction becomes orphaned. No vRO User Interaction will wait for this input form this point in time and vRA just displays the interaction with no content and no options to cancel, reject or submit this task.Only way to get rid of this orphaned Manual User Interaction described… Continue reading Orphaned vRA User Interaction

Dismiss a vRA XaaS deployment

New introduced in vRA 7.5 there is single view for requests and deployments. This feature brings a lot of advantages. Now there is a possiblity to switch from the request to the deployed machine. This works fine for IaaS Blueprints which deploying components or machines. On a failed request you are even able to to… Continue reading Dismiss a vRA XaaS deployment

vRO automated REST endpoint check

Use vRO action to check all configured REST endpoints in a automated fashion and receive a health state.– gathering information of configured REST endpoints of vRO– checking connectivity by telnet of each REST endpoint– report state by eMail based on return value of check– schedule Workflow for daily automated check and report

How a release pipeline could look like within a small vRA environment

This environment consists: -vRSLCM, 2x vRA minimal Deployment, 2x MSSQL database, 1x external vRO Instance, 1x external vRO instance per developer Consider to have a look at: as well on the vRO Coding-Design Guide:

vRealize Automation EBS Lifecycle States & Events

I tried to visualize in a diagram the vRealize Automation Event Brocker System. More exactly for the Lifecycle States and Events triggered during a Machine Provisioning with Provisioning Workflows: Clone Workflow BasicVMWorkflow VMPSMasterWorkflow32 You can download this diagram here: This diagram was created based on the information in the documentation of vRA 7.5

Categorized as vRA