top of page
  • viquarmca

What is the Difference between Harbor Repository and Content Libraries

Over past few weeks i had this question in my mind and some of the team mates did ask why do we use Harbor in Telco Cloud Automation , when we have the Content Libraries. Surprisingly as i thought it wasn't too difficult to differentiate both of them and use.

Harbor Repository :

Harbor is an open source registry that secures artifacts with policies and role-based access control , ensures images are scanned and free from vulnerabilities and signs a trust.

Also Harbor is a CNCF (Cloud Native Computing Foundation) is an open source that promotes the adoptions of Cloud-native computing platforms like k8s and Dockers.

Harbor can manage different kinds of artifacts that are bundled in an OCI-compatible format, such as Helm chart or OPA bundle(open public Access). So in a Typical Telco Cloud Automation when we want to create a CAAS (Container as a service) all of your images are either pointed to Harbor or CBAM (CloudBand Application Manager ) is a ready to use Generic Virtualized Network Function Managers and Air Gap Repository are used As a Partner Systems in TCA. Harbor can be specified during the CNF instantiation , each harbor can be associated with one or more VIM(Virtual Infrastructure Manager). These Harbor repository hold the helms chart and one or more harbor can be installed in any k8s environment .

Content Libraries :

Content Libraries are container objects for VM and vAPP Templates and other types of files, such as ISO images, text files , and so on . To deploy virtual machine and vApps in the vSphere inventory you can use the templates in the library.

You can also use content libraries to share content across vCenter Server instance in the same or different locations.

A content library stores and manages content in the form of library items, example the OVF template is a set of files (.ovf,.vmdk, and .mf).

55 views0 comments

Recent Posts

See All


bottom of page