I think I am missing something about Hyper-V....?
-
@scottalanmiller said in I think I am missing something about Hyper-V....?:
@stacksofplates said in I think I am missing something about Hyper-V....?:
@scottalanmiller said in I think I am missing something about Hyper-V....?:
@bnrstnr said in I think I am missing something about Hyper-V....?:
@scottalanmiller said in I think I am missing something about Hyper-V....?:
@bnrstnr said in I think I am missing something about Hyper-V....?:
My opinion is Hyper-V is only an option when you need vSAN, otherwise I’m just not buying it.
What makes it special in that case? AFAIK there is no production vSAN for Hyper-V that is unique to it. Hyper-V is effectively completely dependent on Starwind for vSAN and they recommend KVM most of the time.
Right, Starwind makes it a more viable solution because it’s free and easy and well documented, right?
No, Starwind does not. Starwind just doesn't discriminate against it. Starwind is just as easy on VMware or KVM. So it's a draw, unless you consider Xen, then it is just a negative for Xen.
Eh not really. They dropped support for the virtual appliance on anything other than VMware. So you have to manually do the work on KVM/Hyper-V or just aren't able to do it at all. I can't tell.
Same document: "Right now we are releasing the new Linux version, compatible with all industry-standard hypervisors: Microsoft Hyper-V, VMware ESXi, Xen and KVM. It includes Web Management Console, so you can use any convenient HTML5-capable browser to check and configure your infrastructure."
Maybe they are revamping the VSA and the VSA is about to be the legacy version just for VMware and the new stuff is for everything.
To be fair their documentation has said that for over a year.
So was it just never supported?
-
@stacksofplates said in I think I am missing something about Hyper-V....?:
@scottalanmiller said in I think I am missing something about Hyper-V....?:
@stacksofplates said in I think I am missing something about Hyper-V....?:
@scottalanmiller said in I think I am missing something about Hyper-V....?:
@bnrstnr said in I think I am missing something about Hyper-V....?:
@scottalanmiller said in I think I am missing something about Hyper-V....?:
@bnrstnr said in I think I am missing something about Hyper-V....?:
My opinion is Hyper-V is only an option when you need vSAN, otherwise I’m just not buying it.
What makes it special in that case? AFAIK there is no production vSAN for Hyper-V that is unique to it. Hyper-V is effectively completely dependent on Starwind for vSAN and they recommend KVM most of the time.
Right, Starwind makes it a more viable solution because it’s free and easy and well documented, right?
No, Starwind does not. Starwind just doesn't discriminate against it. Starwind is just as easy on VMware or KVM. So it's a draw, unless you consider Xen, then it is just a negative for Xen.
Eh not really. They dropped support for the virtual appliance on anything other than VMware. So you have to manually do the work on KVM/Hyper-V or just aren't able to do it at all. I can't tell.
Same document: "Right now we are releasing the new Linux version, compatible with all industry-standard hypervisors: Microsoft Hyper-V, VMware ESXi, Xen and KVM. It includes Web Management Console, so you can use any convenient HTML5-capable browser to check and configure your infrastructure."
Maybe they are revamping the VSA and the VSA is about to be the legacy version just for VMware and the new stuff is for everything.
To be fair their documentation has said that for over a year.
So was it just never supported?
KVM was their main focus, but was a recent shift from Hyper-V. It was never available for paid support, but was supposed to be their next core product.
-
Also I can't find anywhere on how to actually deploy systems with this. It has a set up guide for the VSA but nothing else. There are guides for both Hyper-V and VMware but I can't find anything for KVM (other than the previously mentioned VSA guide).
-
Just spoke to them, they are revamping their product line so it's a moment of limbo between one being moved out of support for new deployments and the follow up being released, but KVM is their main focus of the new release.
-
@irj said in I think I am missing something about Hyper-V....?:
I find it funny that Microsoft doesn't use their own virtualization for Azure.
Proof?
-
@phlipelder said in I think I am missing something about Hyper-V....?:
@irj said in I think I am missing something about Hyper-V....?:
I find it funny that Microsoft doesn't use their own virtualization for Azure.
Proof?
Read the entire thread? Already answered.
-
@irj I find that to be an odd claim. Azure Stack is based on Storage Spaces Direct (S2D) and that's Hyper-V.
Nothing in Azure/O365 is the same as what we work with outside of their DCs. Nothing.
Nano gives us a bit of a glimpse into what is being done there. Calling what Nano does, and Windows Defender Application Guard which is the virtual isolation of Edge, Hyper-V is a bit of a stretch.
The hypervisor is just that. A layer between the guests and the hosts whatever it's named.
-
@jaredbusch No, I didn't realize just how long it was until I posted that. :S
-
@scottalanmiller said in I think I am missing something about Hyper-V....?:
@bnrstnr said in I think I am missing something about Hyper-V....?:
My opinion is Hyper-V is only an option when you need vSAN, otherwise I’m just not buying it.
What makes it special in that case? AFAIK there is no production vSAN for Hyper-V that is unique to it. Hyper-V is effectively completely dependent on Starwind for vSAN and they recommend KVM most of the time.
Storage Spaces Direct is Microsoft's equivalent to vSAN.
-
We've been deploying virtualization solutions on Hyper-V since Longhorn/2008. We built our first cluster on the Intel Modular Server (probably the first to do so with Hyper-V) back in the day with our first IMS cluster deal following that up.
AD is not required for the Hyper-V host in standalone setups. We don't join a standalone Hyper-V host to the guest's domain. That provides a barrier between production and the virtualization stack.
Depending on client requirements, when we build-out a cluster setup we prefer to have a separate management AD for the cluster and the production AD for the guests separate. This is not always possible.
Why Hyper-V? We don't have to pay anything extra to build-out a virtualization platform for one.
We've done well with Hyper-V and Storage Spaces.
-
@phlipelder said in I think I am missing something about Hyper-V....?:
We've been deploying virtualization solutions on Hyper-V since Longhorn/2008. We built our first cluster on the Intel Modular Server (probably the first to do so with Hyper-V) back in the day with our first IMS cluster deal following that up.
That's impressive because because from what I remember hyper-v was terrible in 2008.
-
@irj said in I think I am missing something about Hyper-V....?:
@phlipelder said in I think I am missing something about Hyper-V....?:
We've been deploying virtualization solutions on Hyper-V since Longhorn/2008. We built our first cluster on the Intel Modular Server (probably the first to do so with Hyper-V) back in the day with our first IMS cluster deal following that up.
That's impressive because because from what I remember hyper-v was terrible in 2008.
Heh, it took 9 months of life, front-line access to the IMS engineering team, and some handholding by Ben Armstrong and Jose Barreto to get it going. It was a really cool moment to see the VMs Live Migrate between all of the nodes and then start right back up when we started testing failover scenarios.
And yes, it was very painful as we committed to deploying all clusters with Server Core and still do so today. Though, with PowerShell it's a lot less painful.
EDIT: And, thanks!
-
@phlipelder said in I think I am missing something about Hyper-V....?:
@irj said in I think I am missing something about Hyper-V....?:
@phlipelder said in I think I am missing something about Hyper-V....?:
We've been deploying virtualization solutions on Hyper-V since Longhorn/2008. We built our first cluster on the Intel Modular Server (probably the first to do so with Hyper-V) back in the day with our first IMS cluster deal following that up.
That's impressive because because from what I remember hyper-v was terrible in 2008.
Heh, it took 9 months of life, front-line access to the IMS engineering team, and some handholding by Ben Armstrong and Jose Barreto to get it going. It was a really cool moment to see the VMs Live Migrate between all of the nodes and then start right back up when we started testing failover scenarios.
And yes, it was very painful as we committed to deploying all clusters with Server Core and still do so today. Though, with PowerShell it's a lot less painful.
EDIT: And, thanks!
Good. I'm glad somebody is doing things right. I'm pushing an initiative to be remove GUI from as many windows severs as possible. It doesn't go over too well with techs that aren't powershell guys.
-
@irj said in I think I am missing something about Hyper-V....?:
@phlipelder said in I think I am missing something about Hyper-V....?:
@irj said in I think I am missing something about Hyper-V....?:
@phlipelder said in I think I am missing something about Hyper-V....?:
We've been deploying virtualization solutions on Hyper-V since Longhorn/2008. We built our first cluster on the Intel Modular Server (probably the first to do so with Hyper-V) back in the day with our first IMS cluster deal following that up.
That's impressive because because from what I remember hyper-v was terrible in 2008.
Heh, it took 9 months of life, front-line access to the IMS engineering team, and some handholding by Ben Armstrong and Jose Barreto to get it going. It was a really cool moment to see the VMs Live Migrate between all of the nodes and then start right back up when we started testing failover scenarios.
And yes, it was very painful as we committed to deploying all clusters with Server Core and still do so today. Though, with PowerShell it's a lot less painful.
EDIT: And, thanks!
Good. I'm glad somebody is doing things right. I'm pushing an initiative to be remove GUI from as many windows severs as possible. It doesn't go over too well with techs that aren't powershell guys.
You really don't need PowerShell on Gui-less Windows server. Most everything can be done via a remote GUI tool on your admin workstation. It's extremely rare that I will ever need to RDP to a Windows server, GUI or not.
-
@irj said in I think I am missing something about Hyper-V....?:
@phlipelder said in I think I am missing something about Hyper-V....?:
@irj said in I think I am missing something about Hyper-V....?:
@phlipelder said in I think I am missing something about Hyper-V....?:
We've been deploying virtualization solutions on Hyper-V since Longhorn/2008. We built our first cluster on the Intel Modular Server (probably the first to do so with Hyper-V) back in the day with our first IMS cluster deal following that up.
That's impressive because because from what I remember hyper-v was terrible in 2008.
Heh, it took 9 months of life, front-line access to the IMS engineering team, and some handholding by Ben Armstrong and Jose Barreto to get it going. It was a really cool moment to see the VMs Live Migrate between all of the nodes and then start right back up when we started testing failover scenarios.
And yes, it was very painful as we committed to deploying all clusters with Server Core and still do so today. Though, with PowerShell it's a lot less painful.
EDIT: And, thanks!
Good. I'm glad somebody is doing things right. I'm pushing an initiative to be remove GUI from as many windows severs as possible. It doesn't go over too well with techs that aren't powershell guys.
I always wonder what "I'm not a powershell guy" means. I hear it a lot. Does it mean these people aren't fans or they just don't know it? I think a lot of us probably prefer bash here. I'm not a powershell guy--meaning i don't swear by it, but I still read on it and learn it.
-
@wirestyle22 said in I think I am missing something about Hyper-V....?:
@irj said in I think I am missing something about Hyper-V....?:
@phlipelder said in I think I am missing something about Hyper-V....?:
@irj said in I think I am missing something about Hyper-V....?:
@phlipelder said in I think I am missing something about Hyper-V....?:
We've been deploying virtualization solutions on Hyper-V since Longhorn/2008. We built our first cluster on the Intel Modular Server (probably the first to do so with Hyper-V) back in the day with our first IMS cluster deal following that up.
That's impressive because because from what I remember hyper-v was terrible in 2008.
Heh, it took 9 months of life, front-line access to the IMS engineering team, and some handholding by Ben Armstrong and Jose Barreto to get it going. It was a really cool moment to see the VMs Live Migrate between all of the nodes and then start right back up when we started testing failover scenarios.
And yes, it was very painful as we committed to deploying all clusters with Server Core and still do so today. Though, with PowerShell it's a lot less painful.
EDIT: And, thanks!
Good. I'm glad somebody is doing things right. I'm pushing an initiative to be remove GUI from as many windows severs as possible. It doesn't go over too well with techs that aren't powershell guys.
I always wonder what "I'm not a powershell guy" means. I hear it a lot. Does it mean these people aren't fans or they just don't know it? I think a lot of us probably prefer bash here. I'm not a powershell guy--meaning i don't swear by it, but I still read on it and learn it.
Not being a PowerShell guy to me means one can't efficiently script in PowerShell. That's not at all a requirement to administer a GUI-less Windows server.
There's no scripting at all needed to administer a GUI-less Windows server... none... To me, it just shows laziness and incompetence when someone says that.
To administer a server with PowerShell, you only need to memorize two commands, and such extreme basics that it just amazes me when people use the "i'm not a powershell guy" phrase.
Get-Command -Noun *whatever*(where "whatever" is a word related to what you want to work with on the server)For example, if you need to make a change to a network adapter on Hyper-V Server:
Get-Command -Noun *net*That will display enough for you to narrow it down. Once you find what you need, and you need examples or explanations:
Get-Help Set-NetAdapter -DetailedYou don't have to be "a PowerShell guy" for Windows server administration... and these cases only come up when there's no way to remote to your server using an RSAT tool.
You're in the exact same situation on Linux... nobody can remember all of the commands, but if you know how to search for a command and use help, you're golden.
There's really no difference in administering either one... the big difference lies in the scripting parts and general logic when diving down further than you need to past simple administration.
-
@obsolesce Bash makes a lot more sense to me than powershell, but part of the job is learning what you need to not necessarily just what you want to
-
@wirestyle22 said in I think I am missing something about Hyper-V....?:
@obsolesce Bash makes a lot more sense to me than powershell, but part of the job is learning what you need to not necessarily just what you want to
Meh, I feel the both make equal sense in their own way... I like PowerShell's verb-noun and flow, and also the basic logical way of bash.
-
@wirestyle22 said in I think I am missing something about Hyper-V....?:
@irj said in I think I am missing something about Hyper-V....?:
@phlipelder said in I think I am missing something about Hyper-V....?:
@irj said in I think I am missing something about Hyper-V....?:
@phlipelder said in I think I am missing something about Hyper-V....?:
We've been deploying virtualization solutions on Hyper-V since Longhorn/2008. We built our first cluster on the Intel Modular Server (probably the first to do so with Hyper-V) back in the day with our first IMS cluster deal following that up.
That's impressive because because from what I remember hyper-v was terrible in 2008.
Heh, it took 9 months of life, front-line access to the IMS engineering team, and some handholding by Ben Armstrong and Jose Barreto to get it going. It was a really cool moment to see the VMs Live Migrate between all of the nodes and then start right back up when we started testing failover scenarios.
And yes, it was very painful as we committed to deploying all clusters with Server Core and still do so today. Though, with PowerShell it's a lot less painful.
EDIT: And, thanks!
Good. I'm glad somebody is doing things right. I'm pushing an initiative to be remove GUI from as many windows severs as possible. It doesn't go over too well with techs that aren't powershell guys.
I always wonder what "I'm not a powershell guy" means. I hear it a lot. Does it mean these people aren't fans or they just don't know it? I think a lot of us probably prefer bash here. I'm not a powershell guy--meaning i don't swear by it, but I still read on it and learn it.
In this context it means "aren't savvy". It's not the right way to phrase it. It's "techs who don't know the systems that they work on and need a GUI to make it easy to find basic tasks." Has nothing intrinsic to do with PowerShell. It's CLI and shells in general.
-
@obsolesce said in I think I am missing something about Hyper-V....?:
@wirestyle22 said in I think I am missing something about Hyper-V....?:
@obsolesce Bash makes a lot more sense to me than powershell, but part of the job is learning what you need to not necessarily just what you want to
Meh, I feel the both make equal sense in their own way... I like PowerShell's verb-noun and flow, and also the basic logical way of bash.
I honestly find nothing redeeming about PS. It's better than nothing, but compared to no real world alternative is it a respectable scripting and automation language.
