I’ve been working on creating a vSphere appliance for CentOS for easy deployments. I’ve applied the same technique used in Photon OS as an SRM Test VM. It’s the solid process that William Lam devised and is used to build VEBA, the VMware Event Broker Appliance.
I’ve spent a lot of time recently working on a lab install of Site Recovery Manager and vSphere Replication. As well as the installation and configuration of SRM and vSphere Replication I wanted to be able to replicate, protect and recover VMs. In my homelab I have a two site setup running nested ESXi on a single physical ESXi host.
VMC has a similar but different permissions model to normal on-prem vCenters. Chief among the differences is that you don’t get access to an account that has full permissions over the vCenter. This makes sense as you could break some critical to the provision of the service. The highest level of access is a role called CloudAdmin.
VMware Cloud on AWS relieves the VI Admin of a lot of the heavy lifting needed to setup and maintain a VMware SDDC.
I’ve been working a lot recently on automating VMware Cloud on AWS. For Direct Connect and Route Based VPNs we needed to set the BGP ASN.
This post follows on from my blog about the new AppInfo component in VMware Tools 11.0
The latest (11.0) release of VMware Tools is out and one interesting feature that caught my attention was a new component call AppInfo. This component collects information of running processes inside the guest OS. It then makes this information available through normal VMTools procedure to the vSphere Admin. That means we can access guest OS data out-of-band and without needing guest OS credentials. Pretty cool!