Observe, Enhance, & Control: VMs to Containers
•
1 gostou•245 visualizações
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2953E8u. Mitchell Hashimoto takes a look at VMs, what solution architectures worked there, and discusses why these architectures are no longer adequate in a containerized world. Hashimoto then discusses how these same problems are being solved today, and how we can expect similar problems to be solved as the container world matures. Filmed at qconlondon.com. Mitchell Hashimoto is best known as the creator of Vagrant, Packer, Terraform and Consul. Mitchell is the founder of HashiCorp, a company that builds powerful and elegant DevOps tools.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais de C4Media
Mais de C4Media (20)
Último
Último (20)
Observe, Enhance, & Control: VMs to Containers
- 1. Observe, Enhance, Control: From VMs to Containers
- 2. InfoQ.com: News & Community Site • 750,000 unique visitors/month • Published in 4 languages (English, Chinese, Japanese and Brazilian Portuguese) • Post content from our QCon conferences • News 15-20 / week • Articles 3-4 / week • Presentations (videos) 12-15 / week • Interviews 2-3 / week • Books 1 / month Watch the video with slide synchronization on InfoQ.com! https://www.infoq.com/presentations/ vm-containers
- 3. Purpose of QCon - to empower software development by facilitating the spread of knowledge and innovation Strategy - practitioner-driven conference designed for YOU: influencers of change and innovation in your teams - speakers and topics driving the evolution and innovation - connecting and catalyzing the influencers and innovators Highlights - attended by more than 12,000 delegates since 2007 - held in 9 cities worldwide Presented at QCon London www.qconlondon.com
- 7. HashiConf 2016 June 13-15 Amsterdam One day of training followed by two days of talks in Amsterdam on all things HashiCorp HASHICONF.EU > by HashiCorp
- 8. Observe, Enhance, Control: From VMs to Containers
- 9. Welcome to the Age of Containers!
- 10. or… Age of Reinvention?
- 13. Monitoring Configuration Deployment Nagios Sensu Chef Puppet Fabric Chef, Puppet Still W idely Used!
- 14. What is going on? • Not a singular event • Happening across a lot of categories • The work of many well-accepted “smart” people • Gathering real adoption! (Or, real abandonment)
- 19. Age of the Virtual Machine (Circa 2006)
- 20. Circa 2006 Datacenter • No APIs • No elasticity • Monolithic applications • Young IaaS
- 21. Circa 2006 Datacenter Problems • No APIs • No elasticity • Monolithic applications • Young IaaS • Uniformity of servers • Scalable change management • Auditing server state • Early service discovery
- 22. Circa 2006 Datacenter Problems Software • No APIs • No elasticity • Monolithic applications • Young IaaS • Uniformity of servers • Scalable change management • Auditing server state • Early service discovery • Manual node (de)registration • Single master servers • Check/correct divergence • Agent model • (Relevant: lots of Ruby)
- 23. Circa 2006 • Datacenters introduce constraints • Applications fill constraints and cause problems • Software written to help solve those problems in an architectural way that is comfortable for the time
- 24. Datacenter + Problems → Software
- 29. Applying the Model • What happens if we apply the same model to today? • Will it fit? • What would it tell us?
- 30. Age of the Container (Present Day, 2016)
- 31. Today: 2016 Datacenter • API-driven • Highly elastic • Small, bin-packed servers • Containers on VMs • Fast
- 32. Today: 2016 Datacenter Problems • API-driven • Highly elastic • Small, bin-packed servers • Containers on VMs • Fast • Infrastructure management • Service discovery • Configuration • Scale: speed and size
- 33. Today: 2016 Datacenter Problems Software • API-driven • Highly elastic • Small, bin-packed servers • Containers on VMs • Fast • Infrastructure management • Service discovery • Configuration • Scale: speed and size ?
- 34. Today: 2016 Datacenter Problems Software • API-driven • Highly elastic • Small, bin-packed servers • Containers on VMs • Fast • Infrastructure management • Service discovery • Configuration • Scale: speed and size • Distributed systems • Failure expectation • API-driven, Infra as Code • Low resource usage
- 35. Today: 2016 • Software designed for a 2006 architecture doesn’t adapt well to the needs of software in 2016 • Rather than wait for existing vendors to catch up, new vendors are showing up and filling in gaps
- 39. 2006 vs 2016 • My disclaimer: the examples used from 2006 are still highly deployed, highly successful, and highly relevant. • But that shouldn’t stop the community (and hasn’t) from trying new designs and testing if they’re better • It is going to take years to reach the same level of maturity and production-hardening
- 40. From VMs to Containers: Molding Our Thinking
- 41. Out vs. Up Build Out Build Up
- 42. Build Out • New tools • Not abstracting anything new • Solve existing problems • Lay a new foundation
- 43. Build Up • Assume lower layers are correct (or correct enough) • Leverage existing solutions • Create new abstractions
- 44. Out and Up • I argue we had to build out for containers • The build out will continue • What will we build up? (Platforms?)
- 45. Age of Reinvention • We aren’t reinventing anything. • We’re building the same wheels, but instead of for a car they’re for a fighter jet.
- 47. Watch the video with slide synchronization on InfoQ.com! https://www.infoq.com/presentations/vm- containers