Who actually owns network automation in your org — NetOps, DevOps, or just whoever had time to learn Python?
Been thinking about this after a few conversations recently.
In theory, network automation should have a clear owner. In practice it seems like it usually ends up being one of three things:
- A network engineer who picked up Python and just ran with it
- A DevOps or platform team who inherited it because "it's code"
- Nobody, and it's a pile of scripts held together by one person who's definitely leaving someday
What's interesting is how much the ownership question affects the outcome.
Curious what it actually looks like in your environment, is there a clear owner, or is it more of a grey area?