2019 Q2 Hyperledger Cello


Project Health

Project health is largely the same as in previous update. The community is making  changes to make Cello more of a production ready tool. Features and capabilities are now more based on common use cases and behaviors of the Blockchain applications. Weekly meetings often see 10+ participates and often run over the allocated 30 minutes due to discussions and questions. In some cases, very well run pass 1 hour mark.


There are no major issues at this time.


  • v0.9.0: Support v1.1/v1.2 fabric in k8s agent, Add v1.3 capabilities to ansible agent.
  • v1.0.0: Most of the changes to the project are towards this release. We like to be very cautious and prudent on this release and will not rush it out.

Overall Activity in the Past Quarter

  • Ansible agent continued with many features additions:
    • Continue working on Interop artifacts generation, join request, orderering system endpoints and certificates integration
  • Talk with Justitia proposal submmitter to bring the proposed functions/idea into cello and/or basically merge its work into Cello
  • Added agent creation function on user dashboard
  • Adding Fabric K8S operators with the Intership
  • Continue improving user experience for user dashboard.
  • Based new and future cello work on fabric 1.4.2 (community decision)
  • Design the new architecture to support blockchain governing.
  • Bug fixes and documentation improvement.

Current Plans

Use new framework to unify all the user interface panelsHigh

Organize and manage fabric network dynamically

Adopt the Interop working group channel expansion methodLow
Support fabric 1.4 and later version (if using ansible agent, this is done already)Medium

Maintainer Diversity

Current there are 4 maintainers, and those active developers who contribute to cello continuously (3 month) will be nominated.

  • Baohua Yang (Oracle)
  • Haitao Yue (IBM)
  • Tong Li (IBM)
  • Jiahao Chen (VMware)

Contributor Diversity

Contributions to the projects maintain the similar rate as Q1. Lot of discussions on bringing user management components from a third party which already has the function in their product.

Additional Information

Reviewed by

  • Arnaud Le Hors
  • Baohua Yang
  • Binh Nguyen
  • Christopher Ferris
  • Dan Middleton
  • Hart Montgomery
  • Kelly Olson
  • Mark Wagner
  • Mic Bowman
  • Nathan George
  • Silas Davis
  • No labels


  1. Can you please comment on Cello development regarding designing for security and designing for accessibility?

  2. Cello is a tool to deploy and manage a blockchain network such Fabric network. Its self is secured by common security measures such as TLS and user name and password just like any other common applications. In terms of security of the fabric network or any other network, we use what each production provides. For example, you can set up fabric using tls and certificates, cello will provide options for users to do that. In terms of the accessibility, our user interface team is using a very popular framework and I believe it is baked in the framework. But I am not 100% sure if we have done anything special. That will need to be deferred to Haitao Yuefor a better answer.

  3. For the RESTful APIs by Cello, there are typical security mechanism like token to protect the service.

    There's no plan for accessibility now. It should be post the v1.0 release.