Forbid deployments with omitted dependencies
Before actual deployment when user clicks deploy button Murano should validate whole environment and show an error message if there are issue which may prevent successful deployment.
Murano should check dependencies between services and should block deployments with incorrect configurations.
Murano should perform some logic-testing for services dependencies before the deployment and should propose to revert new changes with incorrect configuration or correct new configuration accordingly to the logic-testing-
For example, user creates AD+IIS and after that deletes AD service and want to deploy this. This deployment will does not work, because workflow for IIS contains part 'join this host to domain' and this workflow will fail during the deployment.
Blueprint information
- Status:
- Complete
- Approver:
- ruhe
- Priority:
- Undefined
- Drafter:
- Timur Nurlygayanov
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
- Ekaterina Chernova
Related branches
Related bugs
Sprints
Whiteboard
User Story #1:
User has some already deployed complex enironment with several dependent services.
User wants to make some changes to this environment - add new services and delete some services, but user want to test this environment before the start of deployment - because new changes can break all.
User clicks on button 'Deploy This Environment' and if something wrong in new configuration, Murano will returns error message and proposes to change the incorrect configurations. User can revert new changes or fix it and when configuration will be correct user can deploy this environment without the risk.
Work Items
Work items:
Add new functionality 'dependecies' to Conductor: TODO
Add new parameters to workflows: TODO
