Aminotes - NTCC Project Docker AND Kurbernetes Containers PDF

Preview

Summary

Download Aminotes - NTCC Project Docker AND Kurbernetes Containers PDF

Description

Term Paper on DOCKER AND KUBERNETES CONTAINERS Submitted to Amity University Uttar Pradesh

nt of

award of the degree

Te in nce and by Aminotes A2305219999 Under the guidance of Ms Faculty Name

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING AMITY SCHOOL OF ENGINEERING AND TECHNOLOGY AMITY UNIVERSITY UTTAR PRADESH JULY 2017 i

Declaration

I Aminotes student of B.Tech (3-C.S.E.-21(Y)) hereby declare that the project titled “Docker and Kubernetes Containers” which is submitted by me to Department of Computer Science and Engineering, Amity School of Engineering Technology, Amity University Uttar Pradesh, Noida, in partial fulfillment of requirement for the award of the degree

pute Science and Engineering, has not been

previou

of a

egree, diploma or other similar title or

recogn

The Au

has b

appear

he use of any copy righted material

/ Pro

proper

n brief excerpts requiring only

olarly

Date: _

is acknowledged.

_____

Amino A2305 3CSE-

16-20

ii

CERTIFICATE

This is to certify that Mr Aminotes student of B.Tech in Computer Science and Engineering has carried out work presented in the project of the Term paper entitle “Docker and Kubernetes Containers” as a part of First year program of Bachelor of Technology in Computer Science and Engineering from Amity University, Uttar Pradesh, Noida under my superv

______ Ms Fac Depart

and

ASET,

iii

ACKNOWLEDGEMENT The satisfaction that accompanies that the successful completion of any task would be incomplete without the mention of people whose ceaseless cooperation made it possible, whose constant guidance and encouragement crown all efforts with success. I would like to thank Prof (Dr) Abhay Bansal, Head of Department-CSE, and Amity University for giving me the opportunity to undertake this project. I would like to thank my faculty guide Ms force ehind my successful completion of the

Facult project right di able to me, he

ve an hout

ery of mine and also guided me in the and inspiration, I would not have been

I wo

hank my batch mates who guided

otiva

.

Amino

iv

ABSTRACT

It wasn’t much earlier that the application software were big, huge and monolithic. They were stored in large blocks sitting lonely within lumps of steel and silicon and they would stay here opposing alteration and not ready to shift or move from there place. This was a problematic issue for organisation that required to move fast. So it was no big deal that the virtual machin

ps w e no further attached to these pieces of

hardwa

iftly.

comple

nside

is still

d since virtual machines are smaller

y of

Docker

h. If y

comple

from

simple

uiring management. inside a container, it separates the rneath making the infrastructure

asier

leap in

is organizational efficiency, the

d effi

boot in

hines is dramatic. Containers

not m

applica

per to

way th

o, not

Kubern

anot

and Co

er computer, and this virtual computer

ds m

and eas

This re

unfortunately, these VM’s are also very

roduc ers, a

llocated. This makes your ns tha

tect your application in the

s the con

, inflexible infrastructure.

tform just li Docker and its fun ious concepts, some

usage.

v

cise history of Docker ect

and about its

TABLE OF CONTENTS DECLARATION

ii

CERTIFICATE

iii

ACKNOWLEDGEMENT

iv

ABST

v

TABL

vi

1. IN 1.1

1 ner?

2

1.2

2

1.3

3

1.4

r

4

1.5

4

2. RE 2.1

ker p

2.2

6 chines (VM

7

ker good for?

8

ners

2.3

what

2.4

cker

ns

10

.4.1. 2.4. 2.5. C

TECHNOLOGY: How it fits i

challenges?

r 11

2.6. PROS

12

2.7. CONS

13

CONCLUSION AND FUTURE PROSPECTS

14

REFERENCES

15

vi

1. INTRODUCTION 1.1 OVERVIEW Docker is an effective container technology currently used worldwide. It lets you to “build, ship, and run any app, anywhere.” It has achieved a lot in an unbelievably short span of time, now considered to be a standard method for solving one of the costliest features of software that is Docker

oftwa

contain

ode w

running

es. Operators are using Docker to

along

precise

d segregated containers to get well

s use

transpo

build swift and easy software

new

Windo

y, safely and confidently for both

Linux eakdo

Docker reduce

many “small apps” with their

nd pu

might b

k on

are no

the

synerg Accord

to eliminate “works on my machine”

opers

problem

tainer platform. It is an open source

e who o an a

“Docke is a to

ed c

is way many small teams

on, usin

nology for their task (you

s the entir

Moreover, it has great

vices. nux.com; e an application and its d

that can run

er. This helps enable flexibil

application

on premises, public cloud, private

Figure 1: Docker logo [1]

ual container where the c.”

Figure 2: Kubernetes logo [2] 1

Kubernetes is another platform just like Docker. It is an open source system which is used to manage containerized applications or software across numerous hosts, serving basic tools for deployment, scaling, and maintenance of apps. “Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale using a system called Borg, combined with best-of-breed ideas and practic

s is

osted by the Cloud Native Computing

Founda

1.1.1 Each a

ble a

into is

ware to function and run is packed the containers don’t package a

ers.

comple

just

ecessary to make the software

functio

ed. Th

weight, self-contained systems

and as

e wil

, irrespective of where it is

deploy Contai code th this co require

eloper over, is an n insi

pplicatio

mponents, so the stack of

connected w

r packaged up in a box

ent inside whic

n got everything that is

.

1.2 HIST Docker was started as an in-house project by Solomon Hykes in France within DotCloud Company, along with other engineers in DotCloud Company namely ‘Andrea Luzzardi’ & ‘Francois-Xavier Bourlet’. Also Jeff Lindsay was involved in it as an independent collaborator. The DotCloud's registered technology got evolved into Docker, after which it became so famous leading to DotCloud rebranded as Docker Inc.

2

Docker was initially released in March 2013, as an open source project. On 13 March 2014, with the release of version 0.9, Docker dropped LXC as the default execution environment and changed it with its own libcontainer library written in the Go programming language. Then Docker 1.0, released in June 2014, when Docker Inc. thought and considered that this software container platform is suitably advanc

ction with the

compa

sup

This pr

own

release

despite rapid change. On 24th

was r

than 25

red GitHub project with more

more

On Ma

tely 1,100 contributors.

udy ly ‘

organis Google

wei,

Docker

nce i

con m’, Ca

ocker were the following ryLink, Cisco, Amazon,

soft. in 2016 which

n a study of LinkedIn

uary

Kubernetes w

declared

ard and backward compatibility),

able f

Octobe

[3]

ages sourced from any version of

her v

someth

Figure 3:Evolution of the Docker Inc.

has

ship’

Docker

linked wit

ures,

found

howev

profile

onthly

ng u

and ad

choices.

Brendan Burns, Craig McLuc

was rapidly

gineers including Brian Grant

was first

-2014. Its design and development

d by the

Google's Borg system, and plenty of its top contributors to the project earlier worked on Borg. ‘Project Seven’ was the original codename within Google for Kubernetes, a reference to a Star Trek character that is a 'friendlier' Borg. Even on the Kubernetes logo, the seven spokes present on circular wheel of logo represents the codename.

3

On 21st July 2015, Kubernetes v1.0 was released. Along with it, Google united with the Linux Foundation forming the “Cloud Native Computing Foundation (CNCF)” and they presented Kubernetes to be core technology.

1.3 OBJECTIVES The destination of the research project undertaking is: 1.

Docke

2.

proj

3.

ifference b/w containers & VM’s.

r hub

4.

iles, Docker images, etc.

nd w

5.

ocker is good for?

nd C

1.4 S

nd its applications in advanced IT

ER

Well D

thing

Docker

y the

last yea

gotte

stars. I

nowle

compa

ding

soft

all time. Recently, over the

forks a

und 30 thousands GitHub

amount of

from the likes of big

co, Google, Mi

VMware.

hit

by responding to a

organiz ons: t

software in an open an

“

Docker

nd Container technology.

reliably and programmi configura

fo many software hen deploy it

ferent contexts. There is n

earn a new

hase costly hardware, or do muc

allation or

and run applications portably.

”

It has got a huge scope in the future. This technology is really revolutionising not only the way we develop and deliver an idea applications but also the way deliver the IT infrastructure.

4

1.5 APPLICATION Docker Inc., the company has established a straight pathway on progress of the cross service management (libswarm) and the core capabilities (called ‘libcontainer’) and also on messaging between containers (libchan). In the meantime the company already has exhibited an eagerness to consume its own environment with the ‘Orchard Labs’ acquisition. With a benevolent dictator in the shape of CTO Solomon Hykes at the helm there is a clear nexus of technic

d the project. From the beginning the starting

Eightee

dac

person “

bility of moving fast just by the use of its

ere of

Many i

ures m

a deca

Mware’s ESX/vSphere platform from

ere th

expecta

pportunities) lie between enterprise

y of

networ

nt Docker ecosystem. Areas like

ined

present

ing.

for the contents of containers) are

existi

d provide opportunities for both

start-up Over t

at the

Docker

less

aspects

s here

import

hat ha

ontainers (the ‘run’ part of will

to the ‘build’ and ‘ship’

estion o

ns to Docker?’ much less

ustry as a r

?’

”

Figure 4: Image showing the containers for shipping applications [4]

5

2. REVIEW 2.1 The Docker project The ‘Docker project’ is not the same as Docker Inc., the company. The Docker Inc. were somewhat like the guardian of the Docker project, they were at where it all started and are the major driving force behind it but they really don't own it. The Docker, the container techno Its ope

o con

they ad

licen

The aim

abou

and run

se awesome open tools to built, ship

r and

more t

e Doc

‘Docke

core

running

. The same way the VMware is ton ay more than Docker engine. The uilding & managing images and

know

Engine

te to the comparison, Docker

e tec

with th

er project technologies along

build

Everyo

dy to

industr

d in

core D

mpone

that ca It’s hea

e to it, use it and download it so long as

of goo avail

d. ibuting

the biggest names in the

there for t

on Github. By the way

Go’ or ‘GoLa

programming language

ee the plenary rec heavily developed bac

l

d.

Docker H

Docker registry, a place where

trieve the

Docker i

are almost over 240 thousands rep

es from

those repositories have been pulled and so downloaded and used well over a billion times. Over 5 million pulls and downloads every day. But that’s only public repositories and it’s only on the official Docker hubs. So Docker hub itself, it also has its private repositories then away from Docker hub there’s third party registries as well so the actual numbers will be even higher.

6

Figure

rom t

2.2 Co

Virtu

Contai

ual m

but the instead

VM same kin

in a ware.

olation & allocation aids,

use containe

operating system (OS)

ontainers are m

quiring less space and

efficien

2.2 CON Co taine togethe with

ion at the app layer that b

pendencies

rs are able to run on the same s

OS kernel

aking up less space. Each running

in user

space.

2.2.2 VIRTUAL MACHINES Virtual machines (VM), they are an abstraction turning single server into multiple servers. The hypervisor allows many VMs to run on one machine. Each VM contains a complete copy of an OS, one or more apps, necessary libraries and binaries - taking up tens of GBs. VMs can also be slow during booting time. 7

Figure 6

of Hy

Contai

el and

lesser R

mpare

commi

foot

princip

e deployed containers share overhead than VMs, so the

withi

assessm

ux con

2.3 Fo

PLAC

applicat

or

container against the same

of IB

published a performance

machines.

t pur

Do ker ca

Dock

which makes use of RAM over

icatio

applica

[6]

This can result into substantially

Conta

perform

1)

the Container

good for? CHINES (VMS) cing VMs in several situatio

rn about the

operating system, Docker can s

Not only is

to spin up, it is more light-weight

because

of its layered file system, it is much quicker and easier to share changes along with others. It’s also smoothly rooted in the command line and is extremely scriptable. 2) PROTOTYPING SOFTWARE If you want to experiment or make any changes with software without disturbing your current setup or going through the trouble of provisioning a VM, Docker can provide you a sandbox atmosphere in milliseconds. 8

3) ENABLING A MICROSERVICES ARCHITECTURE Docker facilitates the disintegration of a complex system into a sequence of compose-able parts, which allows you to reason about your services in a more discrete manner. This can permit you to restructure your software to make its parts more pluggable and manageable without disturbing the whole. 4) PACKAGING SOFTWARE Do

re be

dep

an c

run

ava, w

5)

se a Docker image has commendably no t your image and be assured that it can using a JVM.

S

Sin

eds o

net

n a single machine, so modelling

is ca

g real world scenarios without

bre 6)

LL-S

Sin

ndle

can

ese t

OFFLINE syste

to Docker containers, you

top and w

ove, even when you are

off 7) Co

UCIN ex ne

asp ct wit problem mann

VERHEAD different teams regardin We have individually experie

d is common sions about

; broken libraries; updates app

he wrong

bugs, and so on. Docker permits yo

(even in

script form) the steps for debugging the problem on a system with known properties, forming bug and environment reproduction a much easy & simpler affair, and one normally separated from the host environment given. 8) ENABLING CONTINUOUS DELIVERY Continuous delivery (CD) is a paradigm for software delivery based on a pipeline that rebuilds the system on every change and then delivers to production (or “live”) through 9

an automated (or partly automated) process. Because you can control the build environment’s state more exactly, Docker builds are more reproducible and replicable than traditional software building methods. This makes implementing CD much easier. Stand...