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

IBP Fabproxy doc changes #77

Closed
Changes from all commits
Commits
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
8 changes: 4 additions & 4 deletions examples/fabproxy-removal/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ docker run -it --rm -u $(id -u) -v "local fully qualified path to fabproxy remov
Example:

```
docker run -it --rm -u $(id -u) -v ./examples/fabproxy-removal:/playbooks ghcr.io/hyperledger-labs/fabric-ansible:sha-c9330b9 bash
docker run -it --rm -u $(id -u) -v ./examples/fabproxy-removal:/playbooks ghcr.io/hyperledger-labs/fabric-ansible:sha-c7cd5e4 bash
```

At the command prompt, change directory to '/playbooks' and copy the fabproxy removal playbooks.
Expand Down Expand Up @@ -218,6 +218,9 @@ After migrating all CA addresses. Before proceeding to the next step. If the cus

## Step 7: Migrate the orderering node address.

***Note:***
In the `common-vars.yml`, set the `dry-run` variable to true for the first run. This will ensure all channels are reachable and all actions can be completeted with making changes to the channels.


1. The steps migrate renew the Orderer TLS certificate and migrate the Orderer address.

Expand All @@ -233,10 +236,7 @@ After migrating all CA addresses. Before proceeding to the next step. If the cus
5. Once the aforementioned command has been executed, confirm that the respective Orderer nodes are restarting. If its restarted navigate to the console and click the Orderer node. In the Orderer `info and usage` page the `Operations url` and `API url` port has been changed into `443`.


***Note:***

In the `common-vars.yml`, set the `dry-run` variable to true for the first run. This will ensure all channels are reachable and all actions can be completeted with making changes to the channels.
!important

## Step 8: Update anchor peer in the channel.

Expand Down
Loading