2022-01-31 Peer Programming Call

Summary

• Discussed refactoring to use OrbitDB for emissions factors #321 - Problem is that OrbitDB requires Node 16 whereas the Fabric images use Node 12.
• Discuss using Bevel to streamline deployment of Fabric applications.  Bevel seems to be a very good tool for managing deployments of Fabric across multiple cloud infrastructures using Kubernetes.
  • The network is configured through a YAML file
  • Operations such as add peer, add organization, add order organization, remove organization, upgrade chaincode are performed by creating a YAML file and then running through ansible playbook 

Next steps

• Harsh Sharmawill email the Fabric list about using Node 16
• Meanwhile we will test using the OrbitDB emissions factors outside of Fabric
• We will continue the refactoring for Scope 3 emissions by changing the data model of emissions factors #319
• Set up project with Bevel team for deployment of Fabric emissions network

Time:

• Monday at 09 AM Pacific
• Add Climate Action and Accounting SIG calls to your calendar   

Dial-In Information:  [ZOOM]

You can join either from your computer or from your phone:

• From computer: https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
• From phone: +1(855)880-1246 (toll free US number) or view International numbers

• Meeting ID: 622 333 6701