[RFE] Indexable JSON fields
Bug #1525376 reported by
Lucas Alvares Gomes
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Opinion
|
Wishlist
|
Unassigned | ||
Bug Description
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.
| tags: | added: rfe |
| Changed in ironic: | |
| assignee: | nobody → Lucas Alvares Gomes (lucasagomes) |
| importance: | Undecided → Wishlist |
| Changed in ironic: | |
| status: | New → Confirmed |
| summary: |
- Indexable JSON fields + [RFE] Indexable JSON fields |
Revision history for this message
| Jim Rollenhagen (jim-rollenhagen) wrote | #1 |
Revision history for this message
| Jim Rollenhagen (jim-rollenhagen) wrote | #2 |
| tags: | added: needs-spec |
| Changed in ironic: | |
| assignee: | Lucas Alvares Gomes (lucasagomes) → nobody |
Revision history for this message
| Michael Turek (mjturek) wrote | #3 |
| Changed in ironic: | |
| status: | Confirmed → Opinion |
To post a comment you must log in.
Spec is here: https:/