18
DevOps – how we do it Marina Nikitchuk Anton Krasikov

DevOps - how we do it

Embed Size (px)

Citation preview

DevOps – how we do it

Marina NikitchukAnton Krasikov

15 GLOBAL LOCATIONS:

NYC

London Switzerland

Germany

Eastern Europe

Latin America

Who We Are

DataArt is a technology consulting firm that builds end-to-end solutions to help clients achieve their business goals.

INDUSTRY EXPERTISE:

Financial Services Travel & Hospitality

Healthcare & Life Sciences

Media & Entertainment

IoT/M2M

Telecom

Intros

• Anton Krasikov

• Solution architect, PM & DevOps

• 8.5 years with DataArt

• Telecom, retail, travel, finance

• Now ~ 1.5 year in banking

What’s up?

• What is DevOps?

• How we do it

• Practises and tools

• Challenges

DevOps – what is it?

• Culture, movement, practice

• Bridge between development, QA and operations

• Agile methodologies’ best friend

• Continuous delivery

DevOps components

How we do it

• Plan

• Agile – Kanban, SCRUM

• JIRA, YouTrack

• Code

• Source control management – GitHub, Stash

• Code review

• Infrastructure as a Code – Ansible/Chef/Puppet

How we do it

• Build

• Continuous Integration – Jenkins, TeamCity

• Packages & versions – Maven, Artifactory

• Infrastructure – Docker, Ansible, Puppet, Chef

• Test

• Automation – JUnit, Selenium

• Reporting

• Infrastructure – Docker, Puppet

How we do it

• Release & Deploy

• CI server

• Custom scripts

• JIRA integration

• Operate & Monitor

• Logging – Splunk, ELK (ElasticSearch/LogStash/Kibana)

• Monitoring – Zabbix

Continuous delivery pipeline

Example – Java web app

• Version control – Git

• Build – Maven

• Build server – Jenkins

• Infrastructure & provisioning – Vagrant/Puppet

• QA – Selenium/JUnit

• Release process – custom build script with phase rollout

• Automatic rollback on every stage

Challenges

• DevOps – cultural change

• Learning new tools

• Business pressure

• Legacy systems

Questions?

Thank you!