New Infrastructure to Replace Scale Cluster
-
KVM also has this option but I've not gone through and set it up here.
-
@Dashrender said in Ovirt
I do both, and it just seems easier when I have build an application, or custom dev, I can just spin up a machine in my own environment and do what I need to do. plus I have all this equipment already.
But it's not. It's just as easy to spin up a machine in Vultr, etc.
-
@Dashrender said in Ovirt:
@Dashrender said in Ovirt
I do both, and it just seems easier when I have build an application, or custom dev, I can just spin up a machine in my own environment and do what I need to do. plus I have all this equipment already.
But it's not. It's just as easy to spin up a machine in Vultr, etc.
And not ever have to look at or manage any hardware.
-
The obvious issue we have here is Sunk Cost Fallacy.
You already have all of that current infrastructure, and you don't want to loose the value in that investment. I get that. But likely, your best bet is to let it go - Sell it - sell it now, fast! get as much money for it as you can, and move your hosting to a solution like Vultr.
You can also kill that huge internet pipe you have, go to something cheap for your location. Internet will be included in the price of the hosting at Vultr.
-
So @mroth911 oVirt is likely a really great option if you required a hyperconverged infrastructure. From the sounds of it though, you don't.
Going with that premise, why not using XCP-ng and XO, create a pool out of your three hosts? If any host goes offline the VMs get migrated to another host within the pool.
You might have a minute of downtime while this occurs, but this amount of downtime doesn't appear to be unacceptable based on this topic alone where you are wanting to learn how to setup and manage oVirt for your business.
-
@DustinB3403 said in Ovirt:
XCP-ng
I really want a product that works and can be put in productions. I have 24 cpanel servers that I cant have go offline.
-
Thats what I am trying to do I dont like shared storage. Its a single point of failure.
No, it is not. It's what protects you against single points of failure.
You should never "like" or "dislike" things in IT. You should evaluate them logically, not emotionally. Disliking basic building blocks of systems causes big issues.
Imagine "disliking" hyperthreading or "if" statements! You can't refuse to use basic technological concepts necessary for standard computing.
-
@scottalanmiller understood
-
@DustinB3403 said in Ovirt:
XCP-ng
I really want a product that works and can be put in productions. I have 24 cpanel servers that I cant have go offline.
You're still looking at this with brown colored glasses.
First you're wanting to setup something you've never used for production out of the gate. Granted there is a lot of documentation, but the same amount of documentation can make managing and setting this up difficult.
oVirt is powerful, but you have 3 hosts. Meaning if you lost power your systems go offline anyways. All 24 cPanel down.
Same thing would occur with any on-premise solution, power, internet, switching issue.
The idea that XCP-ng (or ESXi or Hyper-V or XenServer) aren't production ready are weird, when you have access to numerous choices for support. Only with ESXi is support more difficult to obtain freely.
-
-
@Dashrender No warranty on hardware. I am not big enough to get contracts etc.
I'm big enough to get contracts for home, how small is the business?
Warranty is something you get on a single server. Why so many servers, the scale you are installing doesn't match with your other limitations.
-
@DustinB3403 said in Ovirt:
I'm assuming you require HA from a Scale type offering and that is why you are looking at oVirt. But I'm just confirming that you actually require this.
Since you said you're so small that you can't get support.
If so, that doesn't "jive" with his "no shared storage" requirement. SS is part of HA. No SS, no HA.
-
@DustinB3403 said in Ovirt:
I have 24 cpanel servers that I cant have go offline.
This statement here leads me to think that you need to purchase support. Period. Or host these in the cloud.
On-premise is the "I can accept some downtime option".
Exactly - how are you protecting these servers from an hour+ long power outage? Do you have multiple ISPs delivering you internet access? etc. HA requires so much more than just multiple servers with shared storage, etc.
-
I have multiple ips, 2 generators, on LP.
-
-
ISP
-
I get everyone view on this. However, I have a ton of equipment. I already have 5 year contracts with fiber. It would cost me more money to cancel the contracts 20K per ISP for me to put my stuff in the cloud. SO While I have all this equipment here that is collecting dust I can use it to make sure I stay up and running.
-
@mroth911 said in New Infrastructure to Replace Scale Cluster:
I get everyone view on this. However, I have a ton of equipment. I already have 5 year contracts with fiber. It would cost me more money to cancel the contracts 20K per ISP for me to put my stuff in the cloud. SO While I have all this equipment here that is collecting dust I can use it to make sure I stay up and running.
And that is fine, it's a cost of business for you at this point in time.
To offset that though, your business is setup so that downtime is unacceptable and is also acceptable at the same time.
Get the point where we are when we look at the topic?
-
You can setup a 200 node pool and have only the transfer time of your VMs.
Nothing would be shared and downtime would be completely minimal with very little to have to learn. Commodity hardware would work perfectly for this and you'd use tools and systems that have a wealth of community support available to you at no charge.
-
@mroth911 said in New Infrastructure to Replace Scale Cluster:
@DustinB3403 yes that is correct. I have a scale cluster already 1150. But its 3 years old. Harddrives are failing. And I cant manage it at all. It just runs and that's it.
Afraid if it craps out I am screwed.
More or less, yes. Purchasing any kind of appliance means a 100% dedication to maintaining support on it for the life of use, it's just part of the initial decision process. You should be able to manage it just fine, but replacing hardware that dies will be a major issue.