...
- Extend architecture to other Hyperledger project(s)
- Choose a HL blockchain project
- Define how architecture can be extended
- e.g., needed components, interfaces, modules
- Create the basic architecture to extend project
Schedule
Quarterly Evaluations | Activities |
July 10: First | 1, 2 |
August 21: Second | 3 |
October 2: Third | 4, 5 |
November 13: Fourth | 6 |
Progress
- 1st Quarterly Evaluation (July 10):
- Successfully accomplished. The source code produces is in https://github.com/raphaelvrosa/umbra defined by the commit 78ee22b5f73af70d83b8e6f671853a96274c0692.
- Observations:
- The support for Fabric 2.0+ is defined for the topology components, but as the events depend on the Fabric python SDK to support Fabric 2.0+ (work in progress by the internship "Add interactive examples to Fabric Python SDK").
- No major changes were required in the source code to support Fabric 2.0 - but new events need to be defined to support the new defined chaincode lifecycle operations.
- Two new components were added to umbra, agent and monitor. Both make use of async to monitor and probe fabric nodes in run-time topologies.
- 2nd Quarterly Evaluation (Aug. 21):
- Delivered Fabric 2.0 implementation for nodes. Missing fabric-python-sdk (wait for the project to support 2.0+).
- 3rd Quarterly Evaluation (Oct. 2):
- Implemented scaling mechanisms. Umbra runs with umbra-cli (new component) to automate the execution of experiments.
- Talk given to Hyperledger webinar about umbra - https://www.youtube.com/watch?v=Aw3AjGiNPF8
- 4th Quarterly Evaluation (Nov. 13):
- Makefile, Vagrant, dockerfile created/upgraded to enable full automation and easy experimentation.
- Examples commented with functionalities implemented.
- Using Containernet install stable for Ubuntu 20.04.
- Merged fuzzing capabilities to scale to multiple environments (servers).
Communication
On weekly basis by zoom call with other umbra related projects