Deploy Fabric Cactus connector¶
Prerequisites¶
To deploy cactus connector a fully configured Fabric network must be present already, i.e. a Fabric network which has Orderers, Peers, Channels (with all Peers already in the channels). The corresponding crypto materials should also be present in their respective Hashicorp Vault.
NOTE: Deployment of cactus connector has been tested on an existing network which is created by Bevel. Networks created using other methods may be suitable but this has not been tested by Bevel team.
Modifying Configuration File¶
Refer this guide for details on editing the configuration file.
While modifying the configuration file(network.yaml)to deploy the cactus connector, all peers in member organizations should have cactus_connector tag as enabled e.g.
name: orderer2
type: orderer
consensus: raft
grpc:
port: 7050
ordererAddress: orderer2.supplychain-net.org1proxy.hlf.blockchaincloudpoc-develop.com:443
- orderer:
..
..
country: CH
fabric_console: enabled # To deploy Fabric console for this organization
ca_data:
certificate: /path/manufacturer/server.crt
cloud_provider: aws # Options: aws, azure, gcp, digitalocean, minikube
aws:
access_key: "aws_access_key" # AWS Access key, only used when cloud_provider=aws
secret_key: "aws_secret_key" # AWS Secret key, only used when cloud_provider=aws
..
..
For reference, see network-fabricv2.yaml file here.
Run playbook¶
The setup-cactus-connector.yaml playbook is used to deploy a cactus connector for Fabric. This can be done using the following command