Azure Virtual Machine Images
- Why vm becomes unusable after vm image creation?
- As user specific information is removed before vm image creation
- As user specific information is removed before vm image creation
-
Azure Images are of two types
- Managed Image
- snapshot of disk
- meta data name, region, creation information
- Compute Gallery: This was designed to have versions for the image, allow copying to multiple regions if required.
- Managed Image
-
Azure VM Image: Generally Azure VM Has the following attributes
- Publisher: Who is publishing the image (user/organization)
- Offer: This speaks about the vm image (ubuntu server/centos/redhat/Window Server)
- SKU: This is category in the offer (ubuntu 16.04, redhat 7, centos 8)
- Version: Specific build information (latest)
- Azure VM image urn is expressed as
<publisher>:<offer>:<sku>:<version> - Lets create a compute Gallery









- Now create a php info vm and capture the image into image defintion created above

- Create a vm from image and cross check the application
Exercise
- Create a compute gallery
- Create an image defintion
- publisher => you
- offer => learning
- sku => php-info-ubuntu (php-info-redhat)
- Now create two vms one ubuntu and one redhat. install php-info
- Capture the images in respective sku’s
- From any one image create a vm and install java `sudo apt install openjdk-11-jdk -y’ and create a new version
