You can create a local content library programmatically by using the vCloud Suite API. The API allows you to populate the content library with VM and vApp templates. You can use these templates to deploy virtual machines or vApps in your virtual environment.

To make the library content available for other vCenter Server instances across the vCloud Suite environment, you must publish the library. Depending on your workflow, select a method for publishing the local library. You can publish a local library that already exists in your vCloud Suite environment.

You can publish a local library at the time of creation to enable other libraries to subscribe and use the library content.

You can subscribe to public content libraries. The source objects for a public content library can be: a library created on a vCenter Server 6.0 instance, a catalog created on a vCloud Director 5.5 instance, or a third-party library. When you subscribe to a library, you must specify the backing storage for the library content. You must also provide the correct user name and password if the library requires basic authentication.

When you subscribe to a published library, you can configure the settings for downloading and updating the library content.

You can update the settings of content library types in your virtual environment by using the vCloud Suite API.

You can free storage space in your virtual environment by removing the subscribed library content that you no longer need.

When you no longer need a content library, you can invoke the delete method on either the LocalLibrary or the SubscribedLibrary service depending on the library type.