3 ms·

But according to a sibling comment, you support containers too (like libvirt)... you must already have an abstraction layer between you and QEMU. libvirt expose

by catern 9y ago

But according to a sibling comment, you support containers too (like libvirt)... you must already have an abstraction layer between you and QEMU. libvirt exposes pretty much every QEMU feature in existence, anyway, and allows passing through raw command line arguments to QEMU if you need it. How does minimega run, if not with a daemon? You can certainly copy a libvirt binary + deps to a bunch of hosts and run it, nothing stopping that... My guess is that minimega just grew out of your bespoke internal tools, and you never seriously tried to get rid of those tools and replace them with a more standard tool, like libvirt. It's disappointing. We're never going to get a viable alternative to Openstack if people keep writing things from scratch instead of reusing existing tools.

mdekkers 9y ago
My guess is that minimega just grew out of your bespoke internal tools, and you never seriously tried to get rid of those tools and replace them with a more standard tool, like libvirt. It's disappointing I must have missed the toolchain-police memo that you can only work on one toolchain. This stuff works for them, has a few cool features, and sounds interesting - I will be trying it out. Nothing wrong with growing out of your internal tools, and open sourcing them. By your reckoning, we'd all still be messing around with 386BSD or MINIX
- catern 9y ago
  There's also nothing wrong with wanting tools to reuse existing platforms rather than reinvent the wheel. minimega looks neat, but I don't want to sacrifice all the other libvirt-based tooling that's out there. If minimega's virtualization abstraction for a single host was somehow superior to libvirt's, then I would be happy to see them forging ahead. But it's not.
  - mdekkers 9y ago
    minimega looks neat, but I don't want to sacrifice all the other libvirt-based tooling that's out there Great! So libvirt is a good fit for you, awesome. Maybe other people have other needs or wants, and now they have an alternative that might suit them better. Isn't Open Source neat? TBH, your argument is starting to sound very much like "libvirt is my tool of choice and I'm pissed that not every available person is working on the betterment of my preferred tool, instead choosing to work on something that is of no interest to me"

by catern 9y ago

mdekkers 9y ago

My guess is that minimega just grew out of your bespoke internal tools, and you never seriously tried to get rid of those tools and replace them with a more standard tool, like libvirt. It's disappointing I must have missed the toolchain-police memo that you can only work on one toolchain. This stuff works for them, has a few cool features, and sounds interesting - I will be trying it out. Nothing wrong with growing out of your internal tools, and open sourcing them. By your reckoning, we'd all still be messing around with 386BSD or MINIX

catern 9y ago
There's also nothing wrong with wanting tools to reuse existing platforms rather than reinvent the wheel. minimega looks neat, but I don't want to sacrifice all the other libvirt-based tooling that's out there. If minimega's virtualization abstraction for a single host was somehow superior to libvirt's, then I would be happy to see them forging ahead. But it's not.
- mdekkers 9y ago
  minimega looks neat, but I don't want to sacrifice all the other libvirt-based tooling that's out there Great! So libvirt is a good fit for you, awesome. Maybe other people have other needs or wants, and now they have an alternative that might suit them better. Isn't Open Source neat? TBH, your argument is starting to sound very much like "libvirt is my tool of choice and I'm pissed that not every available person is working on the betterment of my preferred tool, instead choosing to work on something that is of no interest to me"