Nowaker

The general unavailability of everything was caused by the system.

We're likely to use it in the future to choose the right provider and plan. However, I would definitely want to see DigitalOcean and Linode here.

"We spend the time and energy searching all over the web for cheaper reservations for you", are you really spending time on searching things manually? If so, I wouldn't pay anything for such a service, because you may apparently go on holiday and don't care about my reservation. If all is automatic, then I could go for it. However, then "spending time and energy" is a lie.

I believe anyone should be able to submit their reservation, along with credit card details. If you do find the cheaper rate somewhere, you charge them at that point and present with the offer.

BTW, A typo: we can try to ehysave you money.

VirtKick is open source, the code is on GitHub: https://github.com/virtkick

That's indeed extremely funny. I spotted it some time after I wrote the original post, then started writing my auto-trolling reply to self. ;)

I found the reason to visit Stackshare real quick. I just checked today's Analytics of my startup https://www.virtkick.io - 20% visits originates from stackshare, so I now have to claim it. ;) Quite funny, I tell ya.

It doesn't change the main concern, though. leanstack.io was the greatest site to find services.

Leanstack.io was extremely useful for discovering services. Needed best A/B testing tools? I used to go to Leanstack. I don't seem to find any reason to visit Stackshare. I don't really care whether Twitter uses Zendesk or Freshdesk.

You may be surprised that VirtKick wraps WebVirtMgr and uses it as a JSON API for libvirt. :-) This is a temporary solution but does the job - it allowed us to start real quick with features that users care about, instead of harnessing libvirt. (Of course, SSH key injection is in a scope of our project! https://github.com/virtkick/virtkick/issues/6)

I'm sorry but we missed your comment. Just created an issue to track this problem: https://github.com/virtkick/virtkick/issues/65 Please subscribe to the issue so you'll get the updates.

Oh, forgot to actually add something there. To give you a better understanding, it'll work the same way as on Heroku.

Cloud Foundry is a self-hosted Heroku. Both are PaaS (but it's you who provide the "P" with the former).

VirtKick is a self-hosted DigitalOcean. Both are very simple IaaS (but it's you who provide the "I" with the former)

Does it explain?

Thanks, can't wait!

Frankly, there are two mutually exclusive camps: free software and open source. I myself sympathize with free software (GPL) whereas RushPL with open source (MIT). Selling proprietary versions has never been the reason for CLA, though! We want to be able to re-release VirtKick under MIT (and automatically get rid of CLA) if we get funded, so businesses have no problems with it. (See https://news.ycombinator.com/item?id=8527999)

It's not our intention though, see https://news.ycombinator.com/item?id=8527999

Exactly right, we value existing tools - that's what makes DO so strong. :)

What one regards as a feature, other regard as misfeatures. If you like virt-manager, then VirtKick isn't really for you. We value a simple UI more than virt-manager, and REST API more than virsh. We don't say your way is wrong. It's just more difficult.

Existing libvirt clients, at least those that we know of, aren't super reliable though. libvirt stucks when there's too much happening on the HV, or denies jobs without even trying (e.g. when a pool has async jobs). A backend that schedules tasks for background execution is needed for that (and we have it), so even now we're not "just" a frontend for libvirt.

The use case is a very simple panel with zero virt knowledge needed to start.

Thanks for your comment.

Yep. Our 128 GB hypervisor wasn't enough. We redirected traffic to a static HTML prototype, so - at least - you guys have a chance to see the design and planned features. https://demo.virtkick.io/

Not at this point. We're focusing on features now. However, installing an alpha is a matter of 4 commands, give it a try: https://github.com/virtkick/virtkick-starter#virtkick-take-c...

Not at this point (we mount an ISO as CD), but we've got it planned: https://github.com/virtkick/virtkick/issues/6

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

We don't intend to sell modified proprietary versions. In fact, we planned to re-release it under MIT. Just see on the bottom: "Get excited: (...), MIT..." http://goo.gl/w64Ic5 from https://www.indiegogo.com/projects/virtkick-take-cloud-back We'd just want to get funded, so we can work on it without worrying about other things.

Oh, that's relatively easy at the moment. Put your distro in these two files. ISO will be autodownloaded by `virtkick-starter` script, and the distro will appear on VM create screen. It'll be configurable in the settings in a month, of course. http://goo.gl/u1LKwi http://goo.gl/j1j80f

"Pain to configure" is a blocker here, though. That's why we sacrifice flexibility for simplicity. OpenStack is great for environments that need it - VirtKick won't fit them.

Flynn, Deis, Heroku are PaaS - they are focused on applications.

VirtKick is like DigitalOcean or Linode - they are focused on machines (and containers, that you think of as machines). You install it on your Linux desktop (for localhost hacking), or home or dedicated server (for something more).

Will try to express it a little bit better. Thanks for your feedback.

Our intention is that you share code back to the project if you modified it and added some new great features. :) If I'm not wrong, it only applies to the modified source code, and not the data/machines that you work with. http://stackoverflow.com/a/18406382/504845

Excactly right - plus on remote hypervisors too.

External monitoring integration, and off-site status page, will be actual features of VirtKick. Think of VirtKick is a 1-click installable panel that you can use both on your desktop and as a VPS provider. Instead of paid features, we want it to be forever free - instead, we aim to be crowdfunded. https://www.indiegogo.com/projects/virtkick-take-cloud-back

I didn't spot your question. The best way would be to contribute. :) We currently have virtkick-starter, a bunch of scripts that set everything up. You could try it out on Guix and improve if needed. https://github.com/virtkick/virtkick-starter

Sorry for that. The hypervisor died, which results in errors like this. We use Bugsnag so we've got all the stacktraces - we'll handle distasters. :)

https://www.virtkick.io/ works OK, but it seems you killed https://alpha.virtkick.io/ (our 128 GB hypervisor wasn't enough to handle load). https://demo.virtkick.io/ is a static HTML prototype to get familiar with planned features.

A complete re-working - as OpenStack is too big if you're not a corporation with a very big infrastructure.