Fabric Contributor Meetings Personal Notes 2021-Oct-13th

Fabric's current jobs

• 2.4 Gateway and slim SDK are expected to be released this quarter, and are currently preparing for cases and release, system testing and documentation.
• Ledger troubleshoot tool
• Rest application case
• Privacy Data Clearance RFCs Related to GDPR
• zenhub panel on github, planned to replace jira

Fabric Strategic Priorities survey results

1. BFT
2. Clean up old blocks
3. replace goleveldb
4. performance optimization
5. Smart client (lib project)
6. query support
7. Token
   

Kubernetes Test Network - Josh Kneubuhl

Objectives:

• Provide a simple, one click activity for running the Fabric test network.
• Provide a reference guide for deploying production-style networks on Kubernetes.
• Provide a cloud ready platform for developing chaincode, Gateway, and blockchain apps.
• Provide a Kube supplement to the Fabric CA Operations and Deployment guides.
• Support a transition to Chaincode as a Service.
• Support a transition from the Internal, Docker daemon to External Chaincode builders.
• Run on any Kube.

The Kubernetes Test Network re-establishes the Hyperledger test-network as a cloud native application.

The Test network is still too difficult to use, so this project aims to be able to deploy fabric on the local k8s instead of using docker-compose. Although docker-compose can be used, it is not cloud deployment.
When we combine the two flexible software k8s and HLF. Configuration can become complicated for beginners. From an implementation point of view:

• Contracts as services.
  cryptogenSave the file locally, but for the cloud environment. Even if we have fabric ca client we need to have MSP directory.
  
  Reference network:
  
  only call the k8s API to interact with the cluster.
  
  Application scenarios and demos
  
  support debug chaincode and the ability to migrate to other k8s environments.
  
  Local chaincode image support to achieve local packaging and deployment
  Local chaincode debug
• chaincode as a service
• The exposed ports are in HLF Chaincode related settings
• Start Chaincode through VScode's debugger and related configurations,
  so that the contract can be started through vscode's debug mode, and the corresponding debug events.
  

Original article:
https://wiki.hyperledger.org/display/fabric/Contributor+Meetings+2021