6 ms·
My opinion: it grew to a gross, large set of python and apis that, when combined with multiple implementations, extensions, and company-specific customizations,
by kodablah 8y ago
My opinion: it grew to a gross, large set of python and apis that, when combined with multiple implementations, extensions, and company-specific customizations, made it an unmaintanable mess that was difficult to deploy and code around.
So, although the author compares it with the growing k8s project out there now, at least k8s more clearly stewarded, more developer oriented instead of only for ops (with code quality to match), and doesn't feel as hamstrung by environments and dependencies (just try to run a little openstack setup on your laptop for development... very annoying for a project of such age with so many company's hands in the pot).
- gboudrias 8y agoI wanted to like OpenStack but at the time I felt like it didn't... Let me? It did everything complicated in a relatively straightforward manner, but I didn't want dev to be complicated. I wanted my dev simple, and I felt like they just weren't really interested in that (strangely enough). Could be wrong though. Never found a way to justify adoption to the team.
- m0zg 8y ago>> k8s more clearly stewarded Not clearly enough, IMO. Not very "clean" to begin with, it's accumulating cruft at an alarming pace, and doesn't drop much legacy over time (a painful, but necessary step in fighting code entropy). It seems to have inherited Google's internal modus operandi: launch new shit and then let it rot.
- dilyevsky 8y agoYou’re either kidding or simply not aware of how much refactoring and breaking changes are introduced each release.
- p_l 8y agoIt has a very clear API stability process, preventing the typical arguments about google dropping things willy-nilly. I rarely have to change anything in my manifests to get them to run after upgrading k8s