Template Connector Difference
6 replies, 100 views
Posted on January 9, 2017
Edited by wrekdoll on January 9, 2017
wrekdoll
Registered user
Joined: July 21, 2016

Hi,

Wondering if anyone could explain the use case (or point to some doc) for the two vmware Template Connectors.We currently use the vCenter Connector to publish our images to VC then make all the requisite changes and deploy to our horizon pools. Is there some advantage to the Horizon Connector?

 

Thanks

Randy

Posted on January 9, 2017
Gunther Anderson
Unidesk employee
Joined: May 17, 2010

Are you sure you mean Platform Layer?  It almost sounds like you're talking about the Connector instead. 

But if you mean Platform Layer, where is the Horizon Agent installed?  The purpose of telling Unidesk exactly what hypervisor, provisioning system and broker are going to be installed is for us to handle cross-platform deployments.  The things in those three pull-downs are the things we will permit to be written into the image that uses that platform layer.  So if you build a platform layer, select a broker of None, and then go ahead and install Horizon View agent, we will dutifully scrub it out because, according to the platform layer options, it's not supposed to be there.  So you always need to make sure the platform layer specification includes what's actually there.  Otherwise, in your published image, you'll find things mysteriously missing.

Posted on January 9, 2017
Edited by wrekdoll on January 9, 2017
wrekdoll
Registered user
Joined: July 21, 2016

man your quick, just realzed I had mis-identified the component I as confused about and came to correct.

So yes I was looking at the connector options for the image templates and wondeing what the differences are there, and why i might want to use one v. the other.

Thanks

 

Edited; original question to make the topic less confusing.

Posted on January 9, 2017
Gunther Anderson
Unidesk employee
Joined: May 17, 2010

The Horizon View connector will make the snapshot for you when you shut down the machine.  You still need to associate it with a Composer pool, so it doesn't work the whole process end-to-end for you.  But publishing to vSphere really is already 80% of what publishing to Horizon View does.  Publishing to vSphere has us make the machine and walk away from it.  The Horizon connector sticks around a little bit longer, to help you make that snapshot.

Posted on January 9, 2017
wrekdoll
Registered user
Joined: July 21, 2016

so we would still have to make the processor count and video memory changes before shutdown, correct ?

Posted on January 9, 2017
Gunther Anderson
Unidesk employee
Joined: May 17, 2010

You can.  We have some defaults we set, but if you're consistently changing those, make a VM Template in vSphere with the settings you want, and select that in the connector.  Then we'll always use that to make our machines for you, saving yuo that step.  You can have multiple connectors that are otherwise identical that just specify different VM templates, if that's convenient.

Posted on January 9, 2017
Edited by wrekdoll on January 9, 2017
wrekdoll
Registered user
Joined: July 21, 2016

Awesome! glad to see that,

Could you also explain the purpose of the "Layer disk cache" in the connector settings?

 

found this in the doc for the vSphere connector -

Layer Disk Cache Size in GB (optional) - The size of the Disk Cache that Unidesk use when creating Layers. If you leave the size blank or set it to 0, Unidesk does not use a Disk Cache. If you specify a size, Unidesk users a Disk Cache of up to this size to keep copies of boot disks and packaging disks and reuses these disks to create new packaging machines. The reuse of these boot disks and packaging disks reduces the time it takes to package an Application Layer.

 

where is this cache file located?

Login to post comments