API Consistency Cleanup
Currently, there are lots of inconsistency and lose validation in APIs.
Those inconsistencies are because of v2 API compatibility.
Because of loose validation for request body and query param, APIs ignore
the unknown and invalid inputs silently. This gives the impressions to the user
that, requested unknown or invalid inputs are valid and taken care by Nova.
But Nova ignore all unknown or invalid inputs at API layer itself without
any warning to users.
server representation is not consistent among all APIs which return the
server info in the response body.
GET, PUT, REBUILD /servers APIs return the server representation (with all
server attributes). But PUT and REBUILD /servers response does not
match with GET /servers API.
These are 2 examples of API inconsistency and there might be more such example
which are described in https:/
Blueprint information
- Status:
- Complete
- Approver:
- melanie witt
- Priority:
- Low
- Drafter:
- Ghanshyam Maan
- Direction:
- Approved
- Assignee:
- Ghanshyam Maan
- Definition:
- Approved
- Series goal:
- Accepted for train
- Implementation:
-
Implemented
- Milestone target:
-
train-3
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
Approved for Train. -- mriedem 20190530
Gerrit topic: https:/
Addressed by: https:/
Fix test_flavors to run with correct microversion
Addressed by: https:/
WIP: Multiple API cleanup changes
Addressed by: https:/
Add mising tests for flavor extra_specs mv 2.61
Addressed by: https:/
DRY get_flavor in flavor manage tests
Addressed by: https:/
doc: cleanup 2.75 REST API microversion history doc
Addressed by: https:/
api-ref: add config_drive to 2.75 rebuild response parameters
Addressed by: https:/
Update api-ref for 2.75 to add config_drive in server update response
Released with the 2.75 microversion. -- mriedem 20190820
