Clean legacy tables
Originally the Tricircle provided an OpenStack API gateway and networking automation functionality, but now it is dedicated to networking automation across Neutron. Hence many tables should be removed as they are no longer used in the Tricircle database.
The Tricircle includes five data models, including resource model, pod model, tenant and pod binding model, routing model and asynchronous job model. Each model contains lots of tables. Currently only pod model, routing model and asynchronous job model are needed, so the other two models are going to be removed from the Tricircle to clean the tables. As for the reserved models, all the tables are required to be renamed for better understanding.
Blueprint information
- Status:
- Complete
- Approver:
- Chaoyi Huang
- Priority:
- Medium
- Drafter:
- Dongfeng Huang
- Direction:
- Approved
- Assignee:
- Dongfeng Huang
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
ocata-3
- Started by
- Dongfeng Huang
- Completed by
- Dongfeng Huang
Related branches
Related bugs
Sprints
Whiteboard
1. Tricircle table clean after splitting etherpad
addressed by: https:/
2. Specification of this blueprint
addressed by: https:/
3. Removing these tables without new features introduced.
addressed by: https:/
4. Removing these tables with new features to solve the dependency on deprecated tables.
addressed by: https:/
