This repository has been archived by the owner on Oct 24, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 522
feat: Updating Windows VHD build files to support building for multiple OS versions #3847
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
3d084ee
Updating configure-windows-vhd.ps1 to support multiple Windows OS ver…
marosset c0576b4
Updating configured-windows-vhd.ps1 to not use containerd from a pers…
marosset f8da922
Updating windows packer file to take in windows os version specific v…
marosset 9e31e77
updating windows build pipeline/packer.mk to pass new vars file to pa…
marosset e900e76
formatting configure-windows-vhd-ps1
marosset 687ca37
vhd-builder-windows.yaml adding missing WINDOWS_SERVER_VERSION to mak…
marosset fc8dffe
fixup! updating windows build pipeline/packer.mk to pass new vars fil…
marosset 4f7c6a2
fixup! Updating windows packer file to take in windows os version spe…
marosset a855d41
fixup! Updating windows packer file to take in windows os version spe…
marosset File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
{ | ||
"image_publisher": "MicrosoftWindowsServer", | ||
"image_offer": "WindowsServer", | ||
"image_sku": "datacenter-core-2004-with-containers-smalldisk", | ||
"image_version": "19041.508.2009070256", | ||
"windows_server_version": "2004" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
{ | ||
"image_publisher": "MicrosoftWindowsServer", | ||
"image_offer": "WindowsServer", | ||
"image_sku": "2019-Datacenter-Core-smalldisk", | ||
"image_version": "17763.1339.2007101755", | ||
"windows_server_version": "2019" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,10 +8,15 @@ | |
"client_id": "{{env `AZURE_CLIENT_ID`}}", | ||
"client_secret": "{{env `AZURE_CLIENT_SECRET`}}", | ||
"container_runtime": "{{env `CONTAINER_RUNTIME`}}", | ||
"image_publisher": null, | ||
"image_offer": null, | ||
"image_sku": null, | ||
"image_version": null, | ||
"tenant_id": "{{env `AZURE_TENANT_ID`}}", | ||
"subscription_id": "{{env `AZURE_SUBSCRIPTION_ID`}}", | ||
"location": "{{env `AZURE_LOCATION`}}", | ||
"vm_size": "{{env `AZURE_VM_SIZE`}}" | ||
"vm_size": "{{env `AZURE_VM_SIZE`}}", | ||
"windows_server_version": null | ||
}, | ||
"builders": [ | ||
{ | ||
|
@@ -23,12 +28,12 @@ | |
"location": "{{user `location`}}", | ||
"vm_size": "{{user `vm_size`}}", | ||
"os_type": "Windows", | ||
"image_publisher": "MicrosoftWindowsServer", | ||
"image_offer": "WindowsServer", | ||
"image_sku": "2019-Datacenter-Core-smalldisk", | ||
"image_version": "17763.1339.2007101755", | ||
"image_publisher": "{{user `image_publisher`}}", | ||
"image_offer": "{{user `image_offer`}}", | ||
"image_sku": "{{user `image_sku`}}", | ||
"image_version": "{{user `image_version`}}", | ||
"resource_group_name": "{{user `resource_group_name`}}", | ||
"capture_container_name": "aksengine-vhds-windows-ws2019", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this will change from There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it should be ok. This is only used in the paths in the storage account the VHD gets captured into correct? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah should be fine, we get the URI directly from the output so we don't expect it to be in a specific place 👍 |
||
"capture_container_name": "aksengine-vhds-windows-{{user `windows_server_version`}}", | ||
"capture_name_prefix": "aksengine-{{user `create_time`}}", | ||
"storage_account": "{{user `storage_account_name`}}", | ||
"communicator": "winrm", | ||
|
@@ -49,7 +54,8 @@ | |
"elevated_password": "{{.WinRMPassword}}", | ||
"environment_vars": [ | ||
"ProvisioningPhase=1", | ||
"ContainerRuntime={{user `container_runtime`}}" | ||
"ContainerRuntime={{user `container_runtime`}}", | ||
"windowsServerVersion={{user `windows_server_version`}}" | ||
], | ||
"type": "powershell", | ||
"script": "vhd/packer/configure-windows-vhd.ps1" | ||
|
@@ -67,7 +73,8 @@ | |
"elevated_password": "{{.WinRMPassword}}", | ||
"environment_vars": [ | ||
"ProvisioningPhase=2", | ||
"ContainerRuntime={{user `container_runtime`}}" | ||
"ContainerRuntime={{user `container_runtime`}}", | ||
"windowsServerVersion={{user `windows_server_version`}}" | ||
], | ||
"type": "powershell", | ||
"script": "vhd/packer/configure-windows-vhd.ps1" | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should 2019 be an environment variable so it can be configured on the job?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly. We still need to have a discussion around what images aks-engine should actually be producing. If we want to produce more than just Windows Server 2019 + Docker I think I would rather just update the pipepline to build all the images as different stages and avoid the need to trigger multiple pipelines.
I'm hoping we can resolve that with a different PR tho.