This is an awesome project! Thanks for choosing the AGPLv3!<p>I tried to create a VM on the demo site, and got a nice Ruby error message next to the VM's name on the 'Machines' page: undefined method `+' for nil:NilClass<p>Still, I'm very excited about this!<p>If anyone from the project reads this: Where is the appropriate place to request support for an additional GNU/Linux distribution? I would love to get GNU Guix running on this.<p>Edit: It seems that I have jumped the gun with my enthusiasm for this project. They will be selling proprietary re-licensed versions as a reward and require copyright assignment for contributions.<p>VirtKick, please reconsider your decision to require copyright assignment. I want my contributions to the free software community to remain free.
This looks cool, but I can't see why contributors should assign you copyright so you can sell proprietary versions of VirtKick. Very few free software projects have copyright assignment requirements (GNU being a notable exception).
So what exactly is the advantage of using this layer over the existing libvirt ecosystem? If this is supposed to manage your VMs for you instead of you using the existing libvirt tools, I can see a number of disadvantages.<p>* No virt-manager with SPICE, networking configuration, and other features<p>* No virt-install for very easy creation of VMs, even straight from distro repository URLs<p>* No virsh for command-line management<p>* In general, no seamless use of any of the vast ecosystem of tools around libvirt<p>Is the only advantage that it supports Docker? In that case, why not just add support for Docker into libvirt, and Docker images into virt-install?
Is the advantage that it's a web UI for libvirt? There are certainly plenty of those already, but I guess creating another one is fine.
I really don't see the use-case.
So just for clarity. I'll be able to download your source/package, install, go to the web interface and start spinning up VM instances on the same machine?<p>Are the extras like monitoring 3rd party integrations that I'll have to pay for, or actual features of VirtKick?
This looks interesting: I've often wanted something with more features than just kvm+libvirt but less complexity than OpenStack or other "private cloud" projects. The one thing that worries me about the pitch is the emphasis on the management panel. I don't want to create a VM in 5 clicks, I want to create it in one API call.
I feel as though this is one step above just a web page with an email box. Aside from listing a suite of popular OSS, you haven't explained what this app does. Is it similar to Panamax in that it offers you a UI, but only for one box / Flynn or Deis which is trying to create an open source Heroku / something completely different?
This is a great project. However, given the nature of the project and the license, would this then require any software hosted with it to be AGPLv3? Could I run software that is a mix of Apache, MIT, and Erlang Public License in a VirtKick container without violating AGPLv3?
Trying this, seeing a LOT of '[virtm] libvirt: XML-RPC error : Cannot recv data: ssh: connect to host localhost port 22: Connection refused: Connection reset by peer'<p>This is because I don't use port 22 for SSH.
Can I fix this easily?
It seems we have HN'ed the service; after creating a Debian image: "internal error: pool 'HDD' has asynchronous jobs running."
Without any judgement over the project and its quality, I would not call it "Self-hosted DO".<p>Because DigitalOcean, basically, is a way to get VMs without self-hosting them!