Assembler. Does not detect subscribed content libraries.

[Michael Cornn]

In Aria Automation Assembler, the cloud account detects local content libraries but not subscribed libraries. Why is that?

Our vCenter, named d1vcenter, has three content libraries in three datacenters.

• C1 Content Library is type Local. It holds all of our VM templates. 
• D1 Content Library is type Subscribed. It is subscribed to C1.
• BV Content Library is type Subscribed. It is also subscribed to C1. 

In Aria Automation Assembler, under Image Mappings, only images in the C1 Content Library appear. 

As a result, deployments to any datacenter pull image files from the C1 Content Library. Deployments to the D1 and BV datacenters are very slow, because the deployment copies the image file from the C1 library, even though there's a subscribed content library in those datacenters. 

Is there a way to get Assembler to use the subscribed content libraries?

-------------------------------------------

[MohammadHadi Milani]

Yes that is expected behavior in VMware Aria Automation Assembler.

If you want to use a subscribed library create a new local library and sync items to the subscribed one

-------------------------------------------

[RebeccaW]

If you have cases where there are multiple available Content Libraries on a given vCenter but you need to be specific on which one should be used by Image Mapping you will need to turn off image enumeration. KB below will show the steps. Note that you will have to do this process every time after you reboot (unless someone has a way how to make it permanent!). After the steps are done, when you go to Image Mapping you will have a choice between all found machine templates found on the Cloud Account. 

https://knowledge.broadcom.com/external/article/326137/vra-83-and-above-images-are-no-longer-vi.html

-------------------------------------------