[WIP] [Placement Group] resizing placement group feature part1: dynamic add bundles.

[clay4444]

Why are these changes needed?

resizing placement group feature part1: dynamically add bundles.

the design doc API proposal

Note that there is a new update at the end of the document.

Python integration tests will be added later.

Related issue number

Closes #16403

Checks

• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[bveeramani]

‼️ ACTION REQUIRED ‼️

We've switched our code formatter from YAPF to Black (see #21311).

To prevent issues with merging your code, here's what you'll need to do:

1. Install Black

pip install -I black==21.12b0

2. Format changed files with Black

curl -o format-changed.sh https://gist.githubusercontent.com/bveeramani/42ef0e9e387b755a8a735b084af976f2/raw/7631276790765d555c423b8db2b679fd957b984a/format-changed.sh
chmod +x ./format-changed.sh
./format-changed.sh
rm format-changed.sh

3. Commit your changes.

git add --all
git commit -m "Format Python code with Black"

4. Merge master into your branch.

git pull upstream master

5. Resolve merge conflicts (if necessary).

After running these steps, you'll have the updated format.sh.

[rkooo567]

cc @edoakes

[clay4444]

sorry, Sang, @rkooo567 , The pub-sub module was refactored too much, Do you know how can I configure enable Redis pub-sub for the test case?

[rkooo567]

Hey @clay4444 this has slipped for some reasons.

I think you need to set

false, 'redis', false

cc @mwtian can you confirm if this is right?

[mwtian]

Redis pubsub is no longer supported. Ray only supports external Redis KV now. I guess we need a guide for adding new topics to Ray pubsub.

[wuisawesome]

Hey @clay4444 how will this PR work with the autoscaler? Can we make sure we understand the plan for how this will work with autoscaling before merging?

[mwtian]

This is an example of adding a channel to Ray pubsub: https://github.com/ray-project/ray/pull/20075/files

[kfstorm]

‼️ ACTION REQUIRED ‼️

We've updated our formatting configuration for C++ code. (see #22725)

This PR includes C++ code change. To prevent issues with merging your code, here's what you'll need to do:

1. Merge the latest changes from upstream/master branch into your branch.

git pull upstream master
git merge upstream/master

2. Resolve merge conflicts (if necessary).

After running these steps, you'll have the updated C++ formatting configuration.

3. Format changed files.

scripts/format.sh

4. Commit your changes.

git add --all
git commit -m "Format C++ code"

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

• If you'd like to keep this open, just leave any comment, and the stale label will be removed.

[rkooo567]

It's not stale

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

• If you'd like to keep this open, just leave any comment, and the stale label will be removed.

[stale]

Hi again! The issue will be closed because there has been no more activity in the 14 days since the last message.

Please feel free to reopen or open a new issue if you'd still like it to be addressed.

Again, you can always ask for help on our discussion forum or Ray's public slack channel.

Thanks again for opening the issue!