Hello Contributors, The time has finally come. The Hyperledger Fabric maintainers are planning for a migration of the core Fabric repository to GitHub this Friday morning Eastern Standard Time. We

You need to sign and submit with the OrdererMSP admin identity to change consensus type parameters, not the application/peer org admins. Thanks, ~Jason

When you use `peer chaincode install` to install chaincode from source code, it automatically package it as cds format and upload it to a peer node. But how would you install a cds file if you

Hello Team, I am migrating from kafka to raft, When I have changed state from "NORMAL" to "STATE_MAINTENANCE" and created the final expected envelope as per the procedure. Note: We are using BYFN

@Alexandre Pauwels: could you please point me to some references about where to get started to make RAFT work using coredns? Thanks.

We have the same question, anyone can help us??

We are using fabric server to generate certs and use raft. Is there any reference to add new orderers?

Nye, It would be nice if you could share some technical details of k8s that harm p2p network. I believe it could benefit both communities (HL and CNCF) cheers, - J

To rebuild peer's state database: stop peer, drop state database, restart peer. State database will automatically be rebuilt from the blockchain. To rebuild peer's channel blockchains and state

Not to stray too far off topic, but k8s emerged from a client/server microservices/stack deployment requirement, not a p2p requirement. Its popularity for that purpose has (unfortunately, IMO) bled

To add a bit more to Brian's note... If you target upcoming 2.0 (and that'd be my advice) you lessen fabric side changes considerably thanks to the "external" builder framework. So good to get started

I guess K8S is the preferred way to deploy many things not only Fabric ;) and we will go production in a few months with Fabric in K8S. We are not mixing K8S clusters for now, as it's not a

I've said it before on this mailing list and I guess I'll say it again, I don't understand this hate with k8s and Fabric. Using nginx and coredns you can achieve nearly any sort of routing combination

So, in the case of a network across 2 k8s clusters, I have to make all orderer nodes accessible outside of k8s, and put the public host names and ports in the genesis block. Correct? K8s is still a

This is precisely why k8s and p2p are never a good match. K8s simply breaks far too many networking rfcs. It is suitable for asymmetric client/server microservices or stacks, and even then a tiny

The idea of anchor peer is providing information about other peers in the same organization. There is no need for a peer to be completely public but it should be at least accessible by other peers

If I have 2 orgs contributing orderer nodes using etcd raft consensus, and each org runs its nodes in its own Kubernetes cluster. How can I make Raft work across these 2 orgs? I guess that every

Many thanks Brian, this is helpful and very much appreciated! Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, November 19, 2019 6:56 PM,

Thanks for the reply. also adding another link to this thread about same question:

Modest insights ahead, and IANAM (I am not a maintainer): Both seem like non-trivial lifts, so be sure that you really need each of them. There is emerging and improving