MJenne
Contributor
Contributor

Content Library vs. Read-Only NFS Datastores

My environment:
We have lots of vCenter islands ( 20'ish ) that are not linked and for the time being can't be. These are split across 2 physical locations and are all running 6.7

We would like to ease the pain of managing templates and other artifacts (ISO's, scripts, OVFs) and there appear to be some options.

The overall size of this library is likely < 200GB, and I'm not terribly worried about duping that data across vCenter datastores if the overall solution is easier to manage.

Other than the overhead of having duplicate copies of the same bits, is the simpliest solution to create a single publishing content library and then have every other vCenter have a subscribing content library? Would this solution effectively create a single location to edit the contents of the library?

Should I even look at using NFS datastores with some RW and others RO as a means of making these artifacts available in all of my vCenter environments?

Thanks in advance for your thoughts,

MJ

0 Replies