Slashdot Mirror
Dev vs. Ops: The State of Accountability (overops.com)
Here's an analysis by OverOps on how shared accountability affects the delivery of reliable software in a DevOps environment, and what are some of the top challenges teams face when it comes to building and maintaining quality applications. Conclusion from the report [PDF], which relies on a survey of over 2,000 IT professionals around the globe : At the center of this DevOps adoption chaos is the evolving relationship between development and operations. Many organizations are already taking a shared approach to accountability for application health, however they still lack the tools and application visibility needed to know who is ultimately responsible for addressing and fixing each issue. As the lines between these two teams continue to blur, organizations will need to focus on adopting tools that deepen visibility into their applications. Clarifying ownership of applications and services, and avoiding the "multiple owners = no owner" syndrome is a crucial for even the most bleeding edge organizations.
The "Dev vs. Ops: State of Accountability" survey revealed that as more organizations begin the transition to DevOps workflows, defining roles and processes becomes more difficult and more important. Furthermore, businesses of all sizes are building and releasing new code and application features faster than ever before, which adds additional pressure across the entire software delivery supply chain. Organizations going through the DevOps transformation are more likely to face visibility challenges that make it difficult to maintain or improve application quality and reliability.
The "Dev vs. Ops: State of Accountability" survey revealed that as more organizations begin the transition to DevOps workflows, defining roles and processes becomes more difficult and more important. Furthermore, businesses of all sizes are building and releasing new code and application features faster than ever before, which adds additional pressure across the entire software delivery supply chain. Organizations going through the DevOps transformation are more likely to face visibility challenges that make it difficult to maintain or improve application quality and reliability.
... devops actually sucks just like every other âoeagileâ fad that came before and produced nothing of value other than the ability to avoid accountability
IT and the "movement disease".
I am sort of tired of this constant "revolution" garbage that surrounds the IT industry in general. I work in this shit industry, I am well paid for what I do, but one thing is always certain... It will always suck because everyone in charge of IT came from college where stupid is the only thing being taught when it comes to computer science.
There is never anything innovative being done, by the time I am done listening to a sales pitch I realized I have heard all of this shit before, it's the same shit product emulating another shit product surrounded by proprietary technology that works like shit just in a different shitty way.
There is also the problem that every industry has... 20% of the folks do 80% of the work. Do you know what else tends to happen? 20% of the people are the only ones that knows what to do or what is going on. Do you know what else? IT is not a meritocracy either... it is still the same brown-nosing ass licking who you know path to success, like every other department. Those in the know are constantly assaulted by their lesser skilled and capable "co-workers". Those in the know are constantly waiting for some other knob in a different department to do their own damn job. And all of this while management keeps not getting a fucking clue and piling on more and more work to the point that more than 50% of projects fail by either never having the proper amount of time & expense dedicated to it.
These bullshit "cultural DevOps, ITIL, Agile, Waterfall, blah blah blah" are all stupid ideas people keep coming up with to address the problem of an industry that is riddled with incompetent management trying to rule over an incompetent group of pseudo intellectual nerds that know far less than they put on. And that is another problem as well... people hate IT personnel that do not sound "over confident" it is a practical requirement for IT pro's to act like they know every fucking thing there is to know and yet those of us at the top know different. We are all running around trying to figure out every little fucking thing on the fly because experience has taught us to just roll up our fucking sleeves and work it out... regardless of whichever newfangled fucking "operation ideology" that someone pushes.
I'm in a situation now where a new VP of IT was hired late last year at the smallish (approx 500 employees total) company where I work but he came from a large multinational. Since coming in he started introducing various changes to our development and deployment processes, wringing his hands frequently about how bush league we supposedly are and frequently invoking "well in other companies they _typically_ do X".
The "funny" thing being that every time he introduces some new process that supposedly will improve delivery, it makes it worse and orders of magnitude more time consuming. We've gone from the past where deployments were total non-events and never posed any problem to a place where they are a walk through hell involving dozens of people for no good reason and they all bike-shed and conflate the unrelated so much that each and every deploy is now a fiasco.
The other "funny" thing is he constantly spouts agile terminology while forcing us to undertake a process that is virtually the exact opposite of agile.
old concept learn to operate a mainframe and nothing fundenmentally new will be under your sun
Docker is getting more and more heavy weight, i.e. becoming full blown VMs (Though in the strict sense of the word they always were). Now part of the problem I see is that projects end up with containers scattered around like jack straws, like the "DLL hell" many experienced in the past, or plug-in hell. All docker does is allow the complexity to take a different form. Also stateless containers in my experience are pretty useless. Working on back end "heavy lifting" applications somewhere you need to maintain state and Docker and stateless containers, by definition, cannot do that.
Cloud is just putting the application somewhere else and paying by the cpu cycle. No different than before, it just makes it opaque as to what is going on and who is responsible. There's really not much new under the sun and good ideas are basically reinvented over time. Mainframe == cloud hosted apps on your mobi or browser. Nothing to see here, move along...
putting the 'B' in LGBTQ+
Application Virtualization is nothing new.
Just because you change it does not make it innovative.
Innovative means NEW... application virtualization is not.
I have been doing this for a while... sure I might be a problem, but likely only to the people recycling old hat like it is a new hat.
Dev Ops is an example of the willing, led by the unknowing, doing the impossible for the ungrateful.
Our Dev Ops team has adopted the slogan, "Delivering Yesterday's Technology Tomorrow!"
Just cruising through this digital world at 33 1/3 rpm...
I was our company's monitoring department and was checking systems and applications and it fits this question quite well, and you know what, IT SUCKS!
Between management that does not give two f**ks, developers who don't understand infrastructure and systems administrators who cannot manage applications, no one wants to be on the hook for anything. Just TRYING to get them fix issues without pointing a finger is a nightmare. It is like being the IRS, you never get a call from them saying you did a good job.
Everyone is afraid of looking bad because management, which does not understand IT or process, falls to politics to address issues and everyone else is afraid to make a move that make get them into trouble.
DevOps and Agile crap, will not fix broken management.
DevOps typifies the phrase "jack-of-all-trades, master of none". This is a trend I've started to see where I work. A push to get everyone at least a little knowledgeable about everything, so anyone can fill in for anyone else. The idea that specialized skills allow a good team to be more efficient and productive is mostly lost on my coworkers.
this is so spot on!!!
Dev Ops is responsible for the Great Lab Hack where I work.
Short version: because some genius thought Dev Ops means that no one needs people with actual operations experience, we wound up with hundreds of old VMs that were spun up during some ancient sprint, then left online and never updated, never properly secured, and using weak passwords. (Some genius dev-op declared that all dev VMs for his team should use the same weak root password so every developer could use them.) Eventually someone found the lab through the firewall and was able to get remote SSH access to one of the servers that was using a weak password and, since nothing was ever updated, basically got complete control of every VM in there.
If you thought this meant that anything changed, then you clearly don't work in modern IT. We're still doing dev ops, there's still no inventory of VMs and what they're running (beyond what the VM software itself provides - which doesn't include what they're being used for even though there's a description field that's never filled in), and there are still no requirements to properly secure servers and retire old VMs that are no longer in use. Instead the hack was blamed on IT and the firewall.
Welcome to Dev Ops.
Here's the thread where we talk about developers bundling ancient versions of libraries with vulnerabilities in their Docker images, calling Ops people obstructionists, and then blaming them for security failures. Also, people who refused to use CI, introduce breakage, and then try to cast blame while someone else fixes it.
Don't work for a tech company where the CEO isn't an engineer.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
The complicated interconnected nature of this sort of thing means issues land initially in one expert's lap, only to be delegated to another expert. The key is to be flexible and responsive to issues and not worry so much about who is responsible for what, but who is responsible now as an issue progresses. The hand-off of responsibility is more important than defining the responsibility.
I thought you were supposed to maintain the state in whatever framework you're using to generate the docker containers?
I guess that is the problem; the more common practice is to receive containers rather than to build them. So whatever state you need is tacked onto the side.
IMO if you're using cloud computing to run your services, it should only be providing horizontal scaling. Nothing else should change. In that way of thinking, the statelessness is something you build into parts of your architecture by compartmentalizing the state in such a way that the parts that scale horizontally are stateless at runtime. This has to be done from inside the problem domain, it isn't going to be turn-key and also fit well. Docker is useful as a container, but a container isn't a framework. It is like having a nice lunch box; it tells you nothing about the lunch inside. And simply trading lunches with people who have nice lunch boxes doesn't imply that your personal dietary needs will be met.
Cloud computing solves the problem, "What happens when you need two mainframes? Or maybe three? And what if it changes from hour to hour?" Unfortunately, a lot of devs treat it as "Geocities for elite programmers" and forget to also plan their architecture before they implement it.
Apple is based on Unix, not Linux. And as someone who spends a lot of time writing shell scripts, I assure you they are quite different.
You can only auto scale if the APPLICATION is built to handle it. It isn't magic. That isn't new either. Machines need to be maintained: just not by you. That isn't new either.
Non-coding managers will always be be prey to anyone or anything insulating them from the unacceptable truth that making software system sing is an art form more similar to making music than a production line. Find the right artists and keep the band together and sweet music will flow to your customers.
"Knowing everything doesn't help..."
I so dislike this attitude of 'I am not going to change' instead of looking at the methods and technologies and see how they can be of use to you. Some might be great for your organisation, some not. But dismissing everything on forehand is just so stupid and the reason some organisations are stuck in old, unmaintainable and inefficient IT environments while the world moves on.