embrace devops : delivery value with puppet...
TRANSCRIPT
Embrace DevOps :
Delivery Value with Puppet Automation
Meet the Speaker
• Application Architect, proficient DevOps engineer
with passion for Automation
• AWS Certified Solution Architect
• Enjoys working with cross-functional teams to
develop innovative business solutions
Navin Kumaran KSr. Cloud Solution Architect,8KMiles Software Services Ltd.
Why DevOps with Puppet?
Quick Stats + Latest Insight!
Puppet Governance Power
Automate IT
Practical Use Case
Eventually what we need?
Questions!!
AgendaAt a Glance
Puppet what/how?
Deploy code 30x more frequently
Contribute to 50 % higher market cap growth
With 50% fewer failures
Why DevOps with Puppet?
• DevOps is how IT gets lean
• Makes Continuous delivery and Faster resolutions
possible
• Less complex problems to fix
• Don’t have to choose stability versus new
features
• Maintain balance between Agility and Reliability
• Enhance the 4 powers of Puppet – Performance,
Scalability, Measurability and Flexibility
Quick Stats + Latest Insight!
60x fewer failures
168x faster recovery from failure
Deploy 30x more frequently
200x shorter lead times
Sustainable and faster delivery
Puppet Governance Power
• Manages every node’s desired state at any time irrespective of
the OS flavor
• Highly scalable and stable Governance Tier
• Drilled down management of the application inline with the
infrastructure components
• High degree of security w.r.t module, data, configurations and
data transfer while catalog runs
• Orchestration is easy and efficient
Automate IT
• Understand the need for Automation
(it doesn’t mean everything should be automated)
• Automate tasks and Orchestrate processes to achieve
speed
• Organizes a stable and reliable production system
• Helps to be aware of the up-to-the-minute state of the
system
• Handoffs are pretty clean and has low chance
of errors AutomationVs
Primitive
Reliability
Agility
Real World Example
Server Fleet Management via Puppet
• Centralized Governance i.e. manage and maintain huge fleet of
servers
• Composite OS flavors
• Distributed across VPC’s
• Multiple departments with specific infra requirements
• Every node must adhere to Global Golden Standards
of the company
• Monitoring and Alerting
• Hooked and centralized version controlling system
So… How did we achieve it ?
• Design DevOps practice
• Puppet for centralized governance
• VPC Peering
• VPN Tunnel
• GIT for version control
• iNotify to aid sync operation
• Auto healing Puppet Master
Practical Difficulties & Things to watch out for…
• Cross Region access
• CA Management
• Scaling Puppet Master
• Node Classification
• Load balanced + CA
• Sensitive data security
• Dynamic data management
Eventually we need…
• Break down barriers and reduced cycle times
• Stable and agile production deployments
• Improved Defect Detection and Effectiveness
• Reduced Deployment Failures and Rollbacks
• Controllable / Manageable
and finally… keep C A L M and carry on…
Culture Automation Lean Measurement
Admin
Infra / App
PuppetMaster
Infra / App
Crash ORIssues
Infra / AppAdmin
Questions ?
