Content Library was introduced in vSphere 6.0 as a way to centrally store and manage VM templates, ISOs, and even scripts. Content Library operates with a Publisher/Subscriber model where multiple vCenter Servers can subscribe to another vCenter Server’s published Content Library so that the data stored within that Content Library is replicated across for local usage. For example, if there are two data centers each with their own vCenter Server a customer could create a Content Library to store their VM templates, ISOs, and scripts in and then the vCenter Server in the other data center could subscribe and have all of those items replicated to a local datastore or even NAS storage. Any changes made to the files in data center 1 would be replicated down to data center 2.
With vSphere 6.5 VMware has added the ability to mount an ISO directly from the Content Library versus having to copy it out to a local datastore prior to mounting. Customers also now have the ability to run VM customizations against a VM during deployment from a VM template within a Content Library. Previously, customers need to pull the template out of CL if a customization was required. Customers can now easily import an updated version of a template as opposed to replacing templates which could disrupt automated processes.
There are now additional optimizations related to the synchronization between vCenter Servers reducing the bandwidth and time required for synchronization to complete.
Customers can also take comfort in knowing that their Content Libraries are also included in the new file-based backup and recovery functionality as well as handled by vCenter HA.
- Improved operational features
- Mount an ISO file from a Content Library
- OS customization during VM deployment from a library
- Update an existing template with a new version
- Optimized HTTP sync between vCenter Servers
- Part of VC backup/restore and VC HA