vCPU and logical CPU sizing with Hyper-Threading explained

When sizing virtual machines you should be aware of the number of physical cores available in your ESXi-host and whether or not it has Hyper-Threading enabled. If you blindly follow the number of vCPU's you can add that VMware presents to you, then you could end up with VM's that offer poor performance. If you want to understand Hyper-Threading and why this is important for sizing please read the articles that I have listed at the bottom of this page.

Tags:

vRealize Orchestrator workflow to find a workflow by it's ID

When you have the ID of a workflow then how do you find out what the name of the workflow is and where it's located. To simplify this search I have created this workflow.

You can download the workflow here.

This is the code of the scripting element that is used for the search:

Using the Switch element in vRealize Orchestrator

vRealize Orchestrator (v6) contains a switch element that can be used to evaluate a series of values. In scripting and programming languages the switch construct is also named Case or Do Case.

For example if we want to check the status of a VM and there are three possible values then we would have to use three if statements or three decision elements to check what the status is.

if status = poweredOn 
if status = poweredOff 
if status = suspended 

vRealize Orchestrator workflow with approvals and timeout

This workflow demonstrates an approval process whre two approvers will have the opportunity to approve or deny a request and when both approvers don't respond within the time limit then the workflow will continue as if it was approved. So this will actively give the two approvers a time window to deny a request after which it is automatically approved. Is designed to use n AD group for approver 1 and another AD group for approver 2.

Follow us on LinkedIn

  

   

   

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer