Dave Kelsey

Doing the following ``` ./network.sh up -s couchdb ./network.sh createChannel -c mychannel ``` results in the fabric network being recreated by the createChannel command using levelDB. The reason for this...

- this should support both building/launching chaincode as well as supporting external chaincode - ideally written in Go so that it is platform agnostic (so can support nano-bash and a...

Things like - publish a version of the docs for that tag - publish official docker images and npm modules - bump the code to the next unstable version Basically...

This is a great idea as it will provide proper descriptions of the various scenarios tested by the integration tests and would also make our whole integration test strategy much...

The fabric tests used to test this when it controlled the fabric configuration. Now that it uses test-network I don't think the integration tests drive prometheus in any way. Also...

The rows should correspond to number of submitted transactions, but it's not clear about the value of the first row. In this case as we can have 0 submitted transactions,...

This one is not so important as most people would use the manager to launch the workers but technically you could launch the workers yourself and communicate via process so...

We need an integration test that tests the use of distributed workers communicating by mqtt, ideally appearing to run on different machines (use container technology to achieve this) see https://github.com/hyperledger/caliper/issues/1554...

Given that Fabric is really the only upto date SUT here, I think it's only worth targeting this SUT for now or we could target the pingpong connector if one...