All of the hypervisors are built for this. It's the storage and clustering that may or may not be built for this. As a rule, highest performance systems are not clustered at all, the can't be. Clustering takes a performance hit.

But in the extreme performance space products like VMware and Starwind are the top dogs. Both have multiple solutions, but they are using tech like memory sharing, localized data, NVMEoF, log structuring, and others to do things that Gluster just can't do. So much so that products like Gluster sometimes use these techs on top to accelerate them (example: Starwind makes a CEPH accelerator platform.)

@scottalanmiller said in New Infrastructure to Replace Scale Cluster:

So if a VM dies, oVirt will provide non-FT failover, yes. And by having failover you might achieve HA. And oVirt is a critical part of making that possible. But it itself isn't HA, nor does it guarantee HA. It's just a failover component that you can use to "do" HA.

It's a component you buy (well, this one is opensource, but still), part of a solution that would cover other potential failure points. The solution in general is also something you can buy, in order to achieve a certain level of HA for those VMs

@momurda said in Building a Basic DRBD Cluster on OpenSuse 12.2:

What is the purpose of 'zypper -remove patterns-openSUSE-minimal_base'
I know what it does, but is it necessary? Does this minimal_base package prevent you from installing certain packages at a later date? Or you just making things nice n neat?

It's been quite some time, but if I remember correctly it interfered with some packages that we needed as the "minimal" blocked adding a bunch of stuff.

@dafyre said:

Best way I've heard it described is that when you enable Hyper-V on a Windows Server, your Windows Server Core (or GUI) becomes the Linux equivalent of Dom 0

And exactly like installing Xen onto Linux, Xen inserts itself as a "shim" under Linux and then reboots, booting into Xen instead of Linux. HyperV is identical, inserting itself as shim under Windows, rebooting and booting into HyperV instead of Windows.

HyperV is modeled identically after Xen.

Sorry for the confusion- its a development server, but i still need to make sure that these are updated with minimal downtime. I am trying to push the AD changes to some other time at least wait for the dev team to complete the tasks in hand, but not very sure if they will stop it just for us