Red Hat Bugzilla – Bug 815136
libvirt should support some sort of 'ipmi server'
Last modified: 2016-10-28 12:53:45 EDT
Description of problem:
It would be especially convenient if libvirt supported some sort of 'ipmi server' so that sysadmins could plug kvm hosts and others into their existing ipmi management infrastructure.
Via ipmitool we would then be able to get virsh consoles, power status and so on.
There are probably some issues such as how would this work when a virtual machines migrates to a different host? My recommended solution would be to simply have the ipmi run on the primary virtual IP that is supporting the cluster and always connect to that when looking for your host. When the VM moves, so does the IP, and ipmi always goes to the right place.
Thanks in advance!
In general, some of libvirt's functionality could probably be made to work through IPMI, so if you're interested in submitting patches, you should take this up on the mailing list. It's a tremendous amount of work, though, and I'm unsure of what limitations there are on implementing IPMI. You'd want to confirm that there aren't any licensing limitations before you start.
One caveat wrt migration: libvirt is explicitly a single node management api so if you really need IPMI to work with migration, you would need to write a stand-alone daemon that implements the IPMI interface and talks to multiple hosts. IMO, a stand-alone daemon is probably the right approach in any case, rather than trying to bundle this functionality into libvirt itself, but that's just my $.02.
None of that is meant to discourage you--it's a cool idea and you should raise it on the upstream list if you think you could implement it. I'm sure you'd get some good feedback.
I appreciate the comments!
The licensing issue (if there is one) didn't even occur to me :(
My plate is kind of full for the upcoming while, so if it's okay, I'll leave this idea here as a seed, and maybe it will grow. -- Sorry for not sticking this on the mailing list first, I figured the libvirt people were using mostly this bugzilla anyways.
Since this seed never really grew, keeping this bug open doesn't accomplish much except add mass to the bug list. closing