Set of practices that emphasize the collaboration and communication of both software DEVelopers and IT OPerationS professionals while automating the process of software delivery and infrastructure changes, which aims at establishing a culture and environment where building, testing, and releasing software can happen rapidly, frequently, and more reliably.
"which ultimately means building digital pipelines that take code from a developer’s laptop all the way to revenue-generating prod awesomeness"
some myths that should be addressed before deep dive into DevOps
Myth - DevOps replace Agile
DevOps is the next step of agile
DevOps principles and practices are compatible with agile
agile is an enabler of DevOps
not a replacement, but is a logical continuation
a 'deployable piece' of code rather than a 'potentially ship-able piece' of code after each sprint
Myth - it "All Dev & No Ops"
the nature of IT Ops work may change.
ops collaborate far earlier in the software life cycle with Devs.
Devs continue to work with Ops long after the code is in prod.
Myth - DevOps is just automation
it requires automation for sure.. But that's not all.. it's much beyond that.
Myth - DevOps is a Tool/Product
it's rather a combination of tools
we don't buy DevOps.. instead, we do DevOps
In an organisation where everything gets automated for seamless delivery the generic logical flow will be:
"which ultimately means building digital pipelines that take code from a developer’s laptop all the way to revenue-generating prod awesomeness"
some myths that should be addressed before deep dive into DevOps
Myth - DevOps replace Agile
DevOps is the next step of agile
DevOps principles and practices are compatible with agile
agile is an enabler of DevOps
not a replacement, but is a logical continuation
a 'deployable piece' of code rather than a 'potentially ship-able piece' of code after each sprint
Myth - it "All Dev & No Ops"
the nature of IT Ops work may change.
ops collaborate far earlier in the software life cycle with Devs.
Devs continue to work with Ops long after the code is in prod.
Myth - DevOps is just automation
it requires automation for sure.. But that's not all.. it's much beyond that.
Myth - DevOps is a Tool/Product
it's rather a combination of tools
we don't buy DevOps.. instead, we do DevOps
In an organisation where everything gets automated for seamless delivery the generic logical flow will be:
- Developers develop the code and the source code is managed by a Version Control System tool like Git, then developers send this code to the git repository and any changes made in the code is committed to this repository.
- Then Jenkins pull this code from the repository using the git plugin and build it using tools like Ant or Maven.
- Configuration management tool like Ansible/Puppet deploys this code & provision testing env. and then Jenkins releases this code on the test environment on which testing is done using tools like selenium.
- Once the code is tested, pipelines configured using Jenkins send it for deployment on the production server (even production server is provisioned & maintained by tools like Ansible/Puppet)
- After deployment, it is continuously monitored by tools like Nagios.
- Docker containers provide a quick environment to test the build features.