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>

* changes:
  Allow ledger selection to be done at runtime for solo.
  Add a fileledger implementation in rawledger.

The life-cycle system chaincode (lccc) manages chaincodes for a chain in an
endorser. The life-cycle is basically the "deploy", "upgrade", "stop"
and "start" actions. This changeset provides the basic chaincode for
creating the table of chaincodes and implements just the "deploy" command.
This work will be developed till the basic endorser functions are fully
implemented.

This driver for this chaincode will be checked in the next changeset.

NOTE - this change also fixes the limitation where only one system chaincode
can be running at a time.

This is part of the feature development of FAB-181, FAB-182, FAB-183.

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

This includes structure of the new code conforming to new architecture
and a basic working implementation.

Change-Id: I885e122c0001ff82301cd1448a7ddad80db931b0
Signed-off-by: manish <manish.sethi@gmail.com>

This changeset adds tests which are generally applicable to
rawledger implementations.  It enables these tests for both
ramledger and for fileledger.

You may notice that these tests are substantially similar to
the tests in file ledger and were derived from there,
substituting black box equivalents for the implementation
details of fileledger.

This new suite of tests also caught a bug in the ramledger
implementation which could result in a crash when the
specified block was exactly the block number of the oldest
block in storage.  A fix is included.

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

This also adds a README.md file which has a basic explanation
of the pieces currently in the orderer dir.  It also contains
brief instructions regarding how to use the existing code, as
well as some future plans.

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



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

This addition supplements the existing ramledger rawledger
implementation.  Neither this, nor the ramledger is intended to be
performant, but they are both intended to be extremely simple.

In the case of this added fileledger, it is intended to allow data
persistence between stopping and starting of an orderer.

Ultimately, the expectation would be that for the performant case,
a high performance database of some sort, such as RocksDB or other
would likely be used for persisting data.

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



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

This also removes the ramledger implementation from solo,
and turns it into its own package, utilizing the new
rawledger interface.

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



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

Mock chaincode implements (function string, args []string) interfaces for
backward compatibility. We need to move away from this so we can implement
[]byte arguments using new API.

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

The "mock" framework provides a base starting set
of support APIs such as Get/Put/Delete state and
Range for unit testing chaincodes. As tables are used
extensively, this change enhances the framework with
table support.

This addresses https://jira.hyperledger.org/browse/FAB-345



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

Change-Id: Id811b29aa319e242d505ab80bb330934cf07f352
Signed-off-by: jeffgarratt <garratt.jeff@gmail.com>

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

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

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

Change-Id: Ia99432c76f75f4f6dde953209631af9a5f459bd2
Signed-off-by: jyellick <jyellick@us.ibm.com>

Change-Id: I1bf2c44e5dc77a13b4749ea82c1df7fed618fd2f
Signed-off-by: jyellick <jyellick@us.ibm.com>

Change-Id: Ie4efc31a2f1b61a59353ebcaec7382a5b13d3862
Signed-off-by: jyellick <jyellick@us.ibm.com>

Updated to latest ab.proto

Change-Id: I53ff31f22052cff6ca75892bbaf61e3983ac2079
Signed-off-by: jeffgarratt <garratt.jeff@gmail.com>

Change-Id: I220d3c5a184da7d87118a14cc2c6b55e0bf79914
Signed-off-by: jeffgarratt <garratt.jeff@gmail.com>

This change includes a new fabric.proto file that defines
messages between the SDK, endorsers, ordering service, and
committers. These messages are required by the next architecture.
The messages have been derived from the Hyperledger Protocol
Working Group and many others working on the next architecture.
This API is not the final form, but a proposed start that
can be used and evolved as the new components are built.

Appended "2" to those structs that are common with fabric.proto.
This allows us fabric-next to co-exist with fabric and helps
keep track of structures that would need to be renamed as
integration progresses.

Also introduced a ID field in Proposal to help make transition
from current "Transaction" processing code in the fabric smoother
(such as in chaincode execution paths which relies on a txid to
keep track of transactions currently being processed).

Added fabric-next_test.go to test for exact match for fields
Change-Id: I42130175d6a81dc5de3d92c6adba7de0d3266bed
Signed-off-by: Srinivasan Muralidharan <muralisr@us.ibm.com>

Fixes Github issue #2222 (from pre gerrit/jira days).  Forward
ported at the request of @cbf.

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