Forum Discussion
Loren_129786
Nimbostratus
NimbostratusHorizon View 7 Dynamic session detection iapp????
I am hoping for some help from the community. Four years ago we implemented view 5 as a dual pod and load balanced based off of security groups using APM. This was a rough iapp at that time but we di...
FYI, the Dynamic Session Detection (aka User Persistence) iApp has been abandoned. It never went beyond RC1. At this point, VMWare's Cloud Pod Architecture (CPA) is considered mature enough that F5 User Persistence is no longer necessary.
On the F5 side, you can use GTM, APM, and LTM to configure a single namespace for connectivity to VMWare. This works perfectly to round-robbin a new connection to a VMWare Connection server. Then, CPA takes over and, if it determines the user's VDI is in a different data center, tunnels the session to the appropriate back-end server to provide the desktop.
Take a look at this article written by Justin Venezia. It was written back in 2014, and refers to User Persistence, but aside from that it provides a clear picture of how this works. The only scenario discussed that might still warrant User Persistence is for situations where the pipe between the two data centers is so slow as to be an impediment to users. However, it seems that is no longer considered a legitimate concern.
Toby_Garcia_146
Altostratus
AltostratusFYI, the Dynamic Session Detection (aka User Persistence) iApp has been abandoned. It never went beyond RC1. At this point, VMWare's Cloud Pod Architecture (CPA) is considered mature enough that F5 User Persistence is no longer necessary.
On the F5 side, you can use GTM, APM, and LTM to configure a single namespace for connectivity to VMWare. This works perfectly to round-robbin a new connection to a VMWare Connection server. Then, CPA takes over and, if it determines the user's VDI is in a different data center, tunnels the session to the appropriate back-end server to provide the desktop.
Take a look at this article written by Justin Venezia. It was written back in 2014, and refers to User Persistence, but aside from that it provides a clear picture of how this works. The only scenario discussed that might still warrant User Persistence is for situations where the pipe between the two data centers is so slow as to be an impediment to users. However, it seems that is no longer considered a legitimate concern.
Loren_129786Thank you for everyone's post to my question. I have worked countless hours with Justin Venezia for my previous view 5.3 and the Dynamic Session Detection. Once this thread told me to reconnect with F5 I followed up with some tech leaders and peers of Justin to find out what Toby just posted.
We are now using the F5's with the default view iapps, primarily to provide single name space and we use Vmware Pod/Pod architecture on 7.2 to load balance the users between the sites. It is working perfectly and is actually supported by Vmware which is great.
Thank you for your help Loren