Open stevepereira opened 9 years ago
@stevepereira Yes you are correct DevOps is assisting organizations to remove constraints. But what we are looking here is that if organizations don't have operations team in house. So either they have to hire operations team or get 3rd party. If we check ()-as-a-Service(a-a-S) stands for a number of things including X as a service, anything as a service or everything as a service. The acronym refers to any of an increasing number of services provided over the Internet that have been traditionally provided locally. It's not possible to completely eradicate manual DevOps involvement and thats not even the intention. But the aim is to certainly make it easier like a plug and play thing especially in scenarios wherein organizations dont have a DevOps culture. It's not important every car manufacturing company should make their own engines. That's what I am thinking of. Why can't companies have DevOps as-a-Service. Still I am scratching my head, it's a thought we are working on. Will definitely get back you in day with some concrete pointers. By the way thanks a lot for putting up very valid point. Which i have to answer in very rock solid way.
I understand your intention, it's still just Ops though.
What i think, DOAAS is not about removing the constraints between Developers and Operations team but it is about introducing them to DevOps. There are many StartUps and small companies which are not much familiar about DevOps and it's benefits and how it actually works. Through DOAAS they can actually learn the benefits of DevOps and not only DevOps they will also learn about new tools and new technologies that are used in DevOps as a team like Version Control,Chef,Puppet etc etc.
That's called education or consulting. 'X-as-a-Service' means: we do X so you don't have to. DevOps can never be provided as a service. It's entire existence hinges on inter-organizational collaboration.
The question is why? Why can't DevOps be a service. Although it definition so be it. What we have learned all those years in computer science Definition stresses the Implementation. The more well defined definition we have the better implementation we can achieve. http://www.computerworld.com/article/2497859/cloud-computing/platform-as-a-service-heats-up.html
I'm not sure what you mean by including the link. Maybe I wasn't clear before, though. DevOps has been defined from the beginning as collaboration between ops and dev organizations, specifically within a company. That's not to say you couldn't provide a facilitation service but it would be a huge stretch to claim such an offering as DevOps-as-a-Service. With other XaaS offerings the outsourcing model and advantage is very clear, but I'm not sure there's a parallel in your explanation.
DevOps as a service would be actively assisting organizations to remove constraints and handoffs between Developer and Operations staff, unless you have a different definition. What's the rationale for calling it DevOps?