KUBERNETES AS A FRAMEWORK FOR WRITING DEVOPS & MICROSERVICES TOOLING
Cloud Foundry Summit 2015: Devops, microservices and platforms, oh my!
-
Upload
pivotal -
Category
Technology
-
view
965 -
download
1
Transcript of Cloud Foundry Summit 2015: Devops, microservices and platforms, oh my!
• no experience • no mentors • no testing • no backups • no version control • no automation
¯\_(ツ)_/¯
Computational Science
• model bioelectric fields• solve for measurements• visualize• rinse and repeat
Linux ‘server’ in your Pocket
• custom board• 400 MHz PowerPC• 64 MB SDR SDRAM• 512 MB NAND FLASH• USB Powered• biometric auth
Big Vision
• Identity Solution• Policy Based Provisioning• Citrix Desktop• On demand ‘deb’ package• Poison Pill• Mostly Worked
Learned More Things
• Formative• Learned to Computer• Introduced to Agile™• Testing• Project Management• Lord Conway Reigns• Disassociated Identity
Automation…
• write a script for common tasks
• share the scripts around office
• modify the scripts for new task
• hope things works
–Werner Vogels, CTO Amazon
“The traditional model is that you take your software to the wall that separates development and operations, and throw it over
and then forget about it. Not at Amazon. You build it, you run it. This brings developers into contact with the day-to-day
operation of their software. It also brings them into day-to-day contact with the customer. This customer feedback loop is
essential for improving the quality of the service.”
Software in the beginning
• shipped on physical media
• hard to change after release
• runs on other peoples computers
• have to worry about bugs
• process doesn’t run very long
• no worries about uptime
The Process
• have a good idea!
• request a server
• get a purchase order from supervisor
• wait
• wait
• server arrives
• server gets power and network
• server gets operating system
• start to configure for deploy
Traditional IT
The System Admin
• keeps systems running
• don’t care about your application
• not paid to care
• other people waiting for their servers
• might have to worry about many other servers
• and email
• and printers
The shift to services
• the internet changes everything
• runs on other your computers
• can change your computers
• still have to worry about bugs
• process run a long time
• uptime is everything
The Process
• have a good idea!
• request a server
• get a server in minutes
• run configuration tools
• everything is up in minutes
Netflix Lessons
• Speed wins in the marketplace
• Remove friction from product development
• High trust, low process, no hand-offs between teams
• Freedom and responsibility culture
• Don’t do your own undifferentiated heavy lifting
• use simple patterns automated by tooling
• self service cloud makes impossible things instant
But we are an enterprise, we do not have the talent to do this.
“But Netflix has a superstar development team, we don’t”
microservices leverage baseline operational capabilities and team dynamics to isolate failure and maximize velocity
continuously delivered microservices are the natural evolution for services that need to run at scale and be changed frequently
Amazon, Google, Netflix, Flickr, Etsy, WealthFront, Lyft, Uber, Shopzilla, Pied Piper, all built one off platforms to do this
The Process
• have a good idea!
• push code to platform
• code is running in seconds
• self service
• self healing
• and they all lived happily ever after
no one originally set out to do devops, continuous delivery, microservices, or platforms these were natural consequences
don’t fixate on the words, fixate on the outcomes