Microsoft Azure Cost Optimization and improve efficiency
•
2 gefällt mir•2,033 views
Cloud solutions could not be best solution if it is not chosen. One factor businesses deviates from cloud solutions is unawareness of getting best out of cloud solutions with increasing efficiency. This presentation addresses gaps between discussion had at the global azure bootcamp New Jersey.
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Microsoft Azure Cost Optimization and improve efficiency
Ähnlich wie Microsoft Azure Cost Optimization and improve efficiency (20)
Mehr von Kushan Lahiru Perera
Mehr von Kushan Lahiru Perera (11)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Microsoft Azure Cost Optimization and improve efficiency
- 2. Kushan Lahiru Perera Principle Consultant at Independent Consultant – Cloud and Office 365 Passionate about: Enterprise Collaboration - O365/ SharePoint Cloud Services - Microsoft Azure & GCP Client Side Frameworks Microsoft MVP (Most Valuable Professional)
- 3. Agenda 1. Motivations to cloud? 2. Introduction to optimization 3. Techniques cloud cost optimization Demos: • Tagging • Azure Runbooks • Azure cost calculator
- 4. What is CLOUD (revisit)? Pay-as-You-Go Zero capital ($) to start Outsourced services – No unpredictable costs
- 5. Why Optimize? Utility Compute and Storage are a utility so ‘turning off’ should be natural Efficiency Efficiency allows more to be done within a given budget Architecture Cost awareness drives todays architectural decisions
- 6. What you will get (benefits)? Reduced Risk Cost/ Time Efficiency Availability
- 7. Scenario: Usage of server within a business day.
- 8. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad
- 9. Capacity of 1 Server 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad
- 10. Traditional capacity required Capacity of 1 Server 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad
- 11. Traditional capacity required Capacity of 1 Server 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad 1 Server for 8 hours
- 12. Traditional capacity required 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad 1 Server for 8 hours Capacity of 1 Server 1 Server for 8 hours 1 Server for 8 hours
- 13. Traditional capacity required 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad 1 Server for 8 hours Capacity of 1 Server 1 Server for 8 hours 1 Server for 8 hours 1 Server for 8 hours
- 14. Capacity of 1 Server Traditional capacity required 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad 1/3rd Saving
- 15. Azure RIs (Reserved VM Instances) Reservation of VMs in advance and get discounts • Predictive budgets • One or three year terms • Prioritized compute • Flexible cancel or exchange • Easy purchase
- 16. Naming and Tagging Make accountable and transparent • Resource naming convention <company> <department> <productline> <environment> Eg. softhonic services business prod • Tagging • Name value pairs assigned to resources or resource groups • Each resource could have up to 15 tags
- 18. Scale Right Buy only what you need Workload Workload Workload
- 19. Scale Right… cont Buy only what you need • Auto scale • Know your capacity • Audit • Continuous monitor
- 20. Decommission & Automate Pay only when you need • Auto shutdown • Logic apps • Web Jobs • Automation – Runbooks • Azure Dev Test Labs • Windows Scheduler Tasks • Etc. • Deallocate unused resources • Audit with PowerShell for unattached disks and resources • $ 0
- 21. Azure Automation - Runblocks https://github.com/ratchetnclank/Invoke- Autoshutdown/blob/master/Invoke-Autoshutdown.ps1
- 22. Choose right Pay only when you need • Price deviates from resource location https://azure.microsoft.com/en-us/global-infrastructure/locations • Find best service for your requirement Go server-less when its POSSIBLE No maintenance No License Less knowledge curve
- 24. Bring Your Own Licenses (BYOL) Use what you have • Research licenses from 3rd party • Purchase directly • If you have Visual Studio enterprise – you have licenses
- 25. Educate end-users Use what you have • If you scheduled to shutdown VMs at 6.00 PM • User on half day and leaves around 2.00 PM • If user shutdown at 2.00 PM, you save 4 hour compute
- 26. Pay as you go but keep eye on distance you go.
Hinweis der Redaktion
- https://blogs.technet.microsoft.com/ukplatforms/2018/02/21/azure-cost-optimisation-series-identify-orphaned-disks-using-powershell/