Ability to export / import metadata in ovf
OVF Container images contain a variety of pieces of embedded metadata that can be used to identify the operating system associated with the image.
Use-case: as a Cloud Provider, I would like to set specific properties to a Windows image which could represent a signature, and useful for licensing requirements.
To do that, I should be able to export / import an image with user properties included.
The idea here is to be able to identify an image after cloning or whatever with a property field. Of course, the user could break it in editing the image manually, but I consider he / she won't.
Then, a user could reuse the import image in the public cloud, and Glance will be aware about its properties.
Blueprint information
- Status:
- Complete
- Approver:
- Mark Washenberger
- Priority:
- Undefined
- Drafter:
- Emilien Macchi
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Emilien Macchi
Related branches
Related bugs
Sprints
Whiteboard
I think it is a good time to start looking more into this feature, though it is still blocked by some efforts it depends upon. In particular, I'm curious which ovf settings you are particularly interested in?
On the import side, there is another related blueprint that takes a bite out this problem:
https:/
markwash more-info 2014-02-18
Hi: I see this blueprint as a duplicate of epa-ovf-
The OVF use case will will be handled by this blueprint:
https:/
Based on the VMware driver use case in Nova, it makes more sense to actually store the OVF descriptor instead of parsing properties.
At this moment, please store your OVF+disks as an OVA tarball.
-arnaud
Let's see how the artifacts API develops, it will probably cover your use case.
rosmaita rejected 2014-03-07
Work Items
Dependency tree
* Blueprints in grey have been implemented.
