Feature #847
Support a list of UI-specific metadata keys to be copied from Image to newly-created Server
| Status: | Closed | Start date: | 07/17/2011 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Kostas Papadimitriou | % Done: | 0% |
|
| Category: | Cyclades UI | Spent time: | - | |
| Target version: | v0.6 |
Description
Whenever Server s is created from Image i, the UI currently copies the value of metadata key i.OS to the newly created server, as s.OS.
This mechanism should be extended to support an arbitrary set of metadata keys, configurable in in settings.d/.
Need to explore how the API allows setting server metadata: Does the OS API provide a mechanism to specify all metadata values in a single POST /servers call? Is there a mechanism to create all metadata at once with a single POST call after POST /server has returned?
This mechanism may then be used to specify that a set of US-specific Image metadata keys, e.g., "OS", and "loginname" are to be inherited from the parent image (useful for #801).
Related issues
Associated revisions
Clone specified image metadata on vm creation, Refs #847
History
#1 Updated by Vangelis Koukis almost 13 years ago
- Target version changed from v0.5.2 to v0.5.3
#2 Updated by Vangelis Koukis almost 13 years ago
- Target version changed from v0.5.3 to v0.5.5
#3 Updated by Kostas Papadimitriou over 12 years ago
Added a new setting to specify the image metadata keys that should be cloned to the virtual machine instance on its creation. bcd451e
#4 Updated by Kostas Papadimitriou over 12 years ago
- Status changed from New to Feedback
#5 Updated by Vangelis Koukis over 12 years ago
- Target version changed from v0.5.5 to v0.6
#6 Updated by Vangelis Koukis over 12 years ago
- Status changed from Feedback to Closed
Merged, closing.