I can't seem to find a way to mount ISOs to VMs from Content Library across my clusters. My Content Library ISOs are not on a shared datastore, because each cluster has his own LUNs. With the release of vCenter 6.5, it should be possible to mount ISO stored in your content library (no shared storage needed?)... I have no luck with it. I can only mount it, if stored on shared datastore within cluster.
Thanks in advance!
Not sure if i completely got your question, but still would try to answer. Please correct me if this is not what you wanted.
1. One way is to publish the content library externally by clicking the "publishing option" and copy the Subscription URL under Edit settings of content library.
2. Create another content library -> Under "Configure content library" -> click Subscribed content library(provide the subscription URL of existing content library) ->"Add Storage" Select a datastore local to cluster2. Choose if you want to download content immediately / when needed.
When you edit settings of a VM in cluster2 and add CD/DVD Drive -> choose Content Library ISO file-> You can select the ISO.
VMware documentation link is Create a Library
>>2. Create another content library -> Under "Configure content library" -> click Subscribed content library(provide the subscription URL of existing content library) ->"Add Storage" Select a datastore local to cluster2. Choose if you want to download content immediately / when needed.<<
So Content Library needs a local datastore for each cluster? I thought with Version 6.5 is possible to store contents on a datastore managed by the vCenter Server instance, in order to centrally store and manage VM templates, ISOs, and scripts. But if I need local datastore for each cluster, and have a multiple of libraries how can it be called "centrally"? I've read that CL would try to find such host that has access to CL datastore and then found host and target host would handle copying
Does the Content Library datastore need to be masked (presented) to all the ESXi hosts in the respective vCenter for this to work correctly? I would like to use Content Library for mounting ISOs to all of clusters without the CL datastore to be visible by all the hosts. Is that incorrect thinking?
>>So Content Library needs a local datastore for each cluster? I thought with Version 6.5 is possible to store contents on a datastore managed by the vCenter Server instance, in order to centrally store and manage VM templates, ISOs, and scripts. But if I need local datastore for each cluster, and have a multiple of libraries how can it be called "centrally"? I've read that CL would try to find such host that has access to CL datastore and then found host and target host would handle copying<<
Not sure if the changes you are expecting is present in 6.5. I referred to the official VMware published document on changes in 6.5 . Refer the section "Content Library"
I'm not sure if there has been any resolution on this but I have recently run into the same issue and need to find a solution. The perplexing thing for me is that I can deploy a Content Library OVA contained on a datastore in one cluster to another cluster that doesn't see that same datastore but can't attach an ISO under the same circumstances. What is different in the way a Content Library template is presented from one cluster to another and the way an ISO is presented?
I will be opening a ticket with support on this. If they give me any useful information, I'll pass it along.
Well RonBrownUAL ,
You can only mount an ISO file from a content library to a virtual machine if the datastore or storage device where the ISO file resides is accessible from the virtual machine host. If the datastore or storage device is not accessible, the user interface shows an empty dialog box.
Try this workaround: Make the storage device where the ISO file resides accessible to the host where the virtual machine resides. If policies prohibit this, you can copy the ISO file to a library on a datastore that is accessible to the virtual machine.
I have the same problem.
One of the main benefits of Content Library was that this was not supposed to be necessary. We have 3 vCenter instances, linked in a single SSO domain. One of the vCenters (where the primary CL exists) has the problem where only the cluster that has the CL storage presented to it can see the CL items. The other 2 vCenters don't have this problem, as all of their clusters can see their CL items. I am not able to find any config options that would affect this. I am confused as to why it works properly in 2 vCenter environments but not in another.
I just opened a support case, and will post findings.
any update on this?
we also zone our datastores to individual clusters.
if the content library is hosted on cluster A datastore, i can mount it on any VM within cluster A.
the box is empty when trying to mount on a VM in cluster B.
i can however, deploy a cloned VM to cluster B from a template hosted in cluster A so that's helpful.
having a content library in every cluster with the same content to mount ISOs is not practical.
this is also all within one embedded PSC/VCSA environment, not linked-mode
The answer I got from Support was that I need to present the CL datastore to every host, everywhere, and that this is by design. They provided me with a KB article that stated this (but I don't have the link). I still find this ridiculous, but I pushed back multiple times and got this same answer.
A found solution from another post.
To see the Content Library, the user needs a Read-Only role assigned as a global permission.
. LOGON TO VCENTER using a user with admin rights from vsphere client (html5 or web client).
- create a role (I called it "custom read CL") with privileges of : Content Library + Read storage, Description = "Allow Read Content Library".
- then select the vcenter object from "Host & Cluster Menu", select permissions tab, click on + select the domain - type the user desired and select the role "custom read CL".
- that's it, this process works for me.
thanks to.. msripada