Additional common image properties
In order to make images more easily searchable in different openstack installations, it would be useful to add some common properties to Glance images that identify operating system characteristics .
Blueprint information
- Status:
- Complete
- Approver:
- Brian Waldon
- Priority:
- Medium
- Drafter:
- Brian Rosmaita
- Direction:
- Approved
- Assignee:
- Brian Rosmaita
- Definition:
- Approved
- Series goal:
- Accepted for grizzly
- Implementation:
- Implemented
- Milestone target:
- 2013.1
- Started by
- Brian Rosmaita
- Completed by
- Thierry Carrez
Related branches
Related bugs
Sprints
Whiteboard
[gabrielhurley] Could I also suggest adding a property that indicates whether or not an image is "bootable" (for example, not a ramdisk or kernel image, etc.)?
@ gabrielhurley : is the current disk_format property insufficient for this? It's not exactly what you want, but I think you can determine "bootablity" from it? (See http://
[gabrielhurley] Glance's "filtering" mechanism in the API only allows for positive assertions. I can't say "give me all the images which *are not* ARI, AKI, etc." That means having a common flag that everyone can recognize as "this image *is* bootable" would be extremely valuable.
Gerrit topic: https:/
Addressed by: https:/
Adding new common image properties
Addressed by: https:/
Adding new common image properties
Also, please look over the proposed admin docs for this:
https:/
[daniel berrange] This separation of "os_distro" and "os_version" may seem like a good idea, but it doesn't really work very nicely when you consider Windows. Although Windows releases do have versions, they are not the versions that users think of, and the version number is the same for products that most people consider different, so they don't provide a good unique identifier. ie Windows 2k8 and Window Vista are both considered version 6.0 by Microsoft.
The libosinfo library (http://
Rather than having openstack invent new vocabulary for this OS data, I'd prefer to see openstack simply declare that it uses the same data vocabulary as libosinfo.
[james scollard] I have another use case associated with this feature, but don't think it fits into this blueprint.
https:/