Is Anyone Using Long-Distance VM Mobility in Production?
I had fun times participating in a discussion focused on whether it makes sense to deploy OTV+LISP in a new data center deployment. Someone quickly pointed out the elephant in the room:
How many LISP VM mobility installs has anyone on this list been involved with or heard of being successfully deployed? How many VM mobility installs in general, where the VMs go at least 1,000 miles? I'm curious as to what the success rate for that stuff is.
I think we got one semi-qualifying response, so I made it even simpler ;)
Let’s start with a way simpler target: "How many VM mobility installs in general… that actually get used"
So far, I haven’t seen a single one, apart from the case where a DC was split across two buildings 100 m apart with tons of dark fiber in between.
I see lots of people building stretched VLANs for all sorts of crazy reasons (most common: “Because the VMware consultants told us to do so”) and think they solved the disaster recovery use case.
OTOH, I haven’t seen anyone actually shifting workloads across the DCI link (excluding migrations) because performance tends to suck after you increase latency by orders of magnitude.
In summary, a lot of people spend significant amount of money (OTV licenses), time and mental energy to create a ticking bomb (because broadcast storm or DCI failure) that adds zero real-life value.
Hot tip: If you can’t persuade your peers what a bad idea stretched VLANs are, tell them Gartner said so ;)
Amazingly, I was able to hold the server team to no L2 on storage or vmotion (so moves are SRM or Hyper-V replication). Further, because I'm not using LISP to steer host traffic, the OTV extension is only for "DR lite".
So, another datapoint for not using long distance VM mobility. I continue to push towards applications that don't depend on L2 or static IPs.
I think he has never heard anything about DCI at all