Revision history [back]

Hello Avladu - thanks for taking a look. I confirm that the MAASAPIKEY[0] is not literal, and is just a placeholder as I didn't want to publish the actual key (but I still wanted to show what parts of the API key were going where)

Curtin hooks are present, and were installed during the image creation process via the config.ini setting image_type=MAAS. Just to confirm as well, the virtual_disk_format=RAW leaves me with file myimage.raw, which is then tar.gz'ed into a `'myimage.tgz' file. I'm uploading into MAAS using the below, which hasn't generated any errors, so I just figured it was OK. Will the filetype of ddtgz make all the difference?

maas MY_LOGIN boot-resources create name='windows/win1022h2' title='Windows 10 22H2 (cloud)' architecture='amd64/generic' filetype='tgz' content@=Win10_22H2_English_x64v2_custom.tgz

Hello Avladu - thanks for taking a look. I confirm that the MAASAPIKEY[0] MAAS_API_KEY[0] is not literal, and is just a placeholder as I didn't want to publish the actual key (but I still wanted to show what parts of the API key were going where)

Curtin hooks are present, and were installed during the image creation process via the config.ini setting image_type=MAAS. Just to confirm as well, the virtual_disk_format=RAW leaves me with file myimage.raw, which is then tar.gz'ed into a `'myimage.tgz' file. I'm uploading into MAAS using the below, which hasn't generated any errors, so I just figured it was OK. Will the filetype of ddtgz make all the difference?

maas MY_LOGIN boot-resources create name='windows/win1022h2' title='Windows 10 22H2 (cloud)' architecture='amd64/generic' filetype='tgz' content@=Win10_22H2_English_x64v2_custom.tgz

Hello Avladu - thanks for taking a look. I confirm that the MAAS_API_KEY[0] is not literal, and is just a placeholder as I didn't want to publish the actual key (but I still wanted to show what parts of the API key were going where)

Curtin hooks are present, and were installed during the image creation process via the config.ini setting image_type=MAAS. Just to confirm as well, the virtual_disk_format=RAW leaves me with file myimage.raw, which is then tar.gz'ed into a `'myimage.tgz' file. I'm uploading into MAAS using the below, which hasn't generated any errors, so I just figured it was OK. Will the filetype file type of ddtgz make all the difference?

maas MY_LOGIN boot-resources create name='windows/win1022h2' title='Windows 10 22H2 (cloud)' architecture='amd64/generic' filetype='tgz' content@=Win10_22H2_English_x64v2_custom.tgz