Page History

Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: Hyperledger Code of Conduct

Announcements

Agenda for this week is:

• DWG meetings for 2019/2020
  1. This is the last meeting of 2019
  2. DWG meetings will restart Friday Jan 10 2020
• V2.0 release status: Pam/Joe–
  

Discussion

• •  Beta and GA
• Operations Guide — early proposal and reaction (Joe)

Early announcement for upcoming calls:

• Early announce of ledger API walk-through on first call next year (Anthony)
• Recap discussion with Rich Zhao, Pam and team on Chinese national language translations for Fabric
• Early announce of possible IOT Blockchain demo from Chris G early in new year

Discussion

1. Release Status
   1. V2
      1. Beta is now available and docs in very good shape.
      2. Assuming GA in Q1, no final date decided.
      3. Really important to read upgrade docs before migrating
      4. 2.0 requires rebuild of state databases and other significant time consuming activities
   2. 1.4
      1. LTS release including 1.4.5 bug-fix release is in-plan
2. Operations Guide
   1. Refer to:
   2. Joe walks the team through this material
   3. Structure of Operations Guide needs work
   4. Break into sections within operations guide - discussion on this structure
   5. CA docs are relevant issue
      1. Should Fabric CA docs be integrated?
      2. All 3 options outlined in discussion
   6. Anthony on using lifecycle to inform structure of topics
      1. start with identity and use build network to inform TOC structure
   7. Agree that CA docs need to be integrated fully
      1. Joe outlined how this might happen
      2. Close relationship to MSP
      3. Root CA and ICA need to  be advised as best practice
   8. Chris: Should have a DWG focus day on CAs
   9. Need more guidance on burying Root CA from Chris
      1. per best practice – Root CA should never be online
      2. Analogy with AWS discussion cluster defaults
   10. Discussed CA, Peer, OS... running order
       1. New material and re-orged material will be needed.
   11. Non-functional aspects, e.g. security, performance, reliability, HA discussed
   12. Tried a few different layout ideas to organize
   13. Planning guide vs Operations guide
   14. Importance of Kubernetes discussed
       1. Impact on Fabric operations guide of K8s
       2. How to deploy CA in kubernetes
3. Joe showed the new Hyperledger Fabric v2.0 Beta Release documentation
   
   1. What's new https://hyperledger-fabric.readthedocs.io/en/latest/whatsnew.html
   2. Release notes: https://github.com/hyperledger/fabric/releases/tag/v2.0.0-beta
   3. New test network now available in Fabric samples!!! https://hyperledger-fabric.readthedocs.io/en/latest/test_network.html
   4. Upgrade instructions now available off the main toc https://hyperledger-fabric.readthedocs.io/en/latest/upgrade.html
   5. Chaincode External builder and launcher https://hyperledger-fabric.readthedocs.io/en/latest/cc_launcher.html
   6. Chaincode as an external service: https://hyperledger-fabric.readthedocs.io/en/latest/cc_service.html
4. Pam showed the latest updates for the MSP key concept topic: https://github.com/hyperledger/fabric/pull/307
   1. requested that workgroup review again and see if it helps
   2. OK to duplicate the section on Identity classification here although it is also in the Operations Guide? General agreement this is useful.
   3. Chris Gabriel pointed out that there is more information needed about the config.yaml file - likely in the MSP Operations topic - which explains the importance of and the relationship between the Fabric CA Server and Client and the CSR.
   4. General agreement that we need to update the MSP Operations Guide topic as well. Next task once we settle on the MSP Key Concept topic.
5. Chris pointed out the lack of Fabric documentation around how to configure an Intermediate CA with a Fabric Root CA and pointed to the questions in the RocjetChat #fabric-crypto channel around this. He demonstrated how he reverse engineers some of that process using the logs in the VSCode extension. Suggestion was that he start a Jira requesting that this information be added to the Fabric CA Operations Guide and we start the discussion there to get the right people involved. He said this is truly a barrier to adopting Fabric.

Video of this week's session at: Recordings

...