Save Information about The Deployment in The Database
For cases of LCM we need to save the deployment information(
In first implementation this information can be added to task object as "blob".
The task serialisers should be reworked to operate with serialised cluster info instead of work with nailgun database. This will help us to move orchestrator from nailgun to separate module and isolate logic of task serialiser from nailgun.
Because we need current and previous deployment info, the tasks workflow should be modified, there should not be API to manually remove any task, instead we should have background process to remove old tasks. All logic in UI that is related to manually removing tasks should be reworked.
Blueprint information
- Status:
- Complete
- Approver:
- Ihor Kalnytskyi
- Priority:
- Essential
- Drafter:
- Bulat Gaifullin
- Direction:
- Approved
- Assignee:
- Bulat Gaifullin
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
9.0
- Started by
- Vladimir Kuklin
- Completed by
- Vladimir Kuklin
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add spec for deployment info history in DB
Addressed by: https:/
Save deployment_info in Task object
Gerrit topic: https:/
Addressed by: https:/
Store settings and networks in deployment tasks
Gerrit topic: https:/
Gerrit topic: https:/
Work Items
Dependency tree

* Blueprints in grey have been implemented.