51–60 of 96 posts
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).
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 actually wanted to create something like this. Does it do ssh key injection when VMS are created?
Earlier quoted context omitted.
A complete re-working - as OpenStack is too big if you're not a corporation with a very big infrastructure.
That's really not true. I run it on small deployments all the time: http://www.stackgeek.com/guides/gettingstarted.html
With Juno imminent, I might just start over and hope the Juno installation isn't so difficult, though that doesn't seem to be a top priority for the developers.
VirtKick is closer to a scale that I have time to manage, I think. Of course there are tradeoffs; with the big players running OpenStack in production, security fixes are available quickly and I love/hate the short release cycle. VirtKick has layers of security risks and (so far) no big-money contributors who need to get fixes out quickly.
* No virt-manager with SPICE, networking configuration, and other features
* No virt-install for very easy creation of VMs, even straight from distro repository URLs
* No virsh for command-line management
* In general, no seamless use of any of the vast ecosystem of tools around libvirt
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.
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.
Thanks for your comment. UI comes first as every user will hit it. API comes next. We planned DigitalOcean-compatible API altogether with a CLI. Looks like we removed this from our website by mistake (will get it back real quick), but it's listed in our IGG campaign: https://www.indiegogo.com/projects/virtkick-take-cloud-back
some documentation...?
Because DigitalOcean, basically, is a way to get VMs without self-hosting them!
It seems we have HN'ed the service; after creating a Debian image: "internal error: pool 'HDD' has asynchronous jobs running."