fabric-samples/test-network
Dave Kelsey e2d351ed61
Minor improvement to test network docs (#607)
Also fix the version of prometheus and grafana being used
to ensure the queries remain compatible as well as avoid
issues whether they may not work if latest images already
exist on machine but are not at a level that will work

Signed-off-by: D <d_kelsey@uk.ibm.com>

Co-authored-by: D <d_kelsey@uk.ibm.com>
2022-02-01 15:53:30 +00:00
..
addOrg3 remove shift after verbose (#586) 2022-01-19 14:35:20 +01:00
configtx chore: minor simplification of configtx yaml (#459) 2021-07-12 17:42:23 +02:00
docker Adding examples of CCAAS and support into the test-network (#560) 2021-12-17 13:18:22 +00:00
organizations Fix creating channel when ${PWD} contains space. (#402) 2021-01-20 16:32:38 +01:00
prometheus-grafana Minor improvement to test network docs (#607) 2022-02-01 15:53:30 +00:00
scripts Adding examples of CCAAS and support into the test-network-k8s (#527) 2021-12-17 14:09:03 +00:00
system-genesis-block [FAB-17145] Add test network to Fabric Samples 2019-12-11 10:28:39 -05:00
.gitignore Allow install of a chaincode 2020-07-15 10:39:12 -04:00
CHAINCODE_AS_A_SERVICE_TUTORIAL.md Minor improvement to test network docs (#607) 2022-02-01 15:53:30 +00:00
monitordocker.sh Adding examples of CCAAS and support into the test-network (#560) 2021-12-17 13:18:22 +00:00
network.sh remove shift after verbose (#586) 2022-01-19 14:35:20 +01:00
README.md Minor improvement to test network docs (#607) 2022-02-01 15:53:30 +00:00
setOrgEnv.sh Add in a setEnvOrg script (#487) 2021-09-08 14:54:11 +00:00

Running the test network

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 chaincode. For more information, see Using the Fabric test network. 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 to follow the instructions to Install the Samples, Binaries and Docker Images in the Hyperledger Fabric documentation.

Using the Peer commands

The setOrgEnv.sh script can be used to setup the environment variables for the ogrganziations, this will will help to be able to use the peer commands directly.

First, ensure that the peer binaries are on your path, and the Fabric Config path is set Assuming that you're in the test-network directory.

 export PATH=$PATH:$(realpath ../bin)
 export FABRIC_CFG_PATH=$(realpath ../config)

You can then set up the environment variables for each organization. The ./setOrgEnv.sh command is designed to be run as follows.

export $(./setOrgEnv.sh Org2 | xargs)

(Note bash v4 is required for the scripts)

You will now be able to run the peer commands in the context of Org2. If a different command prompt you can run the same command with Org1 instead. The setOrgEnv script outputs a series of <name>=<value> strings. These can then be fed into the export command for your current shell

Chaincode-as-a-service

To learn more about how to use the improvements to the Chaincode-as-a-service please see this tutorial. It is expected that this will move to augment the tutorial in the Hyperledger Fabric ReadTheDocs

Prometheus and Grafana

To enable the collection of fabric networks into Prometheus and also have a default Grafana dashboard please see this tutorial.