Things will Change - Usenix Keynote UCMS'14


Published on

From servers and containers, to services and things. Building an Internet of Things of the clouds and infrastructure we're building today. Maps the future of configuration management and systems artifact management.

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Things will Change - Usenix Keynote UCMS'14

  1. 1. Things will Change Eric Windisch UCSM’14 June 19th
  2. 2. Visionary • Built wearable computer in 2000 • Began building and selling PaaS-like solutions in 2002 • Began selling VM-based VPS in 2006; • Began architecting “cloud” IaaS in 2007 at historic price-points ($5/mo VMs!) • OpenStack contributor since Q1 2011 • Joined Docker in January 2014 @ewindisch
  3. 3. Configuration management
  4. 4. Containers
  5. 5. Microservices
  6. 6. “The Operating System is Dead”
  7. 7. “Two years ago, I said to a colleague: The kernel is dying.
 Now I fear the distribution is dying.”
  8. 8. “Containers technology finally leverages the things the kernel does well.”
  9. 9. “There is, of course, the matter of orchestrated per-tenant VM clusters which run clouds of containers — such as Google does.”
  10. 10. “Its close alignment to the Internet of Things is the disruptive element
 of the microservices movement”
  11. 11. Things
  12. 12. “It’s no surprise that embedded network programming is usually bad, if most developers are working, not only with 80’s hardware, but with developer libraries of a similar vintage — as far as networking is concerned.”
  13. 13. The Cloud
  14. 14. Shoud
  15. 15. “There is no such thing as stateless.”
  16. 16. “However, we can not prevent state from changing. We cannot kill the Chaos Monkey.”
  17. 17. “It is naive to think we can simply throw away VMs or containers — we want to preserve their state for archival and analysis.”
  18. 18. “The biggest problem with blind a d h e r e n c e t o i m m u t a b l e infrastructure & 12-factor… is ignorance of the importance of the implicit state of a system which should not be deemed disposable.”
  19. 19. Things
 will Change
  20. 20. “We cannot control change, we can only effect it and manage it.”
  21. 21. Microservices will Change
  22. 22. “APIs and sensors, both, are inputs.”
  23. 23. Containers
 will Change
  24. 24. “We need to manage containers like we manage Things. Products that do not do this are not good long-term solutions for managing containers.”
  25. 25. Distributed SYSTEMS
  26. 26. C A P
  27. 27. “Because we cannot kill the Chaos Monkey, we need to know how to collect its droppings.
 1 2 - f a c t o r a n d i m m u t a b l e infrastructure fail to acknowledge this.”
  28. 28. “We need to manage change, not prevent it”
  29. 29. Puppet?
 Chef? Ansible? Salt?
  30. 30. “They are not designed for microservices. They are not designed for Things. They are designed for creating change, not for capturing it.”
  31. 31. “My fear is less that they’ll fail to evolve, but that they’ll lose their identities in the process..”
  32. 32. “One could… use Chef as a cloud orchestration solution — in fact, this was the initial scheduling for the Deis project.”
  33. 33. “The new pattern will be to configure Things through their own APIs, rather than through custom agents.”
  34. 34. “This [new fashion of configuration management] will work on all Things, all devices, and across Operating Systems — even Windows.”
  35. 35. “ We c a n n o l o n g e r a b i d e configuration management tools that use specialized agents.”
  36. 36. The future of management services
  37. 37. “Application-specific discovery and inventory mechanisms won’t go away, no more than Gopher has.”
  38. 38. “Just as Hypertext provided an implicit graph, linking and building relationships between websites — our next generation of web technologies will offer an explicit graph to provide discovery and inventory.”
  39. 39. Changing Things
  40. 40. “The worst thing I have to say about Heat is that OpenStack as a whole tends to be overly insular, m a k i n g t h e a d h o c u s e o f components such as Heat, an uncommon exercise. Still, Heat supports standalone installation.”
  41. 41. “In some ways, Chef might already offer many of the right things for the next generation, if only at a relatively local, non-global scale.”
  42. 42. Now you have 2
  43. 43. ”What we need today are hyper- connected Things”
  44. 44. “MQTT solves important problems related to accessing sensor data, but not all the problems of accessing and controlling things.”
  45. 45. Things at REST…
  46. 46. “The primary issue with REST is that it’s not a protocol. It is at best a guideline. That’s not strict enough for building a hyper- connected web.”
  47. 47. “Protocols such as MQTT provide value as a buffer to support idempotency for REST access to Things, but this works better for retrieving data, rather than creating or updating it.”
  48. 48. Things as Services
  49. 49. Proto-types
  50. 50. “MQTT itself is a protocol, not a document-type… but if it doesn’t do all the things we need, we either need a different protocol, or multiple.”
  51. 51. “Every time you create a new standard to solve a problem, you have two problems.”
  52. 52. Upgrade the Internet
  53. 53. “We want to do more. We want devices to connect. We want those devices to know not just who to speak to, but how to speak to others.”
  54. 54. “Google could be super seded by t h e S e m a n t i c Web” — Tim Berners-Lee
  55. 55. “Recognizing that what we want is a Semantic Web, gives us context for researching and understanding the efforts that have come before.”
  56. 56. Semantic Web
  57. 57. “The RDF and OWL efforts have been nearly complete failures.”
  58. 58. “The Semantic Web should not just express the context of things, but provide discoverability.”
  59. 59. Now… time for something different.
  60. 60. “libswarm builds libchan, which builds on top of existing protocols such as SPDY and HTTP2, or WebSockets.”
  61. 61. “This new Internet, or web, needs to be about all Things, not all Devices. Where all services are Things and all Things are services.”
  62. 62. “We need new services and c onfigurati on management solutions that work across devices, clouds, and containers.”
  63. 63. “We need to bet on free, open, and semantic hyper-connected protocols — whatever those protocols may be.”
  64. 64. “Today, we are changing our servers, but tomorrow — We want to change the world.”
  65. 65. Thank you.
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.