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.
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
15. “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.”
19. “However, we can not prevent
state from changing. We cannot kill
the Chaos Monkey.”
20. “It is naive to think we can simply
throw away VMs or containers —
we want to preserve their state
for archival and analysis.”
21.
22. “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.”
34. “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.”
45. “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.”
47. “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.”
48.
49. “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.”
55. “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.”
56. “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.”