2. Pivotal
Perspectives
What’s shaping your future
Decentralized I.T. Workloads in more clouds, localized
app ownership, attention on self-service, and a shared
focus on business value.
Accelerating transformation. Companies moving faster
towards software-driven future. This means new skills,
and more diverse runtimes needed.
Security as a CEO priority. Threats, new and old, have
major business impact. Passive security isn’t enough.
Reactive architecture takes hold. Applications become
event-driven in order to drive real-time insight and
behavior.
3. Objectives
What are we seeing?
● Focus on Business Outcomes: realize business outcomes by achieving velocity
through faster time to market, integrated services, pipelines, reduced downtime and
business capability enhancements
● Increased Agility and Reduced risk: reduce lock-in by enabling multicloud; improve
agility and reduce delivery and project risk through agile methodologies
● Developer Experience and Enablement: enable patterns and services that support
developer innovation, increase productivity and ability to leverage emerging
technologies.
● Standard Operating Model: enable and enforce the Developer, Control and Operator
planes to enable development / operational efficiencies, reduce vulnerability closure
time (rotate, repave, repair), reduce incident frequency and minimize manual
processes
● Increased Infrastructure Utilization: lower infrastructure, software and switching
costs.
● Cost savings: Drive value for money and real savings by improved use of operations
and development teams, eliminating waste and driving modern practices at scale
4. The
Transformation
is Real
T-Mobile goes from 7 months and 72 steps to update
software, to same day deployments.
Liberty Mutual builds and deploys an MVP in one month
and delivers revenue-generating version just months later.
Comcast supports over 1500 developers with an operator
team of 4 people.
The Home Depot ships to production 1,500 times a
month, and 17,000 times a month to all environments.
5. Leading
companies trust
Pivotal
Usage across industries
Over ⅓ of the Fortune 100 depend on Pivotal.
Pivotal customers include::
7 of the largest banks
9 of the largest automakers
7 of the largest insurers
8 of the largest retailers
9 of the largest telcos
6. Operational
Efficiency
● Employ 500:1 developer
to operator ratio
● Perform zero-downtime
upgrades
● Runs the same way
on every public/private
cloud
Developer
Productivity
Comprehensive
Security
● Accelerate feedback
loops by improving
delivery velocity
● Focus on applications,
not infrastructure
● Give developers the
tools and frameworks
to build resilient apps
● Adopt a
defense-in-depth
approach
● Continuously update
platforms to limit
threat impact
● Apply the 3 R’s →
repair, repave, rotate
● Run platforms that
stays online under
all circumstances
● Scale up and down, in
and out, through
automation
● Deploy multi-cloud
resilience patterns
High Availability
The Pivotal value proposition
7. Cover w/ Image
Pivotal Facts
Formed in 2013 as spinout from EMC/VMware.
Chief Executive Officer is Rob Mee.
Mission is to
transform how the world builds software.
Key customers include Comcast,
Allstate, Ford, Citi, GE, Southwest, Verizon.
Investors include GE, Dell, Ford, and Microsoft.
Over 2,700 employees in 20 locations globally.
8. The Cloud Platform Evolution
Traditional IT
Storage
Servers
Networking
O/S
Middleware
Virtualization
Data
Applications
Runtime
You
Manage
O/S
IaaS
Storage
Servers
Networking
Middleware
Virtualization
Data
Applications
Runtime
You
Manage
IaaS
O/S
PaaS
Storage
Servers
Networking
Middleware
Virtualization
Data
Applications
Runtime
You
Manage
IaaS
Business Value, Agility &
Cost Savings
Level of Abstraction
PivotalCF
+
9. vSphere Openstack AWS
Google
Cloud
Azure &
Azure Stack
Shared Services
Shared Security
Shared Networking
Logging & Metrics / Services Brokers / API Management
Credhub / UAA / Single Sign On
VMWare NSX
Embedded Operating System (Windows / Linux)
Application Code & Frameworks
Buildpacks / Spring Boot / Spring Cloud / Steeltoe
PAS
Pivotal Application
Service
PKS
Pivotal Container
Service
PFS
Pivotal Function
Service
Pivotal Services
Marketplace
Pivotal and
Partner Products
Any App
Every Cloud
One Platform
Concourse
PCF 2.0 — for everything
that matters
10. Secure OS
(Windows & Linux)
(Embedded)
NSX-T
Silk/Flannel
CPI (15 methods)
v1
v2
v3
...
CVEs
Product Updates
Java | .NET | NodeJS
Pivotal Application
Service (PAS)
Application Code & Frameworks
Buildpacks | Spring Boot | Spring Cloud |
Steeltoe
Legacy Migration | Elastic | Packaged Software
| Spark
Pivotal Container
Service (PKS)
>cf push >kubectl run
YOU build the containerWE build the container
vSphere
Azure &
Azure StackGoogle CloudAWSOpenstack
Pivotal
Network
“3Rs”
Github
Concourse
Jenkins
Pivotal Services
Marketplace
Pivotal and
Partner Products
Continuous
delivery
Public Cloud
Services
Customer
Managed
Services
OpenServiceBrokerAPI
Repair
— CVEs
Repave
— VMs
Rotate
— Credhub
Ops
Manager
Releases
Deployments
Credhub
11. INFRASTRUCTURE
SITE RELIABILITY
PLATFORM
A Notional, High-Level Model
Agile Operations
Innovation; Plan, design, develop and test
business capabilities as deployable artifacts
Production Apps; config, deployment, QA,
monitoring, scaling
App Platform; upgrade PCF, capacity
planning, service mgmt., scale platform
Infra Platform; Rack and stack, networking,
data storage, etc.
ROLES
Cross-Functional
(Prod. Owner, Dev, QA)
Application Operators
Platform Operators
Engineering
(Storage, Security, Network, etc.)
AREAS OF FOCUS
BUSINESS CAPABILITY
12. Everything
you need to
transform Process &
Culture
Build for
change
Tools
Continuously
Improve
Platform
Any App, Every Cloud,
One Platform
PCF 2.0
Tracker / Spring / Concourse
Pivotal Labs
Data / AI
Apps
Culture, tools, and platform
14. “Transform our clients into
customer centric product
development organizations capable
of enabling teams to continuously
deliver products at startup speed
with enterprise scale.”
16. San Francisco Atlanta Berlin Boston Boulder Chicago
Dallas Denver Dublin London Los Angeles New York
Paris Palo Alto Toronto Singapore Sydney Tokyo
Some of Our Offices
17. “We want to be Agile,
but we don’t know how
to properly implement
and grow it within our
organization”
“It takes forever to
release new features.
We see new
opportunities to engage
with users, but we can’t
respond to change fast
enough.”
"My teams move quickly
at first, but we quickly get
bogged down as new
requirements come in. I
often have to rewrite
entire systems after
they're only a year or two
old."
Common problems we hear from clients...
19. Exploratory
Reducing the risk of lengthy
testing cycles by having an
integrated testing model
■ Pair Programming
■ Test-Driven Development
■ Short iterations
■ Continuous Integration /
Continuous Deployment
Lean
Reducing the risk of
building the wrong thing
while comfortably
changing direction.
User Centered
Design
Ensuring the software solves a
real problem for real users in a
desirable and usable product.
Extreme
Programming
Building working software at a
consistent speed and quality in
the face of changing
requirements.
Design
Product
Management
Engineering
PRACTICES PRACTICES PRACTICES PRACTICES
■ Minimum Viable Product
(MVP) definition
■ Lean experiments
■ Identify & test
assumptions
■ Data driven decisions
■ Tailor-made product
specific test strategy
■ Exploratory Testing and
Product Feedback
■ Automation Testing
■ User Interviews
■ Ethnographic studies
■ Persona definition
■ Prototype creation
Testing
24. How Did We Get Here ?
THROWAWAY CODE (QUICK HACK, KLEENEX CODE, DISPOSABLE CODE, SCRIPTING, KILLER
DEMO, PERMANENT PROTOTYPE, BOOMTOWN)
PIECEMEAL GROWTH (URBAN SPRAWL, ITERATIVE-INCREMENTAL DEVELOPMENT)
KEEP IT WORKING (VITALITY, BABY STEPS, DAILY BUILD, FIRST, DO NO HARM)
SHEARING LAYERS
SWEEPING IT UNDER THE RUG (POTEMKIN VILLAGE, HOUSECLEANING, PRETTY FACE,
QUARANTINE, HIDING IT UNDER THE BED, REHABILITATION)
RECONSTRUCTION (TOTAL REWRITE, DEMOLITION, THROWAWAY THE FIRST ONE, START
OVER)
2
26. Migrating the Monolith
OLD SCHOOL
Measure Twice, Cut Once
Detailed Application Assessment
Magic Quadrant Application Suitability
Static Analysis Rule Sets
Questionnaires
Analysis - Paralysis
NEW SCHOOL
Repeated smaller experiments
Push app to production
Test Driven Migration
Replatforming
Refactoring
Extreme Refactoring
2
27. What We Believe
Start With
“One Thing”
Keep Your
Feedback
Cycle as
Short as
Possible
Automate
Everything
You Can
(TDD,
CI/CD)
Build New
Skills
Through
Pairing and
By Doing
28. Don’t Plan Everything; Start Small and Let Your Work Inform the Strategy
How to Start
▪ Scope
- Get the right people in a room
- Define the business value to drive
- Identify candidate apps
▪ Discover & Frame
- Assess from a 15-factor standpoint
- Decide on migration flows
- Flag risks and assumptions
▪ Begin With a Time-Bound Pilot
- Designate the right people
- Work for 6 to 10 weeks
- Translate lessons into patterns