Basic Math in an Aria Automation Cloud Template

I was helping someone with a small challenge in their Aria Automation Cloud template and had to dig to find the solution.  They didn’t find any examples through a search, and neither did I –  so I thought I would share.   The goal was to do basic math (addition) in the YAML of the Cloud Template.

The use case was a cloud template adding multiple disks in a virtual machine.  They had a need to control the name of the VMDK differently than was specified in the Project Custom Naming template.    They were using an array of disks in the Cloud Template and the index of that array to make the VMDK name unique (The second disk for the vm should be called mytestvm_disk2.vmdk).

As most arrays in computing are, the index was zero-based (the second disk was called mytestvm_disk1.vmdk). While this would provide a unique name for each disk, the preference was to start with 1 to make it easier on the large number of admins who manage workloads in the environment.  They tried various ways of formatting the YAML to get the addition correct; but could not find a way that worked as expected.

I cannot share the code that this customer wrote; but have worked up a simple example to illustrate.   The use case this code sample represents is not something you would normally do; but will serve to highlight the syntax to allow some basic math in an Aria Automation Cloud Template.

Continue reading “Basic Math in an Aria Automation Cloud Template”

Importing vSphere Networks into Aria Automation – Part 4 – Update Network Profiles

If you are standing up a new Aria Automation environment and have a large number of vSphere Networks (aka Port Groups), it could take a very long time to Aria Automationenter this information manually.  I have written a few scripts that can make Importing vSphere networks into Aria Automation fairly easy!

This blog article is the last in a 4-part series that discusses how you can update the Network Profiles configured in Aria Automation.  Before an Aria Automation Network Profile can be associated with the vSphere Networks in an environment, both the Network and IP Range definitions must be updated.

Blog Series Overview –  Importing vSphere Networks into Aria Automation

  1. Export Networks with Missing IP Info – This will export a file that can be used to determine which networks need updated.  This will be the basis for the other 3 sections as an input file to target updates.  This file will need updated with the pertinent IP information.
  2. Update Network IP Info  – This script will use the file created in step 1 to update the IP Information for vSphere networks discovered by Aria Automation
  3. Update IP Ranges – This script will use the file created in step 1 and define IP Ranges for the subnets used by the discovered vSphere Networks.  This must be completed after the networks have updated IP Information
  4. Update Network Profiles – The final step is to take the results from the prior 3 steps and create Network Profiles that can be used by Aria Automation for workload deployment

Update Network Profiles

Now that the networks all have valid IP Information and the IP ranges defined, we can complete the task and update the existing Network Profiles in Aria Automation so workloads can be deployed!    The Network Profile definitions are located in Cloud Assembly, under Infrastructure -> Configure -> Network Profiles.

The environment this script was written for has 1 Network Profile for each Cloud Account (named after the vCenter it represents).  Each Network Profile will have all of the networks for that vCenter.

Continue reading “Importing vSphere Networks into Aria Automation – Part 4 – Update Network Profiles”

Importing vSphere Networks into Aria Automation – Part 3 – Update IP Ranges

If you are standing up a new Aria Automation environment and have a large number of vSphere Networks (aka Port Groups), it could take a very long time to enter this information manually.  I have written a few scripts that can make Importing vSphere Aria Automationnetworks into Aria Automation fairly easy!

This blog article is the 3rd in a 4-part series that discusses how you can update the IP Ranges configured in Aria Automation.  Before an Aria Automation Network Profile can be associated with the vSphere Networks in an environment, both the Network and IP Range definitions must be updated.

Blog Series Overview –  Importing vSphere Networks into Aria Automation

  1. Export Networks with Missing IP Info – This will export a file that can be used to determine which networks need updated.  This will be the basis for the other 3 sections as an input file to target updates.  This file will need updated with the pertinent IP information.
  2. Update Network IP Info  – This script will use the file created in step 1 to update the IP Information for vSphere networks discovered by Aria Automation
  3. Update IP Ranges – This script will use the file created in step 1 and define IP Ranges for the subnets used by the discovered vSphere Networks.  This must be completed after the networks have updated IP Information
  4. Update Network Profiles – The final step is to take the results from the prior 3 steps and create Network Profiles that can be used by Aria Automation for workload deployment

Update IP Ranges

Once the Aria Automation Network definitions have accurate IP Information for the networks in vSphere, IP Ranges need to be created/updated.  This allows Aria Automation or an external IPAM provider to manage IPs on that network. You can find these definitions in Cloud Assembly, under Infrastructure -> Resources -> Networks -> IP Ranges.

Continue reading “Importing vSphere Networks into Aria Automation – Part 3 – Update IP Ranges”

Importing vSphere Networks into Aria Automation – Part 2 – Update Network IP Info

If you are standing up a new Aria Automation environment and have a large number of vSphere Networks (aka Port Groups), it could take a very long time to enter thisAria Automation information manually.  I have written a few scripts that can make Importing vSphere networks into Aria Automation fairly easy!

This blog article is the 2nd in a 4-part series that discusses how you can update Network IP Information for vSphere networks discovered by Aria Automation.  While Aria Automation will discover vSphere Port Groups for any vCenters added into a Cloud Account, it does not automatically fill out the various details about the IP Configuration.

Blog Series Overview –  Importing vSphere Networks into Aria Automation

  1. Export Networks with Missing IP Info – This will export a file that can be used to determine which networks need updated.  This will be the basis for the other 3 sections as an input file to target updates.  This file will need updated with the pertinent IP information.
  2. Update Network IP Info  – This script will use the file created in step 1 to update the IP Information for vSphere networks discovered by Aria Automation
  3. Update IP Ranges – This script will use the file created in step 1 and define IP Ranges for the subnets used by the discovered vSphere Networks
  4. Update Network Profiles – The final step is to take the results from the prior 3 steps and create Network Profiles that can be used by Aria Automation for workload deployment

Update Network IP Info

Aria Automation will discover vSphere Port Groups that exist in any Cloud Accounts that have been configured.  The next step is to fill out the details for those various Networks:

  • Default Gateway
  • CIDR
  • DNS Servers
  • Search Domains
  • Domain

Continue reading “Importing vSphere Networks into Aria Automation – Part 2 – Update Network IP Info”

Importing vSphere Networks into Aria Automation – Part 1 – Export Networks with Missing IP Info

If you are standing up a new Aria Automation environment and have a large number of vSphere Networks (aka Port Groups), it could take a very long time to enter this information manually.  I have written a few scripts that can make Importing vSphere networks into Aria AutomationAria Automation fairly easy!

This blog article is the 1st in a 4-part series that discusses how you can import vSphere Networks into Aria Automation.  The environment these scripts were written for has multiple vCenter Server instances – each with multiple clusters.   The network infrastructure is using Layer 2 stretched VLANs.  As a result the same VLAN can exist in multiple locations.  The vSphere Port Groups are all named the same, and have the same characteristics.

Blog Series Overview –  Importing vSphere Networks into Aria Automation

  1. Export Networks with Missing IP Info – This will export a file that can be used to determine which networks need updated.  This will be the basis for the other 3 sections as an input file to target updates.  This file will need updated with the pertinent IP information.
  2. Update Network IP Info – This script will use the file created in step 1 to update the IP Information for vSphere networks discovered by Aria Automation
  3. Update IP Ranges – This script will use the file created in step 1 and define IP Ranges for the subnets used by the discovered vSphere Networks
  4. Update Network Profiles – The final step is to take the results from the prior 3 steps and create Network Profiles that can be used by Aria Automation for workload deployment

Export Networks with Missing IP Info

Aria Automation will discover vSphere Port Groups that exist in any Cloud Accounts that have been configured.  This will create definitions in Infrastructure -> Resources -> Networks -> Networks; but does not necessarily populate the necessary IP Information.

Aria Automation - vSphere Network missing IP Info

 

 

 

 

 

 

In order to deploy workloads to these environments using Aria Automation, a Network Profile needs to be created.  This profile requires Network IP Information and IP Ranges to be defined for each vSphere Network.

Continue reading “Importing vSphere Networks into Aria Automation – Part 1 – Export Networks with Missing IP Info”

vToolbelt – October 2023

End of Technical Guidance for vSphere 6.5 and 6.7

These two versions of vSphere have served us well; but on November 15, 2023, all technical support for vSphere 6.5 and 6.7 will end as the products leave Technical Guidance. If you are still running these versions please upgrade now. If you have questions about the planning or upgrade process let us know!

Security Advisories

Upcoming Events


VMware Modernize Core Infrastructure Roadshow – Cleveland
Date: October 17, 2023
Location:  Corporate College East – Warrensville Heights

You will hear the latest on how to get the most out of your vSphere Infrastructure with sessions on Multi-Cloud Operations with VMware Aria, securing your workloads using tools built into vSphere, and learn about Disaster Recovery Planning.

Register


Continue reading “vToolbelt – October 2023”

vToolbelt – September 2023

End of Technical Guidance for vSphere 6.5 and 6.7

These two versions of vSphere have served us well; but on November 15, 2023, all technical support for vSphere 6.5 and 6.7 will end as the products leave Technical Guidance. If you are still running these versions please upgrade now. If you have questions about the planning or upgrade process let us know!

Security Advisories

  • VMSA-2023-0017 – VMware Horizon addresses multiple vulnerabilites
  • VMSA-2023-0018 – Aria Operations for Networks address vulnerabilities
  • VMSA-2023-0019 – VMware Tools update addresses SAML Token Signature Bypass

 

Product Support Watch

The following products are nearing the End of General Support.  You can find the full list on the VMware Lifecycle Product Matrix.

vSphere – vCenter and ESXi

  • Technical guidance for versions 6.5 and 6.7 will be ending soon.  You can still upgrade to Version 7
  • Site Recovery Manager 8.5 – 10/1/23
  • vSphere Replication 8.5 – 10/1/23
  • VMware Workstation 17 – 2/17/24

Continue reading “vToolbelt – September 2023”

Using Aria Automation APIs with PowerShell

I needed to update a few bits of information for the networks in my on-prem Aria Automation deployment.  It would have been pretty easy to update via the GUI.  I thought this was a great opportunity to start learning about using Aria Automation APIs with PowerShell.

I thought I would share what I found to hopefully help someone new to APIs. This could also be useful if someone needed to make these changes in bulk.    Let’s take a look!

Figuring things out

I started by reviewing the Aria Automation API Documentation (also known as the Swagger UI) built into each vRA install (in your environment go to https://your-vra-fqdn.com/automation-us/api/docs).

The Swagger UI will help describe how to use the APIs and even provides an interface to test them out.

Continue reading “Using Aria Automation APIs with PowerShell”

vToobelt – July 2023

End of Technical Guidance for vSphere 6.5 and 6.7

These two versions of vSphere have served us well; but on November 15, 2023, all technical support for vSphere 6.5 and 6.7 will end as the products leave Technical Guidance.    If you are still running these versions please upgrade now.  If you have questions about the planning or upgrade process let us know!

Security Advisories

  • VMSA-2023-0007 – Aria Operations for Logs (Log Insight) – update to existing advisory to indicate code to exploit this vulnerability has been published.
  • VMSA-2023-0012 – Aria Operations for Networks (vRealize Network Insight) addresses multiple issues
  • VMSA-2023-0013 – VMware Tools Authentication Bypass
  • VMSA-2023-0014 – vCenter Server Memory Corruption

Upcoming Events

 


VMware Explore 2023
Las Vegas, Nevada
August 21-24 2023

The Content Catalog and Schedule Builder are available

Registration is open now!
You can use PSO credits to purchase a conference pass (full pricing information)


Continue reading “vToobelt – July 2023”

SMTP Forwarding in a Home Lab

I use a small Linux VM in my environment to relay outbound SMTP using my e-mail provider. This is primarily used to get alerts and notifications from my Home Lab systems to my inbox.

My Ubuntu version was at end-of-life so it was time to rebuild with the latest version.  I thought this was a good time to publish my notes to help myself – and anyone else!

Acknowledgements

I relied on 3 different blog articles to get this setup.  I am sure there are other ways to accomplish this task; but these worked for me:

Goals

  • SMTP host capable of relaying emails from internal systems to my e-mail provider.
    • No inbound SMTP is needed or desired
    • SMTP had to send email using specific username/credentials
  • Initially it had to work with Gmail.  I had the legacy free version of Google Apps since 2010.  When that was initially announced to be shuttered, I moved all of my email services to Apple.  Shortly after I had moved everything.  Google announced it had changed its mind and was not shutting down Legacy G Suite after all; but that was too late for me.  The steps below work for both Gmail and Apple mail.

Continue reading “SMTP Forwarding in a Home Lab”