From 5e20ae5e801b97bdf0bb3f5577cb30f44b70e674 Mon Sep 17 00:00:00 2001 From: Koushik Gavini Date: Wed, 28 Aug 2024 05:37:42 -0700 Subject: [PATCH] Update raft_bft_migration.md Updated Migration instructions to add pre migration checklist and security considerations. Signed-off-by: Koushik Gavini --- docs/source/raft_bft_migration.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/docs/source/raft_bft_migration.md b/docs/source/raft_bft_migration.md index 901fca4566a..1a18cee48aa 100644 --- a/docs/source/raft_bft_migration.md +++ b/docs/source/raft_bft_migration.md @@ -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: @@ -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. \ No newline at end of file +3. The attempt to switch to `STATE_NORMAL` mode fails.