amuck-landowner

VirtKick - a simple, open source alternative to SolusVM

Jade

NodeServ
Verified Provider
I like the look of this, and the idea that the support part is right within the same interface is wow.
 
Last edited by a moderator:

MeanServers

New Member
Verified Provider
Nice simple, clean layout though from the looks of the demo. Keep up the good work!
 
Last edited by a moderator:

mhosts

New Member
Verified Provider
UI looks good as others have said.

However, your website claims that your app will be fully open source, yet your github repo does not have any code other than the web demos.

Are you looking to develop this in the open source community model? or are you looking to sell your service for a profit once it is done (if so, it's not really open source)?
 

Zigara

New Member
I was already not impressed with his mock-ass Ruby web demos with no application logic, then I saw https://www.virtkick.io/become-a-sponsor.html and tried out the 'core' he plans on ripping.

He plans on using https://github.com/retspen/webvirtmgr as a 'core'.

https://github.com/retspen/webvirtmgr/wiki/Screenshots

It's a fully functional panel written in Python. It's beautiful. Everything works very smoothly. It's written by some guy in Ukraine.

How about you contribute to the webvirtmgr project directly instead of trying to get sponsorship for writing a piss-poor Ruby web interface for it?
 

Nowaker

New Member
However, your website claims that your app will be fully open source, yet your github repo does not have any code other than the web demos.
And it is 100% open source! It just meant there was no other code. :) The development of the real webapplication started just now. Let me paste what I wrote on lowendtalk.com. This describes why I started with UI prototyping, and not the real code.

  1. UI prototype came first. It's the most important thing. Since VirtKick is user focused, UI has to be tested out in the wild as fast as possible. It allowed us to find and address UI problems really fast, and gather feedback from many people. And, what's important, we can could things out before any irreversable (or at least costly) backend/code decisions are taken.
  2. Now comes the real web application and a small backend server that talks to WebVirtMgr. That's right - an existing, working solution. (We are currently at the beginning of this step)
  3. Once things are sorted out, we will switch to our backend. No hurry with it. We will do that when WebVirtMgr starts limiting us. And it will when we start working on support for Xen, OpenVZ, Bhyve, Amazon EC2 or Docker containers.

Hope this clarifies that VirtKick indeed is 100% open source right from the start.
 

Nowaker

New Member
Oh, @Zigara posted at the same time. WebVirtMgr is a frontend for KVM and libvirt only. It's not meant to support any other technologies, nor it's to provide billing, support, auto-configure hypervisors, download ISOs of most interesting distros, integrate with DNS and many more. If you like WebVirtMgr and you don't need anything else, that's fine. I like WebVirtMgr too for some use cases.

Open souce is about using other's code to build bigger things. I have never hidden the fact the first version will use WebVirtMgr so that VirtKick has got faster Time to Market. My very first answer on lowendtalk.com: http://lowendtalk.com/discussion/comment/707699/#Comment_707699
 
Last edited by a moderator:

Nowaker

New Member
Thanks for letting me know! Sent you a priv message @GIANT_CRAB so we can track down the reason.

EDIT: The reason is disconnect.me extension. Will try to work it around.
 
Last edited by a moderator:

hostinghouston

Member
Verified Provider
This is awesome. I am interested to see it grow and more virtualization technologies to be supported along with features and functions. Good job and thanks for sharing.
 
Top
amuck-landowner