GitAuto: 【多云编排】创建多云工作负载时, 调度策略可以提示一下,部署策略中的调度类型会多一个 #5943
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #3146
What is the feature
Provide suggestions for scheduling strategies when creating multi-cloud workloads. Additionally, address the issue where an extra scheduling category appears in the deployment strategy.
Why we need the feature
When creating multi-cloud workloads, the current scheduling strategies lack guidance, making it difficult for users to choose the most appropriate option. Furthermore, an unexpected additional scheduling category in the deployment strategy causes confusion and hampers effective workload management. Enhancing the scheduling strategy with prompts and correcting the deployment strategy ensures a smoother and more intuitive user experience.
How to implement and why
Enhance Scheduling Strategy Interface:
Fix Deployment Strategy Scheduling Categories:
Update Documentation:
Testing and Validation:
About backward compatibility
The proposed changes will maintain backward compatibility by only enhancing the user interface and correcting existing scheduling logic without altering the fundamental functionality of workload deployments. Users will benefit from improved guidance and a streamlined deployment strategy without experiencing disruptions to their current workflows.
Test these changes locally