Embed Size (px)
Citation preview
[email protected]@josh_atwellgithub.com/joshatwell
NotWinner
Infrastructure Extensibility at Home and in DevOpsan Ignite Talk
Infrastructure Extensibility
• APIs and SDKs to manage• Integration with common tools
@josh_atwell
Infrastructure Extensibility
• APIs and SDKs to manage• Integration with common tools
• Agility to change programmatically• Maximum feature availability
@josh_atwell
Image from bestbuy.com@josh_atwell
@josh_atwell
@josh_atwell
I can’t get the TV audio on and the mower is mowing the neighbor’s driveway again.
¯\_(ツ)_/¯
@josh_atwell
@josh_atwell
@josh_atwell
Why Does Infrastructure Matter to DevOps?
Continuous Integration for code deployment is a sign
of DevOps maturation
@josh_atwell
@josh_atwell
The “Great”Wall of
Deployment
@josh_atwell
CLI based expect scripts
Integrations only available through manufacturer
Very little agility
Limited accessibility
@josh_atwell
• APIs and SDKs becoming common
• REST for the wicked• Integration with common tools
@josh_atwell
@josh_atwell
@josh_atwell
Policy Based Management• Policies define identity and behavior
@josh_atwell
Policy Based Management• Policies can be one to many• Consistent, flexible, predictable• Control and monitor configuration drift
@josh_atwell
The“Great”Wallof
Deployment
>“helloworld!”
Leveraging new infrastructure capabilities to bridge over the wall of deployment
>“helloworld!”>“helloworld!”
@josh_atwell
@josh_atwell
