Custom Images

Quake AI concept: Images

• Linode treats custom images as account images that you either capture from an existing Linode disk or upload yourself, and the service explicitly distinguishes these from temporary recovery images. The docs say custom images do not expire and remain until you delete them, which is different from OpenStack Glance's general image registry model where lifecycle is not tied to Linode-style disk capture and recovery workflows. Akamai Cloud Images
• The Linode API exposes image management through `/v4/images`, including `POST /images` to create an image, `POST /images/upload` to create a private image instance and upload image data, and `POST /images/{imageId}/regions` to replicate an image to another compute region. OpenStack Glance does not use this region-replication and upload-instance pattern in the same way. Linode API summary
• Linode custom image storage is region-aware: a captured image is stored in a specific region, and an uploaded image must be placed in a core compute region that supports Object Storage, while distributed regions cannot be used for uploads. The docs also say an image can later be deployed to any compute region you have access to, which is a different placement model from OpenStack's image service. Akamai Cloud Images
• Linode prices custom images at $0.10 per GB per month, while recovery images created automatically on deletion are provided at no charge but expire after a limited lifecycle. OpenStack Glance does not prescribe this Linode-specific billing split between user-managed custom images and auto-generated recovery images. Akamai Cloud Images