Homogeneous pools, how similar do the CPUs need to be?
-
@CodeMercenary Yes, vMotion (Guest VM migration) and 10G ethernet are your friends... if you have enough spare resources and things are setup for migration.
With a pool you generally have shared VM storage on a NAS/SAN. That way when you migrate VMs from one host to another you are only moving the memory and the storage stays on the SAN. If you use local storage then the migration includes the storage and can take a long time if you have a large dataset. It does work but you need enough disk space on the other machine.
There are some shared host storage solutions, but not a point an click option at this time.
10G network cards and switches are very reasonably priced these days. I see the Dell R630/R730 10G X540 cards for $25USD.
For Intel Xeon E5 CPUs, the upgrade from v1->v2, and v3->v4, etc. is an incremental improvement and not a huge leap. Most of the Xeon systems support two generations of CPU. That's why you see the same server (by model) with different CPUs.
-
Another option is to just manage several hosts but not have a pool, may not be ideal but just mentioning that it's entirely possible. It's the setup I use in my home lab actually, one XOCE managing 3 hosts of different CPU generations (all AMD but one is a 3970X and the others are 19XX series AMD units). It's all still managed pretty similarly to a pool and then you don't lose CPU features on any of the hosts.
-
@CodeMercenary And you can still migrate VMs (and their storage) between hosts. Without shared storage a pool is not a lot of help. You still only need one XO setup and you can see everything there.
-
Oh, that's great to know @planedrop and @Andrew. While live migration would be cool, I don't know when I'd be able to set up a SAN or have a NAS big enough, fast enough and with fast enough networking, to be able to keep my VMs on it. Knowing that I can just put them in different pools and I can still offline migrate them is cool.
Are there any downsides when it comes to backups if they are in different pools? I assume XO is fine with backing up VMs in one pool to a remote in another pool.
I'm planning to put 10GB ethernet in the R630 so the servers can all communicate fast. When it comes to the XCP restrictions about ethernet ports and such, that's only if they are in pools so using separate pools eliminates that problem too, right?
The R730XD arrived while I was typing this. It's gonna be a fun weekend. Already making plans to remove the current processor and get two better ones plus add more RAM (only has two 8GB sticks right now). Nice that processors that were $2500 when this server was built are now around $100.
-
@Andrew said in Homogeneous pools, how similar do the CPUs need to be?:
@CodeMercenary ... The pool will use the features of the lowest CPU...
So this will make a pool of 5 machines with one old CPU use only the available features of the old CPU?
So if I need some newest cryptographic extensions for OpenVPN or something similar they will not be available on the whole pool if one server CPU does not support them?Is this to support migrations only? It would be better to just say "this guest from this host can not be migrated, it has to be shut down to move" or something similar.
-
As soon you are in a pool, it's meant to live migrate VMs around. That's why all the CPU instructions will be limited to the lowest CPU.
If you don't want to do that, just don't pool your hosts together
-
@CodeMercenary To answer your questions about backups, they should all be fine, the remote is attached to XO rather than the host itself so XO can backup any VM from any host it has access to, to any remote configured in XO.
-
Hi,
What about joining hosts with older Intel CPUs to pool?
So if i have one pool and VMs running on hosts with newer Intel CPU (Intel Xeon Gold 6XXX) can i join two host with older Intel CPU (Intel Xeon E5-2699 v3) to that pool?
Or is better practice to create new pool with hosts with older CPUs and then migrate the VMs over?And could migration from newer to older even can be done? Or should i shutdown the VM and then start it on host with older CPU?
-
- Yes you can
- All VMs booted after the join won't use the most recent CPU features that you don't have on your old CPUs.
The only trick is for previously existing VMs with recent CPU: you need to shutdown then start then again to be sure they aren't using those features (features are applied on boot). So it's doable, but both options are possible.
-
@arc1 i would suggest separate pools and use warm migration in advanced tab between pools
or shutdown VM and do a DR job or copy VM
as simple as that -
Thank you both for fast answer.
Currently I prefer the option with a separate pool, as I find it more transparent.
Only one question. So currently i have ISCSI storage on cluster with newer hosts.
Can i join same storage pools to new pool with older CPU? Or do i need seperate ISCSI storage pool for new pool in XCP?Thank you!
-
You cannot share the same LUN between different pools (butyou can share the same SAN with different LUNs)
-
Thank you!
So in this case, if better option for me to join the hosts to existing pool and then shutdown VMs and start it on host with older CPUs.
Thank you again!
