6 ms·

So what is this? A project based off of openstack, a complete re-working of an openstack-like environment or something different?

Nowaker 12y ago
A complete re-working - as OpenStack is too big if you're not a corporation with a very big infrastructure.
- deleted 12y ago
  [deleted]
- q3k 12y ago
  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.
  - Nowaker 12y ago
    "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.
- kordless 12y ago
  That's really not true. I run it on small deployments all the time: http://www.stackgeek.com/guides/gettingstarted.html http://www.stackgeek.com/guides/gettingstarted.html
  - faster 12y ago
    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.
    - kordless 12y ago
      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!
- sciurus 12y ago
  It would be nice to see an architecture diagram, or just a list of the planned components and their responsibilities.
  - RushPL 12y ago
    Just made something that can answer few questions: https://www.virtkick.io/dia.svg https://www.virtkick.io/dia.svg

Nowaker 12y ago

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

deleted 12y ago
[deleted]
q3k 12y ago
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.
- Nowaker 12y ago
  "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.
kordless 12y ago
That's really not true. I run it on small deployments all the time: http://www.stackgeek.com/guides/gettingstarted.html http://www.stackgeek.com/guides/gettingstarted.html
- faster 12y ago
  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.
  - kordless 12y ago
    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!
sciurus 12y ago
It would be nice to see an architecture diagram, or just a list of the planned components and their responsibilities.
- RushPL 12y ago
  Just made something that can answer few questions: https://www.virtkick.io/dia.svg https://www.virtkick.io/dia.svg