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.

Sign up for GitHub

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

Jump to bottom

Update raft_bft_migration.md #4968

Merged
merged 1 commit into from
Sep 10, 2024
Merged

Update raft_bft_migration.md #4968

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion docs/source/raft_bft_migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,18 @@ To migrate, upgrade from version 2.x to version 3.0.0.

This tutorial will describe the migration process at a high level, calling out specific details where necessary.

## Pre-migration Checklist
Before beginning the migration process, ensure the following:
1. All ordering service nodes are running Fabric v3.0.0 or greater
2. All peers are running at least Fabric v3.0.0
3. All channels are configured with the V3_0 or later channel capability
4. The number of nodes is configured as 3f + 1, where f is the number of tolerated failures
5. BFT metadata and ConsenterMapping are prepared for each channel

## Security Considerations
1. Ensure all communication channels are encrypted
2. Verify node identities and certificates before and after migration
3. Update access controls if necessary after migration

## Assumptions and considerations
Before attempting migration, take the following into account:
Expand Down Expand Up @@ -152,4 +164,4 @@ There are a few states which might indicate migration has failed:

1. Some nodes crash or shutdown.
2. There is no record of a successful leader election per channel in the logs.
3. The attempt to switch to `STATE_NORMAL` mode fails.
3. The attempt to switch to `STATE_NORMAL` mode fails.
Loading