Change-Id: I9e33f6a177511f6cbb5a1ff5e20188008d2efae6
Signed-off-by: conghonglei <conghonglei@wanda.cn>

This is change 3 of 4 for FAB-2725 CouchDB optimizations

Motivation for this change:
Interactions with CouchDB are currently done individually.
Need to switch to using bulk operations to get optimal performance
from CouchDB. Need to performance test and stress test.

- Change CouchDoc to use pointers for attachments

Change-Id: I8dcbb29432073514c20033e4cdc1204ecbabc0ef
Signed-off-by: Chris Elder <chris.elder@us.ibm.com>

This is change 2 of 4 for FAB-2725 CouchDB optimizations

Motivation for this change:
Interactions with CouchDB are currently done individually.
Need to switch to using bulk operations to get optimal performance
from CouchDB. Need to performance test and stress test.

- Add bulk select methods to couchdb

Change-Id: I463530e0875176de0e0ab3cdf7971b1e3d7b4b36
Signed-off-by: Chris Elder <chris.elder@us.ibm.com>

The committer implementation reports an error if the publishing
of a block committing event failures due to an error that is related
to the eventhub server.

The method shouldn't return a failure, but only log a message to the log,
because if it returns failure- the state transfer module in gossip/state/state.go
doesn't update its metadata.

Change-Id: I134874654f1ce1453eb30939fedfa2c86c2634da
Signed-off-by: Yacov Manevich <yacovm@il.ibm.com>

This change-set does the following:

1. It addresses FAB-2411 (https://jira.hyperledger.org/browse/FAB-2411

)
by computing the PKI-ID of a peer identity as the hash of the
concatenation of the corresponding serialized identity's fields.

Tests have been updated to reflect the changes.

Change-Id: If78ffca85bdf7811744c3b11043ef007db542186
Signed-off-by: Angelo De Caro <adc@zurich.ibm.com>

This is change 1 of 4 for FAB-2725 CouchDB optimizations

Motivation for this change:
Interactions with CouchDB are currently done individually.
Need to switch to using bulk operations to get optimal performance
from CouchDB. Need to performance test and stress test.

- Add bulk update methods to couchdb

Change-Id: Iabd673c9a56fb3d1e25ad7e869c787ebcf6f0bb4
Signed-off-by: Chris Elder <chris.elder@us.ibm.com>

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



We have now two ways to install a chaincode on the FS
   raw ChaincodeDeploymentSpec (current model)
   SignedChaincodeDeploymentSpec (under implementation)

This checking prepares higher level components such as
LCCC use  fabric to use either package types seamlessly.

This paves the way for install to use either types of
packages.

Change-Id: I24c68db5e58d1b64956806bec9919128788c7730
Signed-off-by: Srinivasan Muralidharan <muralisr@us.ibm.com>

This change-set does the following:
1. Removes references to BCCSP defaults opts
like SHAOpts.

This comes in the context of
https://jira.hyperledger.org/browse/FAB-2362



Change-Id: Iddcb5ded78529658f8f4327267468f191a518bc5
Signed-off-by: Angelo De Caro <adc@zurich.ibm.com>

Marbles02 chaincode was using timestamp function from
github.com/golang/protobuf/ptypes.  This caused problem
in docker environment since the go package would
have to be vendored into the chaincode. Replaced
with native golang timestamp function, to avoid
having to vendor.

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

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



CLI is enhanced
  . create a chaincode package (extenstion to "package")
  . sign a previously created package (new "signpackage" subcommand)

The main files affected are "package.go" and "signpackage.go". Rest
of the changes to chaincode CLI files are just for API adjustment.

Also added tests and cc-packaging-and-signing.rst.

Change-Id: Ieb55334d33d5f03bd315f7722b02badc2010675f
Signed-off-by: Srinivasan Muralidharan <muralisr@us.ibm.com>

This change-set does the following:
1. It changes the msp identity's GetOrganizationalUnit method
to return an array of FabricOUIdentifiers. A FabricOUIdentifier
carries information about an organization unit and
its corresponding certification chain identifier.
2. It updates the msp principal ORGANIZATION_UNIT check to
take in account also the certification chain identifier.

This comes in the context of the following FAB:
1. https://jira.hyperledger.org/browse/FAB-2400



Change-Id: I007ff7f5a588a99103751e8454157b0b95eb2bcc
Signed-off-by: Angelo De Caro <adc@zurich.ibm.com>

This change-set does the following:

1. It removes the fabric/accesscontrol package.
The reason for removing that package is because
it is not compatible anymore with v1.
A side effect of this is that the chaincode examples
using that package have been removed as well.
At the current stage, a chaincode developer can perform
access control by reasoning about the creator of a proposal.

2. It removes the fabric/core/crypto package.
The accesscontrol package was the only one using
that package. Recall that all the crypto operation
are now performed using the BCCSP.

Change-Id: If222d353974cba1ec1bd7f5d5dc5451f9a455c18
Signed-off-by: Angelo De Caro <adc@zurich.ibm.com>

 - ChaincodeBase updates:
   - query() method removed
   - run() return type changed to Reponse to mirror
     golang chaincode.
   - updated SimpleSample java chaincode
   - deleted bdd
   - introduce example02 'clone' in Java
   - Parameterized TestExecuteInvokeTransaction so
     that is runs w/ both Java and Go chaincode.
   - Added TestChaincodeInitializeInitError test.

NOTES:
   - more cleanup is still needed, but this gets
     Java chaincode deployment going.
   - the other java chain samples need cleanup
   - there might be some features in the shim
     copy in fabric-sdk-java that should be merged
     into this version.

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

Proposals to application chaincodes must be checked against the channel
writers as agreed in the discussion section of the JIRA item. There are
no tests because they were originally added in 2fc6bc60

.

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

Maintaining the vagrant-baseimage is difficult since we lack
suitable automation facilities.  It has therefore become an
impediment to producing new docker baseimages.  In addition,
it is also less important these days since most of the heavy
lifting is performed by the docker infrastructure.

Consider that when the baseimage for vagrant was created, we
still needed to compile a bunch of basic tools (golang, protobufs
rocksdb, etc).  This is no longer true: Some of the tools
are now available in binary form, others are exectuted within
docker, and others are no longer used (e.g. rocksdb).

Therefore, we can greatly simplify our processes by simply
eliminating our reliance on a precompiled baseimage for
vagrant.  Because of the dockerization effort, all we really
need is a basic platform with make, git, golang-1.7, and docker.

We also include a few other items for developer convenience,
such as behave, nodejs, and java.

Fixes FAB-3000

Change-Id: Ic0749a1c0361a0b4a83d7ca6879e9d2bb50a5456
Signed-off-by: Gregory Haskins <gregory.haskins@gmail.com>

Currently while peer joins the channel it provided the genesis block
which is used to generate the ledger and consequently being committed
into newly generated ledger. Currently the creation has been done in
two phases.

This commit switches the create ledger from the genesis block
functionality to use atomic function which creates ledger with already
committed block.

Change-Id: I8371f9ee8f026bd98194817b48d8118c4df08dd7
Signed-off-by: Artem Barger <bartem@il.ibm.com>

We should force the mode bits, rather than accepting what the
filesystem just happened to present.

Fixes FAB-2865

Change-Id: I02618026927607cc78fd5545e05880bf01bea5af
Signed-off-by: Gregory Haskins <gregory.haskins@gmail.com>

This change-set does the following:
1. Add access control to qscc by verifying that the caller
has read access to the channel.
A new test has been added to cover this access control

This change-set comes in the context of:
1. https://jira.hyperledger.org/browse/FAB-2969



Change-Id: Ieca0babd3b65ecffda450b29cc82797a101f8671
Signed-off-by: Angelo De Caro <adc@zurich.ibm.com>

This change-set does the following:
1. It allows a chaincode to get the SignedProposal object from the chaincode shim.
This is propaedeutic to the enforcement of access control in chaincodes.

This change-set comes in the context of
1. https://jira.hyperledger.org/browse/FAB-2968
2. https://jira.hyperledger.org/browse/FAB-2969



Change-Id: I6f1af65c6959591af314e110d569558b3ab32ce5
Signed-off-by: Angelo De Caro <adc@zurich.ibm.com>

Add java_package specification for the new
ledger protos that got introduced in
https://gerrit.hyperledger.org/r/#/c/7303/

.

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