Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Project repo: https://github.com/hyperledger-labs/blockchain-automation-framework

Deliverables

  •  Helmcharts Helm charts required to set-up Clique consensus with Besu
  •  Ansible scripts to automate the generation of Helm value files.
  •  Documentation on how to use BAF for deploying HL Besu with Clique consensus.
  •  Documented, upgrade of Besu to latest stable on BAF.

...

  •  Deploy Besu with Clique consensus on local network manually.
  •  Manual steps for Besu with Clique documented.

Eval 3:

  •  Helmcharts created for Besu with Clique deployment.
  •  Tests and Documentation created for the Helmcharts.

Eval 4:

  •  Ansible scripts to automate the deployment of Besu with Clique.
  •  Updated documentation.

...

DatesTask/PlanStatus
June 1 - June 14Mentee intro with the mentor. Introduction to the concepts of BAF.Done
June 15 - June 28

Setup local environment for Development

Done
June 29 - July 12

Setup a Besu network with clique consensus manually/locally using Besu documentation.Eval on July 10: Provide reports for first quarter to the program organisers.


Done

Eval Completed

July 13 - July 26

Setup GKE environment for Development (added because local minikube was not feasible due to memory issues)

Done
July 27 - Aug 9

Complete local Besu network with clique consensus.

Done

August 10 - August 23

Set-up a small Besu network using local/GKE Kubernetes network using BAF.

Eval on August 20: Provide reports for first quarter to the program organisers.


Done 

Eval Completed

August 24 - Sept 6Document changes needed to implement Clique consensus.Done
Sept 7 - Sept 20Make the changes in Ansible and Helm charts.In ProgressDone
Sept 21 - Oct 4

Test the scripts and make additional changes in Ansible and Helm charts.

Eval on October 1: Provide reports for second quarter to the program organisers.

PendingDone

Eval PendingCompleted

Oct 5 - Oct 18

Buffer to complete the Besu network deployment using Clique.

PendingDone
Oct 19 - Nov 1

Update the documentation.

PendingOn going
Nov 2 - Nov 12

Prepare final presentation.


Pending

Eval Pending

Row 3: Eval on July 10: Provide reports for first quarter to the program organisers.

Row 6: Eval on August 20: Provide reports for first quarter to the program organisers.

Row 9: Eval on October 1: Provide reports for second quarter to the program organisers.

Row last: Final Eval on November 12: Provide reports for completion.

...

Pending

...

Methodology

I am following the “Code-Test-Document​” methodology.

...