vRA7.2 and vSphere Integrated Containers

Published on 19/12/2016 - Read in about 1 min (176 words)

Published under Cloud Native, vRealize Automation, vSphere #containers #vic #vra7 #vRealize Automation #vsphere integrated containers

This article is now 9 years old! It is highly likely that this information is out of date and the author will have completely forgotten about it. Please take care when following any guidance to ensure you have up-to-date recommendations.

One of the cool new features released with vRealize Automation 7.2 was the integration of VMware Admiral (container management) into the product, and recently VMware made version 1 of vSphere Integrated Containers generally available (GA), so I thought it was time I started playing around with the two.

In this article I’m going to cover deploying VIC to my vSphere environment and then adding that host to the vRA 7.2 container management.

Deploying vSphere Integrated Containers

VIC is deployed using a command line interface, which deploys a vApp and a container host VM onto your ESXi host or vSphere cluster. There are a LOT of different ways to configure VIC so I strongly suggest you read and digest the VIC Installation Guide . For the sake of simplicity, I’m going to deploy as basic a setup as I can figure out.

The following command is broken down into multiple lines for readability:

./vic-machine-darwin create is the executable (for MacOS), followed by the command “create”. No surprises there.

vRA7.2 and vSphere Integrated Containers

Deploying vSphere Integrated Containers

Adding vSphere Integrated Containers to vRealize Automation 7.2 {.brush:.bash;.gutter:.false}

Share this post