Split Storage Drivers
Split backend deriver model into two seprate drivers:
1. Config/admin
2. Message store
Splitting our current model in two will make configuration less confusing, while allowing us to maintain drivers separately and give us the flexibility to choose the best tool for the job (BTFJ). Once that work is done, we can drop support for sqla as a message store backend, since it isn’t a viable non-AGPL alternative to MongoDB. Instead, we can look into some other backends that offer a good mix of durability and performance.
Steps
1. Decouple pool management from data storage (two separate drivers - one admin/config driver and one message store driver)
2. Keep pool management driver for sqla, but drop the sqla data storage driver
What constitutes the control plane?
1. list of pools
2. list of flavors
3. mapping between pools and queues
4. list of queues
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Kurt Griffiths
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Feilong Wang
- Completed by
- Feilong Wang
Related branches
Related bugs
Sprints
Whiteboard
Moving to Kilo
Now, we have ControlDriver and DataDriver, is it not what we want?(jeffrey4l)
