Today VMware launched vSphere 6.7 and there are lots of new enhancements in this release. But first the news. This is the final release for both vCenter Server for Windows and the vSphere Web Client (flash). The vCenter Server path is set and has been for a while with the vCenter Server Appliance (VCSA). The vSphere Client (HTLM5) is getting close to feature complete in this release.
There are some considerations around upgrades for this release. First, I can’t stress it enough read the release notes, they are your friend. vSphere 6.7 will only support upgrades and migrations from vSphere 6.0 or 6.5. What does this mean for vSphere 5.5? In short a vSphere 5.5 to 6.7 upgrade or migration is multi-step. Also, a vCenter Server 6.0 or 6.5 managing ESXi 5.5 hosts will also be a multi-step upgrade. In this case, the ESXi 5.5 hosts will need to be upgraded to at least vSphere 6.0 before upgrading the vCenter Server. OK on to the What’s new with vCenter Server Appliance 6.7.
vCenter Server Appliance 6.7 CLI Installer
vSphere 6.7 has improvements in several areas of the vCenter Server appliance. Let’s start with the CLI installer. For the most part, the vCenter Server Appliance 6.7 ISO is the same compared to 6.5 with one exception. There is now a templates schemas directory under the CLI installer directory. The schemas are meant as a data type guide for the JSON templates. This is actually a good segway to the VCSA CLI installer.
If you haven’t use the CLI installer, you’re missing out. This release introduces a new enhancement called batch operations. Prior we had to run each JSON individual and in the correct sequence manually. With batch operations, we can now drop several JSON files in a single directory and the CLI installer will handle the deployment and sequence. We are still responsible for making sure the JSON templates correctly filled out. Also ensuring the correct replication agreements are in place. Then sit back and watch the magic happen. The Batch operations also handles the VCSA lifecycle of install, upgrade, and migrate 🙂
CMSSO-Util Repointing Tools
There are a couple of updates to the cmsso-util for repointing. Keep in mind both of these updates are only for external deployments. The first is not actually new but is making a return. If you said repoint across sites, you are correct. Repointing is supported within a site and across sites in vSphere 6.7.
The second repointing update is new in vSphere 6.7. Now you can repoint your vCenter Server across a vSphere SSO domain. Think vSphere SSO domain consolidation! Domain repoint comes with a pre-check option which generates any discrepancies before repointing. These discrepancies are logged in a JSON file to be verified and corrected prior to repointing. If the pre-check option is not used the opportunity to resolve any discrepancies is not available. Therefore, it highly recommended to use it. The domain repoint feature migrates licenses, tags, categories, and permissions from one PSC to another.
vSphere Appliance Management Interface (VAMI)
The vSphere Appliance Management Interface (VAMI) has received a significant amount of improvement. VAMI is becoming the VCSA tool for monitoring and out of band troubleshooting. Now sporting the new Clarity theme for a more unified look across the VMware portfolio. There are several new tabs and enhancements in the VCSA 6.7 VAMI, these include:
- Monitoring – visibility to CPU, memory, network, and database utilization.
-
- A new addition called disks is now available under the monitoring tab. Here we can see all the disk partitions for the VCSA, space available and utilization.
- Improved alerting in the vSphere Client based on triggered events.
- Services – previously in the vSphere Web Client and now in VAMI for out of band troubleshooting. All the services that make up the VCSA, their startup type, health, and state are visible here. We are also given the option to start, stop, and restart services if needed.
- Syslog – increased the supported number of syslog forwards to three. Prior, vSphere 6.5 only supported forwarding to only one.
- Update – there is now more flexibility in selecting patches and updates. Information about each patch or update is available such as type, severity, and if a reboot is necessary.
-
- Expanding a patch or update in the main view will display more information about what is included a patch or update.
- Option to either stage or stage and install a patch or update from the VAMI. This capability was previously only available from the CLI.
- File-Based Backup – was first introduced in vSphere 6.5 under the summary tab, now it has its own backup tab.
-
-
Native scheduler included in the UI.
-
Retention option available, select the number of backups to keep.
-
Activities of completed and failed backup jobs logged with detailed information.
-
- File-Based Restore – workflow now includes a backup achieve browser.
-
-
The browser displays all your backups without having to know the entire backup path.
-
External PSC restores are not supported when other replication partners are available.
-
External and Embedded Enhanced Linked Mode supported with the reconciliation of vSphere SSO domain credentials.
-
Simplified Architecture
-
No load balancer required for high availability supports native vCenter Server High Availability.
-
Site boundary removal provides flexibility of placement
-
Supports vSphere scale maximums
-
Allows for 15 deployments in a vSphere Single Sign-On Domain
-
Reduces the number of nodes to manage and maintain
Migrate to the VCSA
- Import historical data in the background
- Import all data now
Beside each of the data import options is an estimated time of how long each option will take when migrating. Estimated time will vary based on historical and performance data size in your environment. Selecting the data import in the background option gives the ability to pause and resume. Once the VCSA 6.7 is deployed and configured, log into the VAMI and a banner is displayed at the top to manage the data import along with the current percent.
Workload Mobility
Now let’s talk about a different type of migration, the workload kind. vSphere 6.7 has enhancements removing the boundaries for workload mobility. vMotion 6.7 now supports workload mobility across vCenter Server versions going back to 6.0 U3. The only blocker was from 6.5 to 6.0 U3 which has removed in 6.5 U1.
EVC is usually a cluster level setting, now in vSphere 6.7, it’s also a VM level setting with Per-VM EVC. Per-VM EVC takes us across clusters, datacenters, vCenters, and VMware Cloud on AWS. EVC, only allows CPUs from a single vendor, meaning you can not cross the streams between Intel and AMD. Per-VM EVC does require a VM to be on the latest VM compatibility version 14 included in vSphere 6.7.
vSphere Client (HTML5)
- vSphere Update Manager
- Content Library
- vSAN
- Storage Policies
- Host Profiles
- vDS Topology Diagram
- Licensing
- More…
Some of the workflows mentioned above are not all feature complete. VMware will continue updating the vSphere Client outside of the normal vCenter Server release cycle through updates and patches.
Platform Services Controller UI
Say goodbye to the PSC UI (/PSC) and hello to one less client. The PSC functionality is now part of the vSphere Client and all functionality is now located under the Administration menu. Certificate management has its own tab and all other PSC management is under the configuration tab.
Conclusion
Now that you’ve seen what’s new in the vCenter Server Appliance 6.7, go and give it a spin. I’ll have more information shortly on enhancement mentioned above until then check out the following vSphere 6.7 resources: release notes, documentation, videos, and configuration maximums [ links coming soon]
Salam Emad
No load balancer required for high availability supports native vCenter Server High Availability”
Above statement apply to PSC under LB NSX
So no more required to run PSC under NSX LB
Regards
It only applies to embedded deployments. The PSC is just a services running in an embedded deployment and can be protected using vCenter Server High Availability (VCHA).
Is there a migration path to the new simplified architecture? If i already have multiple sites in ELM with (6.5) vcsa’s with external psc’s? Hopefully it isn’t one of these just rebuild everything and move you hosts over train wrecks.
There will be guidance in this area, thats all I can say for now 🙂
Thank you for your comforting words! I was also digging around the internet already for guidance of migrating back to the embedded PSC with ELM and was really NOT looking forward to rebuilding the management environment.
I really hope you can tell us more within a reasonable period of time.
ps. Nice job on keeping the new 6.7 release silent during the NL-VMUG event 🙂
Hi Emad
Is there migration path available for PSC on windows to appliance. We have PSC cluster running on separate servers.
Yes, you can use the native migration tool that is part of the VCSA ISO.