You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Abstract

The overall objective of the current mentorship program is to improve test coverage for Kubernetes Operators support for Fablo, implement crucial missing features and fix most important issues that come up as a result of testing.

Mentors

Name

Timezone

Email

Jakub DzikowskiCET

jakub.t.dzikowski@gmail.com

Mentee

Name

Timezone

Email

Joan NdegwaGMT +3joannjerin@gmail.com 

Project codebase:

https://github.com/hyperledger-labs/fablo


Outcomes:

  • Bash scripts with automatic tests covering Fablo/K8s and HLF features
  • Tested features matrix for Fablo with Kubernetes Operators
  • A list of issues documenting missing features and errors in the current implementation
  • Implementation resolving part of the created issues


Timeline:

Week

Deliverables

Status

Jun 19 - Jul 2
  • Onboarding
  • Get high level understanding of Fablo codebase
  • Environment Setup
  • Running integration test on local machine
  • Learning guided by mentor: General information about blockchains, Hyperledger Fabric and Fablo infrastructure
Done
Jul 3 - Jul 16

Phase 1 starts - improving our testing toolkit

  • First PR - fix chaincode sample
  • Implement invoke command for Docker setup

Jul 17 - Jul 30
  • Implement query command for Docker setup
  • Implement chaincode list command for Docker setup
  • Add TLS support for invoke, query and chaincode list

Jul 31 - Aug 6
  • Implement invoke and query for Kubernetes setup
  • Implement chaincode list for kubernetes setup

Aug 7 - Aug 20
  • Implement channel list for Kubernetes setup
  • (some time buffer)

Aug 21 - Sep 3

Phase 2 starts - testing

  • Determine test cases and test matrix for Kubernetes
  • Implement tests, create issues for things to improve

Sep 4 - Sep 17
  • Second iteration - improve test cases, test, create issues

Sep 18 - Oct 1

Phase 3 starts - fixing

  • Iteration 1 - prioritize, pick and work on issues

Oct 2 - Oct 15
  • Iteration 2 - prioritize, pick and work on issues

Oct 16 - Oct 29
  • Iteration 3 - prioritize, pick and work on issues

Oct 30 - Nov 12
  • Iteration 4 - prioritize, pick and work on issues

Nov 13 - Nov 30
  • Iteration 5 - prioritize, pick and work on issues
  • Final evaluation

Methodology

  • Lean, iteration-based development with mentor guidance
  • No labels