System-owned server metadata
Mogan already has the concept of server-metadata, however, this is used for *user-provided* metadata.
Currently, Mogan doesn't have a way to store arbitrary key/value pairs for a server which are only used internally by the compute service. For example, Mogan will integrate with RSD to support composing node on the fly, so it is better to save the related field in system metadata which will not be exposed to end-user, while the compute service knows that.
The proposal is to provide a new table, `server_
Blueprint information
- Status:
- Not started
- Approver:
- Zhenguo Niu
- Priority:
- Undefined
- Drafter:
- Xinran WANG
- Direction:
- Needs approval
- Assignee:
- Xinran WANG
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add manageable server information into system metadata