Skip to content

Support N MongoDB shards #2219

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

Open
wants to merge 11 commits into
base: development/2.12
Choose a base branch
from

Conversation

williamlardier
Copy link
Contributor

Here, we only support deployment of multiple shards. Upgrades is managed by upper layers for now.

Issue: ZENKO-4641

We add support for multiple shards.
The Kustomization file is thus removed, and we instead generate it
based on the current configuration.

Issue: ZENKO-4641
Added to Zenko as an annotation, but now compatible with multiple
shards.

Issue: ZENKO-4641
This implementation tries to use a single MongoDB mongod process
per instance so that we maximize RAM usage and performances.

Issue: ZENKO-4641
Selectors should now be updated to consider the current shard

Issue: ZENKO-4641
- Mutualize http tests in a single CI run.
- All deployments must now be sharded, hence testing separately
  http endpoints is not enough.
- We also mutualize the runner to enable HTTPs after the initial
  deployments. This reduces costs, and ensure basic set of tests
  are executed when using 2 shards.

Issue: ZENKO-4641
We useed to re-run Vault functional tests in Zenko.
This is not needed, as covered by CTST test suite now.

Issue: ZENKO-4641
@bert-e
Copy link
Contributor

bert-e commented May 6, 2025

Hello williamlardier,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@williamlardier williamlardier changed the base branch from development/2.11 to development/2.12 May 6, 2025 11:05
@scality scality deleted a comment from bert-e May 6, 2025
@scality scality deleted a comment from bert-e May 6, 2025
@bert-e
Copy link
Contributor

bert-e commented May 6, 2025

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

- We want to support one P-S-S topology ever 3 servers.
- With 6+ nodes support added, we now need to ensure the replicas
  of configsvr & shardsvr are not exceeding 3.

Issue: ZENKO-4641
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.

2 participants