Add service dependencies policy when restart the kolla-kubernetes cluster
Registered by
Kevin Zhao
Now after deploy the OpenStack cluster with Kolla-kubernetes, when user need to restart the cluster, the deployment service don't follow a guide to start in proper order, that will induce the deployment failed and we could not use the OpenStack after restarting.
So it is better to add start policy, to let several service have dependencies.
For example:
We need to let the mariadb and openvswitch as a denpendency of memcached, so when start memcached, it will first check whether the mariadb or openvswitch already start, then start memcached.
If either mariadb or openvswitch don't start, will first start mariadb or openvswitch and then start memcached.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Kevin Zhao
- Direction:
- Needs approval
- Assignee:
- Kevin Zhao
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)