/
Fabric Operations Labs

Fabric Operations Labs

Nov 08, 2023

Note: The information below is now out of date – check out the Fabric Ecosystem page for a more up to date view of Fabric related projects and labs.

 

What labs projects do we have that are related to Fabric operations?  This is a list I made going through github, so you may disagree how related some of these projects are (or you may want to add some that I left off–there is some gray area).  Red indicates the lab is archived. Graduated

Initial groups to reach out to:

  1. HLF Operator (Kubernetes):  https://github.com/hyperledger-labs/hlf-operator ("kungfu operator")

  2. Bevel (formerly Blockchain Automation Framework lab)

  3. Cello: https://github.com/hyperledger/cello 

  4. fabric-test network operator : https://github.com/hyperledger/fabric-test/tree/main/tools/operator 

  5. Fablo (Docker): https://github.com/hyperledger-labs/fablo

  6. Minifabric:  https://github.com/hyperledger-labs/minifabric

  7. Fabric Performance Sandbox: https://labs.hyperledger.org/labs/PerformanceSandBox.html 

Other groups to reach out to:

  1. Fabric Operations Console:  https://github.com/hyperledger-labs/fabric-operations-console

  2. Microfab :  https://github.com/IBM-Blockchain/microfab 

  3. Hyperledger Fabric Operator https://github.com/KompiTech/hyperledger-fabric-operator (KompiTech) 

  4. Kubernetes Operator for Hyperledger Fabric https://github.com/raftAtGit/hl-fabric-operator  (Hakan Eryargi +/- Accenture) 

  5. Hyperledger Fabric K8S Operator https://github.com/litong01/fabric-operator (Tong Li) 

  6. Kaleido https://www.kaleido.io  

  7. Fabric Token SDK:  https://github.com/hyperledger-labs/fabric-token-sdk

  8. Xilinx Blockchain Machine for Fabric (hardware accelerator):  https://github.com/hyperledger-labs/fabric-machine

  9. HLF Connector (REST interface):  https://github.com/hyperledger-labs/hlf-connector

  10. Fabex (block explorer):  https://github.com/hyperledger-labs/fabex

  11. MirBFT (consensus algorithm, originally intended for Fabric):  https://github.com/hyperledger-labs/mirbft

  12. Fabric Smart Client:  https://github.com/hyperledger-labs/fabric-smart-client

  13. Fabric-chaincode-ocaml (Ocaml support for Fabric smart contracts):  https://github.com/hyperledger-labs/fabric-chaincode-ocaml

  14. Operations Smart Contract (OpsSC) for Hyperledger Fabric v2.x:  https://github.com/hyperledger-labs/fabric-opssc

  15. Fabric-chaincode-wasm:  https://github.com/hyperledger-labs/fabric-chaincode-wasm

  16. Fabric-chaincode-Haskell:  https://github.com/hyperledger-labs/fabric-chaincode-haskell

  17. Convector (Fabric operations):  https://github.com/hyperledger-labs/convector

  18. Keyhole-Fabric-API-Gateway (Restful API):  https://github.com/hyperledger-labs/keyhole-fabric-api-gateway

  19. Fabric Block Archiving: https://github.com/hyperledger-labs/fabric-block-archiving

  20. Chaincode Analyzer:  https://github.com/hyperledger-labs/chaincode-analyzer

  21. Nephos (Fabric to Kubernetes):https://github.com/hyperledger-labs/nephos

  22. Blockchain Analyzer:  https://github.com/hyperledger-labs/blockchain-analyzer

  23. Fabric Consortium Management:  https://github.com/hyperledger-labs/fabric-consortium-management

  24. Fabric Chrome Extension:  https://github.com/hyperledger-labs/fabric-chrome-extension

  25. Fabric-VMS-Provision (Ansible):  https://github.com/hyperledger-labs/fabric-vms-provision

  26. Blockchain network on kubernetes: https://github.com/IBM/blockchain-network-on-kubernetes

2022 Hyperledger Mentorship Programs

  1. Enable Kubernetes Operators support for Fablo : https://lf-hyperledger.atlassian.net/wiki/display/INTERN/Enable+Kubernetes+Operators+support+for+Fablo 

  2. Expand Minifabric with k8s operator support : https://lf-hyperledger.atlassian.net/wiki/display/INTERN/Expand+Minifabric+with+k8s+operator+support 

 

There are 23 labs related to Fabric operations!  Some of them are of course archived.  We have 12 non-archived labs (so at least a little bit active).  

Of these, it seems like Fabric Operations Console, HLF Operator, Fablo, Fabric Smart Client, Operations Smart Contract, and Minifabric serve very related objectives.  Would it be possible to convince them to work together?  Cello may also want to be a participant.

Comments:

  1. Yes, we should certainly try to encourage these groups to work together.  My thought is we might need to segment this a bit more though to figure out where there are the best opportunities for engagement.  Just because a lab is doing something related to Fabric doesn't mean they'll be interested in another lab related to Fabric.  For instance, the hardware acceleration Xilinx is doing would be relevant for other performance related labs, like Tape or Performance SandBox, but it doesn't seem like there's necessarily much in common with other labs that have something to do with Fabric.  Another example of segmenting is finding all of the labs interested in Fabric and Kubernetes and trying to bring them together.