FAB-1505 refactors CouchDB code to be aligned with LevelDB structure.
FAB-1337 applies all ledger tests written for LevelDB against CouchDB.

In order to test the CouchDB refactor,
had to implement FAB-1337 in same changeset to test.

Like most refactors, this changeset touches a lot of files and code,
since it is not feasible to do a partial refactor.

Tests related to versioning and deleting have been commented out,
these will be re-enabled in subsequent changeset when CouchDB
has the support, in order to keep this changeset size more reasonable.

Change-Id: I0d2d6cca89bd0252f6e84317457a9140b3a0d7a5
Signed-off-by: denyeart <enyeart@us.ibm.com>

https://jira.hyperledger.org/browse/FAB-1650



The chain-config.proto file is misleadingly named, as it contains only
MSP principal things.  The hyphen in the name is also causing problems
with the proto generation for the python bdd, so this should be changed.

Change-Id: Ieb0165826c38ad995cda1cdb351fdc987625d642
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

Have the BDD tests comminucate with the docker
environments via exposed ports, rather than relying
on the existance of bridged networks (which are not
exposed on macOS).

 - Only did enough work to get the orderer.feature
   tests running. This is one of the only two features
   enabled in CI.

 - The other feature enabled in CI, endorser.feature
   does not currently work. CI currenlty ignores that
   this feature fails.

 - All the other pre-fabric 1.0 features are currently
   disabled. More work will be needed to get those
   working.

Change-Id: I73ea1f3fc3e7b46088f73b6fc55882835459b0ef
Signed-off-by: Luis Sanchez <sanchezl@us.ibm.com>

This changeset just adds the new config property.
A subsequent changeset will exploit it.

Change-Id: I2c0f46b4036575a8d53d71546335c6480a6618c3
Signed-off-by: Luis Sanchez <sanchezl@us.ibm.com>

https://jira.hyperledger.org/browse/FAB-1651



The broadcast_timestamp client has gotten slightly out of sync with the
orderer code, and does not work.  It is a simple fix to set the
signature header field as seen in the diff.

Change-Id: I70c00b356ac65b74d06e59f1bd05eab0e9f4097d
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

In gossip, a couple of polling loops continuously output debug
logs that makes debugging difficult. I am removing them at this
point. Note also that logging level shouldn't be set in the
code but in the yaml file to be controlled by the environment.

Change-Id: I7af3fbeaef492aa848ccd8fbcf7c741263caf13f
Signed-off-by: Binh Q. Nguyen <binhn@us.ibm.com>

See https://jira.hyperledger.org/browse/FAB-1597 for this issue.
The problem is that we could not build COP in vagrant.
The reason was that one of COP's vendored packages has native code
with an 'import "C"' statement in it which uses cgo, which uses the
CGO_LDFLAGS env variable to link, which had "-lrocksdb" on it.

This change set removes CGO_LDFLAGS from devenv/setup.sh

While this change set fixes the COP build issue, there are other
references to rocksdb in fabric examples which need cleaning up.
See https://jira.hyperledger.org/browse/FAB-1636



Change-Id: I54e877b2c1f872811a18e983b1e1c05eb5ab1700
Signed-off-by: Keith Smith <bksmith@us.ibm.com>

This CR fixes the copyright date on some new files introduced in the
following changesets.

https://gerrit.hyperledger.org/r/#/c/3887/
https://jira.hyperledger.org/browse/FAB-1613

https://gerrit.hyperledger.org/r/#/c/3895/
https://jira.hyperledger.org/browse/FAB-1614

https://gerrit.hyperledger.org/r/#/c/3897/
https://jira.hyperledger.org/browse/FAB-1615

https://gerrit.hyperledger.org/r/#/c/3899/
https://jira.hyperledger.org/browse/FAB-1617
https://jira.hyperledger.org/browse/FAB-1619



Change-Id: Ibb32ec10051ed996939d66fc167ef9bce69042c7
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

https://jira.hyperledger.org/browse/FAB-1617
https://jira.hyperledger.org/browse/FAB-1619



This changeset removes some of the duplicated orderer bootstrap code
from the protos/utils package.  It does this by introducing a
common/configtx/test package which uses a sample config template to
produce a genesis block.

This can also be used in the future for clients wishing to create a
chain creation transaction.  This is demonstrated in the
broadcast_config client.

This removes the vestigal utils methods for creating configuration
transactions via the 'oldConfiguration' mechanisms.

Change-Id: If064ed3cfcdbd2e59e8fb6c7bf72c8af160dc5f6
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

https://jira.hyperledger.org/browse/FAB-1615



This changeset defines a proto to represent a configuration template.

It also defines a tool in the orderer directory to produce this template
for the orderer.

Change-Id: I3b14a81fcc73a37029f50a9ae0da08e5642d2f4f
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

https://jira.hyperledger.org/browse/FAB-1614



This changeset converts the orderer provisional bootstrapper to use the
new configtx.Template mechanism.

This is a precursor to removing the duplicate genesis code from
protos/utils.

Change-Id: I47ca9a9c8bcfab2b4eeff5b40b84da71a0230a08
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

SBFT used the ledger and an iterator to get the last
batch. This commit changes this and tries to use a
"local copy" that is generally a field in the backend
struct.
There are two cases:
    - backend (System implementation) only knows about
      Genesis, we can assume that the last batch is one
      with an empty header, empty signatures and empty
      payload batch
    - backend's Deliver is called on (re)connection or
      at batch delivery - here we can use the argument
      (batch of type Batch) to update the last batch

Change-Id: Ibd381347df832643a547a3b05bdc7331f4fb1382
Signed-off-by: Gabor Hosszu <gabor@digitalasset.com>

https://jira.hyperledger.org/browse/FAB-1613



This changeset adds the notion of templating configuration transactions
to enable clean construction of configuration transactions, compositing
multiple pieces of configuration from different pieces of code and
ultimately producing chain configuration transaction templates.

Change-Id: I63f054252e68112c945d06d912b38a2130da8144
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

Change-Id: If153df0ca493942d76aaaba66622e5d701f3d320
Signed-off-by: Gabor Hosszu <gabor@digitalasset.com>

Use platform specific testenv image as base image for orderer kafka
behave tests instead of using x86_64 specific openjre image. This ensures
'make behave' works on all platforms (x86_64, ppc64le and s390x).

Change-Id: Ib12a3e1162b0bbec19f7c17cd35b2a91dc9afa74
Signed-off-by: Krishna Harsha Voora <krishvoor@in.ibm.com>

https://jira.hyperledger.org/browse/FAB-1612



The orderer.yaml file is currently very confusing because it mixes
configuration variables which are set one time via provisional genesis
with variables which can change on restart.

This changeset clarifies this issue.

Change-Id: I80cdd9f8c7702b158186468b0413ffc6f46ec6ff
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

https://jira.hyperledger.org/browse/FAB-1352

In the version that was rebased on top of the common components, this
option was kept out in order to minimize the complexity of the changeset.

This changeset introduces it so now the Kafka-based consenter uses the
BatchTimeout setting in shared config, and posts time-to-cut (TTC-X)
messages according to the design document posted here:
https://docs.google.com/document/d/1vNMaM7XhOlu9tB_10dKnlrhy5d7b1u8lSY8a-kVjCO4/edit



The respective unit tests from the solo package have been ported, as well
as additional tests specific to the time-to-cut logic. Do note that this
path shall be revisited with integration tests.

Change-Id: I743d4412cf8a3536fcb854433dfcbb3baa221d95
Signed-off-by: Kostas Christidis <kostas@christidis.io>

Change-Id: Iabc72f20afe75f8878cc5d52fdd8b09a841d24f8
Signed-off-by: Ry Jones <rjones@linuxfoundation.org>

This change set introduces a more flexible way of describing the identity
associated to a policy. So far we had support for serializing the
certificate associated to the identity. We introduce a new structure that
supports that and 3 other ways of listing identities: i) the admin of an
MSP, ii) the CA of an MSP and iii) a valid certificate for an MSP.

Furthermore, policy evaluation is now performed using the MSP infrastructure:
cauthdsl receives a policy principal and an Identity instance and then it can
use the interfaces offered by the MSP to check whether the identity satisfies
the principal and whether the signature verifies. The semantics of policy
verification has somewhat changed: an identity (and its signature) can be used
to satisfy only a single principal. This has the benefit of better dealing
with the policy "two signatures from org0", but it has the downside that a
single identity can no longer be used to satisfy two principals (e.g. if
we need signatures from an identity with attribute A and one with attribute
B, a single signature from an identity with both attributes would not be
sufficient).

Change-Id: Id18a5933e341781334080965b5d04dc07d4f1b99
Signed-off-by: Alessandro Sorniotti <ale.linux@sopit.net>

Change-Id: I96c46d16bd160a6be30f361bef63e0ffb511583f
Signed-off-by: Ry Jones <rjones@linuxfoundation.org>