Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Approve/Reject node membership from CLI #3594

Merged
merged 4 commits into from
Mar 15, 2024
Merged

Conversation

rossjones
Copy link
Contributor

@rossjones rossjones commented Mar 12, 2024

This PR adds the ability to approve/reject node membership to the cluster, based on each node's approval state. The approve/reject commands are similar and implemented using the same principle.

bacalhau node approve [nodeid] <-m message>

bacalhau node reject [nodeid] <-m message>

it is expected that this same approach can be used for node pause and node drain etc.
Currently the system does nothing to react to the change of state, a future PR will add pubsub for node events so that jobs can be scheduled etc based on approval/rejection/join/leave events.

Additionally this PR resolves a small issue in AuthenticatingClient which was proxying calls with the wrong methods, and adds a basenats test suite for testing against a nats enabled devstack.

TODO:

  • Clarify who is allowed to do this.

Copy link
Contributor

coderabbitai bot commented Mar 12, 2024

Important

Auto Review Skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository.

To trigger a single review, invoke the @coderabbitai review command.


Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@rossjones rossjones force-pushed the approve-reject-nodes branch 2 times, most recently from 2ad899c to 45fbbb5 Compare March 12, 2024 10:43
@rossjones rossjones changed the title WIP: Node management from CLI Approve/Reject node membership from CLI Mar 13, 2024
@rossjones rossjones marked this pull request as ready for review March 13, 2024 10:05
@rossjones rossjones requested review from wdbaruni and frrist March 13, 2024 10:09
@rossjones rossjones force-pushed the approve-reject-nodes branch 2 times, most recently from c8b5379 to 3136c3c Compare March 14, 2024 07:51
@rossjones rossjones requested a review from a team March 14, 2024 16:50
Copy link
Collaborator

@aronchick aronchick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rossjones rossjones force-pushed the approve-reject-nodes branch from 3136c3c to c505e8a Compare March 14, 2024 17:39
Copy link
Contributor

@simonwo simonwo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO:
Clarify who is allowed to do this.

You can probably leave that to the purview of the authn/z system.

Adds an approve and a reject subcommand to the node command, allowing
the user to approve/reject a node's request for cluster membership. This
commit adds the foundations for sending other command (like drain, pause
etc) to the requester API.
@rossjones rossjones force-pushed the approve-reject-nodes branch from c505e8a to 37084c7 Compare March 15, 2024 10:57
@rossjones rossjones enabled auto-merge (squash) March 15, 2024 10:57
@rossjones rossjones merged commit f285c3a into main Mar 15, 2024
12 checks passed
@rossjones rossjones deleted the approve-reject-nodes branch March 15, 2024 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants