Don't Dev the Wrong Ops

Transcript

1. © Copyright 2017 Pivotal Software, Inc. All rights Reserved. Version 1.0 Don’t Dev the Wrong Ops Chuck D’Antonio Boston DevOps Meetup October 25, 2017
2. Does Your DevOps Have a Brain?
3. Does your DevOps Have a Brain?
4. Product Perspectives Usability How will users experience this product? Feasibility Can this product be built and maintained. Viability Is there a market for this product? Balanced
 Team Product
 Management Product
 Design Engineering Empathy Value Quality
5. The Product Value Stack Users Needs Uses Features Deliver LEARN
6. Effective Iteration is Key… MVP The smallest feature set you can build to gather validated learning. Pivot or Persevere Decision to stay the course or change strategy. Not a change in vision. Innovation Accounting A concrete way to know whether your team is learning.
7. What Are You Providing? Speed To Market Degree Of Opinion / Standards Container Orchestration Services Ecosystem Multicloud Infrastructure Automation Elastic Scale High Availability CD Pipeline Monitoring & Mgmt Self-Service/RBAC App & Platform Zero Downtime Upgrades App & Platform Security Java/.Net Microservices Support Logs, Metrics & Tracing Packaging & Ent. Support Dev/Prod Parity Technical Debt Creation Platform Technology
8. If it has a ticket today… It should have an API tomorrow
9. Your product is not just technology
10. The anti-goal OPERATORS DEVELOPERS PLATFORM OPERATORS
11. Establish a Platform Team Establish a Continuous Delivery Practice Establish a Cloud Native Dev Enablement team Establish avenues for Dev, Ops Collaboration Strong Exec Support and one Owner/Champion Dev Ops Key Activities
12. Auto-scaling High Availability Observability Security Zero Downtime Updates … Health Management Acceleration of Your Digital Transformation $$$$ ROI Funds Transformation Replatform Modernize Migrate Runs on Your Platform Existing Workloads Cloud Native Built for Your Platform New Initiatives Cloud Native Modernize Replatform Migrate
13. The Value of Your Platform Security ! High Availability ! Blue/Green ! Resilience
 ! Initial Dev Setup ! App Dev ! Release Engineering ! Day 2 Operations ! Infrastructure Costs ! Middleware ! OS ! Automation Software ! Elasticity ! Resource Utilization ROI
14. Measures of Platform Success Stability Speed Scalability
15. What really matters to Comcast
16. You don’t want unnecessary toil
17. Typical Platform Evolution !17 Scripting Built some automation and containers New Reality
18. CONTAINERS EVENT-DRIVEN FUNCTIONS DATA SERVICES MICROSERVICES Batches MONOLITHIC APPLICATIONS Companies have many ways to package and run their workloads in the cloud
19. Their goal: pick the right runtime for each workload CONTAINERS EVENT-DRIVEN FUNCTIONS DATA SERVICES MICROSERVICES Batches MONOLITHIC APPLICATIONS IaaS Container Orchestrator (CaaS) Application
 Platform (PaaS) Serverless
 Functions (FaaS)
20. Container Orchestrator Container Scheduling Primitives for Network, Routing, Logs & Metrics CONTAINER Choose the right tool for the job Developer Provides Tool Provides Application
 Platform APPLICATION Container Orchestrator Serverless Functions FUNCTION Application Platform IaaS Container Image & build L7 Network & Routing Logs, Metrics, Monitoring Services Marketplace Team, Quotas & Usage Function scheduling Function exec services Container Orchestrator
21. Container Orchestrator Container Scheduling Primitives for Network, Routing, Logs & Metrics CONTAINER Choose the right tool for the job Developer Provides Tool Provides Application
 Platform APPLICATION Container Orchestrator Serverless Functions FUNCTION IaaS Container Image & build L7 Network & Routing Logs, Metrics, Monitoring Services Marketplace Team, Quotas & Usage Application Platform Container Orchestrator Function scheduling Function exec services Lower complexity, higher efficiency Higher flexibility, lower standardization
22. Hardware IaaS Container Orchestrator Application Platform Serverless Functions Strategic goal: Push as many workloads as technically feasible to the top of the platform hierarchy Higher flexibility and less enforcement of standards Lower development complexity and higher operational efficiency