Page Comparison

Make sure you've done all the Prerequisites. Raft Ordering Service introduced in 1.4.1 (Reference: https://hyperledger-fabric.readthedocs.io/en/release-1.4/whatsnew.html)

Ensure docker images are pulled as per raft supported version (1.4.1 , 1.4.2 as on 18.Jul.2019 - https://github.com/hyperledger/fabric/releases )

Network Architecture

• 5 Orderers
• 2 Organizations
• 4 peers, 2 for each organization
• 4 couchdb, one for each peer
• 2 certificate authority(CA), one for each organization
• 1 cli (Optional)

Setup the Network

1. Set the GOPATH. You can do this by adding this line to your /etc/environment (for a system-wide installation) or $HOME/.bashprofile : export GOPATH=/usr/local/go. Source if you set this in the same linux sesison then, source /etc/environment (OR)  source $HOME/.bashprofile

2. Keep the hyperledger fabric source under GOPATH with the steps mentioned below:

   No Format
   cd $GOPATH/src/github.com/ mkdir hyperledger cd hyperledger git clone https://github.com/hyperledger/fabric.git

   
   

3. Navigate to your home directory or any convenient directory and clone the Hyperledger_Raft branch from our repo:   

   Code Block
   language bash
   git clone -b Hyperledger_Raft https://github.com/TheCognizantFoundry/Insights.git

   
   

4. Navigate into the raft-with-ca folder: cd Insights/raft-with-ca

5. Give permissions to all the executables and shell files which will easily bring up/down the network:
   chmod 777 *.sh
   chmod -R 755 bin

6. Generate the crypto-material. Input arguments to generate.sh are channelname and domain name : 

   ./generate.sh <channelname> <DOMAIN>

   For Example: ./generate.sh mychannel cogdevops.com
Edit the values(DOMAIN, CA_ORG*_KEYFILE etc.) inside the .env file. Refer the list below to know more about the variables of .env:
7. .sh mychannel cogdevops.com

8. Edit the values(DOMAIN, CA_ORG*_KEYFILE etc.) inside the .env file. Refer the list below to know more about the variables of .env:

   Warning
   The tls variables must be set to true as Hyperledger-fabric Raft mandates enabling TLS for better security in network communication. Failing to do so will result in crashing of the orderers. Some of the fields are pre-populated with default values. you may change the values as per requirement. The IMAGE_TAG must be >= 1.4.1 or latest to have raft setup.

   
   

   Code Block
   language bash theme Emacs title .env
   COMPOSE_PROJECT_NAME=<name_of_your_network> IMAGE_TAG=<docker_image_tagraft_tosupported_be_used_for_spawning_containers>tag_1.4.1_or_1.4.2> DOMAIN=<yourCompany_domain_name> ORDERER_GENERAL_TLS_ENABLED=true CORE_PEER_TLS_ENABLED=true FABRIC_CA_SERVER_TLS_ENABLED=true ORDERER_TLS_CLIENTAUTHREQUIRED=true CA_ORG1_KEYFILE=<name of the keyfile residing inside crypto-config/peerOrganizations/org1.cogdevops.com/ca/> CA_ORG2_KEYFILE=<name of the keyfile residing inside crypto-config/peerOrganizations/org2.cogdevops.com/ca/>

   
   

   The tls variables must be set to true as Hyperledger-fabric Raft mandates enabling TLS for better security in network communication. Failing to do so will result in crashing of the orderers.
   Some of the fields are pre-populated with default values. you may change the values as per requirement. The IMAGE_TAG must be > 1.4.1 or latest to have raft setup

   Info
   Warning
   title Hint
   Ensure docker images are pulled as per raft supported version >= 1.4.1 To use raft fabric docker images: Sometimes fabric docker images are pulled with old network architecture(eg., solo) or already present in the system/VM for the image tag "latest", then remove the existing docker images using "docker rmi -f <imageid>" when respective containers are not running. Because, fabric-image with tag "latest" won't pull new image with actual latest tag due to existing reference. Below start.sh will pull the image as per the raft version >=1.4.1 defined in .env file.

   
   

9. Start the Network :

   ./start.sh <channelname> <DOMAIN>

   Note
   You must use the same  channelname and DOMAIN which you used in step 6.

   If you want to learn more about how the network is setup, then do not execute the start.sh. In stead, run the below commands manually from your terminal:

   Code Block
   language applescript title Learn more about the steps performed inside start.sh collapse true
   #Replace $CHANNEL_NAME and $DOMAIN with your channelname and domain respectively. #setup the network docker-compose -f docker-compose-cli.yaml -f docker-compose-couch.yaml -f docker-compose-etcdraft2.yaml up -d sleep 15 #create the channel docker exec -it peer0.org1.$DOMAIN peer channel create -o orderer.$DOMAIN:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem #join org1 anchor peer peer0.org1 docker exec -it peer0.org1.$DOMAIN peer channel join -b $CHANNEL_NAME.block #join org2 anchor peer0.org2 docker exec -it peer0.org2.$DOMAIN peer channel fetch 0 $CHANNEL_NAME.block -c $CHANNEL_NAME -o orderer.$DOMAIN:7050 --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem docker exec -it peer0.org2.$DOMAIN peer channel join -b $CHANNEL_NAME.block #join org1 & org2 docker exec -it peer0.org1.$DOMAIN peer channel update -o orderer.$DOMAIN:7050 -c $CHANNEL_NAME -f ./channel-artifacts/Org1MSPanchors.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem docker exec -it peer0.org2.$DOMAIN peer channel update -o orderer.$DOMAIN:7050 -c $CHANNEL_NAME -f ./channel-artifacts/Org2MSPanchors.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem #join the other peers to the channel docker exec -it peer1.org1.$DOMAIN peer channel fetch 0 $CHANNEL_NAME.block -c $CHANNEL_NAME -o orderer.$DOMAIN:7050 --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem docker exec -it peer1.org1.$DOMAIN peer channel join -b $CHANNEL_NAME.block docker exec -it peer1.org2.$DOMAIN peer channel fetch 0 $CHANNEL_NAME.block -c $CHANNEL_NAME -o orderer.$DOMAIN:7050 --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem docker exec -it peer1.org2.$DOMAIN peer channel join -b $CHANNEL_NAME.block #install the chaincode into the anchor peers docker exec -it peer0.org1.$DOMAIN peer chaincode install -n insightsAudit -v 1.0 -l node -p /chaincode/src/nodejs/ docker exec -it peer0.org2.$DOMAIN peer chaincode install -n insightsAudit -v 1.0 -l node -p /chaincode/src/nodejs/ #install into the other peers docker exec -it peer1.org1.$DOMAIN peer chaincode install -n insightsAudit -v 1.0 -l node -p /chaincode/src/nodejs/ docker exec -it peer1.org2.$DOMAIN peer chaincode install -n insightsAudit -v 1.0 -l node -p /chaincode/src/nodejs/ #instantiate the chaincode inside one of the anchor (here we are doing for peer0.org1) docker exec -it peer0.org1.$DOMAIN peer chaincode instantiate -o orderer.$DOMAIN:7050 --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/$DOMAIN/orderers/orderer.$DOMAIN/msp/tlscacerts/tlsca.$DOMAIN-cert.pem -C $CHANNEL_NAME -n insightsAudit -l node -v 1.0 -c '{"Args":["Init"]}'

   
   

10. Verify if all the docker containers are running:

    docker ps -a

    Info

    You will notice some extra containers running other than the ones mentioned in the network architecture with names like this: dev-peer0.org1.cogdevops.com-insightsAudit-1.0. It is an expected behaviour for the fabric-network. These containers will get spawned whenever chaincode is instantiated in a peer. Since the start.sh script will instantiate the chaincode inside peer0 by default, therefore this container will get spawned.

    At this point your raft setup is complete. Steps mentioned hereafter are for registration and enrollment of a user to be used with SDK.

11. Login into the CA container: docker exec -it ca.org1.<DOMAIN> bash
12. Run the following inside the container:

• Enroll the admin: fabric-ca-client enroll -u https://Admin:adminpw@localhost:7054 --tls.certfiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.<DOMAIN>/ca/ca.org1.<DOMAIN>-cert.pem
• Now register a new user: fabric-ca-client register -u https://localhost:7054 --id.name "newusername" --id.secret "password" --id.type "client" --id.affiliation "org1.department1" --tls.certfiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.<DOMAIN>/ca/ca.org1.<DOMAIN>-cert.pem
• Verify the registration by listing the available users: fabric-ca-client identity list -u https://localhost:7054 --tls.certfiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.<DOMAIN>/ca/ca.org1.<DOMAIN>-cert.pem

You should see the new user inside this list if registration is successful.

     12. Test the Chaincode. Either insert record manually or let the data gets inserted via PlatformAuditEngine. Then run the below query inside any of the peers.             Modify assetID with your Asset ID value and channelname should be the same one used in step 8.

        Query: peer chaincode query -n insightsAuditing -c '{"Args":["GetAssetDetails","<assetID>"]}' -C <channelname>