Skip to content

Commit 064653e

Browse files
march 2020 update 2
1 parent d88ba55 commit 064653e

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/virtual-machines/linux/image-builder-json.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create an Azure Image Builder template (preview)
33
description: Learn how to create a template to use with Azure Image Builder.
44
author: danis
55
ms.author: danis
6-
ms.date: 03/20/2020
6+
ms.date: 01/23/2020
77
ms.topic: article
88
ms.service: virtual-machines-linux
99
ms.subservice: imaging
@@ -91,7 +91,7 @@ By default, Image Builder will not change the size of the image, it will use the
9191
```
9292

9393
## vnetConfig
94-
If you do not specify any VNET properties, then Image Builder will create its own VNET, Public IP, and NSG. The Public IP is used for the service to communicate with the build VM, however if you do not want a Public IP or want Image Builder to have access to your existing VNET resources, such as configuration servers (DSC, Chef, Puppet, Ansible), file shares etc, then you can specify a VNET. For more information, review the [networking documentation](https://github.com/danielsollondon/azvmimagebuilder/blob/master/aibNetworking.md#networking-with-azure-vm-image-builder), this is optional.
94+
If you do not specify any VNET properties, then Image Builder will create its own VNET, Public IP, and NSG. The Public IP is used for the service to communicate with the build VM, however if you do not want a Public IP or want Image Builder to have access to your existing VNET resources, such as configuration servers (DSC, Chef, Puppet, Ansible), file shares etc., then you can specify a VNET. For more information, review the [networking documentation](./../aibNetworking.md), this is optional.
9595

9696
```json
9797
"vnetConfig": {
@@ -149,9 +149,9 @@ The API requires a 'SourceType' that defines the source for the image build, cur
149149
- SharedImageVersion - this is used when you are using an image version in a Shared Image Gallery as the source.
150150

151151
### ISO source
152-
We are deprecating this functionality from image builder, as there are now [RHEL Bring Your Own Subscription images](https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/redhat/byos), please review the timelines below:
153-
* 31st March 2020 - Image Templates with RHEL ISO sources will now longer be accepted by the resource provider.
154-
* 30th April 2020- Image Templates that contain RHEL ISO sources will not be processed any more.
152+
We are deprecating this functionality from image builder, as there are now [RHEL Bring Your Own Subscription images](https://docs.microsoft.com/azure/virtual-machines/workloads/redhat/byos), please review the timelines below:
153+
* 31 March 2020 - Image Templates with RHEL ISO sources will now longer be accepted by the resource provider.
154+
* 30 April 2020- Image Templates that contain RHEL ISO sources will not be processed anymore.
155155

156156
### PlatformImage source
157157
Azure Image Builder supports Windows Server and client, and Linux Azure Marketplace images, see [here](https://docs.microsoft.com/azure/virtual-machines/windows/image-builder-overview#os-support) for the full list.
@@ -210,7 +210,7 @@ By default, the Image Builder will run for 240 minutes. After that, it will time
210210
[ERROR] complete: 'context deadline exceeded'
211211
```
212212

213-
If you do not specify a buildTimeoutInMinutes value, or set it to 0, is will use the default value. You can increase or decrease the value, up to the maximum of 960mins (16hrs). For Windows, we do not recommend setting this below 60 minutes. If you find you are hitting the timeout, review the [logs](https://github.com/danielsollondon/azvmimagebuilder/blob/master/troubleshootingaib.md#collecting-and-reviewing-aib-image-build-logs), to see if the customization step is waiting on something like user input.
213+
If you do not specify a buildTimeoutInMinutes value, or set it to 0, this will use the default value. You can increase or decrease the value, up to the maximum of 960mins (16hrs). For Windows, we do not recommend setting this below 60 minutes. If you find you are hitting the timeout, review the [logs](https://github.com/danielsollondon/azvmimagebuilder/blob/master/troubleshootingaib.md#collecting-and-reviewing-aib-image-build-logs), to see if the customization step is waiting on something like user input.
214214

215215
If you find you need more time for customizations to complete, set this to what you think you need, with a little overhead. But, do not set it too high because you might have to wait for it to timeout before seeing an error.
216216

@@ -404,7 +404,7 @@ OS support: Windows
404404

405405
Customize properties:
406406
- **type** – WindowsUpdate.
407-
- **searchCriteria** - Optional, defines which type of updates are installed (Recommended, Important etc), BrowseOnly=0 and IsInstalled=0 (Recommended) is the default.
407+
- **searchCriteria** - Optional, defines which type of updates are installed (Recommended, Important etc.), BrowseOnly=0 and IsInstalled=0 (Recommended) is the default.
408408
- **filters** – Optional, allows you to specify a filter to include or exclude updates.
409409
- **updateLimit** – Optional, defines how many updates can be installed, default 1000.
410410

@@ -415,7 +415,7 @@ By default, Azure Image Builder will also run ‘deprovision’ code at the end
415415

416416
The commands Image Builder users to generalize may not be suitable for every situation, so Azure Image Builder will allow you to customize this command, if needed.
417417

418-
If you are migrating existing customization, and you are using different Sysprep/waagent commands, you can using the Image Builder generic commands, and if the VM creation fails, use your own Sysprep or waagent commands.
418+
If you are migrating existing customization, and you are using different Sysprep/waagent commands, you can use the Image Builder generic commands, and if the VM creation fails, use your own Sysprep or waagent commands.
419419

420420
If Azure Image Builder creates a Windows custom image successfully, and you create a VM from it, then find that the VM creation fails or does not complete successfully, you will need to review the Windows Server Sysprep documentation or raise a support request with the Windows Server Sysprep Customer Services Support team, who can troubleshoot and advise on the correct Sysprep usage.
421421

0 commit comments

Comments
 (0)