12/5/2023 0 Comments Netops domain dossier![]() ![]() Because inside the BIG siloes are even smaller siloes. Operations? System ops.īut it goes even deeper than that. NetOps and Security groups are more likely to work in the construct of a "single function" team. A factor in this misalignment is the continued isolation of operational domains. People, who are still at the heart of IT and comprise the teams that must implement automation and orchestration, are not necessarily aligned on the same goals. In fact, the number one measurement cited for security was "network uptime" at 59% of security pros measured on this metric. No one has time for security and no one is measured on it anyway. Instrumentation and monitoring - the latter which is critical to the sharing component of DevOps - will focus first on the network, and then perhaps on the application. Why is this disparity important? If my primary goal is to keep the network available, I'm going to spend my time focusing on the network. Conversely, nearly twice as many developers and operations (30%) are measured on frequency of deploys than are NetOps (16%) and Security (17%). On the other side of the fence, 59% of developers and operations told us "application uptime" was their primary metric. Nearly three-quarters (73%) of NetOps cited "network uptime" as their primary metric. In it, we found broad disparity between the metrics (measurement) sought after by NetOps and those involved in development and operations. To wit, you may recall the State of Network Automation research in which we joined forces with Red Hat to dive into the murky world of DevOps and NetOps and automation. If we're measured on network uptime, that's what we're going to focus on - even if our counterparts in operations are trying to improve application uptime. We work toward that which we are measured on. It's difficult to change the culture when teams are still isolated by function and focused on metrics that don't matter to other teams. Of particular note is that the three commonly ignored concepts are intertwined. It is the other three that tend to be left behind or outright ignored in the quest to improve service velocity within IT. Of these four, automation is most likely to be embraced with enthusiasm. CAMS stands for: culture, automation, measurement, and sharing. ![]() Impediments to speed are often due to a failure to adopt all the premises of DevOps as organizations seek to transform IT operations.ĬAMS is the most commonly used means to disseminate the core tenets of DevOps. It is important to recognize that it's not always "NetOps" that's getting in the way of deploying the latest thing/app/service. Whether it's the server in a restaurant or a customer service representative for, it is generally the person who interfaces with you that winds up bearing the brunt of your angst/frustration/anger when something goes wrong.Īs IT is digitally transforming itself with a goal of attaining higher optimization and speed, it is the NetOps teams who are most likely to interact with internal "customers" and thus bear the brunt of disgruntled users when processes don't move as quickly as desired. But they are your interface to the kitchen, and ultimately it is they who pay the price for failures that happen out of sight. After all, they didn't prepare your meal. They take it with a smile even though it's not their fault. Frustrated, you speak harshly to the server and perhaps even reduce their tip. You're ready to dig into a meal you've looked forward to all day when you notice that it's undercooked. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |