Everyone has a platform. The choice is not between having a platform or not, the choice is between having an ad hoc organic platform or a deliberate structured platform. An army of administrators running scripts is a platform. The emergence of system automation tools provided powerful abstractions to increase the velocity and consistency beyond traditional approaches, but left orchestration and integration to be accomplished by additional scripts or manual processes. These tools and processes formed new platforms for deploying and managing software services. The new automation frameworks, like Cloud Foundry, represent the first generation developed after the advent of api driven cloud computing. This presentation will walk through the evolution of systems and software, the emergence of the process and practices driving innovation at scale, highlight the patterns of successful platforms leveraging both technology and people to deliver value with practical advice for evaluating and implementing change in the context of your organization. Visit http://pivotal.io/event/vmworld to see the rest of our sessions at VMworld.

1. devops, platforms,
and devops platforms
Andrew Clay Shafer
Senior Director of Technology

2. Andrew Clay Shafer

3. Andrew Clay Shafer
@littleidea

4. EMC Federation
Rules Everything
Around me

5. devops,
platforms,
and devops platforms

6. wat

7. start with definitions?

8. everyone has a platform

9. just kidding
we’ll come back to that

10. start with a story

11. start with my story

13. how did that happen?

14. Previously…

15. The power of automation!!!

16. automation at scale

17. turning the pages

18. I’m sure some of you
have lived this too

19. maybe you didn’t
(maybe you are about to)

20. this scenario played
out over and over

21. everyone trying to
solve similar problems
everyone making
similar mistakes

23. what you automate is just as
important as the fact you do

24. technology can resist automation

25. day 2 matters

26. the architecture matters

27. please quit building installers

28. please quit building
brittle clever solutions

29. please quit building stuff that
will predictably explode

30. Typical Day at Work
maybe you like being a hero?
maybe your co-worker does?

32. Operations is the secret sauce configuration

33. paying interest on technical debt

34. paying interest on automation debt
architecture debt
process debt

35. everyone
over
and over
and over

36. WHERE IS YOUR DEVOPS NOW?

37. there has to be a better way

38. let’s rewind to definitions

39. What is devops?

40. I wrote a blog post.
March 2010

41. devops
• developers and operations can
and should work together
• system administration evolving to
look more like software
development
• evolving together as global
community sharing solutions

42. devops - calms
• culture
• automation
• lean
• metrics
• sharing

43. What is a platform?

44. Everyone has a platform…

45. might be the one guy who runs scripts
might be a bunch of configuration management
might be a public PaaS

46. if you can deploy and operate code
in any capacity, you have a platform
maybe not be very good one

47. who cares about the word…

48. what about success?

49. ‘devops actualized’ represent patterns
that emerged in high performing
organizations that deliver highly available
applications continuously at scale

50. devops,
platforms,
continuous delivery,
microservices…

51. These things
are all one…

52. faster and safer
BLAH BLAH BLAH BLAH
OODA LOOP
SMALL BATCHES

53. from now on, I’m going to call all
that together… ‘Cloud Native’

54. what would cloud natives do?
wwcnd

55. Amazon, a bookstore in Seattle, deploys
code to production every 11 seconds…
1 second

56. –Werner Vogels, CTO Amazon
“The traditional model is that you take your software to the wall
that separates development and operations, and throw it over
and then forget about it. Not at Amazon. You build it, you run it.
This brings developers into contact with the day-to-day
operation of their software. It also brings them into day-to-day
contact with the customer. This customer feedback loop is
essential for improving the quality of the service.”

57. Adrian Cockroft - ex-Netflix
What I learned from my time at Netflix.

58. Netflix Lessons
• Speed wins in the marketplace
• Remove friction from product development
• High trust, low process, no hand-offs between teams
• Freedom and responsibility culture
• Don’t do your own undifferentiated heavy lifting
• use simple patterns automated by tooling
• self service cloud makes impossible things instant

59. Principles > Practices >Tools

60. why > what

61. Netflix Lessons
• Speed wins in the marketplace
• Remove friction from product development
• High trust, low process, no hand-offs between teams
• Freedom and responsibility culture
• Don’t do your own undifferentiated heavy lifting
• use simple patterns automated by tooling
• self service cloud makes impossible things instant

62. Netflix built a platform to enable
self service deployment

63. Netflix built a platform to deploy
and operate microservices

64. Netflix built a platform to
continuously deliver software

65. Netflix built a platform that could
protect itself from failure

66. What Netflix did not do is build a platform
for general ad-hoc automation…

67. Constraints are the contract that
allows a platform to keep
promises.

68. Everyone has a platform.
What promises can
your platform keep?

69. SLAs
we promise

70. Pivotal Cloud Foundry
promises starts at the API

71. •current_vm_id
•create_stemcell
•delete_stemcell
•create_vm
•delete_vm
•has_vm?
•reboot_vm
•set_vm_metadata
•configure_networks
•create_disk
•delete_disk
•attach_disk
•snapshot_disk
•delete_snapshot
•detach_disk
•get_disks
Cloud Provider Interface

72. Cloud Native Infrastructure Automation
CPI

73. need to manage a large distributed system
• deployment
• configuration changes
• updates/upgrades - minimal downtime
• health checks and remediation
• scale out/scale in
• across multiple IaaS

74. Everything as a Service

75. Now that we have a tool chain for
release engineering, deployment,
and lifecycle management of large-
scale distributed services…
What should we do with it?

76. deploy a self-service self-healing
container scheduler, of course!

77. routers
Linux
LinuxLinux
Containers
message bus
cloud controller
loggregators
controller DB
etcd
hm9000
metrics firehose
UAA
login
Cloud Foundry Elastic Runtime
service
brokers
object
store
stagers

78. Cloud Native Runtime Platform
Cloud Native Infrastructure Automation
CPI
BOSH release

79. • role based access to resources
• run code on demand
• coordinate cross service
configurations
• route public requests
• read and write persistent data
• add and remove resources
• record internal and external
events
• isolate resources and failures
• measure performance/health
• detect and determine failure
(plan & provoke failure)
• recover failures
• work tomorrow
What problems does it solve?

80. 12 Factor Ops

81. your pipeline to continuously
deliver microservices is ready
(and win buzzword bingo)

82. ask me about distributed
runtime configuration, service
discovery, and circuit breakers

83. the patterns proven successful
building and operating highly
available systems with predictable
scaling and failure characteristics

84. Cloud Native Runtime Platform
Cloud Native Infrastructure Automation
Cloud Native Application Framework
CPI
BOSH release
12 Factor
Cloud Native Contracts

85. structured contracts
determine the promises a
platform can keep

86. simple patterns
automated by tooling

87. simple patterns
automated by tooling

88. simple patterns
automated by tooling

89. This is the
cloud native
advantage

90. This is what helps
organizations move
quickly at scale

91. Conway’s Law Rules Everything Around You

92. Motivated to change the relationship
between people and the computers
I never set out to DO devops.

93. actually, needed to change the
relationship between people and people

94. no one originally set out to do devops,
continuous delivery, microservices, or
platforms these were natural consequences
don’t fixate on the words, fixate on the outcomes

95. if you want to align people in your
organization, think about the
interfaces, look at the promises they
make and keep with each other.

96. Use tools and simple
patterns to make doing the
right thing the easy thing

97. can you keep promises?

98. DO YOU KEEP PROMISES

99. DOES YOUR PLATFORM
HELP YOU KEEP PROMISES?

100. Thank You
@littleidea

101. We are uncovering better ways of developing software,
by doing it and helping others do it