- How to use VMware vSAN ReadyNode Configurator - Fri, Dec 17 2021
- VMware Tanzu Kubernetes Toolkit version 1.3 new features - Fri, Dec 10 2021
- Disaster recovery strategies for vCenter Server appliance VM - Fri, Nov 26 2021
All these files can be shared within your organization or outside of your organization. The access to content libraries can be password protected. The transfer service on the vCenter Server manages the import and export of content between the subscriber and the publisher libraries. It uses HTTP NFC protocol.
When you enable authentication for the Content Library, you basically set a password on the static username vcsp, which you cannot change. This user account, however, is not associated with vCenter Single Sign-On or Active Directory.
The idea is to have an efficient, centralized method to manage important data required in a vSphere environment. Note that it is possible to edit items only in a local library, no matter whether it is published or not. Library items in subscribed libraries cannot be modified.
The use of subscriptions allows content distribution between a publisher and a subscriber in some scenarios. We can consider the following:
- The publisher and subscriber are in the same vCenter Server instance.
- The publisher and subscriber are in vCenter Server instances that are in Enhanced Linked mode.
- The publisher and subscriber are in vCenter Server instances that are in Hybrid Linked mode.
Create a local or subscription Content Library in vSphere 7
Connect to your vSphere web client and select Home > Shortcuts > Content Libraries. Click Create to start the assistant.
Give it a meaningful name and click Next. You'll have to choose whether you're creating a local library or a Subscribed content library. This is a library that is created in another datacenter or another vSphere environment. You'll need to know the exact address so you can connect to it.
The other option is the Subscribed content library. We'll show you what it looks like here.
It's very important you do not select the "immediately" option because in this case, the system would start to download all the content from the remote library to your environment. And this is probably not what you want.
Once done, you can execute different actions on different objects. In our example, we can see that we have some OVA templates from which we can create a new VM, or we can clone/export them.
When you create a local library within your vSphere environment, you basically create a space where you can store different kinds of files and enable certain new functionality that VMware calls Check-in/Check-out.
This functionality is active for VM templates in Content Libraries and can be edited with version control. You can check out a Virtual Machine from the template while you keep the template as is. You can then patch or edit the Virtual Machine. When you are ready, you can check it back in to update the VM template.
What is Check-In/Check-Out?
Before vSphere 7, when an administrator needed to perform maintenance on a VM template (vmtx), the process was quite manual and included multiple steps. For example:
- Convert the VM template back to a VM.
- Snapshot the VM if rollback is needed.
- Update the guest OS or other VM object settings.
- Convert the VM back to a VM template.
- Copy the VM template back to a Content Library.
- Delete the old VM template(s) from the Content Library.
Now with the check-in/check-out function, you have versioning. You'll be able to check out the VM from this template for edits and then check in that template VM back to the Content Library to save the changes you made.
Simply select the template. The go to the Versioning tab and click Check out VM from this template.
A new wizard will start. Follow the wizard and specify where you want to create and power on this VM.
Once you make at least one change, you'll be able to see the versioning. In our case, we edited the VM's virtual hardware and added some vCPU to test it. Be sure to add some notes so we know what we modified.
The VMTX templates will now be able to see different versions when you change the template. You may want to apply some patches to the VM or change add/remove some of the VM's virtual hardware.
Content Library Roles
vCenter Server uses roles to protect certain areas of the infrastructure from unwanted access. When you work with a team of IT administrators, you can delegate certain roles to different team members.
The Content Library Administrator role is a predefined role that gives a user privileges to monitor and manage a library and its contents.
A user who has this role can:
- Create, edit, and delete local or subscribed libraries
- Synchronize a subscribed library and synchronize items in a subscribed library
- View the item types supported by the library
- Configure the global settings for the library
- Import items to a library
- Export library items
Advanced Content Library settings
The Advanced settings button next to Create on the Content Library page allows you to set some advanced sync operations, the auto sync refresh interval, or adjust some performance optimization settings.
Let's have a look. The auto sync, when enabled, allows you to automatically sync all items from the subscription library to your own local datacenter.
You can find other options by hovering a mouse over the information icon, as we won't be able to explain all settings in this blog post.
What's interesting with subscription libraries is that you can easily share your templates with a sister company and allow those two entities to put a common template together.
When relying on a high-speed fiber internet connection, you don't even need to keep all the templates locally and waste your storage space. Simply deploy a new VM from a subscribed Content Library and this template will be downloaded and transformed into a VM automatically.
Final words
Content libraries are a great way of organizing content and keeping your templates, ISO, and OVF files in one central location accessible for your subsidiary companies, remote offices, and so on.
VMware vSphere 7 Content Library, with versioning available and activated, allows large enterprise IT admins to track changes to those templates and return to the version they need.
Subscribe to 4sysops newsletter!
vSphere 7 Content Library has evolved and become a very simple feature to use, decreasing the time needed to add and remove content.
Hi Seget,
Thank you for this vmware library configuration, I tried different ways to add this library with vsphere, but it keeps giving me the following error
HTTP request error: Connect to wp-content.vmware.com:443 [wp-content.vmware.com/23.41.208.27] failed: Connection timed out (Connection timed out).
I dont use proxy in my local network
Any idea ? I am stucked
Maybe firewall? Most likely.
I am using Windows 10
I turned off the windows Firewall, still getting the same error.
Any idea which firewall to be configured (I am using Cisco FMC to manage my Cisco Firepower 2110)
Thanks for a great article – the advanced settings are just what I’m looking for to have some control over our WAN utilisation.
One question. If the site hosting the publisher is offline/inaccessible is it possible to convert the Subscriber CL so that I can upload new content without waiting for the publisher to come back online? Obviously, we’d have to upload that new content to the original publisher and then reset the subscriber once the whole environment is available. We’re using automation to deploy VMs and would rather not have to pause that while the primary site is unavailable.
Thanks.
This issues commonly seen after upgrading from 6.7 to 7.0.
I have done the following steps and fixed the isseus 🙂
log in VCSA via Putty
You have to Run the following command stop the update manager service :
service-control –stop vmware-updatemgr
Run the following command to reset the Database of VMware Update Manager:
/usr/lib/vmware-updatemgr/bin/updatemgr-utility.py reset-db
Run the following command to delete contents of the VMware Update Manager ( this will delete the contents of the VMware Update Manager)
rm -rf /storage/updatemgr/patch-store/*
You have done with fix , now start the pdate Manager Service and log out and log in .
Start the VMware Update Manager Service:
service-control –start vmware-updatemgr
All the best
Ajith.P