Top Banner
DevOps and Infrastructure
37

DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

May 21, 2020

Download

Documents

dariahiddleston
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

DevOps and Infrastructure

Page 2: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

3. Infrastructure

● Mainframes● Servers● Hypervisors● Virtual Machines● Containers

2.

1. DevOps

● what is DevOps?● Case Study: Netflix● Statistics● Common problems● Advantages● Mindset and tools

4.

2

Page 3: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

What is DevOps ?

3

DevOps is a set of practices that combines software development (Dev) and information-technology operations (Ops) which aims to shorten the systems development life cycle and provide continuous delivery with high software quality.

● Not a tool

● Not a software

● Not a programming language

Page 4: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Case study: Netflix

● Netflix started as DVD rental business

● Introduced its online streaming offering in 2007

● In 2015 the service accounted for over 36% of downstream internet traffic in

North America

● In 2017 its users streamed a little over a billion hours of content each week

● Started moving to cloud providers in 2008, a process they finished in January

2016

● In April 2017, Netflix surpassed one million containers launched a week.

4https://amido.com/blog/a-case-study-of-devops-at-netflix/

Page 5: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Case study: Netflix

“Our journey to the cloud at Netflix began in August of 2008, when we experienced a major database corruption and for three days could not ship DVDs to our members. That is when we realised that we had to move away from vertically-scaled single points of failure, like relational databases in our datacenter, towards highly reliable, horizontally-scalable, distributed systems in the cloud.”

Yury Izrailevsky, VP, Cloud Computing and Platform Engineering, Netflix.

5https://amido.com/blog/a-case-study-of-devops-at-netflix/

Page 6: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

What statistics says

● Traditional Ops are 41% more

time-consuming overall

● Traditional Ops spends an average of 7.2

hours weekly on communication

● Traditional Ops spends 21% more time

putting out fires

● DevOps spends 33% more time on

infrastructure improvements

● DevOps spends 60% less time handling

support cases

● 55% notice improved cooperation and

collaboration

● 38% report a higher quality of code

production

6https://www.upguard.com/blog/devops-success-stats

Page 7: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

So what are we trying to solve ?

7

Page 8: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Common problems

8

Page 9: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Common problems

9

Page 10: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Advantages

● Faster delivery of software● Saves Time and money● More reliable systems● Happier people

10

Page 11: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Mindset and tools for DevOps

If you’re a Developer:

how to make your life easy?

Think of Automation

11

● what tools do you use as a developer?● how do you keep versions of your code?● how do you test a program? unit tests? integration tests?

● how do you provision your environment?● how do you deploy your app?

Page 12: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

12

Page 13: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Do Open Source have something for developers ?

13

Page 14: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Vagrant

what is vagrant?

Vagrant is an open-source software product for building and maintaining portable virtual software development environments, e.g. VirtualBox, KVM, Hyper-V, Docker containers, VMware, and AWS. Vagrant is written in the Ruby language, but its ecosystem supports development in a few languages.

14

Page 15: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Vagrant

why using vagrant ?

15

Cross-platformOpen Source Declarative config file

Page 16: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Vagrant

who uses vagrant ?

16

Page 17: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Vagrant architecture

17

https://hackernoon.com/devops101-vagrant-6737c8c29904

Page 18: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Vagrant - sample Vagrantfile

18

Page 19: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Vagrant - sample Vagrantfile

19

Page 20: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Infrastructure

20

Page 21: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Early 1960s

21

Mainframes

One server (mainframe) serve one application, where IBM dominated the market

Users connected through dump terminals to the mainframe computer(Central)

Centrally located, inflexible, high cost of purchase, maintenance and support

Page 22: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Early 1990s

22

Servers

Demand of applications increased, so the need of mainframes, and mainframes started getting smaller which then called (servers)

Still one Application on each server

Efficient, improving server components like CPU, RAM and Storage, and networks

Servers filled the mainframes cabinets then called Data Centers

Page 23: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Late 1990s and early 2000

23

Hypervisors and Virtual Machines

More increase of application demand

VM started to appears on what is called (Hypervisors)

Data Centers became more efficient and more flexible

Virtualization led to Cloud computing which started with AWS

Page 24: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Since 2006

24https://dzone.com/articles/evolution-of-linux-containers-future

Page 25: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

25

Page 26: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Data Centers evolution for Enterprise

26ServersMainframes Hypervisors and VMs Containers

Page 27: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Data Centers evolution

27

How much time does it take to get new servers ? (Vendors)

What about getting it ready inside Data Center ? (DC Ops)

OS level batching, monitoring, logging and alerting ? (Sys Admins)

ServersMainframes Hypervisors and VMs Containers

Page 28: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Config Management

28

How much time does it take now using the cloud ?

Servers Mainframes Hypervisors and VMs

Containers

Page 29: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Config Management

29

Config management introduced new ways and platforms for management

Page 30: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Config Management benefits

30

● You declare and state your desired configuration

● Allows you to define you machine state● Enables you to analyze, check and test your

configuration● Enable teams to collaborate

Page 31: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Do Open Source have something for System

Admins ?

31

Page 32: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

what is Ansible?

Ansible is an open-source software provisioning, configuration management, and application-deployment tool. It runs on many Unix-like systems, and can configure both Unix-like systems as well as Microsoft Windows. It includes its own declarative language to describe system configuration.

32

Ansible - Introduction

Page 33: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

why using Ansible ?

33

Cross-platformOpen Source Declarative config file

Ansible - Introduction

Page 34: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

Ansible architecture

34

Page 35: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

35

Ansible - sample inventory

Page 36: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

36

Ansible - sample playbook

Page 37: DevOps and Infrastructure · of mainframes, and mainframes started getting smaller which then called (servers) Still one Application on each server Efficient, improving server components

37

Thanks for listening