As I understand it, each org is similar to a real-world business entity, and should have its own CA. Each org may or may not own an orderer node. If an org contributes both peer and orderer nodes,

Yes, as I keep saying, your peers and ordering nodes should belong to different Fabric organizations. If there are subgroupings within a large entity like a bank, this separation should still happen

Thanks Joe, So it is technically feasible but not recommended for decentralization purposes, right? I could imagine a use case where we don't have such a large organization with different arms like

Harris, This is not a recommended configuration. Each entity (ie, Bank of America) should have an org that owns their peers and a separate org that owns their ordering nodes. Regulations or business

Hi Joe and Jean, Looking at the example of Jean I am wondering if it is possible to use Org1 and Org2 as the organizations of the orderers. So instead of creating new organizations for each orderer

Joe, Thank you very much for your great explanation which was exactly the kind of insights I was looking for. Unless I'm wrong (if so correct me please), the illustration I made in my previous post

Ah. Thanks for the explanation.

There's not actually a flag ... you simply specify the full path to the package (e.g. ./mypackage.cds) as an argument (e.g. after all the flags). peer chaincode install -n mycc -v 1.0 -p

How do you do it, Gari? I checked 'peer chaincode install --help', and could not see a flag to specify a cds package. My version of the peer command is 1.4.4. Thanks.

Jean-Gael, So Fabric organizations are similar to organizations as we think of them in the real world (Bank of America is an "organization"), but there are differences that affect the way you should

You can actually specify the package as an argument to the command: peer chaincode install [flags] pkg ----------------------------------------- Gari Singh Distinguished Engineer, CTO - IBM

Thanks for you quick reply. I read this documentation a while ago and indeed some elements are present there: I have a couple of questions though about some sentences I found:I feel a bit confused

You need to drop the entire CouchDB data volume (or /data directory within the volume) to trigger the state database rebuild, not individual databases within the CouchDB instance. Dave

I got it working, as described in section "add new orderer node" of my project: https://github.com/yxuco/fabric-operation/blob/master/operations.md You need to update the system channel config with

see this video where it is shown that dropping the db and restarting the peer does not rebuild the db: https://youtu.be/h0NjZRH9RXE Rebuilding Fabric State Database youtu.be

That's great news.-- This is my life,but world of us~~

Jean-Gael, Check out https://hyperledger-fabric.readthedocs.io/en/release-1.4/orderer/ordering_service.html. It should have some of the answers to your questions. Regards, Joe Alewine IBM

Hello All, We hold our regulardocumentation workgroup call this week, both Eastern and Western hemispheres. As is now usual,you can read the summary minutes for last week's call:

Hi all, This topic is more a conceptual one around orderers and organizations as we are moving from solo mode to Raft. In solo mode, as we had a single orderer, the organization matter was quite

Nice work! Thanks. Hopefully, this will make it easier for people to contribute - using the more familiar Github workflow. Chris