Anúncio
Check these out next
OSCON: Incremental Revolution - What Docker learned from the open-source firehouse
24 de May de 2016•0 gostou•2,620 visualizações
1 gostaram
Seja o primeiro a gostar disto
mostrar mais
visualizações
Vistos totais
0
No Slideshare
0
De incorporações
0
Número de incorporações
0
Baixar para ler offline
Denunciar
Tecnologia
Since Solomon Hykes unveiled Docker at the PyCon conference three years ago, containers have revolutionized how developers and ops teams build, ship, and run applications. Solomon explores the past, present, and future of our container ecosystem and shares lessons learned from managing successful open source projects across several dimensions: technology, people, products, and business. Sign up for the Docker for Mac and Windows beta: beta.docker.com
Docker, Inc.Seguir
Docker, Inc.Anúncio
Anúncio
Anúncio
Recomendados
PaaSTA: Running applications at YelpNathan Handler
OSCON: Better Collaboration through ToolingDocker, Inc.
Building a Docker Swarm cluster on ARM by Dieter Reuter and Stefan Scherer Docker, Inc.
DockerCon EU 2015: Finding a Theory of the Universe with Docker and Volunteer...Docker, Inc.
From Docker Swarm to OCCS and Wercker: Live-hacking at Oracle CODE Mexico 2017Frank Munz
OSCON: System software goes weirdDocker, Inc.
OSCON: Incremental Revolution - What Docker learned from the open-source firehouse
- Incremental revolution What Docker learned from the open-source firehose
- Docker in a nutshell:
- 1. The world needs tools of mass innovation.
- 2. A programmable Internet would be the ultimate tool of mass innovation.
- A commercial product, built on a development platform, built on infrastructure, built on standards. 3. Docker is building a stack to program the Internet.
- Open-source at Docker 50+ repositories 2000+ contributors 18000+ github issues 1200+ patches/month
- What did we learn from the firehose?
- No is temporary, yes is forever. If you're not sure about a new feature, say no. You can change your mind later. Yes, I know they have pitchforks.
- Challengers: use open source to level the playing field.
- Open-source is your slingshot. What you aim for is up to you.
- A case study
- Problem: Developing for Docker on the Mac is too hard.
- 1. Too complicated to install 2. Broken file sharing 3. Broken networking 4. Vbox is slow and buggy 5. Doesn’t feel “native” Top 5 Docker issues on Mac
- 1. Too complicated to install 2. Broken file sharing 3. Broken networking 4. Vbox is slow and buggy 5. Doesn’t feel “native” Docker for Mac Solution:
- Docker for Mac 30,000 developers signed up in the first 24 hours https://beta.docker.com
- The best platforms have a great developer experience…
- … backend by hard systems engineering The best platforms have a great developer experience…
- Docker for Mac architecture (simplified)
- Hypervisor Framework vmnet Framework Docker Container Engine Hypervisor Linux VPN Data Service Interface Client Libraries Admin GUI CLI Security Sandbox Docker for Mac internals
- Hypervisor Framework vmnet Framework Docker Container Engine Hypervisor Linux VPN Data Service Interface Client Libraries Admin GUI CLI Security Sandbox Docker for Mac internals
- Hypervisor Framework vmnet Framework Docker Container Engine Hyperkit Linux VPNKit DataKit Client Libraries Admin GUI CLI Security Sandbox Improving Docker with unikernel tech
- Let’s open-source some stuff!
- Learn more about Hyperkit, VPNKit, DataKit Docker Contribute Session Tomorrow 3pm, room 6 Don’t miss the Docker & Unikernel talk! Today 11:55am, ballroom A Come say hi! @solomonstre
- Thank you!
Anúncio