Moving frequently using reads to slave db connection
Starting from Juno we've got an slave_connection to MySQL. In order to increase read-only API performance including:
* fernet token issuing/validation
* assignment/
varios operations can be send to slave.
More info:
https:/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Atsuko Ito
- Direction:
- Needs approval
- Assignee:
- Atsuko Ito
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Needs Code Review
- Milestone target:
- None
- Started by
- Atsuko Ito
- Completed by
- Lance Bragstad
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Keystone slaveification spec
Addressed by: https:/
Keystone slaveification
Changing the status to next since this should ideally depend on some oslo.db work to specify if a connection is read-only or read/write
procedural change of milestone target, feel free to target to mitaka-2 or mitaka-3
(lbragstad): It's been a while since this has been updated. If there is still a need for this, please don't hesitate to restore the existing specification [0]. It sounds like oslo had some tooling that would make this easier, which we will need to factor into a re-proposed specification.
