ServerTemplate Best Practices - RightScale Compute 2013
•Als PPTX, PDF herunterladen•
0 gefällt mir•449 views
Speakers: Tim Miller - Sr. Director Engineering, RightScale Cary Penniman - Sr. Software Engineer, RightScale ServerTemplates™ are a key to maintaining consistent, production-quality configurations in the cloud. Our ServerTemplate team will discuss best practices for using ServerTemplates. We will cover tips to optimize your development workflow, deliver consistent configurations across your organization, leverage toolboxes, and much more.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Andere mochten auch
Andere mochten auch (10)
Mehr von RightScale
Mehr von RightScale (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
ServerTemplate Best Practices - RightScale Compute 2013
- 1. april25-26 sanfrancisco cloud success starts here ServerTemplate Best Practices Tim Miller, Sr. Director ServerTemplate Development Cary Penniman, Sr. Software Engineer
- 2. #2#2 #RightscaleCompute Agenda • Best Practices • Efficient Development Workflow • Going to Production • How to Control Changes • Customizing • Data Storage with the Storage Toolbox • Q/A
- 5. #5#5 #RightscaleCompute Efficient Development Workflow • Chef workflow using rsync • rs_run_recipe –n cookbook::recipe Run locally first Avoid re-launch
- 6. #6#6 #RightscaleCompute Going to Production • Don’t run on HEAD! • Package Repository Freeze Dates • Cookbook Repositories • External Dependencies
- 7. #7#7 #RightscaleCompute Controlling Changes • Pristine Production, Staging clone for development • Follow standard branching and merging
- 8. #8#8 #RightscaleCompute Customizing • Zero change is ideal • Isolate changes to custom scripts • Start with Base ServerTemplate for Linux (v13.3) • Monitoring, Alerts, Firewall, Logging, NTP, etc. • Latest RightImages
- 9. #9#9 #RightscaleCompute • Keep data in multiple locations! • Local backups to volumes • Remote backups to object storage Data Storage
- 10. #10#10 #RightscaleCompute Data Storage (cont.) • Get to know the RightScale "Storage Toolbox”
- 11. #11#11 #RightscaleCompute Leveraging the Storage Toolbox 1. Backup data to another 2. Restore data in case of outage
- 13. #13#13 #RightscaleCompute For more information • ServerTemplate Developer Guide (http://bit.ly/173Boca) • Chef workflow using rsync (http://bit.ly/100lWHw) • Prepare for Production (http://bit.ly/17oHz90) • Base ServerTemplate (http://bit.ly/NZBNGp) • Storage Toolbox ServerTemplate (http://bit.ly/15fMU5K) https://github.com/rightscale/rightscale_cookbooks
- 14. april25-26 sanfrancisco cloud success starts here Questions?
Hinweis der Redaktion
- How many are using the Chef based STs?How many are using the RightScript based STs?How many are not sure what a ServerTemplate is?
- -- Show production workflow, but then you hava bug. Ugg.-- But we can bypass all that with a workflow enabled by a little known tag, to save a TON of time.The thing you can learn from us here is “Run scripts locally first”DEMO: showing workflow of CHANGE – SYNC – RUN (x3)sync -avz --exclude=.git -e "ssh -i $CLOUD_KEY" . root@$IP:/var/cache/rightscale/cookbooks/default/06297a26fe34ceabe57626f272268b4b/buggy-cookbook/sync_to.rb $IP /var/cache/rightscale/cookbooks/default/06297a26fe34ceabe57626f272268b4b/buggy-cookbook/rs_run_recipe -n buggy-cookbook::default && tailf /var/log/syslog
- - what you tested, is what you launch with.Packages change every dayDevelopers commit changes.Tags and branches are mutable, SHAs are immutablePear.org
- Many of you make changes directly on your Production ST.That works great! Until an escalation comes up and you have changed the ServerTemplate since it was launched. What do you do? Here’s where you can “learn from us”… (click)Keep your Production ST pristine, maintain a Staging clone where all development occurs. (click)Follow standard version control branching and merging strategy – even with your ServerTemplates. So how do you do that?
- Base ServerTemplate – gives you a *HUGE* headstart.
- One of the hardest problem in the cloud is storage
- Taken our yeasr of experience running databases in the cloud and broke it out into a ST you can use to build your our servers that need storage Clone this ST and develop your server right on topSo here is how is works…