-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
FAB-17243 Add support for Fabric CA for Org3 on the (#91)
test network. Signed-off-by: NIKHIL E GUPTA <negupta@us.ibm.com>
- Loading branch information
Showing
17 changed files
with
939 additions
and
230 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,50 +1,5 @@ | ||
## Running the test network | ||
|
||
Use the `./network.sh` script to stand up a simple Fabric test network. The | ||
network has two peer peer organizations with one peer each and a single node | ||
raft ordering service. You can also use the script to create channels, and deploy | ||
the fabcar chaincode on those channels. The test network is being introduced in | ||
Fabric v2.0 as the long term replacement for the `first-network` sample. | ||
You can use the `./network.sh` script to stand up a simple Fabric test network. The test network has two peer organizations with one peer each and a single node raft ordering service. You can also use the `./network.sh` script to create channels and deploy the fabcar chaincode. For more information, see [Using the Fabric test network](https://hyperledger-fabric.readthedocs.io/en/latest/test_network.html). The test network is being introduced in Fabric v2.0 as the long term replacement for the `first-network` sample. | ||
|
||
Before you can deploy the test network, you need follow the instructions to | ||
[Install the Samples, Binaries and Docker Images](https://hyperledger-fabric.readthedocs.io/en/latest/install.html) in the Hyperledger Fabric documentation. You may experience problems if you run the | ||
sample using a local build. | ||
|
||
For more information, see `./network.sh -help` | ||
``` | ||
Usage: | ||
network.sh <Mode> [Flags] | ||
<Mode> | ||
- 'up' - bring up fabric orderer and peer nodes. No channel is created | ||
- 'up createChannel' - bring up fabric network with one channel | ||
- 'createChannel' - create and join a channel after the network is created | ||
- 'deployCC' - deploy the fabcar chaincode on the channel | ||
- 'down' - clear the network with docker-compose down | ||
- 'restart' - restart the network | ||
Flags: | ||
-ca <use CAs> - create Certificate Authorities to generate the crypto material | ||
-c <channel name> - channel name to use (defaults to "mychannel") | ||
-s <dbtype> - the database backend to use: goleveldb (default) or couchdb | ||
-r <max retry> - CLI times out after certain number of attempts (defaults to 5) | ||
-d <delay> - delay duration in seconds (defaults to 3) | ||
-l <language> - the programming language of the chaincode to deploy: go (default), javascript, or java | ||
-v <version> - chaincode version. Must be a round number, 1, 2, 3, etc | ||
-i <imagetag> - the tag to be used to launch the network (defaults to "latest") | ||
-verbose - verbose mode | ||
network.sh -h (print this message) | ||
Possible Mode and flags | ||
network.sh up -ca -c -r -d -s -i -verbose | ||
network.sh up createChannel -ca -c -r -d -s -i -verbose | ||
network.sh createChannel -c -r -d -verbose | ||
network.sh deployCC -l -v -r -d -verbose | ||
Taking all defaults: | ||
network.sh up | ||
Examples: | ||
network.sh up createChannel -ca -c mychannel -s couchdb -i 1.4.0 | ||
network.sh createChannel -c channelName | ||
network.sh deployCC -l node | ||
``` | ||
Before you can deploy the test network, you need to follow the instructions to [Install the Samples, Binaries and Docker Images](https://hyperledger-fabric.readthedocs.io/en/latest/install.html) in the Hyperledger Fabric documentation. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
## Adding Org3 to the test network | ||
|
||
You can use the `addOrg3.sh` script to add another organization to the Fabric test network. The `addOrg3.sh` script generates the Org3 crypto material, creates an Org3 organization definition, and adds Org3 to a channel on the test network. | ||
|
||
You first need to run `./network.sh up createChannel` in the `test-network` directory before you can run the `addOrg3.sh` script. | ||
|
||
``` | ||
./network.sh up createChannel | ||
cd addOrg3 | ||
./addOrg3.sh up | ||
``` | ||
|
||
If you used `network.sh` to create a channel other than the default `mychannel`, you need pass that name to the `addorg3.sh` script. | ||
``` | ||
./network.sh up createChannel -c channel1 | ||
cd addOrg3 | ||
./addOrg3.sh up -c channel1 | ||
``` | ||
|
||
You can also re-run the `addOrg3.sh` script to add Org3 to additional channels. | ||
``` | ||
cd .. | ||
./network.sh createChannel -c channel2 | ||
cd addOrg3 | ||
./addOrg3.sh up -c channel2 | ||
``` | ||
|
||
For more information, use `./addOrg3.sh -h` to see the `addOrg3.sh` help text. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.