38
Diving Into Docker What It Means for Your Enterprise DevOps Strategy March 3 rd , 2016

Diving Into Docker

Embed Size (px)

Citation preview

Page 1: Diving Into Docker

Diving Into Docker What It Means for Your Enterprise DevOps Strategy March 3rd, 2016

Page 2: Diving Into Docker

2

Housekeeping

▪  This webinar is being recorded ▪  Links to the slides and the recording

will be made available after the presentation

▪  You can post questions via the GoToWebinar Control Panel, or…

▪  Join the conversation live on twitter using #DockerDive!

Page 3: Diving Into Docker

3

Meet Your Presenter

Andrew Phillips

VP of DevOps Strategy, XebiaLabs

▪  Lots of Enterprise Software Development on High-Performance Systems

▪  Been on Both Sides of the “Dev…Ops” Fence

▪  Active Open Source Contributor and Committer

Page 4: Diving Into Docker

4

Agenda

•  Setting the stage

•  Docker and microservices lightning intro

•  What do these mean for the enterprise?

•  Recommendations

•  Q&A

4

Page 5: Diving Into Docker

5

V I S I B I L I T Y

AUTOMATION

CONTROL

§  Continuous Delivery and DevOps pioneer, authority and technology leader

§  Global team in US, Europe & APAC

§  Consistently recognized by leading industry analysts

Connecting the dots for Continuous Delivery at enterprise scale

About XebiaLabs

VISIBILITY

AUTOMATION

CONTROL

Page 6: Diving Into Docker

6

Visibility and control across the Software Delivery Process

Integrates the tools you already have without customization

Fortune 100 proven, enterprise-grade technology

Scalable and fast to adopt

XebiaLabs: Proven software solutions for Continuous Delivery at Enterprise Scale

“IT organizations that have

tried to custom adjust current

tools to meet DevOps practices

have a failure rate of 80%”

V I S I B I L I T Y

AUTOMATION

CONTROL

1

2

3

4

Page 7: Diving Into Docker

Setting the stage

And how do we relate to this topic?

Page 8: Diving Into Docker

8

Setting the stage

This is not going to be a technical deep-dive into Docker, Kubernetes, microservices, etc.

We’ll be talking about:

▪  …what these technologies are ▪  …how they relate to all the existing technology

and process you already have ▪  …what you need to bear in mind if you’re considering adoption

Page 9: Diving Into Docker

9

Award-winning tools, recognized by leading industry analysts

Orchestrate, automate and get visibility into release pipelines

Automate and standardize complex application deployments

Analyze test results across multiple test tools

XebiaLabs Solutions: Connecting the dots for Continuous Delivery at enterprise scale

Page 10: Diving Into Docker

10

Provision

Plan Code Build Test Release Operate

Dev Test Prod

mainframe

Orchestratetheen8redeliveryprocess

Page 11: Diving Into Docker

11

Provision

Plan Code Build Test Release Operate

Dev Test Prod

mainframe

Deployanyapplica8on,acrossanytarget

Page 12: Diving Into Docker

12

Provision

Plan Code Build Test Release Operate

Dev Test Prod

mainframe

…andmakewell-informedreleasedecisions,basedonallyourtestdata

Page 13: Diving Into Docker

What is Docker? What are microservices?

Lightning introductions

Page 14: Diving Into Docker

14

What is Docker?

▪  Docker is a format for lightweight virtual machines that are easy to share between teams and companies, and easy to run identically anywhere from a developer’s laptop to a production environment

▪  Hype aside, teams (esp. developers) are looking at Docker because −  It’s a much more lightweight and easy-to-use format than other VMs −  Docker containers are convenient for local test environments,

especially if you’re developing microservices −  Docker containers can easily be shared

and extended, so promise a degree of reusability that other formats do not

−  The promise is that containers can be run much more resource-efficiently than existing virtual machines

Page 15: Diving Into Docker

15

What do people often mean by “Docker”?

▪  A “new paradigm” whereby all applications should be delivered as versioned containers by development teams −  New version of the app = new version of the (set of) containers −  Often also assuming that apps will be built as microservices

▪  The expanding ecosystem of container tools that enable this −  Multi-container frameworks −  Container runtime platforms −  Container delivery pipeline tools

Page 16: Diving Into Docker

16

What are “microservices”

▪  A microservice architecture is one in which a business application/ service is built by composing multiple small, independent elements (the “microservices”) that each perform a single business function

▪  “Moving to microservices” generally means not just architecting new applications in this way, but also converting existing (monolithic) applications to a microservice architecture by “splitting off” more and more functionality of the monolith into separate applications

Page 17: Diving Into Docker

What does this mean for you?

Page 18: Diving Into Docker

18

What changes with Docker?

Docker will impact: ▪  Development and delivery teams, as they will be

shipping “different stuff”

▪  Operations, as they will need to build out the runtime environment (including networking, monitoring etc. etc.)for containers

▪  Security, as they will need to develop new security policies for containers

Page 19: Diving Into Docker

19

What changes with microservices?

Microservices will impact: ▪  Architects, since a microservices transition is fundamentally an

application re-architecture ▪  Development teams and/or external development partners,

since they will have to write applications differently ▪  Testing/QA, since they will have to change the way they test

▪  Release/delivery teams, as they will need to handle many more moving parts

▪  Operations, as they will need better visualization and monitoring to understand what’s running at any given point in time

Page 20: Diving Into Docker

20

What does not change?

▪  Your delivery process does not magically become less complicated: many different tests, sign-offs etc. are still required

▪  Your cross-cutting concerns do not change: security/access control, auditability etc. all still need to be handled…and now with more technologies in the mix!

▪  Your existing applications and runtimes will still be around for a looooong time, even if you get started with Docker and microservices tomorrow

Page 21: Diving Into Docker

21

In brief

▪  Microservices especially will be a pretty disruptive change, Docker somewhat less

▪  Add to that the fact that the technology and best practices in this area are still very, very new and changing all the time

▪  As with most “new waves” of technology, there is very little effort being put into supporting a hybrid setup

▪  …and yet, that will be the reality for the vast majority of enterprises that adopt Docker and microservices for a loooong time

Page 22: Diving Into Docker

22

In brief

▪  That does not mean that you should not consider containers and microservices!

▪  Both Docker and microservices are incredibly promising and have the potential to make a significant impact −  …although, unlike virtualization, not so much from a

cost savings perspective

▪  Key point: identify what the business benefit will be for you ▪  Unlikely to be cost, but could be acceleration, reduction in errors,

employee satisfaction etc. etc.

Page 23: Diving Into Docker

Recommendations

Page 24: Diving Into Docker

24

What should you do now?

Investigate Docker and related technology:

Evaluate multi-container orchestration frameworks

Evaluate container runtime platforms

Understand how you will handle networking and storage

Understand how you will handle cross- cutting concerns: monitoring, access control, auditing etc.

1

2

3

4

Page 25: Diving Into Docker

25

What should you do now?

Understand how you will handle containers in your delivery pipeline/release process

Understand how you will deliver and run a hybrid setup −  …where some components of an application are

in containers, and others are not −  …where a fully-containerized application needs to

talk to other non-containerized services

5

6

Page 26: Diving Into Docker

26

What should you do now?

Investigate microservices:

Identify candidate applications that would benefit from a transition to microservices

Determine whether these smaller applications can be delivered as containers, or not

Understand how your delivery/release process will work when you are no longer delivering one monolithic applications, but many different microservices

1

2

3

Page 27: Diving Into Docker

27

What should you do now?

Understand how your delivery/release process will handle releases of “in transition” applications, where changes to the microservices that have been “split off” may be fast, but changes to the monolith very slow

Understand how you will track and visualize dependencies between the different microservices

Understand how you will monitor business transactions that may now span many different services

5

6

4

Page 28: Diving Into Docker

28

What should you do now?

Quantify the business benefit: §  What would the benefits of containerization be? Are they

sufficient to outweigh the risk of adopting new technology very early in the cycle?

§  What would the benefits of moving to microservices? For new applications, are they sufficient to outweigh the complexity of having many more moving parts? For existing applications to be migrated, do they outweigh the cost of migration?

§  Microservices and containers do not have to go together – you may find that you can justify one, but not the other

Page 29: Diving Into Docker

What is XebiaLabs doing?

Page 30: Diving Into Docker

30

HowcanXebiaLabshelp?

We’redoingawholebunchofthingstohelpyoubereadyforthistransi7on,shouldyoudecidetogodownthispath:

▪  Automa8on:supportforcommoncontainerpla;ormsandframeworksinourreleaseanddeploymenttools−  providesconsistency,supportsstandardiza7onand

takescareofcross-cu@ngconcernssuchasaccesscontrol,audi7ngetc.inahybridenvironment

Page 31: Diving Into Docker

31

HowcanXebiaLabshelp?

▪  Visibility:Supportfordependencymanagementinourdeploymenttools−  helpsyouhandletheincreasedcomplexityofthemanymovingparts

inamicroserviceenvironment−  givesyouinsightintothestateofyourdeliverypipelinesatall7mes−  capturesmetricstohelpyouiden7fyboDlenecksandguide

improvements

Page 32: Diving Into Docker

32

HowcanXebiaLabshelp?

▪  Control:supportforadvanceddeliverypaDernsinourreleasetool−  releasetrainsallowindividualteamstoiteratequicklyastheybreak

awayfromthemonolith,whiles7llprovidinganaggregateoverviewforthereleaseteam,projectmanagersetc.

−  handlerequirementsaroundcompliance,audit,repor7ng,processenforcementetc.

Page 33: Diving Into Docker

33

HowcanXebiaLabshelp?

▪  Scale:asingle,simpleinterfaceandintegra7onapproachacrossteamsandapplica7ons−  reducethelearningcurveforonboardingofnewteamsandprovidea

consistentinterfaceforOpera7onstosupportbothcontainersandexis7ngapplica7onsinahybridenvironment

▪  Guidanceandadvice−  Thisisaveryfast-movingspace,andmostofourusershavetoomuch

goingonalreadytodiveintoyetanothernewtopicinmuchdetail.We’reheretohelpyouunderstandhowcontainersandmicroservicescouldfitintoyourlandscape

Page 34: Diving Into Docker

34

Continuing Education

Check Out Our Many Other Microservices and Docker Resources… ▪  xebialabs.com/solutions/microservices/ ▪  xebialabs.com/solutions/docker/

Page 35: Diving Into Docker

35

Other Great Resources

▪  Get Started with XebiaLabs for Free Today! www.xebialabs.com/products

▪  Download The IT Manager’s Guide to Continuous Delivery xebialabs.com/resources/whitepapers/the-it-managers-guide-to-continuous-delivery/

blog.xebialabs.com

@xebialabs

youtube.com/xebialabs

Page 36: Diving Into Docker

36

§  Continuous Delivery and DevOps pioneer, authority and technology leader

§  Global team in US, Europe & APAC

§  Consistently recognized by leading industry analysts VISIBILITY

AUTOMATION

CONTROL

Page 37: Diving Into Docker

37

Questions?

VISIBILITY

AUTOMATION

CONTROL

Page 38: Diving Into Docker

Thank you!