Introduction to Devops
•DevOps is a practice that enables a single team to handle the whole
application lifecycle, including development, testing, release,
deployment, operation, display, and planning. It is a mix of the terms
“Dev” (for development) and “Ops” (for operations). We can speed up
the delivery of applications and services by a business with the aid of
DevOps.
• Amazon, Netflix, and other businesses have all effectively embraced
DevOps to improve their customer experience.
Continuous Development
• InContinuous Development code is written in small, continuous bits
rather than all at once, Continuous Development is important in
DevOps because this improves efficiency every time a piece of code is
created, it is tested, built, and deployed into production.
• Continuous Development raises the standard of the code and
streamlines the process of repairing flaws, vulnerabilities, and defects.
It facilitates developers’ ability to concentrate on creating high-quality
code.
Continuous Testing
• Anyfirm can deploy continuous testing with the
use of the agile and DevOps methodologies.
Depending on our needs, we can perform
continuous testing using automation testing tools
such as Testsigma, Selenium, LambdaTest, etc.
• With these tools, we can test our code and
prevent problems and code smells, as well as test
more quickly and intelligently. With the aid of a
continuous integration platform like Jenkins, the
entire process can be automated, which is
another added benefit.
Continuous Monitoring
• DevOpslifecycle is incomplete if there was no Continuous Monitoring.
Continuous Monitoring can be achieved with the help of Prometheus
and Grafana we can continuously monitor and can get notified before
anything goes wrong with the help of Prometheus we can gather
many performance measures, including CPU and memory utilization,
network traffic, application response times, error rates, and others.
• Grafana makes it possible to visually represent and keep track of data
from time series, such as CPU and memory utilization.
17.
Continuous Feedback
• Oncethe application is released into the market the end users will use
the application and they will give us feedback about the performance
of the application and any glitches affecting the user experience after
getting multiple feedback from the end users’ the DevOps team will
analyze the feedbacks given by end users and they will reach out to
the developer team tries to rectify the mistakes they are performed in
that piece of code
• Continuous Feedback can increase the performance of the application
and reduce bugs in the code making it smooth for end users to use
the application.
18.
Continuous Operations
• Wewill sustain the higher application uptime by implementing
continuous operation, which will assist us to cut down on the
maintenance downtime that will negatively impact end users’
experiences.
• More output, lower manufacturing costs, and better quality control
are benefits of continuous operations.
Magic of DockerRun
• Pulls the <Ubuntu> image:Docker checks for the presence of the Ubuntu image
and,if it doesn’t exist locally on the host,then Docker downloads it from Docker Hub
website. If the image already exist,then Docker use it for the new container.
• Creates a new container: Once Docker has the image, it uses it to create a
container.
• Allocates a file system and mounts a read-write layer.
• Allocates a network/bridge interface: creates a network interface that allows Docker
container to talk to the local host.
• Find and attaches an available IP address from a pull.
• Runs your application and
• Capture and provides application output.
Docker Container Lifecycle
•Created: A container that has been created but not started
• Running: A container running with all its processes
• Paused: A container whose processes have been paused
• Stopped: A container whose processes have been stopped
• Deleted: A container in a dead state
Docker Swarm
A DockerSwarm is a container orchestration tool running the
Docker application. It has been configured to join together in a
cluster. The activities of the cluster are controlled by a swarm
manager, and machines that have joined the cluster are
referred to as nodes.