Frankly, being an ops person who was dev trained (CS degree, doing ops since) what I've seen from other ops people once exposed to a devops mindset one of a few things:
1. Fear - mostly people who haven't even scripted anything before (common in Windows and pre-OS X Mac environments)
2. Confusion - I'm supposed to learn what with the who now? Mainly this is a tool choice issue - there's an overwhelming number of options out there.
3. Relief - finally, someone ELSE understands what I've been trying to do for the last N years, and I can talk to!
My guess is that, for ops people to accept this is to get the #3's to work with the the #2's on tool choice and familiarity, and then have the #2's convince or prove to the #1's that it's a good idea.
Dev interaction would probably be with mainly the #3's, as that would be the best opportunity for dialogue that would be meaningful to both sides.
Frankly, being an ops person who was dev trained (CS degree, doing ops since) what I've seen from other ops people once exposed to a devops mindset one of a few things:
1. Fear - mostly people who haven't even scripted anything before (common in Windows and pre-OS X Mac environments)
2. Confusion - I'm supposed to learn what with the who now? Mainly this is a tool choice issue - there's an overwhelming number of options out there.
3. Relief - finally, someone ELSE understands what I've been trying to do for the last N years, and I can talk to!
My guess is that, for ops people to accept this is to get the #3's to work with the the #2's on tool choice and familiarity, and then have the #2's convince or prove to the #1's that it's a good idea.
Dev interaction would probably be with mainly the #3's, as that would be the best opportunity for dialogue that would be meaningful to both sides.