For Day 4 of 30 Days of DevOps we’re moving to tools:
Sign up and explore an ops focused tool e.g. Docker.
If you’re new to this, it might seem a bit daunting but don’t worry, there are a few resources to help you jump into this:
Of course there are more options out there so what tool did you choose to sign up to? What did your exploration reveal?
I’m learning about OpenTelemetry, which is an open source project to provide an industry standard for structured events logging that helps with observability. https://opentelemetry.io is one place to start reading about it. I have more links if anyone is interested. Several vendors including Honeycomb and Lightstep are supporting it and contributing to it. My understanding is that if you use “OTel”, you can use a wide variety of vendor and open source observability tools, and switch around without having to change your production code.
I talked to one of my friend who uses jenkin-Docker framework in her company. So, Jenkin is an open source automation tool with plugins built for CI. Jenkin helps to automate entire process of software delivery life cycle. Jenkin picks up the code committed by devs, Compile->Build it->Validate it->Execute unit and integration tests and packages the code to be delivered, here Jenkin doesn’t deploy the code. We need some different tools for that, so there comes Docker
Docker is an Virtualization environment. It just takes few seconds to create server and deployment, its not exactly VM but create an image as vm and act as a container where you can deploy files and later test it, it can support more than one container so you can just schedule it and relax. Docker is gaining lot of popularity these days because it makes it possible to get far more apps running on the same old servers and it also makes it very easy to package and ship programs.
A great thread from Darya about this on Twitter
I have Docker downloaded and have done some exploring. I’ll review https://docs.docker.com/get-started/ and dive in a little more.
Excellent, looking forward to hearing how it went @dtorquiano 