dbeato why are you migrating from Hyper-V to XCP-ng
-
@dbeato why are you migrating from Hyper-V to XCP-ng?
-
If you have no Windows server (which I'm sure he does ) why not?
Likely much easier to manage than all the hoops you need for Hyper-V (need windows 10 machine for example), plus if non domain - tons of setup PITA stuff.
none of That is needed for XCP-ng.
-
@Dashrender said in dbeato why are you migrating from Hyper-V to XCP-ng:
If you have no Windows server (which I'm sure he does ) why not?
Likely much easier to manage than all the hoops you need for Hyper-V (need windows 10 machine for example), plus if non domain - tons of setup PITA stuff.
none of That is needed for XCP-ng.
None of that is needed with Hyper-V either. You can use the CLI interface to manage Hyper-V all day.
-
Don't see why it matters? Use whatever Hypervisor as long as it's stable and being updated don't see what the issue is?
-
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
Don't see why it matters? Use whatever Hypervisor as long as it's stable and being updated don't see what the issue is?
It's a question, since @Dashrender mentioned he migrated away from XenServer to Hyper-V. And to have a discussion on why he decided to go that route.
-
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
Don't see why it matters? Use whatever Hypervisor as long as it's stable and being updated don't see what the issue is?
It's a question, since @Dashrender mentioned he migrated away from XenServer to Hyper-V. And to have a discussion on why he decided to go that route.
could be for the reason that Xenserver has changed how features work and is more restricted now. XCP-NG is Xenserver without anything disabled.
-
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
could be for the reason that Xenserver has changed how features work and is more restricted now.
Citrix changing their license is their choice. I get the reasons for many people dumping it.
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
XCP-NG is Xenserver without anything disabled.
This is wrong, XCP-ng is the last open source version of XenServer, with numerous changes that are not at all in XenServer. It is it's own product now.
-
I see you got dual threads on this....
-
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
I see you got dual threads on this....
Separate threads for separate conversations with separate people.
-
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
I see you got dual threads on this....
Separate threads for separate conversations with separate people.
Ah I See ,fair enough
-
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@dbeato why are you migrating from Hyper-V to XCP-ng?
Because I want to
-
@dbeato said in dbeato why are you migrating from Hyper-V to XCP-ng:
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@dbeato why are you migrating from Hyper-V to XCP-ng?
Because I want to
Fair enough lol. But kind of a conversation killer.
-
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@dbeato said in dbeato why are you migrating from Hyper-V to XCP-ng:
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@dbeato why are you migrating from Hyper-V to XCP-ng?
Because I want to
Fair enough lol. But kind of a conversation killer.
No, in all fairness it is because they were old HyperV 2012 Servers and I already had XCP-Ng implemented for a POOL of 7 servers. So I added those workloads from a couple Hyperv Servers to the already existing XCP-ng. I essentially didn't need additional hosts running outdated and consuming more power.
-
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
could be for the reason that Xenserver has changed how features work and is more restricted now.
Citrix changing their license is their choice. I get the reasons for many people dumping it.
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
XCP-NG is Xenserver without anything disabled.
This is wrong, XCP-ng is the last open source version of XenServer, with numerous changes that are not at all in XenServer. It is it's own product now.
I perhaps worded that wrong, yeah it is a separate product now but it's original code base was from Xenserver.
And they did disable features in 7.3 -
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
could be for the reason that Xenserver has changed how features work and is more restricted now.
Citrix changing their license is their choice. I get the reasons for many people dumping it.
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
XCP-NG is Xenserver without anything disabled.
This is wrong, XCP-ng is the last open source version of XenServer, with numerous changes that are not at all in XenServer. It is it's own product now.
I perhaps worded that wrong, yeah it is a separate product now but it's original code base was from Xenserver.
And they did disable features in 7.3That's more accurate, and when Citrix disabled features, that is what spurred @olivier and his team to create XCP-ng (from XenServer) and to rebrand with XCP-ng. Which XCP is the first iteration I believe of XAPI, which later was branded to XenServer.
IDK the exact history of the naming. But I'm pretty sure it all started with Xen, turned into XCP, was rebranded XenServer, and is now XenServer and XCP-ng as separate products.
-
@DustinB3403 the naming I find a bit weird XCP-NG....not as freindly on the tongue as xenserver lol.
-
They have done great with it though, full praise to them for starting that project.
-
@StuartJordan said in dbeato why are you migrating from Hyper-V to XCP-ng:
@DustinB3403 the naming I find a bit weird XCP-NG....not as freindly on the tongue as xenserver lol.
Well the name is derived from XCP (which was the original XenServer name iirc).
NG is I believe for Next Generation (or New maybe).
-
@dbeato said in dbeato why are you migrating from Hyper-V to XCP-ng:
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@dbeato said in dbeato why are you migrating from Hyper-V to XCP-ng:
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@dbeato why are you migrating from Hyper-V to XCP-ng?
Because I want to
Fair enough lol. But kind of a conversation killer.
No, in all fairness it is because they were old HyperV 2012 Servers and I already had XCP-Ng implemented for a POOL of 7 servers. So I added those workloads from a couple Hyperv Servers to the already existing XCP-ng. I essentially didn't need additional hosts running outdated and consuming more power.
So you decommissioned some old hyper-v servers into your more up to date XCP-ng environment. That's a good reason. Simplifies your stack, removes hardware, saves energy.
-
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@dbeato said in dbeato why are you migrating from Hyper-V to XCP-ng:
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@dbeato said in dbeato why are you migrating from Hyper-V to XCP-ng:
@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:
@dbeato why are you migrating from Hyper-V to XCP-ng?
Because I want to
Fair enough lol. But kind of a conversation killer.
No, in all fairness it is because they were old HyperV 2012 Servers and I already had XCP-Ng implemented for a POOL of 7 servers. So I added those workloads from a couple Hyperv Servers to the already existing XCP-ng. I essentially didn't need additional hosts running outdated and consuming more power.
So you decommissioned some old hyper-v servers into your more up to date XCP-ng environment. That's a good reason. Simplifies your stack, removes hardware, saves energy.
Yes.
