Hacker News new | comments | show | ask | jobs | submit login

Yes, it is an unfair comparison. I was attempting to explain in my comment why I consider it a valid unfair comparison, because it is a matter of perspective.

As a software developer, do I ever want a private cloud? No. Does my employer? Maybe. Is it my job to tell them how to invest their infrastructure dollars? Quite possibly no, because software development and infrastructure are typically held at arms length. But even when they are not in a "proper" DevOps shop, the ballgame of which cloud is then subservient to developer convenience and how easy it is to deploy software to a cloud and how productive developers are writing software for that cloud.

So yes, the purpose of OpenStack and Container technologies are very different and I appreciate that technically. In terms of real world value to me as a software developer, however, I have platform problems not infrastructure problems. I don't care what the infrastructure is under the service so long as it provides a stable, reliable platform for me to build upon. Containers abstract that for me in a way that solves real platform problems that OpenStack was only ever relevant to me in so far as its ability to once hint at a possible solution to. That's not fair and that was expecting too much from OpenStack at the time, but that's life.




Okay, I was reading it as defending why container would solve what OpenStack was set out to solve, which is the proposition I read from the OP I was replying to.

Of course, I would advise against running a private cloud unless there is a dedicated team of at least a dozen or so. I applaud Digital Ocean for able to survive and make good business from their private cloud. As a developer I totally agree I just want my code to be deployed and that all the appendices are deployed and configured.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: