What is KVM Best Management Tools in 2017?
-
@olivier said in What is KVM Best Management Tools in 2017?:
@scottalanmiller Exactly. That's very strange that a new fresh project like Kimchi is made on 1:1 basis. It baffles me.
It doesn't baffle me, but that's not KVM's fault. That's up to the Kimchi-project devs.
-
@romo said in What is KVM Best Management Tools in 2017?:
Maybe that could help as well, they mention they are not fully stable but they are using them in production.
Um.... lol
-
@romo said in What is KVM Best Management Tools in 2017?:
DigitalOcean's apparently using their own built go-qemu and go-libvirt which they opensourced
https://blog.digitalocean.com/introducing-go-qemu-and-go-libvirt/
Maybe that could help as well, they mention they are not fully stable but they are using them in production.
Thanks for the precious hint! I'll take a look
(right now, if I had to build something on API level, I would do it in Rust, but that's just my 2 cents) -
About LibVirt:
The libvirt project strongly recommends against talking to the RPC interface directly. They consider it to be a private implementation detail with the possibility of being entirely rearchitected in the future.
Great.
-
still I do not find the opened source of RHEV
maybe this ovirt page refers to the same but you just need the api. if ovist is the source then you had to deal with the http wrapper around VDSM on top of libvirt on top of qemu/kvm.
-
That's what I feared
edit: thanks for the links!
-
kimchi has always been a single server solution. In the beginning it was ubrellaed (<-?WTF?) by ovirt as web gui for their nodes. eventually it has been replaced by cockpit.
-
@matteo-nunziati said in What is KVM Best Management Tools in 2017?:
still I do not find the opened source of RHEV
Who said that RH had to open source everything?
@matteo-nunziati said in [What is KVM Best Management Tools in 2017?]> maybe this ovirt page refers to the same but you just need the api. if ovist is the source then you had to deal with the http wrapper around VDSM on top of libvirt on top of qemu/kvm.
How else would you access the API without http? Something has to listen.
-
@jaredbusch said in What is KVM Best Management Tools in 2017?:
@matteo-nunziati said in What is KVM Best Management Tools in 2017?:
still I do not find the opened source of RHEV
Who said that RH had to open source everything?
Not they have to. Simply they have worked a lot to open source their virtualization infrastructure. Ovirt was born by the rewriting of the original orchestration tool written by the KVM company.
@matteo-nunziati said in [What is KVM Best Management Tools in 2017?]> maybe this ovirt page refers to the same but you just need the api. if ovist is the source then you had to deal with the http wrapper around VDSM on top of libvirt on top of qemu/kvm.
How else would you access the API without http? Something has to listen.
http is not the issue here. VDSM is. very complex beast. written in java.
-
When I start to read "java", I got a gag reflex
-
it was 2008 citrix acquired xen. red hat reacted buying the only other solution on the market. kumranet were strong in pushing their own orchestration solution.
part of it (the core: KVM) was open. tools givin added value (orchestrator) were closed and billed. don't know why but kumranet written everything in java. Maybe faster to develop then c++. less crosscompile (think mainframes). maybe node or python where simply too young or they where not happy with python speed - node was young for sure.
Red hat gots the entire blob. they have reworked it not rewritten.
-
2007 for Xen and Citrix
(had the chance to meet the former Citrix CEO who did the operation)So for KVM, it makes sense. I think we still feel that lack of fully opened/clear API on top of it, and that's almost the reason of why vendors are making money on that: providing a turnkey stuff on top of it.
-
@olivier said in What is KVM Best Management Tools in 2017?:
When I start to read "java", I got a gag reflex
Java has its place.
This isn't it.
-
@scottalanmiller That's fair to say that yes
-
-
@olivier YUP! and the http server is plain httprequest stuff from CPython, http framework around or stuff like uwsgi!
-
@olivier here is the opposite side: an example of the ovirt->libvirt communication channel
-
@olivier are you listening ??
Anton Gostev of Veeam (google him, if you don't know who he is) has a once week email digest he sends every Sunday.
I thought this was interesting...(quoting parts of this Sunday's email):"However, personally I don't see KVM presenting any significant threat to the leading hypervisors any time soon for a simple reason – it needs solid management layer before it can be successful in any market. In simple words, there's no "vCenter for KVM" available today – just a few point solutions which are rather exceptions proving the issue. Proxmox is a great tool for SMB only; Nutanix AHV does not support deployment into the existing, "classic" (non-HCI) infrastructures; and of course there's OpenStack – flexible and powerful solution for those few with an army of developers on staff. So, the issue with KVM is currently not with the hypervisor itself, and there's a huge opportunity to make it wildly successful even in its current state (as Nutanix already proved) – any ISV who decides to take up on this task has all the chances to become the next VMware, albeit in the shrinking "on-prem data center" market."
-
@fateknollogee said in What is KVM Best Management Tools in 2017?:
@olivier are you listening ??
Anton Gostev of Veeam (google him, if you don't know who he is) has a once week email digest he sends every Sunday.
I thought this was interesting...(quoting parts of this Sunday's email):"However, personally I don't see KVM presenting any significant threat to the leading hypervisors any time soon for a simple reason – it needs solid management layer before it can be successful in any market. In simple words, there's no "vCenter for KVM" available today – just a few point solutions which are rather exceptions proving the issue. Proxmox is a great tool for SMB only; Nutanix AHV does not support deployment into the existing, "classic" (non-HCI) infrastructures; and of course there's OpenStack – flexible and powerful solution for those few with an army of developers on staff. So, the issue with KVM is currently not with the hypervisor itself, and there's a huge opportunity to make it wildly successful even in its current state (as Nutanix already proved) – any ISV who decides to take up on this task has all the chances to become the next VMware, albeit in the shrinking "on-prem data center" market."
Bah, who needs GUI based management tools, right @scottalanmiller?
-
Ha, wonder why @scale doesn't just go all CLI since that's what a "real" sysadmin would use!
