vSphere 6.5. – vCenter Server High Availability (VCHA)
William Lam posted a new interesting article regarding vCenter Server High Availability in vSphere 6.5.
In playing with the new VCHA APIs, William decided to create a few VCHA functions which he thought would be useful to have as a PowerCLI module for others to use and also try out.
vSphere 6.5 accelerates the customer transition to digital transformation and cloud computing by addressing key challenges:
1. Environments growing increasingly complex,
2. Growing IT security threats, and
3. The need to support both existing and new apps and services.
What is new for vSphere 6.5:
The vCenter Server Appliance now has features that are exclusive such as:
- Improved Appliance Management
- VMware Update Manager
- Native High Availability
- Built-in Backup / Restore
VMware also covers general improvements to vCenter Server 6.5 including the vSphere Web Client and the fully supported HTML5-based vSphere Client.
For those of you who are not familiar with the new VCHA feature which is only available with the vCenter Server Appliance (VCSA), Feidhlim O’Leary has an excellent write up that goes over the details and even provides demo videos covering both the “Basic” and “Advanced” workflows of VCHA. I highly recommend you give his blog post a read before moving forward as this article will assume you understand how VCHA works.
Some more from Williams Blog post:
In playing with the new VCHA APIs, William decided to create a few VCHA functions which he thought would be useful to have as a PowerCLI module for others to use and also try out. With that, he has published a VCHA.psm1 module on the PowerCLI Community Repo on Github which includes the following functions:
As noted earlier, VCHA Cluster can be deployed using either a “Basic” or “Advanced” workflow. The VCHA PowerCLI module currently only implements the “Basic” workflow. For those interested in the Advanced workflow, you are more than welcome to extend the script but note that it does require leveraging additional VCHA APIs than the ones used in the Basic workflow. Make sure you also have PowerCLI 6.5 R1 installed before trying to use the module.
Here is a screenshot of my vSphere 6.5 environment which has a self-managed VCSA (which will be required for the Basic workflow) OR you can have management cluster that hosts the VCSA you wish to enable VCHA on as long as it is joined to the same SSO Domain. For management clusters that do not share the same SSO Domain with the VCSA that you want to enable VCHA on, then you will have to use the Advanced workflow. You must also enable SSH on the VCSA before attempting to configure VCHA or else you will run into an error. This is something VCHA itself requires and has nothing to do with the script, you will see this behavior regardless of using the UI or API. SSH can be disabled after VCHA is setup.
Read the complete article here.
You may also like these blog posts from William:
- How to run a Docker Container on the vCenter Server Appliance (VCSA) 6.5?
- VCSA 6.5 CLI Installer now supports new ovftool argument pass-through feature
- How to enable vCenter Server High Availability (VCHA) in vSphere 6.5 w/single ESXi host?
- Updates to VMDK partitions & disk resizing in VCSA 6.5
- How to deploy the vCenter Server Appliance (VCSA) 6.5 running on VMware Fusion & Workstation?
There is a lot more about vSphere 6 .5.:
Part 2 – VMware Gets Serious about RESTful APIs and Expanding PowerCLIPart 3 – Big Improvements to vSphere HA and DRS in 6.5 ReleaseVMware vSphere 6.5 – Native vCenter High Availability (VCSA 6.5 only)