Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

image factory breaking change to Devtest labs custom images #252

Closed
Andy-bridle opened this issue Jun 21, 2017 · 4 comments
Closed

image factory breaking change to Devtest labs custom images #252

Andy-bridle opened this issue Jun 21, 2017 · 4 comments

Comments

@Andy-bridle
Copy link

I've been using the Image Factory scripts to run my own custom image factory.
As of 14th June. DevTest labs custom images no longer create a vhd in the lab storage account. They seem to have been switched over entirely to the managed vm image.

As a result the distribute images script in the image factory example fails to get a sourceVHDLocation for copying. (.Properties.Vhd.ImageName)

As far as I understand support for copying managed images across subscriptions is on the roadmap but not available. Any ideas how to fix this in the mean time?

@gregpakes
Copy link
Contributor

I am using the image factory too (a slightly custom version), but I am not getting this issue. Is your issue specific to distributing images across subscriptions (as I am not doing that)?

@ajay-arora
Copy link
Member

Andy, I am sorry that you ran into this issue.
We will be updating the blog as well as the scripts to reflect the new changes. But in the meanwhile, you will need to update the distribution logic in the following way.
Today to distribute your image across different labs, you create a custom image in source lab, and get its vhd, copy it to target labs, and create a custom image from the imported vhd.
Since custom images dont expose VHDs anymore, you need to get hold of the VHD from the Managed Disk backing the VirtualMachine. To get to the ManagedDisk of a LabVm, navigate to the LabVM resource group, and locate the Compute VM resource (resource type : Microsoft.Compute/VirtualMachine) with the same name as lab VM in that resource group. This should open the Compute VM blade, click on Disks, and navigate to the OS Disk. This will open the Managed Disk blade, and now to get hold of the VHD, you need to click on "Export" button on top of the blade, and you will get a SAS Url to the backing VHD in return. You can use this SAS Url to copy the VHD to the destination lab storage accounts.
Remember to revoke the SAS access after the copy is done.

Let me know if you have any questions.

@Andy-bridle
Copy link
Author

Thanks both, I can understand the reason the distribution is no longer working and I'm now updating my versions of the scripts.

@workleodig
Copy link
Contributor

Pull request 255 contains the script changes to address this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants