Don't be tempted to stay at Holiday Inn Las Colinas. It's a bit of a walk
Agreed. I think I stayed there last year and the walk was a bit exciting at night.
@scottalanmiller How are you liking Mango Languages? I started it and it is different from DuoLingo, but I like it. It provides variety.
I like it a lot. Totally different system. I use Drops, too.
Agreed. I use the same. I'm also looking for another way to talk with other natives. I have used Tandem before but it is only for iOS or Android. I wish they had a web app.
following this thread. Time to test this out on a spare box. I've always steered clear of this due to the feedback on here, but initial research looks like it has some pretty awesome features. The builtin backup features are nice too. And it has an API for even more automation. I like that. Time to spin up a box.
@fuznutz04 so what I'm thinking that I am hearing is, and correct me if I am wrong...
- You perceive platform updates as carrying risk and headache.
- You want to do platform updates at the riskiest times (prime production) rather than waiting on a greenzone. I assume because you work during prime production and sleep during what would be the greenzone.
- You run fragile applications that we generally would not consider production ready and don't care about uptime protection on them in general (but don't want unnecessary downtime, either.)
This is what I think that I am hearing, both in your descriptions of why you want this feature, as well as your perception that the other company's non-HA solution was "great". You are looking at it as a feature to make IT management easier, so the application availability isn't the factor of concern here.
To that I would say that...
- Platform updates on systems like KVM are trivially easy, insanely fast, and not a problem at all. You probably only see this as a concern at all because you were running Hyper-V (or VMware) where system updates are problematic. KVM and Xen aren't like this. So if you use them, I think your entire premise for this evaporates.
- I would simply not do this. Even if I have HA, I wouldn't do it because prime production time is never the time to test your failover systems. Everything fails and HA is a highly risky operation even under ideal conditions and there is no vendor that is completely reliable. Doing off hours maintenance isn't just trivially easy, but it is easily scripted during production hours. Why take on cost and risk that is unnecessary? Just do an update and reboot off hours.
- This is real and we can't easily work around it. But the decision that these would require off hours support for safety was made at the time of acquisition.
Also, the cost to have an MSP do this for you, if you didn't want to do it, would be far cheaper than the cost of HA. And fix the problems way more thoroughly because it would address everything, not just one piece.
All good points here.
Taking time to think about this more, the real want for HA stems from fear of the unknown and time to resolution in case of disaster. Example:
I do an update to the host and it bombs for reason X. How fast can I get my backups restored on another host?
A host crashes - Same question. How fast can I restore to another host?
My team is small, can anyone restore properly in a timely fashion?
Would a simple failover system (let's not call it HA, just an automatic failover to another host) be a good solution to be able to keep the VMs running until the failed host is fixed?
All of the points brought up by you and others definitely make me pause and take a step back and really think about what the source of this post really stems from. So thanks for that. Time to think on this a bit more.
(also, now following the Proxmox thread as well )
I've been thinking a lot about what choice to make if I were to go for a high availability system for VMs.
In a past life, I worked for a medium size software hosting company. They were setup with a full Hyper-V failover cluster, including the standard SAN, etc. It was setup before I got there, but it worked great. The hyper-visors were setup correctly (meaning they used Hyper-V server, NOT the Hyper-V role), they used Cluster Failover manager, etc. Doing system maintenance was a breeze, because I would failover all the VMs to the other hosts, perform updates to the node, and then move them back. This was back when I was using Hyper-V server 2012. As of now, a ton more features are available , including cluster aware updating and Windows Admin center which allows you to manage the whole lot from a web browser. Not too shabby.
So, If you create a cluster with Hyper-V server (not the ROLE), and plan to have only Linux VMs on the cluster, thus eliminating the whole licensing downside to MS, what are the main pros and cons of going with the MS solution, VS something else in the Linux world? I'm not leaning one way or another at this point, but I've been so engrossed in the Linux world for the past couple of years, that MS Hyper-V wasn't even a thought in my mind. But now that I'm thinking about it, I'm not really thinking about any big downsides.
Can't wait to get some good discussion going on this.
Greenfield environment? Totally situational IMO.
What are you running on all of the Linux VMs? What kind of HA do you need? Hardware-level HA? VM level? Site? At what level? App level? Service level (can ping the site, but web app doesn't work)? Network level (everything is up, but nobody can access it)? Etc...? All of them?
Would it make sense to run these services and/apps in the cloud in a likely native HA environment with minimal effort and upfront costs?
It totally depends on what you got going on.
Just wondering.... can you give a specific use case other than just wanting some HA VMs? It's kinda hard to answer generally (for me).
Sure thing. Basically, VM and hardware level. There are plenty of environments and workloads still in existence that are not HA on the application layer. So the ability to provide extra protection from downtime, etc, if the cost is within acceptable budgets, can be worth it.
Windows VMs with software that is not designed for shared databases, shared web hosts, etc.
PBX - Lets say I host a PBX for my company. I want to do maintenance on the node hosting this. I want to do it during the day. I want to live migrate that VM to another node. I don't need application level failover, I just need to move it and not have downtime.
Any other software/workload that for one reason or another, cannot reasonably be moved to a "true HA" solution.
We all know that the BEST scenario is to build your applications against best practices, allowing for HA type functionality. But what about those businesses who are not ready to make that investment? That's what I was thinking about.
Hyper-V is a decent choice if all you want is to protect the platform and not the functionality. If you have real HA, this is useless and will often work against you and at the very least make things more costly and difficult. But if you lack HA and need a platform level alternative, Hyper-V with Starwind is a really good choice. Starwind is the only mechanism I'd consider in that situation.
I was thinking about Starwind. I like what they do. (I like hyper-convergence in general)