How to Implement Agile/DevOps without Leaving Legacy Behind

24
How to do DevOps Without Leaving Legacy Behind June 2015

Transcript of How to Implement Agile/DevOps without Leaving Legacy Behind

Page 1: How to Implement Agile/DevOps without Leaving Legacy Behind

How to do DevOps Without Leaving Legacy Behind

June 2015

Page 2: How to Implement Agile/DevOps without Leaving Legacy Behind

ABOUT THE PRESENTER

Justin Nemmers

@[email protected]

15+ years in US Public SectorHPC administration backgroundConsultingTechnicalSales

Page 3: How to Implement Agile/DevOps without Leaving Legacy Behind

87% of Federal IT managers said they can’t develop and deploy new

systems as fast as the mission requires, citing delays from

operational, policy, and security requirements.

MeriTalk 2015 PS Survey

Page 4: How to Implement Agile/DevOps without Leaving Legacy Behind

THEMES IN IT TODAYDEVOPS AND CLOUDo Seismic shift in how organizations work with IT

OPERATIONAL AGILITYo Automation is required for both DevOps and

Cloud

DEFINE ONCE, RUN ANYWHEREo Automation improves cloud-posture and

technology adoption

INFRASTRUCTUREo Best and easiest place to start w/ automation

Page 5: How to Implement Agile/DevOps without Leaving Legacy Behind

WHAT IS DEVOPS

COLLABORATIVEo Complete end-to-end application lifecycle

management

COHESIVE (COMBINES FUNCTIONS In Theory)o Developmento QA, and o IT operations all working together

FORWARD-LOOKINGo Typically applied to greenfield environments

Page 6: How to Implement Agile/DevOps without Leaving Legacy Behind

DEVOPS IN LEGACY IS HARD

Page 7: How to Implement Agile/DevOps without Leaving Legacy Behind

ENTRENCHED

Page 8: How to Implement Agile/DevOps without Leaving Legacy Behind

LARGE EXISTING

INVESTMENTS

Page 9: How to Implement Agile/DevOps without Leaving Legacy Behind

REUSEIS

DIFFICULT

Page 10: How to Implement Agile/DevOps without Leaving Legacy Behind

BUSY

Page 11: How to Implement Agile/DevOps without Leaving Legacy Behind

TEAM SPANNING

Page 12: How to Implement Agile/DevOps without Leaving Legacy Behind

COMMUNICATION

Page 13: How to Implement Agile/DevOps without Leaving Legacy Behind

DEVOPS NEEDS AUTOMATION

ENABLES REUSEo Leverage existing people, processes, and (often)

technology

INCREASES SAVINGSo Free up time for value add

SPANS SILOSo Keep teams working efficiently with easy

interaction

CREATES REPEATABILITYo Lather, rinse, repeat

Page 14: How to Implement Agile/DevOps without Leaving Legacy Behind

THE LANGUAGE OF ENTERPRISE IT

o Ansible is the first “infrastructure-as-code” that can be read and written across IT… from sys-admins to developers to managers

o Ansible is the only automation engine that can automate the entire application lifecycle & continuous delivery pipeline

DEV/TEST Q/A OPERATIONS MANAGEMENT INFRASTRUCTURE

Ansible Playbook

From development… to production.

Page 15: How to Implement Agile/DevOps without Leaving Legacy Behind

WHY INFRASTRUCTURE FIRST?

o Lots of repetitiono Well defined and understood

processeso High valueo Many consumerso Near-immediate impact

Page 16: How to Implement Agile/DevOps without Leaving Legacy Behind

Typical MethodManualLacks…

continuous compliance

feedback loopsportabilitycooperationcoordination

Page 17: How to Implement Agile/DevOps without Leaving Legacy Behind

CONTINUOUS DELIVERY FOR OS

o Leverage existing build toolso Employ automation to eliminate manual

processeso Frequent small updates with security

baseline testing/applicationo Constant validation to baseline and

definitiono New and existing systems look the sameo OS environments gets version controlo Re-use OS layer in new deploymentso Adopt changes faster

Page 18: How to Implement Agile/DevOps without Leaving Legacy Behind

ANSIBLE & CONTINUOUS DELIVERY

Ansible Tower connects development to operations by

orchestrating complex application environments:

o Application Codeo OS Updateso Web Serverso Databaseso Load Balancerso Networkingo VMs or Cloud Instanceso … and more

Page 19: How to Implement Agile/DevOps without Leaving Legacy Behind

DevOps MethodAutomatedProvides

continuous compliance

feedback loopsportabilitycooperationcoordination

Page 20: How to Implement Agile/DevOps without Leaving Legacy Behind

BENEFITSREDUCES TIME TO DELIVERYo Development and QA get access to prod-configured resources more quickly

IMPROVES COLLABORATIONo Consumers of servers have clear method to define and request changes

ELIMINATES OUTLIERSo Old systems look the same as new systems

INCREASES ASSURANCEo Initial and ongoing compliance validation

EASES TROUBLESHOOTINGo Something breaks? Compare existing to definition for immediate

transparency

PROMOTES ADOPTIONo Automation doesn’t remove responsibility from concerned teams

Page 21: How to Implement Agile/DevOps without Leaving Legacy Behind

GET STARTED

o Automation toolingo Determine Lowest common

denominatoro Automate security baseliningo Unify current build processo Enable auto-application of updates

through CI/CD on OS layer

Page 23: How to Implement Agile/DevOps without Leaving Legacy Behind

CONTACT US

DLT Solutions | Enterprise Solutions Team

www.dlt.com/ansible877.742.8358

[email protected]