Hi,
Per best practice View recommendations, we have two separate View deployments (View cluster, View Management Servers including vCenter, and Desktop Pools) at each of our data centers. Our data centers are separated by a WAN. These are identified as ViewA and ViewB. These are pretty much "isolated" View deployments, and share nothing in common.
Users will belong to either ViewA or ViewB pools. It would be easy to have two separate URLs for users of each View instance to access, i.e, viewa.company.com for users to access ViewA pools, and viewb.company.com to access ViewB pools.
Obviously, this would represent some difficulty in managing users, and trying to determine which users would get the URL for ViewA, and which users would get the URL for ViewB. Our end users are all about simplicity.
So we would want to use a single URL namespace that would represent both View instances. However, even if we can get our A10 load balancer to route intelligently between the two View instances, how would a LB (F5 or A10) know which View instance a user belongs to? For example, if a user belongs to ViewA, how does the LB know that the user needs to be routed to the ViewA instance and not ViewB?
The problem is since our View instances are totally separate, a user's desktop can only exist in only one View instance. But yet, with a single URL namespace in front of a LB, how will the LB know where the user's desktop resides in a particular View instance?
Thank you,
Mooge
