Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update MySQL/PostgreSQL config params for latest API version and fix MS SQL param names #68

Merged
merged 7 commits into from
Mar 30, 2018
Merged

Update MySQL/PostgreSQL config params for latest API version and fix MS SQL param names #68

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
a98c2c4
Updates for new MySQL/PostgreSQL Azure APIs, fix MS SQL param names
Mar 30, 2018
0ecb9f2
Reorder top template params for better grouping
Mar 30, 2018
f4600eb
Change branch name in URLs for testing in new branch
Mar 30, 2018
d7c0958
Reorder template params for better grouping
Mar 30, 2018
10ecf1a
Update loadtest.sh for new DB params
Mar 30, 2018
096f627
Revert branch name back to master for PR & merge
Mar 30, 2018
d3da315
Address PR comments
Mar 30, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
308 changes: 157 additions & 151 deletions azuredeploy.json
View file
Open in desktop

Large diffs are not rendered by default.

11 changes: 5 additions & 6 deletions azuredeploy.parameters.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,13 +17,12 @@
"mysqlVersion": { "value": "5.7" },
"postgresVersion": { "value": "9.6" },
"siteURL": { "value": "www.example.org" },
"skuCapacityDTU": { "value": 50 },
"skuName": { "value": "MYSQLB50" },
"skuSizeMB": { "value": 51200 },
"skuTier": { "value": "Basic" },
"mysqlPgresVcores": { "value": 1 },
"mysqlPgresStgSizeGB": { "value": 5 },
"mysqlPgresSkuTier": { "value": "Basic" },
"vNetAddressSpace": { "value": "172.31.0.0" },
"sshPublicKey": { "value": "GEN-SSH-PUB-KEY" },
"serviceObjective": { "value": "S7" },
"msDbSize": { "value": "250GB" }
"mssqlDbServiceObjectiveName": { "value": "S7" },
"mssqlDbSize": { "value": "250GB" }
}
}
18 changes: 9 additions & 9 deletions docs/Deploy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,28 +115,28 @@ together.

### Database Sizing

As of the time of this writing, Azure supports "Basic" and "Standard"
tiers for database instances. In addition the skuCapacityDTU defines
Compute Units, and the number of those you can use is limited by
As of the time of this writing, Azure supports "Basic", "General Purpose" and "Memory Optimized"
tiers for MySQL/PostgreSQL database instances. In addition the mysqlPgresVcores defines
the number of vCores for each DB server instance, and the number of those you can use is limited by
database tier:

- Basic: 50, 100
- Standard: 100, 200, 400, 800
- Basic: 1, 2
- General Purpose: 2, 4, 8, 16, 32
- Memory Optimized: 2, 4, 8, 16

This value also limits the maximum number of connections, as defined
here: https://docs.microsoft.com/en-us/azure/mysql/concepts-limits

As the Moodle database will handle cron processes as well as the
website, any public facing website with more than 10 users will likely
require upgrading to 100. Once the site reaches 30+ users it will
require upgrading to Standard for more compute units. This depends
require upgrading to General Purpose for more compute units. This depends
entirely on the individual site. As MySQL databases cannot change (or
be restored to a different tier) once deployed it is a good idea to
slightly overspec your database.

Standard instances have a minimum storage requirement of 128000MB. All
database storage, regardless of tier, has a hard upper limit of 1
terrabyte. After 128GB you gain additional iops for each GB, so if
All MySQL/PostgreSQL database storage, regardless of tier, has a hard upper limit of 1
terabyte (1024 GB), starting from 5 GB minimum, increasing by 1 GB. You gain additional iops for each added GB, so if
you're expecting a heavy amount of traffic you will want to oversize
your storage. The current maximum iops with a 1TB disk is 3000.

Expand Down