Difference between revisions of "Glance/ImageAliases"
< Glance
James Penick (talk | contribs) |
James Penick (talk | contribs) |
||
| Line 2: | Line 2: | ||
==== Summary ==== | ==== Summary ==== | ||
| + | |||
Users don't always care about the exact version of their chosen OS or snapshot. Only that the OS is the most recent or the application snapshot is the most stable. | Users don't always care about the exact version of their chosen OS or snapshot. Only that the OS is the most recent or the application snapshot is the most stable. | ||
| − | Image aliases would fix this. Rather than knowing to pick "RHEL 6.4-24017" vs "RHEL 6.4-25001" the users could choose "RHEL 6.X" which the image admin would keep pointed to the most up to date and stable version of that OS | + | Image aliases would fix this. Rather than knowing to pick "RHEL 6.4-24017" vs "RHEL 6.4-25001" the users could choose "RHEL 6.X" which the image admin would keep pointed to the most up to date and stable version of that OS or application image. |
| − | + | Similarly for applications the provider could maintain Test, Stable, Quarantine, etc aliases which point to the most recent of each type. | |
| − | + | ||
| − | + | Ideally these aliases should be at the top of the list, with the actual disk images listed after. And further, the ability to hide the names of the actual disk images would make it even less confusing for the consumers of the disk images. | |
| − | + | ||
| − | |||
| − | |||
==== Assumptions ==== | ==== Assumptions ==== | ||
# You don't need to delete and recreate your disk alias object to change which disk image it points to. | # You don't need to delete and recreate your disk alias object to change which disk image it points to. | ||
| − | # | + | # If you rebuild your VM, it will be recreated with whatever the alias is pointing to /right now/, and not reuse its original base image. |
Latest revision as of 02:55, 6 November 2013
Glance Image aliases
Summary
Users don't always care about the exact version of their chosen OS or snapshot. Only that the OS is the most recent or the application snapshot is the most stable. Image aliases would fix this. Rather than knowing to pick "RHEL 6.4-24017" vs "RHEL 6.4-25001" the users could choose "RHEL 6.X" which the image admin would keep pointed to the most up to date and stable version of that OS or application image. Similarly for applications the provider could maintain Test, Stable, Quarantine, etc aliases which point to the most recent of each type. Ideally these aliases should be at the top of the list, with the actual disk images listed after. And further, the ability to hide the names of the actual disk images would make it even less confusing for the consumers of the disk images.
Assumptions
- You don't need to delete and recreate your disk alias object to change which disk image it points to.
- If you rebuild your VM, it will be recreated with whatever the alias is pointing to /right now/, and not reuse its original base image.
