hyperledger-labs/fabric-operations-console

Console started with no orderers and peers found

Opened this issue · 4 comments

bh4rtp2023 commented

I built a console for my fabric network. It starts ok but displays no orderers and peers. There are some questions:

  1. Need I deploy one grpc-web service for every peer and orderer correspondingly?
  2. Can console automatically archive my fabric network configurations?

Thanks.

dshuffma-ibm commented
  • a brand new console will not come with any fabric components, but you can make them or import them
  • yes a grpc-web proxy is required for every peer/orderer, however if you integrate with the "deployer" and operator we have available, this will be taken care of for you
  • what do you mean by fabric network configurations?
  • 👍1
bh4rtp2023 commented

@dshuffma-ibm thank you for your answer.

  • what do you mean by fabric network configurations?
    A network-config.yaml file is used to tell fabric-node-sdk fabric blockchain network configuration, such as peers, orderers and crypto artifacts. How does console get the configuration of my fabric network?
bh4rtp2023 commented

@dshuffma-ibm how to add peer and orderer? The buttons are disabled in the import pages.

bh4rtp2023 commented

i am using docker swarm cluster. the logs of console:

02:49:27 - info: [athena ws] connection accepted. ready: 1 ip hash: 11ca9
02:49:51 - warn: [deployer apis] import only mode, deployer data requested but there is no deployer to ask
02:49:51 - error: [cluster type] unable to get cluster type from deployer, communication error error=import only - deployer is not available
02:49:51 - warn: [startup - cluster type] unable to retrieve cluster type from deployer

The steps to set up

  1. start up fabric swarm
  2. configure grcp-web for every orderer and peer, console and couchdb docker compose file
  3. start console swarm