The number of connected devices is growing at an accelerated pace. We developers must have the knowledge & skills to help make that happen. But how? As device deployments and data collected grow exponentially, DevOps is the answer to fast, consistent, and sane systems, organizations, and developers. This session will provide a brief-but-thorough examination of key DevOps tenets and how they apply to large-scale deployments of small-scale devices and the platforms that tie them together. A live-coding demo will convert these concepts from ideas to implementations.

1. IoT to Cloud, the DevOps Way
Development at Web Scale on Web Time
Mark Heckler
Principal Technologist & Developer Advocate
Pivotal Software, Inc.
www.thehecklers.org
@MkHeck

2. @MkHeck
Agenda
• Define “DevOps”
• History and perspective
• Why DevOps? Why for IoT in particular?
• Digging In
• IoT: Matches, Misses, & Adaptations
• Walkthrough/Demo/Live Discussion
• Summary

3. @MkHeck
What IS It?
Simply stated:
• Development (Dev)
• Operations (Ops)
• Dev + Ops == DevOps

4. @MkHeck
Traditional Relationship

5. @MkHeck
Historically Opposed Due to
Conflicting Objectives
• Developers’ sole reason for being: drive change
• Better support organization’s objectives
• Hopefully increasing funds available to
organization in the process
• Market/field isn’t immutable; failure to adapt is
death

6. @MkHeck
Historically Opposed Due to
Conflicting Objectives
• Operations’ primary objective: maintain expected
level of service
• Risk/reward balance inverse of developers
• Change is a very real threat to an ops org
• “Don’t touch” policies can take many forms

8. @MkHeck
Why Mess With It?
• “If it ain’t broke, don’t fix it.”
• But it IS broken…
• Time == Money
• At Stake: SURVIVAL

9. @MkHeck
–W. Edwards Deming
“It is not necessary to change. Survival is not
mandatory.”

10. @MkHeck
–Steve Jobs (1995)
“Software is infiltrating everything we do these days. In
businesses, software is one of the most potent
competitive weapons.”
–Marc Andreessen (2011)
“Software is eating the world.”
–Jeff Immelt, GE (2015)
“…every industrial company has to be a software and
analytics company.”

11. @MkHeck
“Silicon Valley is coming. There are hundreds of startups
with a lot of brains and money working on various
alternatives to traditional banking…
We are going to work hard to make our services as
seamless and competitive as theirs.”
–Jamie Dimon, CEO of JP Morgan Chase & Co, 2015 letter to shareholders

12. @MkHeck
Bring Developers and
Operations Together
• Shared Objectives
• Shared Pain
• Shared Reward

13. @MkHeck
–Mel Conway, 1968
“Any organization that designs a system
(defined broadly) will produce a design whose
structure is a copy of the organization’s
communication structure.”

14. @MkHeck
–Werner Vogels, Amazon (2006)
“Giving developers operational responsibilities has greatly enhanced the
quality of the services, both from a customer and a technology point of
view. 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.”

15. @MkHeck
Why is this Important?

16. @MkHeck
Keep CALMS and DevOps

17. @MkHeck
Culture
Sometimes when people see gourmet food and ping pong
tables, they only see the most superficial aspects.
They wonder out loud if people won’t abuse the opportunity.
If people can’t be trusted with food and ping pong, what
makes you think they can be trusted with delivering the
future of a company?

18. @MkHeck
Automation (CD)
–Noah Sussman, Etsy
“If pushing is easy enough, then pushing a fix will be too.”
“Instead of fearing change, we get people used to it. The
risks change, but we take steps to address the risks. It’s a
different way of developing software.”

19. @MkHeck
Lean (Microservices)
Loosely coupled service oriented
architecture with bounded contexts
If every service has to be updated in
concert, it’s not loosely coupled!
If you have to know about surrounding
services you don’t have a bounded
context.

20. @MkHeck
Again: Why is this Important?

21. @MkHeck
IoT: Matches
• Focus upon people and change
• Continuous Integration
• Continuous Delivery
• Measurement
• Collaborative environment

22. @MkHeck
IoT: Misses
• CI/CD for extreme endpoint (often “dumb”) devices
• Direct focus upon end user (with exceptions)

23. @MkHeck
IoT: Adaptations
• Infrastructure as Code
• Microservices

24. Time for a Walk(through)

25. @MkHeck
Example IoT Architecture

26. @MkHeck
An Example of an Enabling
Platform: Cloud Foundry
One consistent API
• On-premises
• Public cloud
• Any provider

27. @MkHeck
Other Helpful Components

28. @MkHeck
Summary
• DevOps isn’t NoOps, HugOps, or ToolOps, but…
• Roles of Devs, Ops do change
• Trust & collaboration a requirement
• Tools enable everything (rapidly, repeatably)
• Already “doing DevOps”? Adapt for IoT
• No? IoT provides overwhelming incentive to do so

29. @MkHeck
Discussion

30. @MkHeck
–Derek Sivers, founder of CD Baby
“The most brilliant idea, with no execution, is worth $20.”

31. @MkHeck
Let’s Keep the Conversation Going!
• www.thehecklers.org
• @MkHeck on Twitter
• Stay in touch, exchange thoughts, and SHARE!
• Thank you for participating