FAB-853

Ledger is removed from
   . core/peer/peer.go
   . core/rest/api.go

Ledger package itself is removed. "ledgernext" is
replaced with "ledger".

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

Following skeletal end to end flow work, this submit
takes the next steps for Endorser/Committer
  . converts chaincode and endorser to ledgernext
  . removes consensus package
  . chaincode unit tests use ledgernext
  . panics if ledger.GetLedger is called so we
    can catch codepaths that still use that. These
    are mainly core/api and core/peer
  . removes unit tests from core/api and core/ledger
    (to avoid GetLedger calls there)
  . created a minimal core/peernext. core/peer is
    still there for comparison but is not used

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

This reverts commit 562a35fd, reversing
changes made to 4a78b412.  This was
done because we inadvertently merged a good chunk of master when
patch a96b9edc was submitted to the v0.6 branch.  We will
cherry-pick a96b9edc

 in a later patch to restore the fix
in the proper way.

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

The main purpose of this checking
  . show commit followed by simulation in action
  . users can get a feel for the flow of the protocol across
    the different legs of the end-end path
  . identify key areas for attention (esp. grep for
    "!!IMPORTANT!!")

"deploy and "invoke" Chaincode commands from CLI will also
convert a successful proposal response into a transaction
and send it to the Orderer (if configured in core.yaml).

"query" is removed from CLI. Invoke can also return values
now in ProposalResponse.Response.Payload.

REST calls should not be affected and should work with
old ledger.

See core.yaml for default orderer setup.

This also introduces a stop-gap "committer" whose only
task is to commit blocks from the orderer.

To test :
1. Terminal 1 - run the "solo" orderer
   cd fabric/orderer
   go build
   ./orderer

2. Terminal 2 - run the peer
   peer node start 1>/tmp/peer.out 2>&1

3. Terminal 3 - deploy and invoke take usual params
   peer chaincode deploy ... 1>/tmp/out 2>&1
   peer chaincode invoke ... 1>/tmp/out 2>&1

/tmp/peer.out and /tmp/out will contain tell tale signs
of the round trip in action.

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

The ledgernext and kvledger packages provide APIs to simulate
transactions by collecting read-write sets from invokes of
chaincodes. This change set integrates this for the Endorser
flows.  The main purpose of this code is to enable read write
sets to be propagated so end to end flow ending in a commit to
the ledger can be tested.

The chaincode unit tests continue to use the old ledger. This
allows us to (1) incrementally integrate ledger and (2) show
that the two packages can coexist from a build and runtime
point of view.

It is worth noting that the file kv_ledgers.go hosts a temporary
container for ledgers. This simple approach is expected to be
revised when (sub)ledgers are implemented.

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

This patch is for https://jira.hyperledger.org/browse/FAB-181

,
FAB-182.

The patch is around endorser.go which implements the basic
Endorser service. The "peer deploy ..." and "peer invoke .."
CLI driver commands have been modified to redirected to use
endorser.ProcessProposal instead of the original "devops"
calls.

The deploy, invoke (and query) CLI calls are unchanged in
non-dev mode from user point of view - but for one difference.
The response is a ProposalResponse.

In dev mode (ie, when peer is started with --peer-chaincodedev)
the deploy command would need to set "CORE_CHAINCODE_MODE=dev"
in the "peer chaincode deploy ..." command. This is because, the
command now computes the chaincode code just like the SDK as
opposed to leaving it to be done by devops in the peer. Example
CORE_CHAINCODE_MODE=dev CORE_LOGGING_LEVEL=debug ./peer chaincode
deploy -n mycc -c '{"Args":["init","a","100","b","200"]}'

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

These changes make sure that the logging.chaincode setting from
core.yaml is used to set the chaincode logging level every time
the chaincode container starts. The peer reads in the value and
passes it to the chaincode via an environment variable as it
does for similar values.

Fix Issue FAB-394

Change-Id: Ic4b7228c57fc673a97dbfafc1b086ad04c41c05c
Signed-off-by: Will Lahti <wtlahti@us.ibm.com>

FIX FAB-158

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



Change-Id: I79aae2b4e537a20a72b2fcc1bf83a40087cfeed6
Signed-off-by: Satheesh Kathamuthu <satheesh.ceg@gmail.com>

Fixes the following issues
https://github.com/hyperledger/fabric/issues/2146
https://github.com/hyperledger/fabric/issues/2139



 1. Separate java docker image
 2. Added java package info to proto files
 3. Removed duplicate .proto files checked into java shim project, and copy it as part of build process
 4. Modified java unit test to refer to new path
 5. Updated JAVAChaincode documentation to reflect new changes and added instructions for developing new chaincode
 6. Split java chaincode examples from java shim project

Change-Id: I7cbe92449c30700f17949b03f8fc7c06e0c7efb6
Signed-off-by: Satheesh Kathamuthu <satheesh.ceg@gmail.com>

This allows applications to easily pass arbitrary blobs without having
to serialize them to strings.  At the same time, we also consolidate
the function argument to be part of the repeated bytes args.

For convenience and to simplify porting of existing chaincode to the
new argument format, we introduce helper functions in the shim which
cast between ([][]byte) and (string, []string).

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

This squashed changeset does the following:
 - It renames UUID to TXID in the code (Go/Java), in tests,
   in proto files, in all chaincode related files
 - It uses all the arguments of the chaincode to
   generate the TXID

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

reassign port numbers to 7050-7060 range to avoid conflicts with
Windows port usage (5000). Fixes #2283
https://github.com/hyperledger/fabric/issues/2283



Port assignments as follows:
7050 REST
7051 peer gRPC
7052 peer CLI
7053 peer events
7054 eCAP
7055 eCAA
7056 tCAP
7057 tCAA
7058 tlsCAP
7059 tlsCAA

NOTE: when this PR lands, it will require people to rebuild their Vagrant
development environment(s), so we will want to make an announcement.

Also @bcbrock recommended that we eventually seek a block of ports from IANA.
We should hold off on that until we sort out Consensus next.

Change-Id: I1e54d45589e155a69a2a779b1dac447d5473cf03
Signed-off-by: Christopher Ferris <chrisfer@us.ibm.com>

Copied from commit sha 346f9fb448140e931fed73b46f528de6dacbc0d0
to Gerrit. Verified that all DCO signoff received or IBM
contribution.

Change-Id: I812a2f48382a3cd37e153cd056d0ea94b7f416a0
Signed-off-by: Christopher Ferris <chrisfer@us.ibm.com>