In this blog post, we are going to synchronise our vRealize Operations costing information with CloudHealth, to provide the ability to have true multi-cloud cost reporting, that includes our on-premises VMware Datacenter.
In the CloudHealth interface, when you go to the vRealize Operations Accounts page under setup, you’ll see that this page points you to the documentation and the VMware Marketplace. As this configuration is initiated by the vRealize Operations Management Pack.
Data Center Tab > Setup > Accounts > vRealize Operations
Download the Management Pack
Start by downloading the management pack from the VMware Marketplace.
In this blog post, I am going to cover the setup of the Active Directory integration with vRealize Automation using LDAPS.
Cloud Assembly supports integration with Active Directory servers to provide out of the box creation of computer accounts in a specified Organizational Unit (OU) within an Active Directory server prior to provisioning a virtual machine.
Note: to join to AD within the Guest OS, you can use CloudConfig properties or vSphere CustomizationSpec.
The VMware official documentation doesn’t really call out LDAPS configuration, only LDAP. So after helping a customer configure this, I thought I’d quickly write something up.
To get started, login into vRealize Automation and select Cloud Assembly.
I was honoured to be a guest on the “Ask an OpenShift Admin” webinar recently. Where I had the chance to talk about OpenShift on VMware, always a hot topic, and how we co-innovate and work together on solutions.
You can watch the full session below. Keep reading to see the content I didn’t get to cover on a separate recording I’ve produced.
Ask an OpenShift Admin (Ep 54): OpenShift on VMware and the vSphere Kubernetes Drivers Operator
However, I had a number of topics and demo’s planned, that we never got time to visit. So here is the full content I had prepared.
Some of the areas in this webinar and my additional session we covered were:
Answering questions live from the views (anything on the table)
OpenShift together with VMware
Common issues and best practices for deploying OpenShift on VMware vSphere
Consuming your vSphere Storage in OpenShift
Integrating with the VMware Network stack
Infrastructure Up Monitoring
OpenShift on VMware – Integrating with vSphere Storage, Networking and Monitoring
Scroll to the bottom of the page, and select “Add/Upgrade”
Select the pak file for installation and follow the wizard.
Create a CSP API Token
For the vROPs management pack adapter to be able to communicate with TMC, we need an API token.
Log into https://console.cloud.vmware.com
Change to correct organisation that contains your TMC instance
Click your name in the top right hand corner and select “My Account”
Select the “API Tokens” tab, and then “Generate a new API Token” button.
Set your API Token name, expiry, and access control as required. Then click the generate button.
You will be shown a dialog box with your generated token. Save this in a safe space we will use it later on.
Connect vRealize Operations management pack adapter to Tanzu Mission Control
In vROPs UI go to Administration > Under Solutions, choose “Other Accounts” and click the “Add account” button.
From the account type list, choose Tanzu Mission Control.
Fill out the necessary details on the New Account screen.
For the credential click the + symbol, add in a name for the credential, and the CSP token you created earlier.
Select your newly created credential.
Select the validate button.
Hopefully you get a successful message.
You will see the account object in the Other Accounts view.
Auto-Discovering Tanzu Kubernetes Grid Clusters
Now you have your account added, whenever you provision a new cluster using Tanzu Mission Control, cAdvisor will be configured in the Kubernetes cluster and a Kubernetes account type will be created in vROps automatically for you.
Below I’ve created a cluster in AWS, and we can see the object has been created in vROPs.
And finally, here is my cluster showing in the one of the Kubernetes Dashboards.
This is a simple to implement feature but can make a massive difference in your ability to monitor your TKG clusters from the infrastructure view that vROPs provides. As your users create clusters via TMC, they don’t need to interact with the monitoring platform to ensure visibility.