DevOps Terms

Continuous integration server

Continuous Integration (CI) is a software development practice where members

of a team integrate their work frequently - usually each person integrates at least
daily - leading to multiple integrations per day. ... We're interested to know which
CI servers you currently use and/or are considering using.

What is the function of CI server?

After that is done, they commit the changes to the shared repository. The CI
server monitors the repository and analyzes changes as they occur. Continuous
Integration builds the system and runs unit and integration tests. The server also
releases deployable artefacts for testing.

Configuration drift management

Configuration drift management automates the process of comparing the current

configuration of devices against their baselines to help keep your network in
compliance.

What is configuration drift?

Simply put, configuration drift occurs whenever someone makes a change to the
production environment without recording those changes and without ensuring
complete parity between staging and production

What is configuration drift in Microservices?

Configuration Drift is the phenomenon where running servers in an infrastructure

become more and more different as time goes on, due to manual ad-hoc changes
and updates, and general entropy. ... However, this may increase the burden of
fairly trivial changes, such as tweaking a web server configuration

Which practice prevents configuration drift?

One option to prevent configuration drift is to regularly destroy your

environments, then rebuild them using automated tools or virtual machines

What is configuration drift in infrastructure as code?

As those modifications and changes happen, the configuration of the applications

and infrastructure changes. These changes might be benign, or they might take
the systems out of a hardened state. This is known as “configuration drift

What are configuration management tools in Devops?

Red Hat Ansible.

Chef.
Puppet.

Top 10 Configuration Management Tools You Need to Know About

CFEngine.
Puppet.
Chef.
Ansible.
SaltStack.
Docker.
PowerShell DSC.
TeamCity Configuration tool.
Why are configuration management tools used?

Configuration management tools make changes and deployments faster, remove

the potential for human error, while making system management predictable and
scalable. They also help you to keep track of the state of your resources, and keep
you from repeating tasks, like installing the same package twice.

Is Docker a configuration management tool?

Docker is a viable alternative to incumbent configuration management tools with

its own advantages and disadvantages. Docker, like configuration management
tools more generally, encourages certain good practices for integration and
deployment of complex computing systems

What is orchestration tool?

Orchestration is the automated configuration, management, and coordination of

computer systems, applications, and services. Orchestration helps IT to more
easily manage complex tasks and workflows. IT teams must manage many servers
and applications, but doing so manually isn't a scalable strategy.

What is an orchestration tool in DevOps?

In comparison, DevOps orchestration is the automation of numerous tasks that

run at the same time in a way that minimizes production issues and time to
market. Automation applies to functions that are common to one area, such as
launching a web server, or integrating a web app, or changing a database entry.

Is Kubernetes an orchestration tool?

Kubernetes is an open source container orchestration tool that was originally
developed and designed by engineers at Google. ... Kubernetes orchestration
allows you to build application services that span multiple containers, schedule
containers across a cluster, scale those containers, and manage their health over
time.

Why is orchestration needed?

It's why orchestration has become central to their IT strategies and applications,
which require automatic execution of massive workflows. Orchestration works by
minimizing redundancies and optimizes by streamlining repeating processes. It
ensures a quicker and more precise deployment of software and updates

What is meant by Microservices?

Microservices is an architectural design for building a distributed application using

containers. Microservices get their name because each function of the application
operates as an independent service. This architecture allows for each service to
scale or update without disrupting other services in the application.

What is Microservices example?

4 Microservices Examples: Amazon, Netflix, Uber, and Etsy.

What are Microservices used for?

Microservices are increasingly used in the development world as developers work

to create larger, more complex applications that are better developed and
managed as a combination of smaller services that work cohesively together for
more extensive, application-wide functionality
What are Microservices?

Microservices are an architectural style that develops a single application as a set

of small services. Each service runs in its own process. The services communicate
with clients, and often each other, using lightweight protocols, often over
messaging or HTTP.

Microservices can be thought of as a form of service-oriented architecture (one of

the most critical skills for Java developers) wherein applications are built as a
collection of different smaller services rather than one whole app.

Instead of a monolithic app, you have several independent applications that can
run on their own. You can create them using different programming languages and
even different platforms. You can structure big and complicated applications with
simpler and independent programs that execute by themselves. These smaller
programs are grouped to deliver all the functionalities of the big, monolithic app.

Microservices captures your business scenario, answering the question, “What

problem are you trying to solve?”

Instead of large teams working on large, monolithic projects, smaller, more agile
teams develop the services using the tools and frameworks they are most
comfortable with. Each of the involved programs is independently versioned,
executed, and scaled. These microservices can interact with other microservices
and can have unique URLs or names while being always available and consistent
even when failures are experienced.

Continuous integration
Continuous integration (CI) is the practice of automating the integration of code
changes from multiple contributors into a single software project. It's a primary
DevOps best practice, allowing developers to frequently merge code changes into
a central repository where builds and tests then run.

The Difference between CI and CD

Simply put, CI is the process of integrating code into a mainline code base. ... CD is
about the processes that have to happen after code is integrated for app changes
to be delivered to users. Those processes involving testing, staging and deploying
code

What is continuous integration in DevOps?

Continuous integration is a DevOps software development practice where

developers regularly merge their code changes into a central repository, after
which automated builds and tests are run.

What is a continuous integration server?

Continuous Integration (CI) is a development practice where developers integrate

code into a shared repository frequently, preferably several times a day. Each
integration can then be verified by an automated build and automated tests. ...
Among them are revision control, build automation and automated testing.

What is the function of a continuous integration server?

Continuous integration server (aka build server, aka CI server) is a software tool
that centralizes all your CI operations and provides a reliable and stable
environment for you to build your projects on.
What are Continuous Integration Tools?

Continuous integration, at its core, refers to the development practice of writing

and integrating code from multiple developers into one shared repository that
forms the current software build. In a collaborative DevOps environment, this
means that different developers can work on and test different parts of the
repository simultaneously. Each completed code branch is then automatically
verified against the current repository build via tests before integrating to avoid
conflicting code. Continuous integration software allows developers to build,
package, and test their software continuously. Companies can make immediate
codebase changes automatically and ensure applications are working properly
before deployment or release. Continuous integration also lets developers detect
software errors early on in the production process and enables quality assurance
teams to identify weaknesses in a piece of software's code. This reduces the risk
of bugs and vulnerabilities in new programs.

Top Continuous Integration Tools: 51 Tools to Streamline Your Development

Process, Boost Quality, and Enhance Accuracy

Jenkins. @JenkinsCI. ...

Travis. @travisci. ...

TeamCity. @teamcity. ...

CircleCI. @circleci. ...

Codeship. @codeship. ...

GitLab CI. @GitLab. ...

Buddy. @BuddyGit. ...

Wercker. @Wercker.

What is KUBE flannel?

Flannel is created by CoreOS for Kubernetes networking, it also can be used as a

general software defined network solution for other purpose. To achieve
kubernetes' network requirements, flannel's idea is simple: create another flat
network which runs above the host network, this is the so-called overlay
network

How does flannel work in Kubernetes?

Flannel helps by giving each host a different IP subnet range. The Docker
daemon will then assign IPs from this range to containers. Then containers can
talk to each user using these unique IP addresses by means of packet
encapsulation. ... The routing is done by a flannel daemon called flanneld

What is KUBE proxy?

The Kubernetes network proxy runs on each node. This reflects services as
defined in the Kubernetes API on each node and can do simple TCP, UDP, and SCTP
stream forwarding or round robin TCP, UDP, and SCTP forwarding across a set of
backends.

What is Kubectl?

kubectl. The Kubernetes command-line tool, kubectl, allows you to run

commands against Kubernetes clusters. You can use kubectl to deploy
applications, inspect and manage cluster resources, and view logs. For more
information including a complete list of kubectl operations, see the kubectl
reference documentation.

What is Kubeadm and Kubelet?

Kubeadm is a tool built to provide kubeadm init and kubeadm join as best-practice
"fast paths" for creating Kubernetes clusters. kubeadm performs the actions
necessary to get a minimum viable cluster up and running. By design, it cares
only about bootstrapping, not about provisioning machines.

What is a Kubelet?

Synopsis. The kubelet is the primary "node agent" that runs on each node. It can
register the node with the apiserver using one of: the hostname; a flag to override
the hostname; or specific logic for a cloud provider. The kubelet works in terms of
a PodSpec. A PodSpec is a YAML or JSON object that describes a pod

Is it safe to restart Kubelet?

Restarting kubelet, which has to happen for an upgrade will cause all the Pods on
the node to stop and be started again. It's generally better to drain a node
because that way Pods can be gracefully migrated, and things like Disruption
Budgets can be honored.

What is flannel network in Kubernetes?

Flannel is created by CoreOS for Kubernetes networking, it also can be used as a

general software defined network solution for other purpose. ... All
containers(Pod) will be assigned one ip address in this overlay network, they
communicate with each other by calling each other's ip address directly.
What is calico and flannel in Kubernetes?

While Flannel is positioned as the simple choice, Calico is best known for its
performance, flexibility, and power. ... Unlike Flannel, Calico does not use an
overlay network. Instead, Calico configures a layer 3 network that uses the BGP
routing protocol to route packets between hosts

What are the limitation of flannel?

Flannel has some limitations including lack of support for network security policies
and the capability to have multiple networks.

What is Jenkins in DevOps?

Jenkins is an open-source automation tool written in Java with plugins built for
Continuous Integration purposes. ... Plugins allow the integration of Various
DevOps stages. If you want to integrate a particular tool, you need to install the
plugins for that tool.

Is Jenkins a DevOps tool?

Jenkins. Jenkins is the go-to DevOps automation tool for many software
development teams. It's an open source CI/CD server that allows you to automate
the different stages of your delivery pipeline. ... Currently, it offers more than
1,000 plugins, so it integrates with almost all DevOps tools, from Docker to Puppet

Jenkins is a free and open source automation server. It helps automate the parts
of software development related to building, testing, and deploying, facilitating
continuous integration and continuous delivery. It is a server-based system that
runs in servlet containers such as Apache Tomcat. It supports version control
tools, including AccuRev, CVS, Subversion, Git, Mercurial, Perforce, ClearCase and
RTC, and can execute Apache Ant, Apache Maven and sbt based projects as well
as arbitrary shell scripts and Windows batch commands.