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.

I disagree - OpenStack scales down perfectly to two-machine or even (one-machine) deployments (if you don't want HA).

It is a pain to configure, but that's the price you pay for flexibility, future-proofing (scalability) and its' true community development model.

"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.

That's really not true. I run it on small deployments all the time: http://www.stackgeek.com/guides/gettingstarted.html

I have used your scripts and I'm quite grateful for the time they have saved me. However, the end result is not a fully functional OpenStack installation. I have no idea how much longer that will take, I'm still working on getting public and private networks configured properly, getting floating IPs to work at all, etc.

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.

Feel free to jump in the Gitter or email me about them. The networking stuff is usually the last mile in OpenStack and is hard to script for a variety of systems. Happy to add to them if I can make it easier for you!

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

VirtKick - a simple, open source cloud panel: https://www.virtkick.io/

Virtual machines and Docker containers made easy. 1-click install on a desktop or server, auto-configure hypervisors, super-usable interface. This week we're releasing a standalone alpha (almost one-click). https://github.com/virtkick/virtkick-starter

tl;dr DigitalOcean for open source.

Works good for me, en_US.

Holy smokes, another Электроника game I played 20 years ago. http://www.pica-pic.com/#/space_bridge/ I'll definitely ask my parents to look for this game, maybe it's still somewhere there.

Ah, Electronika. They made an interesting PDP-11 clone desktop computer: http://en.wikipedia.org/wiki/UKNC

http://en.wikipedia.org/wiki/Electronika

It's actually a brand name. A while lot of different consumer- and professional-grade products were sold under that brand (follow the link to Russian Wikipedia to see the full list)

Found the source here: https://github.com/pawel-winiecki/nu-pogodi-html5-game

Of course! I've been watching it for an hour now (https://www.youtube.com/watch?v=ko6UEwT9i20). I wanted to find something about Nu Pogodi and found the hand-held game I played ~20 years ago.

Maybe place all the marks in the town center?

That would diminish the usefulness of the map quite a bit. People will be interested in this on a ward-by-ward basis - I'm pretty sure. A small random 'shuggle' should be enough to help.

Although I use Chef on most of my servers, I like Rex because it doesn't require any client/agent running on the machine.

The books that I think are must-read are "The Pragmatic Programmer" and "Apprenticeship Patterns". I learned a lot from them.

I'm aware you expect some quick tips from HN though. Have a look at my old blog posts that summarize these books. While 3 years old and written in Polish, Google translated it very well. Direct links to the translations: https://bit.ly/1oZiidn and https://bit.ly/1w8ELhY.