I’d recommend this top 10 as standard requirements for any shop, even if you don’t label yourself as “devops”.
Join us for “The Top 10 DevOps Operational Requirements” – http://www.brighttalk.com/webcast/534/98059 via @BrightTALK
One of the key tenets in DevOps is to involve the Operations teams in the full software development life cycle (SDLC) and in particular to ensure that “operational requirements” (“OR’s”, formerly known as “non-functional requirements”, “NFR’s”) are incorporated into the design&build phases.
In order to make your life easier the DevOpsGuys have scoured the internet to compile this list of the Top Ten DevOps Operational Requirements (ok, it was really just chatting with some of the guys down the pub BUT we’ve been doing this a long time and we’re pretty sure that if you deliver on these your Ops people will be very happy indeed!).
#10 – Instrumentation
Would you drive a car with a blacked out windscreen and no speedo? No, didn’t think so, but often Operations are expected to run applications…
View original post 1,238 more words
I am a Sr. Cloud Solutions Architect for Red Hat.