The VMware vSphere Web Client remote plug-in integrates plug-in functionality into the VMware vSphere Client without having to run inside a VMware vCenter Server. This provides plug-in isolation and enables scale-out of plug-ins that operate in large VMware vSphere environments. The remote plug-in provides a stronger security model, allowing for increased interoperability with plug-ins.
Following are the changes in remote plug-in architecture:
Local plug-ins are deprecated in VMware vSphere 8.0.
Local plug-ins are replaced by remote plug-in.
Local plug-ins are not supported in the next major VMware vSphere release.
More robust architecture by separating VMware vCenter server from the plug-ins
Before VxRail 8.0.210, in a local plug-in deployment, the plug-in was installed on the VMware vCenter Server Appliance. The remote plug-in is available with VxRail 8.0.210. The new installations have the remote plug-in by default. The upgrades convert the local plug-in to a remote plug-in.
Primary remote server plug-in selection is an automatic selection process where the node with the latest versions of VxRail Manager in the VMware vCenter Server is assigned as primary. The node interacts with the VMware vSphere UI service to serve plug-in functionality. You can change the primary server as a part of Day 2 activity, without rebooting the server. The VMware vCenter Server does not rely on the primary plug-in to communicate with other clusters after the initial registration. If the cluster with primary remote plug-in is shut down, the role is automatically reassigned to another cluster.
The following figure shows the primary remote server plug-in automatic selection process:
Figure 1. Primary remote server plug-in automatic selection process
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\
