Its the app stupid - CloudStack 2014 Collaboration Conference #CCNA14
•Download as PPTX, PDF•
2 likes•1,578 views
Slides from my session at #CCNA14 http://sched.co/1hETwSO
Recommended
Recommended
More Related Content
Similar to Its the app stupid - CloudStack 2014 Collaboration Conference #CCNA14
Similar to Its the app stupid - CloudStack 2014 Collaboration Conference #CCNA14 (20)
More from Uri Cohen
More from Uri Cohen (20)
Recently uploaded
Recently uploaded (20)
Its the app stupid - CloudStack 2014 Collaboration Conference #CCNA14
- 1. It’s the App, Stupid! Orchestration, Automation, Scaling & What’s in Between Uri Cohen GigaSpaces @uri1803 #CCNA14 #ItsTheAppStupid
- 2. Meet Petsy, Selling Pet Art and Supporting Pet Artists Since 2013
- 3. So Their Services Are Deployed on CloudStack Gunicorn PostgreSQL Hadoop ActiveMQ Nginx MongoDB Logstash Graphite Jenkins Nagios
- 4. The Business Is Doing Great, Thx (esp. Cat paper crafts), But… Rolling out new code is Painful http://www.interestingtopics.net/storage/5762c0bec0add88fae0c3958d61effe1.jpg
- 5. The Business Is Doing Great, Thx (esp. Cat paper crafts), But… MTTR is… mehhh Mehhh http://fineartamerica.com/featured/wooly-sheep-ramona-johnston.html
- 7. Let’s have a closer look at DevOps Processes It’s about Workflows and Triggers
- 8. Automated Deployment • Triggers: Manual, CI Server • Flow: – Provision Cloud Resources: Compute, Storage, Network – Configure servers – Push code – Start components http://www.flickr.com/photos/smilemark/4611091236/sizes/m/in/photostream/
- 9. Infra Upgrade • Trigger: Critical updates, patches, et c. • Flow: Take down relevant processes, one by one, apply patch, and reconnect to cluster. In some cases restarts server
- 10. Code Push (or more generally, CD ) • Trigger: CI server, Manual • Flow: Canary, Red/Black, A/B… – In general – Partial deploy, verify, rollback / complete deploy
- 11. Node Failure • Trigger: #$%@ happens… • Flow: Detect, provision VM, attach storage, add to network, reconfigure app (load balancer in case of web serve, DB connection in case of database, etc.)
- 12. Scaling • Trigger: System SLAs, Schedule • Flow: Add new nodes, push code, reconfigure dependent nodes, reconfigur e LB
- 13. Automation Encompasses All Layers Proxy Config WAR Schema Infrastructure Middleware Apache Tomcat MySQL Application Host Networks Storage
- 14. Automation Building Blocks Environment Creation SW Infra. Setup & Config Code Push Monitoring & Alarming Repairing Scaling
- 15. Let’s Look at Some Tools
- 16. Orchestration Tools Environment Creation SW Infra. Setup & Config Code Push Monitoring & Alarming Repairing Scaling
- 17. CM Tools Environment Creation SW Infra. Setup & Config Code Push Monitoring & Alarming Repairing Scaling
- 18. Automation Tools Environment Creation SW Infra. Setup & Config Code Push Monitoring & Alarming Repairing Scaling
- 19. Metric & Log Collection Tools Environment Creation SW Infra. Setup & Config Code Push Monitoring & Alarming Repairing Scaling
- 20. Still, when you need to automate & orchestrate, th at’s what is looks like…
- 21. Where You Want to Be Environment Creation SW Infra. Setup & Config Code Push Monitoring & Alarming Repairing Scaling
- 22. How It’s Done in AWS
- 23. How It’s Done in AWS
- 24. He Calls It DevOps Automation http://www.allthingsdistributed.com/2013/02/aws-opsworks.html
- 25. Still a Bit Too Rigid
- 26. OpsWorks – We Can Do Better! • Integrated with CloudStack (and other clouds) • Custom Workflows • Not limited to Chef • Open Monitoring and Policies
- 27. Our TOSCA-Inspired Building Blocks Application Topologies Workflows Policies
- 30. Architecture REST GUI Workflow Engine Task Manager Blueprint + Runtime Data Policy Engine Agent Monitoring Data Agent Monitoring Agent Application Stack Cloudify Manager App VM Invokes Reports Creates Metrics VM Logs + Events Proxy + File Server
- 31. Demo Time!
Editor's Notes
- Goals:Why Workflows are critical part of automation of applications on the cloudClarify the need for something like OpsWorksWhy do we think this OpsWorks is needed in addition to other projects
- They do it manually, pushing code to git, then compiling
- One of their servers failed last week, and it took almost a day to configure and bring up a new server. They use a certain CM tool, Still better than the week it took the time before, but that’s doesn’t cut it
- They also realized that in order to run well in the cloud they need DevOps and automationWhat are the options
- The building blocks are triggers and workflowsTriggers because triggers need to be automated as well as events resulting from policies / integrationetcWorkflows – because these are complex multi-step processesLet’s have a look at few typical use cases
- Great at creating resources, basic integration with Chef / puppet for swconfig, basic built in monitoring and alarming, moving to ceilometer in Havana
- Env setup is not automated SW infra setup is good but has no startup orchestration
- Env setup is not automated SW infra setup is good but has no startup orchestration
- Healthnmon is more geared toward cloud resource monitoring and is has more opinionated domain model, ceilometer seems to be picking momentum and
- http://www.allthingsdistributed.com/2013/02/aws-opsworks.html