Looking forward to it, you'll see my contribution!
Thanks, can't wait!
Show HN: VirtKick – Self-hosted Digital Ocean
81–90 of 96 posts
Re: Show HN: VirtKick – Self-hosted Digital Ocean
#82How does this compare to something like Cloud Foundry?
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?
Re: Show HN: VirtKick – Self-hosted Digital Ocean
#83It seems we have HN'ed the service; after creating a Debian image: "internal error: pool 'HDD' has asynchronous jobs running."
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/
another thing: all the add-on links redirect to the same DNS add-on
Re: Show HN: VirtKick – Self-hosted Digital Ocean
#84Earlier quoted context omitted.
A complete re-working - as OpenStack is too big if you're not a corporation with a very big infrastructure.
It would be nice to see an architecture diagram, or just a list of the planned components and their responsibilities.
Just made something that can answer few questions: https://www.virtkick.io/dia.svg
Re: Show HN: VirtKick – Self-hosted Digital Ocean
#85Earlier quoted context omitted.
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/
another thing: all the add-on links redirect to the same DNS add-on
Oh, forgot to actually add something there. To give you a better understanding, it'll work the same way as on Heroku.
Re: Show HN: VirtKick – Self-hosted Digital Ocean
#86Re: Show HN: VirtKick – Self-hosted Digital Ocean
#87How does this compare to something like Cloud Foundry?
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?
Yes. Quite clear actually too.
My follow-up then would be how would this compare to OpenStack? If they serve the same purpose, where do you want to differentiate from OpenStack?
Re: Show HN: VirtKick – Self-hosted Digital Ocean
#88Earlier quoted context omitted.
> I want my contributions to the free software community to remain free. And you don't feel that the AGPLv3 ensures that...? Or you mean "I don't want my contributions to be distributed under any other license"?
If you have a contributor assignment, the assignee can choose to release the changes under a proprietary license.
> If you have a contributor assignment, the assignee can choose to release the changes under a proprietary license.
Exactly! Hence my request for clarification (see above).
If more explanation is necessary: What davexunit is saying is that he wants his contributions to remain free. The AGPLv3 ensures that, even with copyright assignment. But what I guess davexunit really means is that he wants to be sure that all contributors, present and future, are locked into the AGPLv3 forever. I'm not saying the latter is wrong, I'm just saying you should call a spade a spade.
Re: Show HN: VirtKick – Self-hosted Digital Ocean
#89Trying 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'
This is because I don't use port 22 for SSH. Can I fix this easily?
Re: Show HN: VirtKick – Self-hosted Digital Ocean
#90I've been following this for a while, and it looks like an awesome way to roll your own cloud!