Created storage-iops-latency-throughput with all templates/artifacts #3055
Conversation
…C configs and associated files
|
Hi @jamesbannan, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution! TTYL, AZPRBOT; |
| @@ -0,0 +1,25 @@ | |||
| # 1 VM in vNet - Multiple data disks | |||
|
|
|||
| <a href="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fjamesbannan%2Fstorage-iops-latency-throughput-demo%2Fmaster%2Fazuredeploy.json" target="_blank"> | |||
There was a problem hiding this comment.
you can update these to point to master before merging...
| "description": "This is an array of strings which describe the type of each storage account." | ||
| } | ||
| }, | ||
| "storageAccountNamePrefix": { |
There was a problem hiding this comment.
Can we move this to a var and just generate a name? seems like that still works with your sample
| "description": "This is an array of strings which specifies the string prefix used for each storage account name." | ||
| } | ||
| }, | ||
| "vmName": { |
| }, | ||
| "vmAdminUserName": { | ||
| "type": "string", | ||
| "defaultValue": "vm-admin", |
There was a problem hiding this comment.
remove default value for username
| "description": "The administrative user password." | ||
| } | ||
| }, | ||
| "vmWindowsOSVersion": { |
There was a problem hiding this comment.
since we're largely looking at azure IOPS, move this to a variable
| "description": "The URI of the DSC configuration." | ||
| } | ||
| }, | ||
| "vNetName": { |
| "vmOSDiskName": "[concat(parameters('vmName'),'-','OSDisk')]", | ||
| "vmSize": "Standard_DS3_v2", | ||
| "vNetID": "[resourceId('Microsoft.Network/virtualNetworks', parameters('vNetName'))]", | ||
| "vmSubnetRef": "[concat(variables('vNetID'), '/subnets/', variables('vNetSubnet1Name'))]", |
There was a problem hiding this comment.
user resourceId() and then you can remove vNetId above
| "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#", | ||
| "contentVersion": "1.0.0.0", | ||
| "parameters": { | ||
| "storageAccountType": { |
There was a problem hiding this comment.
I think you can move these to a variable and simplify the deployment a bit - will still get at the main purpose of your sample.
| xRemoteFile DownloadTests | ||
| { | ||
| DestinationPath = "C:\iometerTests\iometerTests.zip" | ||
| Uri = "https://github.com/jamesbannan/storage-iops-latency-throughput-demo/raw/master/files/iometerTests.zip" |
There was a problem hiding this comment.
We'll want to update this after a good ci test (after changes)
| The template also used the PowerShell Desired State Configuration (DSC) VM extension to: | ||
| * Prepare and format the data disks | ||
| * Install ioMeter using Chocolatey | ||
| * Download and extract 20 pre-defined ioMeter tests to C:\iometerTests |
There was a problem hiding this comment.
where do I see the results of the tests? If it's on the VM itself, add a template output for the FQDN of the vm...
|
Some comments - after this - wanna do a sample of this using managed disks? |
|
OK - all done. Do you want a sample of managed disks in this solution, or a separate solution? |
|
do the managed disk sample in another folder/sample... please :) |
This is a template which creates a single Windows Server 2016 VM with multiple attached data disks in order to provision a demo environment which tests Azure storage IOPS, latency and throughput. It uses DSC to format the disks, install Iometer and download some pre-defined Iometer performance tests.