Application and service users expect reliable access and fast response times. When building operational infrastructure supporting high availability, scalability, and robust monitoring, outdated tooling and architecture often reduce DevOps team effectiveness. The WSO2 Carbon enterprise middleware platform and WSO2 Stratos Cloud middleware platform encourages DevOps best practices across: Deployment automation, Maintenance, Monitoring and alerting, Backups and DR ,Scaling/bursting into the cloud, High Availability for services The slide deck will describe how to painlessly run operations with Carbon and Stratos and explore best-practices used to deploy and manage a failure-proof large service clusters.

1. Running Operations for
Carbon and Stratos
Chamith Kumarage
Associate Technical Lead & Manager, Infrastructure
WSO2 Inc.

2. Agenda
● Automated deployment
● Deployment orchestration
● Maintenance
● Monitoring and alerting
● Backups and DR
● Scaling into the cloud
● High availability for services

3. Automated deployment
● Self serving model
● Responsible from the ground up
● Templated configuration
● Enforce checklists and best practices
● Enables orchestration
● Powered by Puppet
“Let there be an AppServer!”

4. Not anymore..
http://www.erie-flooring.com/automation.jpg

5. Deployment orchestration
● Based on Ruby Facts
● Agents publish facts to a broker service
● Orchestrator search for servers based on facts
● Plugins to enable remote management
● Integrates well with Puppet
● Powered by MCollective

6. Maintenance
● Patch management and distribution
● Configuration management
● Centralized management
● Live service migrations
● Remote maintenance
“Reducing deployment complexity is better than
managing complex deployments”

7. http://www.nimmot.net/base/worksamples/bad-timing-maintenance-page1.jpg
404s, less often

8. Monitoring and alerting
● Behavioral monitoring
● JVM monitoring
● System resource monitoring
● Powerd by Ganglia, Nagios and Cacti
● Realtime and historical data analysis
● Email, SMS and phone-call alerts based on the severity
“If it's not monitored, it's not in production”

11. “In operations, you got to
have metrics.
When in doubt, make graphs.”

12. Backups and DR
● Routine backups and restoration drills
● Replicated artifact repositories
● Multi-site replication
● Automated recovery tools
● Documentation
“One cannot take past successes as a
guarantee against future failures”

13. Scaling into the cloud
● Powered by WSO2 Elastic Loadbalancer (ELB)
● Scale up early, scale down slowly
● Based on Jclouds API
● Now: Amazon EC2 and OpenStack Nova support
● Soon: VCloud and Rackspace support

14. High availibility for services
● Service aware loadbalancing
● Multiple service clusters in different sites
● Set min_app_instances to suite your need
● Linux HA
“He who fails to plan is planning to fail”

15. Q &A

16. Thank You!
chamith@wso2.com
@gnuchami