I have built a network following "Building your first network" tutorial. I have also managed to run the network on multiple hosts (example: peer0 on PC1, peer1 and CLI on PC2).
What I know is that I can query or invoke the ledger in the CLI container.
Can I do this outside CLI container on PC2? For example, I need to query it on PC1. What should I do?
Related
what are the containers which are associated with each peer in Hyperledger Fabric (HLF)?
For example: Endorsing peers most have one chaincode container to execute chaincode.
I'm not sure if I understand your question very well, but I still would like to give it a try.
The docker containers associated with a peer are:
Peer container, which manages you peer node. It's the peer container to which you send the transaction proposal either using CLI or through SDK. Every peer container embodies a copy of the ledger. The ledger is segregated using a channel.
Couchdb container, which persists the world state. It saves every key-value pair which you query or invoke using chaincode. The name of the container is usually in the form couchdb.
Chaincode container, where the chaincode is actually deployed. All the modules/packages that your chaincode requires are first installed when you instantiate your chaincode. The chaincode container usually have its name in the form dev-peer0.org1.example.com-fabcar-1.0.1, where dev refers to the environment in which the chaincode is instantiated. peer0.org1.example.com refers to the peer which instantiated it. fabcar here is the name of your chaincode and 1.0.1 is its version, which is changed every time you upgrade your chaincode.
A peer might not have a chaincode container if it's only acting as a validating or committing peer.
CLI container, this container is required for managing peers. At a time, CLI container can only manage a single peer. You can change the peer it's managing by adding/changing the environment variable CORE_PEER_ADDRESS, e.g. CORE_PEER_ADDRESS=peer0.org1.example.com:7051.
I am trying to set up the BYFN Hyperledger Fabric (v1.4.1) network by manually executing the commands, as opposed to running the script byfn.sh, given here: https://hyperledger-fabric.readthedocs.io/en/release-1.4/build_network.html#start-the-network
I observed that the command docker-compose -f docker-compose-cli.yaml up -d
spins up one container per peer and orderer node. But it also spins up a container for a CLI, through which all subsequent commands are run. By examining the docker-compose-cli.yaml file it is also evident that the filesystem of the CLI container contains the crypto material for all the peers and the orderer. This leads me to the following two questions:
Can one not run the subsequent commands for network setup (such channel creation, joining a channel, chaincode installation etc.) by 'exec'-ing into the Docker container of the corresponding peers?
Is it a good practice to spin up a single container which has the crypto material of all network components in one location, as is the case with the CLI container? Won't such a design, when adopted in production, compromise the private keys of the organisations involved?
Yes, you can definitely setup your network without using a cli container. That's just for a shortcut to access multiple peers using a single container. It's basically just a container in which you pass certificates of all the peers or orderers to access to the network. So whatever you are doing from cli you can do seperately from other containers. Now coming back to your questions:
Can one not run the subsequent commands for network setup (such channel creation, joining a channel, chaincode installation etc.) by 'exec'-ing into the Docker container of the corresponding peers?
Yes, you can definitely do that the only requirement is you must set the environment variables accordingly.
Is it a good practice to spin up a single container which has the crypto material of all network components in one location, as is the case with the CLI container? Won't such a design, when adopted in production, compromise the private keys of the organisations involved?
Yes, it will surely be a problem for a production setup. You can't be having a single cli for your peers and orderers. As I have already told you can do everything without a cli container but if you still want a cli then you can have different cli for your orderer container and your peer container.
I am trying to run Hyperledger Fabric first-network. I have a couple of question.
What is the role of CLI container? Is it possible to run the fabric network without CLI container?
if no, then docker-compose-couch.YAML file does not have cli as service. How does that work?
Yes, you could perform all the necessary operation without CLI. Like -
Create Channel
Join Channel
Install Chaincode
Instantiate Chaincode
Invoke Chaincode
Query
In layman terms CLI is there to facilitate you all these functionality in easy manner, because to perform above mentioned operation you need to have some dependent files (e.g - crypto-config,chaincode,channel-artifacts) on accessible place/container, in this case all these files are provided by CLI. You could check below mentioned volume mapped in docker-compose-cli.yaml file.
volumes:
- /var/run/:/host/var/run/
- ./../chaincode/:/opt/gopath/src/github.com/chaincode
- ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
- ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
- ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
Like to create channel,join channel you will have to access .tx file, to install chaincode you need to access specific chaincode on every peer you want to install, one thing would like to mentioned, chaincode you only instantiate once on a single peer and later on you have to install the chaincode.
Hope it would be helpful. :)
The role of the CLI container is to make all the operations regarding the channel and network. The cli container contains the tools necessary for it, like the fabric ca client, the configtxgen and JQ. Yes its possible to run the network without it.
I guess you are talking about the byfn network. You can do all the necessary operations without the CLI container. Of course you will need the tools for it as mentioned above or do all the operations using the fabric SDK.
Current solution:
1. I have a single node running on Hyperledger.
2. I have deployed my car-auction application on it.
Solution looking for:
I want my car-auction application to deploy on the second node and both nodes should be synced on the same channel.
Any suggestion.
Thanks
This basically boils down to the network configuration that you define in Hyperledger Fabric.
This configuration is defined in two files:
crypto-config.yaml: Contains network topology
configtx.yaml: Defines genesis info and channel consortium
Considering your case, I assume your setup to be:
Single Organization
2 peer nodes within this organization
1 Orderer node
A single channel
So, you need to define network topology with an orderer and a single organization containing two peer nodes. You can find references for this complete setup at build your first network docs on fabric documentation.
Once you have that fabric setup ready, you take references from the Composer Docs. Over here, pay close attention to "connection-profile" file that you create. Since you want both these nodes to execute the car-auction chaincode, you'll need to define both of your peers as "endorsing peers" by setting "endorsingPeers" section to be "true" in the connection profile json file.
Follow the same compose reference to generate the PeerAdmin card. Now, when you install the car-auction bna file, it'll be installed on both the peers. Next, when you start the network, both the peer nodes will have their own chaincode container started up.
This way, you'll have two peer nodes connected on the same channel. And since they're on the same channel, they'll be in sync (regardless a peer is endorsing peer or not).
The same kind of setup goes for the multi-org setup.
I currently installed the HL Composer and HL Fabric environment on docker (following the official guide https://hyperledger.github.io/composer/installing/development-tools.html).
I was able to deploy successfully a bna into HL Composer.
But i'm not able to display correctly the console.log("") of transactions processor. I don't understand where is the output of the console.
Thanks in advance for your support.
Output for console.log() in a TP function should be written to the chaincode container.
Use docker ps to see the names of the containers you have running, and then look at the log of the chaincode container. The chaincode container will have the name of your Busniess Network and the version of Composer you are using. E.g. docker logs dev-peer0.org1.example.com-trade-network-0.17.5
(This assumes that you deployed your BNA to the real Fabric, not the Web profile under Playground.)