Installing and instantiating chaincode in Bevel deployed Hyperledger Fabric Network


Hyperledger Fabric network deployed and network.yaml configuration file already set.

Modifying configuration file

Refer this guide for details on editing the configuration file.

The network.yaml file should contain the specific section, which is consumed when the chaincode-ops playbook is run

For reference, following snippet shows that section of network.yaml

    - organization:
      name: manufacturer
        - peer:
          name: peer0          
            name: "chaincode_name" #This has to be replaced with the name of the chaincode
            version: "chaincode_version" # This has to be different than the current version
            maindirectory: "chaincode_main"  #The main directory where chaincode is needed to be placed
              username: "git_username"          # Git Service user who has rights to check-in in all branches
              password: "git_password"
              url: ""
              branch: develop
              path: "chaincode_src"   #The path to the chaincode 
            arguments: 'chaincode_args' #Arguments to be passed along with the chaincode parameters
            endorsements: "" #Endorsements (if any) provided along with the chaincode

Chaincode Operations in Bevel for the deployed Hyperledger Fabric network

The playbook chaincode-ops.yaml is used to install and instantiate chaincode for the existing fabric network. For Fabric v2.2 multiple operations such as approve, commit and invoke the chaincode are available in the same playbook. This can be done by using the following command

    ansible-playbook platforms/hyperledger-fabric/configuration/chaincode-ops.yaml --extra-vars "@path-to-network.yaml"

NOTE: The same process is executed for installing and instantiating multiple chaincodes