VMware has used its VMworld keynotes and sessions to lift the lid on parts of what is included in the vSphere 6.0 Public Beta. This is still in beta, remember, so some functionality may not actually make it into the finally released version and there may still be further bits and pieces revealed.
VMware continues to build out its hypervisor core management application vCenter with more functionality. There are no dramatic architectural changes but VMware is moving slowly to pull apart vCenter into its component parts to be able to run more vCenters at scale and is creating a central services function.
Platform Services Controller (PSC)
VMware is introducing a new component called the VMware Platform Services Controller (which had a previous beta name of Infrastructure Controller)
SSO was the first component to be spun out into what is now being built up as the PSC. SSO was first released in 5.1 and had major issues and was rebuilt as SSO 2.0 for vSphere 5.5
vCenter, vCOPs, vCloud Director, vCloud Automation Center can use the PSC as a shared component.
The PSC now contains the following functionality:
- Certificate Authority
- Certificate Store
- Service (Product) Registration
The Certificate Authority and Certificate Store are new components to at last tame the wild and woefully inadequate management of vSphere certificates. The new VMware Certificate Authority (VMCA) can act as a root certificate authority either managing its own certificates or handling certificates from an external Certificate Authority. VMCA provisions each ESXi host with a signed certificate when it is added to vCenter as part of installation or upgrade. You can view and manage these certificates from the vSphere Web Client and manage the full certificate lifecycle workflow.
Service (Product) registration is a component that all other services register to and is the lookup service in vSphere. It is the service that will tell you all the services that are running in the system.
Other services will be added to the PSC in future releases.
The PSC is built into vCenter and runs as a vPostgres database so there’s no additional database to worry about and it runs in both the Windows and appliance version. The PSCs self replicate and importantly don’t use ADAM so it can replicate between Windows and appliance vCenters.
You can either have the PSC embedded within vCenter Server or run it as an external component to vCenter Server.