#1: The Rise of a New Kind of Administrator
Luke can see the growing trend of admin empowerment within customers and partners from his view at PuppetLabs. His outlook on tools that support admins in complex environments has always been clear, creating tools which allow “you to focus more on the business value of your work and spend a less of your brainpower on implementation details.”
This article looks at the changing role of administrators within organisations as “tools better enable people to build teams to focus on their customer instead of their technology.”
#2: 8 Lessons in Deployment Tooling Lessons Learned
Another great article on learning’s from the UrbanCode guys. This one gives us a history lesson on AnthillPro and what the team learned from creating and using the product. In summary the 8 lessons are;
- Builds are about quality and checking quality.
- Deployment is a serious challenge.
- Developers know jack about audit and security.
- Deployment starts with production.
- Deployment requires co-ordination.
- Deployment starts with high-availability and scalability.
- “Release” is more than just deployment.
- Multiple integrated tools are not optional.
#3: Playing Pitfall with DevOps and CMDB’s
One paragraph in and Sam delivers a stark warning that “there are some underlying shortcomings; some so major they might render DevOps redundant in the near future.”
In summary, he outlines the following challenges;
- DevOps goes against organizational culture; which advocates for the separation of responsibilities.
- Departure from IT Service Management Process
- Configuration Management Database redundancy
- Inadequate Automation
And so it is, that Sam leaves us with one final point to ponder “Be prepared to say goodbye to DevOps and CMDB, as they are sure to be abandoned in favor of new and improved counterparts in the face of a future IT revolution.”
In response, we ask you to consider Gene Kim’s 3 ways as the underpinning to the DevOps philosophy;
- The First Way emphasizes the performance of the entire system – the value stream.
- The Second Way is about shorting and amplifying feedback loops.
- The Third Way is about creating a culture that fosters continual learning and understanding.
If these truly are the essence of DevOps, are they principles that can ever be abandoned?
#4: DevOps Complete Certification Kit
Only 18 Hours and you could be certified! Sounds too good to be true, well it is. As Patrick Debois commented, “they are not getting it!” The geniuses who put this material have really missed the point. We’d love to be certified “DevOps” guys, but instead we’ve focused on recognizing what the practice requires to be implemented.
Don’t get us wrong, education on the background to Agile process and the challenges facing Development and Operations teams is vital, but don’t think that 18 hours of study are going to equip you with all you need to become a “DevOps” engineer (a term in itself which is entirely flawed). Remember this…DevOps is a philosophy, not a qualification.
#5: Agile Alliance has a DevOps Track
DevOps seeks to address the challenges organizations face when applying change to high velocity environments. Speedy software development handing work over to risk-averse operations need not result in bottlenecks of pessimism. The rise of PaaS, SaaS, IaaS combined with improved understanding of systemic dependencies and business risk is changing how collaboration, automation and operations work in today’s modern enterprises. Mental models are shifting from protection mode to enabling-change mode. The track is going to cover the processes, tools and culture shifts shaping the DevOps movement. We look forward to seeing the output from this. Get submitting!