#HackEatofDay

DevOps Tools Library

#HackEatOfDay

Hey, Guys Learner is here with some facts about DevOps.

What’s DevOps?

DevOps is a set of practices that automates the processes of software development and IT teams, in order that they can build, test, and release software faster and more reliably. The concept of DevOps is founded on building a culture of collaboration between teams that historically functioned in relative siloed. The promised benefits include increased trust, faster software releases, ability to solve critical issues quickly, and better manage unplanned work.

The CALMS Framework for DevOps

devops cultureCulture

If we could sum up DevOps culture in one word, it’d be “collaboration” – and if we were allowed two words, they’d be “cross-functional collaboration.” (Ok, that’s more like three words.)

All the tooling and automation in the world are useless if they aren’t accompanied by a genuine desire on the part of the development and IT/Ops professionals to work together. Because DevOps doesn’t solve tooling problems. It solves human problems. Therefore, it’s unlikely you’ll poke your head out of the cubicle one day, look around, and discover that teams at your company embody DevOps culture. But there are simple things you can do to nurture it.

devops automationAutomation

Build, test, deploy, and provisioning automation is typical starting points for teams who don’t have them in place already. And hey: what better reason for developers, testers, and operators to work together than building systems to benefit everyone?

Teams new to automation usually start with continuous delivery: the practice of running each code change through a gauntlet of automated tests, often facilitated by cloud-based infrastructure, then packaging up successful builds and promoting them up toward production using automated deploys. As you might guess, continuous delivery is not a quick and easy thing to set up, but the return on investment is well worth it.

devops is leanLean

When we hear “lean” in the context of software, we usually think about eliminating low-value activities and moving quickly – being scrappy, being agile. Even more relevant for DevOps are the concepts of continuous improvement and embracing failure.

A DevOps mindset sees opportunities for continuous improvement everywhere. Some are obvious, like holding regular retrospectives so your team’s processes can improve. Others are subtle, like A/B testing different onboarding approaches for new users of your product.

We have agile development to thank for making continuous improvement a mainstream idea. Early adopters of the agile methodology proved that a simple product in the hands of customers today is more valuable than a perfect product in the hands of customers six months from now. If the product is improved continuously, customers will stick around.

And guess what: failure is inevitable. So you might as well set up your team to absorb it, recover, and learn from it (some call this “being anti-fragile”). At Atlassian, we believe that if you’re not failing once in a while, you’re not trying hard enough.

Want to prepare for it…

You can go through below topics for DevOps preparation.

  • Learn BugZilla
  • Learn Chef
  • Learn Consul
  • Learn Docker
  • Learn Git
  • Learn Jira
  • Learn Puppet
  • Learn Scrapy
  • Learn MakeFile
  • Learn SVN
  • Learn Gerrit
  • Learn LogStash

{Code With Code@ter}





Leave a Reply