bevel icon indicating copy to clipboard operation
bevel copied to clipboard

feat(fabric): modify base code to incorporate orderer(s) and peer(s) in each organization

Open TheJagpreet opened this issue 3 years ago • 0 comments

Description

As a developer, I want to modify the current network.yaml schema such that, we have both the orderer and peers (one, many, none : all three scenarios) per organisation.

This task will greatly impact the if/when conditions around the roles and certain roles themselves like (configtx related roles, crypto generation roles) and will need deep understanding of both, Hyperledger Bevel and Hyperledger Fabric understanding.

The vision here being, with this enabled, we can move to the next step of individualising network setup, i.e. each organisation to host its own part of setup, iff they want to.

Not necessary initially, but a later issue needs to be created to restrict the block signers to just the subset of certificates authorized for ordering as mentioned here

Acceptance Criteria

  1. Each organization in the network.yaml can have zero, one or many orderers and peers (but one entity of them for sure, no empty organizations)

TheJagpreet avatar Feb 23 '22 08:02 TheJagpreet