Content Catalog - VCAP-DCV-Deploy
Updated: Feb 7
Content libraries provide a central repository for all of your necessary files.
It is a Container objects for VM Templates, vAPP Templates and other typer of files (files, ISO and so on). Each file is referred as a library item. The item can contain a single file or multiple files. Templates and vApp templates are converted into OVF files.
You need to enable HTTP traffic between vCenters
Direct datastore to datastore transfer is possible when both the ESXi host (in different vCenter) share the same storage. i.e. via VAAI
In vSphere you see a listing of the .ovf file other files But e.g. mf, .ovf and vmdk are not visible
An important item to note that is new to 6.7 Update 2 is the ability to maintain the MAC-addresses of virtual machine as well as the ability to include any custom VM configurations on the virtual machine.
In vSphere 6.7 you now have the option to customize VMs deployed from a template in the Content Library.
Subscriptions allows a bi-directional relationships between published and subscriber libraries. You can create subscription on the existing library instead of creating new subscriber library.
You can also change the auto sync refresh intervals and start and stop times for the automatic synchronisation from Administration > System Configuration > Services > Content Library Service
You can create two types of the library (Local and Subscribed)
Use case: Single vCenter. Other vCenter can subscribe to it. You can configure a password for authentication
Once published it cannot be reverted back to a local library and cannot be used to deploy Virtual machines
You can enable “optimize for syncing over HTTP” is only possible during the creation of the library. You cannot modify this later.
You can create subscribe library in the same vCenter or different vCenter.
In the subscribed library you have the option to download all content immediately or download only metadata for the items from the published library and later download on demand.
Subscribed automatically synchronized the content on regular intervals but you can manually enforce it.
After you have used the library you can delete the content to save space.
You are a consumer and not a publisher or a contributor.
Syncing of native VM templates between Content Libraries is now available when vCenter Server is configured for Enhanced Linked Mode.