update strings according to PR

This commit is contained in:
Claudiu Guiman 2016-11-29 13:40:52 -08:00
parent 8270f38b98
commit e2dc3788a5
2 changed files with 3 additions and 3 deletions

View File

@ -128,7 +128,7 @@ Refer to
}
```
If you hit the [storage scalability limits](https://docs.microsoft.com/en-us/azure/storage/storage-scalability-targets) for your custom images on one storage account you should consider using the agent [temporary storage](https://blogs.msdn.microsoft.com/mast/2013/12/06/understanding-the-temporary-drive-on-windows-azure-virtual-machines) or creating multiple storage accounts and spread your agents across multiple templates with the same label.
If you hit the [storage scalability limits](https://docs.microsoft.com/en-us/azure/storage/storage-scalability-targets) for your custom images on the storage account where the VHD resides, you should consider using the agent's [temporary storage](https://blogs.msdn.microsoft.com/mast/2013/12/06/understanding-the-temporary-drive-on-windows-azure-virtual-machines) or copy your custom image in multiple storage accounts and use multiple VM templates with the same label within the same agent cloud.
For more details about how to prepare custom images, refer to the below links:
* [Capture Windows Image](http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-capture-image-windows-server/)

View File

@ -1,7 +1,7 @@
<div>
Enter an URI of a custom user image and operating system type.<br />
Enter an URI of a custom user image and operating system type.<br />
Your custom image has to be available into the same storage account in which you are going to create agent nodes.<br />
<br />
e.g. https://jenkinsarm.blob.core.windows.net/system/Microsoft.Compute/Images/vhds/jenkinsvm5-osDisk.c68efe70-4b40-450e-a8b6-3d10b7d1665f.vhd<br /><br />
If you hit the <a target="_blank" href="https://docs.microsoft.com/en-us/azure/storage/storage-scalability-targets">storage scalability limits</a> for your custom images on one storage account you should consider using the agents <a target="_blank" href="https://blogs.msdn.microsoft.com/mast/2013/12/06/understanding-the-temporary-drive-on-windows-azure-virtual-machines/">temporary storage</a> or creating multiple storage accounts and spread your agents across multiple templates with the same label.
If you hit the <a target="_blank" href="https://docs.microsoft.com/en-us/azure/storage/storage-scalability-targets">storage scalability limits</a> for your custom images on the storage account where the VHD resides, you should consider using the agent's <a target="_blank" href="https://blogs.msdn.microsoft.com/mast/2013/12/06/understanding-the-temporary-drive-on-windows-azure-virtual-machines/">temporary storage</a> or copy your custom image in multiple storage accounts and use multiple VM templates with the same label within the same agent cloud.
</div>