In this blog, I am going to give you a brief idea about Continuous Integration, Continuous Delivery, and Continuous Deployment. I am sure you have heard it as CI-CD at many places but don’t have the in-depth knowledge on these terminologies. So let’s start it. When we are developing an application, first we need to build the application. Sometimes, we need to perform certain tests before building it and make sure the test passes. The same way, there could be some other tasks that need to be done after the developer pushed the code or makes a commit to the source control management/version control system. After every commit, there could be so many steps followed before deploying it to production/hosting platform. Now, the question arises, what if we have a Continuous Integration setup. To understand this, we have to understand what Continuous Integration is. What is Continuous Integration? Continuous Integration (CI) is a DevOps development practice which requires developers to push code into a central hub (also known as Source Code Management System) several times a day. Each commit is then verified and proceed with automated builds and run tests, helping teams to detect the problem early and easily. As mentioned early, the tasks like running tests, creating a build, deploying the application, etc becomes tough when the developers commit the code multiple times in a day....Read More
Author: Ankesh K
Back in days, when DevOps Methodology was introduced to the world, people realized that most of the IT operations such as system administrations are going manually or by a self-written script. This was good until there are one or two in a team but for a large organization, it became devastating to understand the infrastructure. It was quite confusing at the same time complex to understand. And when there is a system failure, it was very hard to figure out the infrastructure issues. Scripts didn’t work well over time. They were better than manual work but still, there are a lot of variations in how people write the script. Everyone has a different style of writing it. Now, when the system configuration grows bigger, the length of the script becomes bigger. Now the complexity arises when more than one person works on the same script. So, scripting was not the best way to write configurations. What is Infrastructure as Code (IAC)? Infrastructure as Code also referred to as IAC, is the process of managing and provisioning computer data centers through machine-readable definition files rather than physical hardware configuration or interactive configuration tools. IAC can manage both physical servers such as bare-metal servers as well as virtual machines. Infrastructure as code is sometimes referred to as software-defined infrastructure. Infrastructure as Code (IAC) for DevOps With the context of...Read More
Containerization Explained We might think the Container is easy to understand and pretty straight-forward to implement. Generally, we misuse the container terminologies and use different terms to symbolize different functionalities but there are important conceptual differences. Actually, the Container is very vast and larger than just Docker. In our last blog, we went through the Basics of Containerization. If you want to go through the basics, click on the hyperlink and come back here. Let’s first understand how containers work. How Containers do work? Containers keep all the components to run the desired software. These components include files, dependencies, micro-services and environment variables that allow a program to be executable. These containers run on the top of Container engine which is on the top of the Operating system. Container Image files are a complete executable version of an application or the service. Docker images are built of multiple layers which starts with a base image. Proceeding with it are the layers of software and dependencies. Each container has their specific container layer, so the images under it can be saved and reused again and again. The image specification contains the information needed to launch the application or service in the container. Items usually bundled into a container include: Application Dependencies Libraries Binaries Configuration files It is very easy to start your container service. The installation is pretty...Read More
Take this course
My name is Surendra Kumar Anne. I hail from Vijayawada which is cultural capital of south Indian state of Andhra Pradesh. I am a Linux evangelist who believes in Hard work, A down to earth person, Likes to share knowledge with others, Loves dogs, Likes photography. At present I work at Bank of America as Sr. Analyst Systems and Administration. You can contact me at surendra (@) linuxnix dot com.