WilliamLam.com

How to download offline copy of the vSphere Kubernetes releases (VKr) Content Library?

by // 2 Comments

As part of the setup for vSphere Kubernetes Service (VKS), a local vSphere Content Library needs be created to store the various vSphere Kubernetes releases (VKr) which users typically synchronize from VMware's online VKr Content Library repository.


I typically recommend configuring the content library subscription to only download files when needed, rather than the entire library, which is currently over 200GB+.

After standing up another VKS environment, I needed to download additional VKr images but I could not reuse my existing subscribed content library since it was configured on a different vCenter Server.

With the ability to host a custom vSphere Content Library on my Synology, I realized a better solution would be for me to simply download the full VMware VKr Content Library and host that locally on my network rather than re-downloading the same images each time I have a new deployment.

[Read more...]

How to setup custom vSphere Content Library on a Synology?

by // 3 Comments

The ability to run a diverse set of custom add-on applications from backup, security, multimedia, developer tools and many more directly on a Synology NAS makes it extremely versatile and can enable a number of new capabilities within your environment.


While browsing through the packages, I noticed there is a WebStation package which can be used to host a basic website (can also support advanced web applications). This immediately gave me an idea as I can now host my own custom vSphere Content Library, also referred to as a 3rd party content library that are managed outside of vCenter Server, directly on the Synology!

Note: Installing add-on applications will consume additional CPU and memory resources on your Synology, make sure you have enough resources, especially memory before running additional services on your Synology.

[Read more...]

How to relocate an existing vSphere Content Library from one vSphere Datastore to another?

by // 11 Comments

When you create a vSphere Content Library using vCenter Server, the content library is comprised of both the raw uploaded files (OVF, OVA, VM Templates, ISO, etc) which are stored in a vSphere Datastore and the metadata that is generated by vCenter Server for the individual files, which are stored in the vCenter Server Database (VCDB). In contrast, when an External vSphere Content Library is created, which can be backed by any HTTP(s) endpoint, both the metadata along with the raw files are stored external to the vCenter Server and is managed separately.

Today, there is not an easy way to relocate or move an existing vSphere Content Library from one vSphere Datastore to another. The process would require creating a new vSphere Content Library, then manually using either the vSphere UI or API to then copy all the files from the previous content library to the newly created one which is backed by a different vSphere Datastore.

Typically, the reason for this use case is either you are running out of storage and can not expand further or you need to decomission the underlying storage backing the content library.

Recently, I needed to look into this for my own homelab setup where I plan to rebuild one of my setup which is running on vSAN and I wanted to preserve existing content library without having to transfer content back/fourth. The context above was important as I was able to figure out this could be done with some minor tweaks to the VCDB (which I typically do not recommend touching for this reason) but for this purpose, it really is the only way which I had also confirmed with Engineering.

Disclaimer: This is not officially supported by VMware, use at your own risk.

[Read more...]