Persist infra container in DB
Infra container (sandbox) is just a container. It is better to persist this container into DB. See whiteboard for implementation details.
Blueprint information
- Status:
- Complete
- Approver:
- hongbin
- Priority:
- Medium
- Drafter:
- hongbin
- Direction:
- Approved
- Assignee:
- feng.shengqin@zte.com.cn
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- hongbin
Related branches
Related bugs
Sprints
Whiteboard
OPTION 1:
* Add a field (i.e. infra_container_id) into the container table. If a container is infra container, this field is None, otherwise, it points to the uuid of its infra container.
* The user experience should be the same as before (i.e. 'list' operation should hide all the infra container).
Sample data model:
- Container(uuid=xxx, name=my_
- Container(uuid=yyy, name=my_container, infra_container
OPTION 2:
* Create a separated table for infra container
* Add a field (i.e. sandbox_id) into the container table.
Sample data model:
- Sandbox(uuid=xxx, name=my_
- Container(uuid=yyy, name=my_container, sandbox_id=xxx, ...)
OPTION 3:
Same as option 2 but leverage the concept of 'capsule' instead (related to this proposal [1]).
Sample data model:
- Capsule(uuid=xxx, name=my_
- Container(uuid=yyy, name=my_container, capsule_id=xxx, ...)
[1] https:/
=======
Gerrit topic: https:/
Addressed by: https:/
[WIP]Persist infra container in DB
Addressed by: https:/
Spec for persisting infra container in DB