Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to A practical approach to provisioning resources in azure
Similar to A practical approach to provisioning resources in azure (20)
Recently uploaded
Recently uploaded (20)
A practical approach to provisioning resources in azure
- 1. A practical approach to provisioning resources in Azure cloudburst 2018
- 2. Morten Christensen Azure Hero @ Umbraco HQ Azure MVP since 2014 Azure and .NET Usergroup co-organizer MicroCPH Conference Intelligent Cloud Conference
- 3. Agenda • Umbraco Cloud • Azure SQL & Elastic Database Pools • Provisioning Azure Resources • Putting it into a Service • Challenges • Future
- 5. Umbraco CMS as a Service Open Source (since 2005) .NET CMS
- 6. Private preview Q4 2014 Launched in Q4 2015 Powering sites like Carlsberg, Coop, Danish Football Association and more
- 7. Running on Azure VMs, infrastructure similar to Azure App Service Each Environment has its own Azure SQL Database All databases are in Elastic Database Pools Powered by Azure
- 8. Demo Creating a Project on Umbraco Cloud
- 10. Business Requirement Creating a new Project should be instant!
- 11. Project Creation • Latest version of Umbraco CMS • Environments with git repository • 1 Database per Environment • Database with Umbraco CMS installed • Dependencies • Configuration
- 12. Azure SQL & Elastic Database Pools
- 13. Azure SQL “Azure SQL Database is a relational database-as-a-service (DBaaS) based on the latest stable version of Microsoft SQL Server Database Engine”
- 14. DTUs vs vCore Two different purchasing models
- 15. Database Transaction Units A bundled measure of compute, storage and IO resources In other words: Microsoft guarantees a certain level of resources for a database
- 16. vCore Independently scale compute and storage resources to match your on-premise performance
- 18. elastic Database Transaction Units A pool of resources shared amongst a group of databases More flexibility in terms of resource utilization and pricing
- 19. Elastic Database Pool tiers and scale limitations
- 20. Pricing example Cost-effective 100 eDTU pool • 2x S3 databases • 15x S0 databases
- 21. Independent database vs Elastic Database Pool In an Umbraco Cloud context
- 22. S1 S2 S3
- 23. Pricing example Elastic Database Pool with 100 eDTUs and 200 databases: ~185.97 EUR / Month 200 x S1 databases (€24.83) = €4966 (break-even at 8 databases) 200 x S2 databases (€62.02) = €12404 (break-even at 3 databases)
- 24. Benefits of Azure SQL • SaaS context • Single Tenant databases • Less Management • Price vs Scale Flexibility • 30 days point in time restore • Retention period for deleted databases
- 26. Azure Resource Creation • Azure Resource Manager (ARM) • Azure CLI 2.0 • Azure Cloud Shell • PowerShell • The Portal • But what about C# ?
- 29. Azure Management Library • Azure Management Client • App Service (WebApps + Functions) • Batch / Batch AI • CDN • Virtual Machines, VMSS, ACS • Container Instance/Registry • CosmosDB • DNS, Networking, Traffic Manager • EventHub, Service Bus • KeyVault • Monitor • Search • SQL Database • Storage
- 30. Azure Service Principal Use Azure CLI 2.0 Using the library
- 31. Demo Creating a Service Principal
- 32. Demo << Create Service Principal >>
- 34. Demo Creating resources using the C# management library
- 37. Demo << Show Code >>
- 40. Putting it into a Service
- 41. Ensure there are always databases available From Manual to Automated to Self-provisioning
- 42. End GoalSitting on a beach in Bali
- 44. Project Creation • Latest version of Umbraco CMS • Environments with git repository • 1 Database per Environment • Database with Umbraco CMS installed • Dependencies • Configuration
- 45. Example Orchestration overview – create servers, pools and databases
- 46. Azure SQL Server 01 Elastic Pool 01 Elastic Pool 02 Resource Group 100 eDTUs 100 eDTUs
- 48. Example Orchestration overview – databases going in and out of Pools backed by Queues
- 55. Example When a Project is deleted
- 57. Summary • Create up to 8 Pools per SQL Server • Create 200 databases per Pool • Maintain queue of available ”slots” • Ensure deleted database ”slots” are re-used • Self-provisioning services are fun!
- 58. Challenges
- 59. Control over Queues Last In, First Out
- 60. Balance Elastic Database Pools Ensure fully utilized resources
- 61. One service doing too much Split it up into smaller services
- 62. Current Responsibilities • Provisioning Projects • Assigning Projects • Adding + Removing Environments • Deleting Projects and Databases • Creating SQL Servers • Creating Elastic Database Pools
- 63. Future
- 64. Did someone say Microservices ? Smaller ”bits” doing one thing
- 68. Questions
Editor's Notes
- Umbraco Cloud – WHY Azure SQL – WHAT Provisioning – HOW Putting it into a Service - HOW
- We don’t want our customers – especially new customers, to wait until a Project is made available to them.
- What is involved with the creation of a single Project. This can easily take up to 10 minutes. And obviously the database creation is an important part of this.
- Ref.: https://azure.microsoft.com/da-dk/blog/a-flexible-new-way-to-purchase-azure-sql-database/
- Ref.: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-elastic-pool
- Ref.: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-elastic-pool
- DTU-based purchasing model example At least two S3 databases or at least 15 S0 databases are needed for a 100 eDTU pool to be more cost-effective than using compute sizes for single databases.
- Show a database growing in size according to Scale ->
- Most of the time an S1 (20 DTU) database will work fine, every once in a while an S2 (50 DTU) would be better and for whose rare spikes an S3 (100 DTU) would be ideal
- Less than a euro per database per month for the Elastic Database Pool version
- Copying files around is easy, and managing git repositiories is also fairly straight forward, but what about the Azure SQL Databases and Elastic Pools?
- The Azure quickstart documentation often has an overview like this … but there is nothing about the Management Libraries
- Find it on github – and nuget Some mentions of the SDK under ” Azure for .NET and .NET Core developers” Should be part of Visual Studio development tool for .NET
- Ref.: https://github.com/Azure/azure-libraries-for-net
- Create a Service Principal using the Azure Cloud Shell
- Locating the Service Principal under the current Subscription
- << Show Code running and creating a Resource Group, SQL Server, Elastic Pool and Databases >>
- A Windows Service The purpose of the Preallocation Service is…
- What is involved with the creation of a single Project. This can easily take up to 10 minutes.
- When we start from Scratch We create a Server in our Resource Group We create an Elastic Pool on our Server We create databases within our Elastic Pool
- Database Availability Queues Project Queues … first the pool is empty
- But we have space for 200 databases So we put those ”availability slots” into a queue (and don’t worry, we don’t have to wait for 200 cylinders going into that other cylinder)
- So when we need a database for a new Project we are creating, We can then just get an availability slot from our availability queue. It contains details about the RG, Server, Pool and Database
- When the Project is ready we put it into a Project Queue. This allows us to have Projects available.
- And so we can continue to create Projects using messages from the queue about availability And we’ll start filling up those Elastic Pools
- When a customer then creates a new Project, we retreive an available Project and assign it to a user and update the hostname
- When a Project is created the database should go back into the queue of available database ”slots”
- In certain situations we want to position a database ”slot” first in line. At other times we just want a regular first in, first out. Maybe we could supplement with an additional ”high priority” queue.
- Ensure full utilization across the board aka make the CFO happy
- After running this service for a while, with maintenance, development, feature ideas and more That its doing too many things, which makes it increasingly difficult to maintain it as a reliable service.
- Automatically balance databases in our elastic pools in order to keep our CFO happy So we can hopefully get funding for our trip to Bali
- What questions do you have?