scheduling: watch the respective scheduler config and trim the prefix

[JmPotato]

What problem does this PR solve?

Issue Number: ref #5839.

What is changed and how does it work?

- Make scheduling service watch the respective scheduler config.
- Trim the key prefix inside the watcher.

Check List

Tests

• Unit test
• Integration test

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• lhy1024
• rleungx

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[codecov]

Codecov Report

Merging #6955 (5e6a088) into master (54981d1) will increase coverage by 0.14%.
The diff coverage is 94.87%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6955      +/-   ##
==========================================
+ Coverage   74.26%   74.40%   +0.14%     
==========================================
  Files         427      427              
  Lines       45270    45315      +45     
==========================================
+ Hits        33618    33718     +100     
+ Misses       8693     8640      -53     
+ Partials     2959     2957       -2     

Flag	Coverage Δ
unittests	74.40% <94.87%> (+0.14%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[rleungx]

Can the schedulers run normally now?

[JmPotato]

Can the schedulers run normally now?

Currently Coordinator directly reads the scheduler config from the storage, so the sync results here can not be used. We may need to do some modifications after this PR to handle these cases:

• Handle the compatibility with the old PD scheduling.
• Determine the new path to store the scheduling-service-created config data.
• Unify the way Coordinator fetches scheduler config whether from storage or watcher.

So currently I'd like to keep this PR to only implement the synchronization logic, WDYT?

[rleungx]

/merge

[ti-chi-bot]

@rleungx: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 2f49527

[ti-chi-bot]

@JmPotato: Your PR was out of date, I have automatically updated it for you.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.