...
Issue 1295: [besu] Added GCP-storageclass
Issue 510: [besu] Updated the documents and added doc changes for besu clique consensus
Milestones
Eval 1:
- Local setup of all tools, Docker, Git, Minikube, Ansible.
- Use existing BAF code to deploy Besu with IBFT consensus on local network.
...
- Ansible scripts to automate the deployment of Besu with Clique.
- Updated documentation.
Timeline
| Dates | Task/Plan | Status |
|---|---|---|
| June 1 - June 14 | Mentee 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. | 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. | Done Eval Completed |
| August 24 - Sept 6 | Document changes needed to implement Clique consensus. | Done |
| Sept 7 - Sept 20 | Make the changes in Ansible and Helm charts. | Done |
| Sept 21 - Oct 4 | Test the scripts and make additional changes in Ansible and Helm charts. | Done Eval Completed |
| Oct 5 - Oct 18 | Buffer to complete the Besu network deployment using Clique. | Done |
| Oct 19 - Nov 1 | Update the documentation. | On goingDone |
| Nov 2 - Nov 12 | Prepare final presentation. | PendingOngoing Eval Pending |
Row 3: Eval on July 10: Provide reports for first quarter to the program organisers.
...