2014/06/10 Dockercon Day 2

by Gene Kim on

#dockercon

Up: Seth Lochen, Release Engineering Mgr, Groupon

  • Lochen: part of Groupon transformation story also involves creating service-oriented architecture, resulting in breakthroughs@nickstinemates: Technology agnostic. Consistent environments. Main reasons for adopting Docker at @Groupon
  • RT @nickstinemates: Technology agnostic. Consistent environments. Main reasons for adopting Docker at @Groupon
  • Lochen: "We do continuous integration; of course, dev runs tests on their system, passes; then it breaks on the CI boxes."@rjtech: RT @electriccloud: Congrats to @tanayciousd @therealnikhil & @Siddhartha90 for being Top 3 #dockercon hackathon winners! Good luck w/ fina…

Up: Solomon Hykes, Founder, CTO of Docker (@solomonstre)

  • .@solomonstre: "Modern sw requirements: loosely coupled, highly scalable, able to use the work of others...
  • .@solomonstre: "We need to make services independent of the infrastructure it runs on; machines are ephemeral (break, go down)
  • @nickstinemates: "Why are we here? Applications have changes. Loosely coupled components iterated quickly and incredibly scalable. Globally."
  • .@solomonstre: "Often, it means we're spending tons of time building a platform, gluing things together
  • .@solomonstre: "Alan Kay: in 70s, the internet seemed like scalable design, we should make a virtual internet of virtual machines that could be cached by hardware; it's really too bad it didn't happen"
  • @rberger: @solomonstre keynote talking about making Alan Kay’s dream come true of a virtual internet of virtual machines
  • @borja_burgos: .@solomonstre "We have a blueprint" #Dockercon Exciting
  • @nasrat: #dockercon @solomonstre talking about collaboration of hackers to build cross cutting large solutions. Arpanet, UNIX, Linux, the web ...
  • .@solomonstre: "What is needed is a standard interface [to achieve Alan Kay's 1970s Internet dream: virtual internet on virtual machines]
  • .@solomonstre: "containers;
  • .@solomonstre: "sandboxing incl libcontainer: betw docker & kernel: namespace, cgroups, capabilities, netlink, selinux, apparmor
  • @Regannc: Dockers not "it", it's a channel to get "it" done - Solomon #dockercon #docker
  • @doug_borg: @solomonstre: “The real value of @docker is not technology, it is getting people to agree on something.”
  • .@solomonstre: "libchan: like Go for channels: allows RPC, worker patterns, can send channels over channels (!!)
  • .@solomonstre: "libchan: like Go channels for network: designed to be easily ported
  • .@solomonstre: "@nickstinemates: @nickstinemates ".. available on spdy, websockets, tcp, Unix sockets, or go channels"-
  • .@solomonstre: "Orchestration: heard lot of it yesterday: I think it's combo of clustering & combination;
  • .@solomonstre: "exciting prob: look at all these solns: shipper mesos geard helios centurion coreos/fleet
    https://pbs.twimg.com/media/BpyDrlvIMAATIgt.jpg
  • .@solomonstre: "announcing libswarm: allows way to combine and organize svcs in distributed system
  • @jonathan_thorpe: .docker ecosystem was looking as fragmented as android! Libswarm to the rescue. Very impressed with the libraries announced
  • @rberger: #dockercon libswarm std interface, compose complex arch from std blocks. avoid vendor lock in, built in library or write you own w API
  • @yugui: #dockercon libswarm has many adaptors to e.g. mesos, fleet, GCE, ... hmm, it certainly sounds like libvirt for service orchestration
  • @nasrat: #dockercon great screen cast from @aanand of @orchardup of aggregate adaptor for libswarm.
  • @nasrat: #dockercon great screen cast from @aanand of @orchardup of aggregate adaptor for libswarm.
  • @sam_alba: RT @cquinn: Libswarm to provide a standard interface for clustering. Mesos, geard, fleet/etcd, google, etc. #dockercon http://t.co/yaqQoYr
  • @jimmycuadra: Awesome new announcements this morning at #dockercon by @solomonstre: libcontainer, libchan, libswarm. These folks are always a step ahead.
  • @johncosta: RT @kartar: Just watched three #docker hosts aggregated and clustered with one command using lib swarm at #dockercon So much awesome.
  • @yugui: #dockercon libswarm; I guess it decouples overall system design from resource allocation and scheduling provided by service providers?
  • .@solomonstre: "Next: help solve probs around authorization & entitlement; to be secure & reliable, we need better foundation
  • @philwhln: Sneak peep of next @Docker component - "Authorization".
  • @jitterted: Next components in Docker ecosystem are identity and authorization and are really important.
  • @RealGeneKim: Awesome. Thx! #dockercon@brentsmi: @RealGeneKim @yugui Here's some good background from our blog: http://t.co/BroZ37UeEw
  • @borja_burgos: .@Docker is doing it RIGHT. Awesome presentation by @solomonstre. Inspiring. #dockercon #libswarm #libchan #libcontainer
  • @kit_plummer: @solomonstre audit needs to be a first-class problem along with authn/authz.
  • @kit_plummer: @solomonstre audit needs to be a first-class problem along with authn/authz.

Up: Jerry Cuomo, Fellow, IBM, CTO Websphere (had blast hanging w/him & @astryker; @JerryCuomo is teller of amazing war stories

  • Cuomo: "Coming together as an industry is so important; feels like 1997, where an industry movement was created [around Java]
  • .@JerryCuomo: "If we do this right as an industry, our users will thank us; break down borders; freedom of choice; speed
  • .@JerryCuomo: "If we give developers speed & flexibility, we give them joy and their lives back [so they can spend w/families
  • .@JerryCuomo: "Let's let developers be fast, but without being sloppy; the only way is the open way
  • .@JerryCuomo: "@rberger: @jerrycuomo: The Open Way is the ONLY WAY! #dockercon http://t.co/JICzNLtpoL
  • .@JerryCuomo: "The Open Way shouldn't mean vanilla or substandard; it should mean [the best way]; repeatable, continuous
  • .@JerryCuomo: "Why am I here at #dockercon? We love docker; docker is the eraser of the borders between clouds"
  • .@JerryCuomo: "
  • @mariusducea: “Docker is the ‘eraser’ of the borderless cloud”
  • .@JerryCuomo: "IBM is undergoing transformation; my entire career, we sold pkged software; now we sell svcs like Blue Mix PaaS
  • @docker: RT @ypeyret: #dockercon is back trending on Twitter!! @docker @DockerCon #BOOM http://t.co/3aeUQFeJWT
  • .@JerryCuomo: "@astryker & team won Netflix CloudOSS Prize" (@adrianco gave prize at Amazon re:Invent conf last yr; congrats!
  • .@JerryCuomo: "Docker + JVM: startup times 2x faster, density per server 2x higher (vs virtualization)
  • .@JerryCuomo handing stage over to @aspyker to demo Acme Air: laptop deploy, burst to cloud, bash w/Chaos Monkey, etc. Neat.
  • @philwhln: "We lost a lot of memory optimization when we virtualized WebSphere. We got that back with @Docker" - @JerryCuomo at #Dockercon
  • (Genuinely curious: Why do people snicker at Java? Some of most admired properties rely on it: Google, Twitter, Facebook..
  • @gazoombo: RT @rberger: “My body has none of the cells I had when I was a baby, but I don’t think I was rebooted for maintenance” @solomonstre at #doc
  • @robertvila: RT @docker: .@JerryCuomo and @aspyker live demo at #dockercon http://t.co/l82cTsEkxM
  • @aneel: @aneel: "Persistent volumes with Docker – Data-only container pattern" http://t.co/g13cliSJEL

Eric Brewer, VP Infrastructure, Google

  • Great talk!! Thank you! @eric_brewer: Slides from my keynote today:
    https://t.co/uffESiLuTU #dockercon

  • @flomotlik: Now Eric brewer from google talking about containers
    @nasrat: Google launches 2B containers a week. Containers in VMs in containers. Issues - interference cpusets, fake NUMA, cgroups., memcg.
    @nasrat: Google launches 2B containers a week. Containers in VMs in containers. Issues - interference cpusets, fake NUMA, cgroups., memcg.

  • @google . #dockercon http://t.co/MdRN2iszee

    https://pbs.twimg.com/media/BpyOpi9CAAAqdT6.jpg

  • RT @flomotlik: Now Eric brewer from google talking about containers @google . #dockercon http://t.co/MdRN2iszee

  • @VMTrooper: Why Containers? - Application-centric view of resource deployment instead of machine-centric view - @eric_brewer

  • @kartar: .@eric_brewer “I wish we’d done Docker images like Docker has … but well now they’ve done it.” :) #docker

  • @stu: Google felt lonely using containers, now "Docker made them exciting and much easier to use" - they are real & useful @eric_brewer

  • @spkane: RT @enmodo: #dockercon Google launches about 2 billion containers per week...

  • RT @spkane: RT @enmodo: #dockercon Google launches about 2 billion containers per week...

  • @ineverthink: Great to see @WIRED on the intro slide for @eric_brewer , read the article here! http://t.co/doORGDHQrc #dockercon #wired #condenast

  • !!! RT @borja_burgos: Even @google could not do containers as well as @docker and the community have done them

  • @stu: Google can do #bigdata workloads due to slack resources (basically free) - goal of using all resources all the time

  • @loribudin: RT @nickstinemates: Eric Brewer Google "we've been using containers similar to Docker for years. We wished we'd done them the way @docker d…

  • @yugui: Eric from Google is talking about common issues in containerization and how to solve them.

  • @nickstinemates: "There is no reason you shouldn't be using all of your resources all of the time." Let's pick up the slack time.

  • @aneel: "in your own apps…you will want to take back your slack resources…and containers will make that easier to do" -@eric_brewer

  • @CITEworld: RT @M_Wein: I wrote about Google's #dockercon announcements, and went into why people love #Docker so much. http://t.co/rn38QNQxFR

  • @pdi: RT @docker: .@ericbrewer on why we love containers at #dockercon http://t.co/3KvpAS4INM

  • @aneel: "we can detect interference by looking at cycles per instruction" -@eric_brewer

  • @VMTrooper: Isolation enforcement in the kernel is critical for performance - @eric_brewer

  • @everpeace: RT @philwhln: "With containers utilization goes down. Nothing else can use those allocated resources. We need slack resources" @eric_brewer

  • @fuzzychef: Google: "We do containers in VMs on top of containers."

  • @borourke: Docker cluster management via kubernetes seems well thought-out... https://t.co/bzx6xpLAIK

  • @aneel: "hope to move LMCTFY functionality to libcontainer" -@eric_brewer

  • @philwhln: "We rarely use single containers. We use groups of nested containers that we call pods" @eric_brewer of Google at

  • @nasrat: lmctfy stable declarative API for resources important to integrate/migrate into libcontainer. cAdvisor container stats & history.

  • @jameskyle75: Google to support docker in their lmctfy container stack. https://t.co/LKYoyyJIFh

  • @mariusducea: cadvisor for container stats and alerts released by @google for the #dockercon hackathon.

  • @VMTrooper: cAdvisor OSS from Google provides stats & alerts for container utilization - @eric_brewer

  • @CloudOfCaroline: RT @philwhln: "We rarely use single containers. We use groups of nested containers that we call pods" @eric_brewer of Google at

  • @ShadowSoftNews: Google's Eric Brewer "OSS containers based on Docker are a core foundation for the future." #opensource #dockercon http://t.co/WrLTtm8XUO

  • @HoReaL: RT @philwhln: New post: "libswarm - Docker Orchestration Announced" http://t.co/xGl6nL0IcL

  • @DockerParis: RT @googlecloud: We've got big announcements: @docker support. Kubernetes. Container stack improvement. http://t.co/IQ7Khs37hS

  • @Sion_Smith: RT @mariusducea: cadvisor for container stats and alerts released by @google for the #dockercon hackathon.

  • @nasrat: Groups of containers (pods) how Google uses containers. Eg shared volumes for log rotation.

  • @philwhln: "Regret: Should have used 1 IP per pod, so that we could define ports at build time" @eric_brewer of Google at

  • @programm3rq: Woo! Another cloud scheduler! #dockercon http://t.co/qCzs6nZ3ww

  • @dguyadeen: RT @philwhln: "OSS containers based on @Docker are the containers that we want to use" @eric_brewer of Google at

  • @tanmaypatil: RT @solomonstre: Here are the slides for my #dockercon presentation. Thanks again @laurelcomics for your amazing illustrations. http://t.co
    @borja
    burgos: .@google marketing team: please please please... Change the name of LMCTFY.
    @gabrtv: "We should have used IP address per pod (group of containers)" -@ericbrewer #dockercon <- interesting, avoids late binding problems
    @aneel: groups are defined by queries against labels/tags— sets can change over time, queries are standing and dynamic -@eric
    brewer

  • @DutchGoogleDevs: An Update on Container Support on Google Cloud Platform #dockercon #cloudplatform #developers

    We're excited… https://t.co/RhTrvXUb63

  • @rjweeks70: Very interesting noting the difference in tweets coming from #dockercon vs #cfsummit vs #cloudexpo. Three entirely different worlds.

  • @0xE4C5: RT @jpetazzo: One of the big announcements of #dockercon (from a "in the trenches" tech perspective) is https://t.co/vFtiUTAd0a. ORCHESTRATE

  • @brianm: RT @docker: Thanks to our today's awesome keynote speakers! #dockercon http://t.co/iP2WNVVJwJ

  • @chihiro: RT @enmodo: #dockercon three new libraries to rule them all... Okay not rule, just help them all get along in perfect harmony. http://t.co/

  • @mkumar1: RT @zzamboni: “Having an explicit desired state is a good idea“ @eric_brewer - where have I heard that before? @cfengine

  • @RealGeneKim: #dockercon Thx! RT @silentlennie: @RealGeneKim because smaller companies prefer less code and most Java styles are very verbose.”

  • @RealGeneKim: #dockercon This is true. At least Java8 has lambda, but… “@dhable: @RealGeneKim Too much repetition in syntax. Feels like talking w/RainMan

  • @doug_borg: @caffeinatederic Just goes to show you can always learn good practices and lessons from a Borg. #dockercon #kubernetes

  • RT @doug_borg: @solomonstre: “The real value of @docker is not technology, it is getting people to agree on something.”

  • RT @jonathan_thorpe: docker ecosystem looking as fragmented as android! Libswarm to the rescue. Very impressed with libraries

  • RT @rberger: #dockercon libswarm std interface, compose complex arch from std blocks. avoid vendor lock in, built in library or write w API

  • Wow. RT @kartar: Just watched three #docker hosts aggregated and clustered with one command using lib swarm at #dockercon So much awesome.

  • RT @yugui: #dockercon libswarm; I guess it decouples overall system design from resource allocation & scheduling provided by svc providers?

  • RT @kit_plummer: @solomonstre audit needs to be a first-class problem along with authn/authz.

  • RT @rberger: @jerrycuomo: The Open Way is the ONLY WAY! #dockercon http://t.co/JICzNLtpoL

  • RT @mariusducea: “Docker is the ‘eraser’ of the borderless cloud”

  • RT @philwhln: "We lost a lot of memory optimization when we virtualized WebSphere. We got that back with @Docker" - @JerryCuomo #Dockercon

  • RT @nasrat: Google launches 2B containers/week. Containers in VMs in containers. Issues: interference cpusets, fake NUMA, cgroups

  • RT @ineverthink: Great to see @WIRED on the intro slide for @eric_brewer; article here! http://t.co/doORGDHQrc #dockercon #wired #condenast

  • RT @stu: Google can do #bigdata workloads due to slack resources (basically free) - goal of using all resources all the time

  • RT @dguyadeen: RT @philwhln: "OSS containers based on @Docker are the containers that we want to use" @eric_brewer of Google at

  • @VanL: RT @philwhln: "Regret: Should have used 1 IP per pod, so that we could define ports at build time" @eric_brewer of Google at

  • RT @VanL: RT @philwhln: "Regret: Should have used 1 IP per pod, so that we could define ports at build time" @ericbrewer of Google at
    @gabrtv: "We should have used IP address per pod (group of containers)" -@eric
    brewer #dockercon <- interesting, avoids late binding problems

  • RT @gabrtv: "We should have used IP address per pod (group of containers)" -@eric_brewer #dockercon <- interesting, avoids late binding problems