Indexable JSON fields
Registered by
Lucas Alvares Gomes
Ironic currently store some data as JSON in the database, this was done by design and have served us well until recently where a consensus decision was made for having a way to filter data stored into some of these fields via the Ironic API. In order to be able to filter resources in a performant way Ironic needs the data of those JSON fields to be indexable.
This spec proposes separating the node's properties and driver_info JSON fields into separated database tables. Both fields contains information that would come handy if able to filter to use for scheduling and inspecting purpose.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Lucas Alvares Gomes
- Direction:
- Needs approval
- Assignee:
- Lucas Alvares Gomes
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
(?)
