KVM or VMWare
-
@stacksofplates said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
I understand NDAs but you have to at least be able to give some more information than "major vendor".
What information would that be? LOL.
Literally anything. I can tell you that I am working with one of the big four right now. Can't say which one, but I can tell you that.
The big four vendors? This isn't a vendor THAT big. I'm not sure how to give away anything about this vendor without it being obvious quickly. Nothing like the size of the big four. But a vendor that has an IT arm.
-
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
I understand NDAs but you have to at least be able to give some more information than "major vendor".
What information would that be? LOL.
Literally anything. I can tell you that I am working with one of the big four right now. Can't say which one, but I can tell you that.
The big four vendors? This isn't a vendor THAT big. I'm not sure how to give away anything about this vendor without it being obvious quickly. Nothing like the size of the big four. But a vendor that has an IT arm.
Big four accounting.
-
@stacksofplates said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
Who was this? People don't believe things you say because you make statements like this and never say who it is. It sounds completely made up.
In IT rarely can you disclose the players involved.
That's just not true. Everyone blasts their customers on their sites. The number of times you can't give any information is very low.
When I worked for the big Wall St. firm, you could never mention them, even in a position context. Red Hat threw a shit fit when I posted that we never needed to call the vendor (Red Hat) for support because their stuff was always able to be fixed by internal IT. They were furious because it suggested that you could get by without paying for support.
They brought reams of papers to the bank and demanded that I be fired. Legal went through and pointed out that I never mentioned the bank so they could go F themselves. That it was positive or negative wasn' the point, few companies are okay with their IT teams discussing them. Most have NDAs. And especially when they make mistakes or do something embarrassing.
No professional IT person is going to disclose customers making mistakes, NDA or not.
-
@stacksofplates said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
I understand NDAs but you have to at least be able to give some more information than "major vendor".
What information would that be? LOL.
Literally anything. I can tell you that I am working with one of the big four right now. Can't say which one, but I can tell you that.
The big four vendors? This isn't a vendor THAT big. I'm not sure how to give away anything about this vendor without it being obvious quickly. Nothing like the size of the big four. But a vendor that has an IT arm.
Big four accounting.
OH, okay. I do work for someone in the Fortune 10. But this isn't them. So that doesn't help, lol.
-
@stacksofplates said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
Taking a clone is fine, but now you either have to maintain that template or it gets old and you have an ancient template sitting somewhere that is just as out of date as the initial OS install, or nearly (sure it'll have SOME updates.)
This is one place where KVM shines, but only libvirt/QEMU. You can update templates without spinning them up through libguestfs and the next time the template is cloned, the clone has all of the updates.
KVM has a lot of features like this, but it needs automated, is limited to libvirt (which cuts down the number of places KVM is deployed), and needs separate tools installed which are only cli based.
If KVM had APIs (not just REST APIs) like VMware, the whole landscape would change, but they don't. The APIs are hard to use and don't have all of the features you would expect. You can't even clone a system with virsh. You need a separate tool to do a lot of manual work behind the scenes.
What does the method of automation matter to making decisions on what to use? One uses an API, the other standard UNIX based tools, both accomplish the same thing.
-
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
I understand NDAs but you have to at least be able to give some more information than "major vendor".
What information would that be? LOL.
Literally anything. I can tell you that I am working with one of the big four right now. Can't say which one, but I can tell you that.
The big four vendors? This isn't a vendor THAT big. I'm not sure how to give away anything about this vendor without it being obvious quickly. Nothing like the size of the big four. But a vendor that has an IT arm.
Big four accounting.
OH, okay. I do work for someone in the Fortune 10. But this isn't them. So that doesn't help, lol.
If it was a vet clinic, and we service hundreds, I could say more specifically "a vet clinic with five doctors in the north east" and give nothing away. But more unique businesses, especially those that are known throughout the industry, you can't.
-
@travisdh1 said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
Taking a clone is fine, but now you either have to maintain that template or it gets old and you have an ancient template sitting somewhere that is just as out of date as the initial OS install, or nearly (sure it'll have SOME updates.)
This is one place where KVM shines, but only libvirt/QEMU. You can update templates without spinning them up through libguestfs and the next time the template is cloned, the clone has all of the updates.
KVM has a lot of features like this, but it needs automated, is limited to libvirt (which cuts down the number of places KVM is deployed), and needs separate tools installed which are only cli based.
If KVM had APIs (not just REST APIs) like VMware, the whole landscape would change, but they don't. The APIs are hard to use and don't have all of the features you would expect. You can't even clone a system with virsh. You need a separate tool to do a lot of manual work behind the scenes.
What does the method of automation matter to making decisions on what to use? One uses an API, the other standard UNIX based tools, both accomplish the same thing.
Because one is easy to write integrations with, the other is not. The landscape would change because people and companies could easily create integrations and tools.
-
@stacksofplates said in KVM or VMWare:
The landscape would change because people and companies could easily create integrations and tools.
did you mean... If?
-
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
The landscape would change because people and companies could easily create integrations and tools.
did you mean... If?
Yeah I said that earlier here:
If KVM had APIs (not just REST APIs) like VMware, the whole landscape would change, but they don't.
-
@stacksofplates said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
The landscape would change because people and companies could easily create integrations and tools.
did you mean... If?
Yeah I said that earlier here:
If KVM had APIs (not just REST APIs) like VMware, the whole landscape would change, but they don't.
I thought so, but you typed "because" and it didn't quite make sense. Yes, I agree, cool APIs that make loads of automation easily consumable by third party applications would be a great upgrade and make it even more broadly applicable.
-
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
@stacksofplates said in KVM or VMWare:
The landscape would change because people and companies could easily create integrations and tools.
did you mean... If?
Yeah I said that earlier here:
If KVM had APIs (not just REST APIs) like VMware, the whole landscape would change, but they don't.
I thought so, but you typed "because" and it didn't quite make sense. Yes, I agree, cool APIs that make loads of automation easily consumable by third party applications would be a great upgrade and make it even more broadly applicable.
IF they had that, I would change my opinion about the easier tool to use. Sure cloud providers can write the tooling for KVM (libvirt or not) but VMware makes things much more consumable.
For instance, you want to give someone their own storage space and access to only their VMs. Have fun with bare KVM. You need to use polkit and write custom rules around Unix users who can access those VMs. But that only manages the guest domain. Not the networking or actual storage. In VMware, it's just creating a folder and giving permissions to a user in that folder with some resource scoping.
Bare KVM is fine if you have one person or a couple people with the same privileges managing systems. Outside of that it gets really hard really fast.
Edit: forgot the VMware side.
-
Let's talk about why Microsoft are not releasing Hyper-V Server no more. I should imagine they were eventually going to kill it, but they have done it quite quickly then imagined.
-
@stuartjordan said in KVM or VMWare:
Let's talk about why Microsoft are not releasing Hyper-V Server no more. I should imagine they were eventually going to kill it, but they have done it quite quickly then imagined.
Because they want you to use Azure Stack HCI instead.
-
@obsolesce I should of imagined it had something to do with Azure.
-
@stuartjordan said in KVM or VMWare:
@obsolesce I should of imagined it had something to do with Azure.
Probably has a little something to do with the $10 per core/month fee as well.
-
@obsolesce said in KVM or VMWare:
@stuartjordan said in KVM or VMWare:
Let's talk about why Microsoft are not releasing Hyper-V Server no more. I should imagine they were eventually going to kill it, but they have done it quite quickly then imagined.
Because they want you to use Azure Stack HCI instead.
Not instead, in addition to. Azure Stack HCI is built on Hyper-V and a number of other technologies. ASHCI is MS doubling down on Hyper-V, not abandoning it.
But this is like saying that they want you to buy Datacenter instead of a desktop version of Windows. Both are Windows, one is really expensive, one is really cheap. Sure they "want" you to pay for the expensive one. But that doesn't imply that they would make the crazy move of not still promoting and providing the free one.
Virtualization isn't a game where you can risk not having a free version. VMware owns the entire space of "paid only" and their options are super cheap. Azure Stack HCI has no cheap option whatsoever. This is a premium product. Maybe worth it, maybe not, but not something cheap. Loads of companies could never consider it because it is just too costly for much of the SMB. With servers typically being 16+ cores, that makes ASHCI $160/mo just for the integration of components. That adds up super fast for an SMB, so it's not for everyone.
-
@scottalanmiller said in KVM or VMWare:
Not instead, in addition to.
If Hyper-V Server as a single product is going away, then it can't be "in addition to". He said Hyper-V Server, not Hyper-V.
@scottalanmiller said in KVM or VMWare:
ASHCI is MS doubling down on Hyper-V, not abandoning it.
Right, not what I was referring to. He said, "Hyper-V Server". We all know that Hyper-V is not going away.
-
@obsolesce said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
Not instead, in addition to.
If Hyper-V Server as a single product is going away, then it can't be "in addition to". He said Hyper-V Server, not Hyper-V.
@scottalanmiller said in KVM or VMWare:
ASHCI is MS doubling down on Hyper-V, not abandoning it.
Right, not what I was referring to. He said, "Hyper-V Server". We all know that Hyper-V is not going away.
So basically, correct me if I am wrong, one has to pay to use Hyper-V going forward in the future (After Hyper-V Server 2019 is EOL)?
-
@pmoncho said in KVM or VMWare:
@obsolesce said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
Not instead, in addition to.
If Hyper-V Server as a single product is going away, then it can't be "in addition to". He said Hyper-V Server, not Hyper-V.
@scottalanmiller said in KVM or VMWare:
ASHCI is MS doubling down on Hyper-V, not abandoning it.
Right, not what I was referring to. He said, "Hyper-V Server". We all know that Hyper-V is not going away.
So basically, correct me if I am wrong, one has to pay to use Hyper-V going forward in the future (After Hyper-V Server 2019 is EOL)?
Depends on the use case, but yes. I haven't looked much into it because I don't use "Hyper-V" anymore outside of my Windows Desktop and Laptop.
-
@obsolesce said in KVM or VMWare:
@scottalanmiller said in KVM or VMWare:
Not instead, in addition to.
If Hyper-V Server as a single product is going away, then it can't be "in addition to". He said Hyper-V Server, not Hyper-V.
@scottalanmiller said in KVM or VMWare:
ASHCI is MS doubling down on Hyper-V, not abandoning it.
Right, not what I was referring to. He said, "Hyper-V Server". We all know that Hyper-V is not going away.
All of this @scottalanmiller. To my knowledge, no one in this thread said Hyper-V was going away.
