Add a new ledger blockstorage index for History
that will map (blocknum,trannum) to the file storage
location for this block transaction

This index will be used for the API  GetTransactionsForKey()
for (chaincode1,key1).  It will do a key range query on chaincode1~key1
to pick up all chaincode1~key1 records.  Results will indicate
the set of (blocknum,trannum) transactions that updated this key.

Change-Id: I81da09e5526d7e2966634c78a03d34011d514442
Signed-off-by: Mari Wade <mariwade@us.ibm.com>

This is an initial check-in that will
1) create the history database in couchDB if it does not exist.
2) add the history commit to the LEDGER Commit if history is enabled
3) stores the history in the history database

The History functionality is not enabled unless both
couchDB and History are enabled in the config.

Note that tests will be added to validate the writes
and the actual data written to the database in future
changes.  The tests to validate history is not possible
until the query APIs are put in place in future changes.

Change-Id: Id207007ab5faae957c1e05234e441566a116ea33
Signed-off-by: Mari Wade <mariwade@us.ibm.com>

per pbft protocol, new-view messages for old views must not be processed.

It is not clear if there was a bug, but with this changeset the
implementation is more streamlined and slightly optimized.

Change-Id: Idbd9e9fdb883516dcf142ef7bdf56794313c8352
Signed-off-by: Marko Vukolic <mvu@zurich.ibm.com>

Despite the verification running and returning positive, the merge seems
to have created an import cycle, this changeset fixes that.

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

There was a XXX in the multichain manager to push the blockcutter
batchSize into the blockcutter via sharedconfig, rather than to pass it
at construction time.  This is necessary to be able to dynamically
change the value of the batch size after genesis.

This changeset also introduces a sharedconfig mock structure in the
orderer/mocks package as it will likely be more broadly useful to other
tests going forward.

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

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



This changeset introduces a sample client that sends a single envelope
via the broadcast RPC to the ordering service. This envelope contains a
configuration envelope that calls for the creation of a new chain.

The client is invoked as follows:

$ broadcast_config -cmd new-chain -chainID newChainID

As is the case with the bd_counter sample client, the user can also set
the logging level (-loglevel) and the address of the RPC server
(-server).  The user may also set the backing creation policy
(-creationPolicy).

This changeset also adds chainID support for the deliver_stdout and the
broadcast_timestamp sample clients.

Change-Id: I782eb77c45f5c8d91c75c4440e47a20ab76a560e
Signed-off-by: Kostas Christidis <kostas@christidis.io>
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

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



There are components in the orderer/common directory which are of more
general use outside of the orderer, such as the cauthdsl, configtx, and
policies components.

Because there are likely other useful common components, such as the
impending gRPC server, logging, and msp/bccsp work, this changeset
creates a fabric/common directory and moves the above listed components
from the orderer to this directory.

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

This changeset introduces the runtime  chain creation logic into the
orderer.  It's presently only exercised via unit tests, pending the
creation of bdd and sample clients to exercise this behavior.

The chain creation checking is still somewhat limited, and does not
enforce the sorts of keys which can be created, or do real policy
evaluation at this point, but the plug points are there.

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

This changeset adds an orderer configuration item with key
ChainCreators.  This configuration item should only be set for the
system chain, and will allow the specification of chain creation
policies for an orderer.

This changeset simply introduces the new configuration item but does not
utilize it in any way (so as to simplify the diff).  An additional
changeset follows which utilizes this new config.

This is the server side half of the FAB-814 item but does not complete
it.

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

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

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



List of parameters to many of the chaincode APIs is growing
   . chaincode name
   . chain ID
   . version (needed for upgrade)
   . Proposal
   . txid

Before getting into the meat of upgrade, simplify the APIs
using a CCContext structure. In addition to cleaning and
simplifying APIs, this will make the upgrade CR easier to
follow

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

In order to prevent payloads buffer tests fail intermitently
added syncronization to make sure assertion won't happen before
message appears in the channel.

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

Added implementations for the following:

    QueryExecutor.GetStateRangeScanIterator()
    QueryExecutor.GetStateMultipleKeys()
    TxSimulator.DeleteState()
    TxSimulator.SetStateMultipleKeys()

Unit testing was extended for the range query in couchdb.go

Additional unit testing for simulation functions will be added
following a refactoring of unit tests for goleveldb.

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

After receiveing a hello message, a replica would not cleanup its sbft
state (checkpointDone and timer cancellation). This would leave a replica
hanging not able to process new requests.

Added a test (TestHelloMsg) to demonstrate this. This required also
enabling sbft TestSystem configuration with disabled Timer interface.

Change-Id: I4f8dc7e57c656a09ad536b229c9709213c5eb6af
Signed-off-by: Marko Vukolic <mvu@zurich.ibm.com>

Update test case to only test for presence of part of the stack trace.

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

Add gossip service entity to encapsulate gossip + state instance.
Make service instance a singelton and add JoinChannel method so
cscc will be able to leverage it.

Change-Id: I38233781276d538f861e472a427a1df12887c887
Signed-off-by: Artem Barger <bartem@il.ibm.com>
Signed-off-by: Yacov Manevich <yacovm@il.ibm.com>

The constant "fabric" is not used in new release.

Change-Id: Ie37ba66f067518fda0652dbe56fa9f746511378c
Signed-off-by: Baohua Yang <baohyang@cn.ibm.com>

This commit supports FAB-1020 work later. It provides some utilities
on block manipulation and a test configuration block to be used in
testing new chains.

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

Change-Id: Ie3576e05f53600ee234125b85ba0d69e0dbe128f
Signed-off-by: Akash Sethi <akash.sethi@knoldus.in>

This change-set presents a better organisation of the MSP package: code that
belongs to msp proper is in fabric/msp, whereas core that instantiates and
manages msps for the peer was moved in fabric/core/peer (a new package was
created to avoid import cycles). Furthermore, configuration of the local
MSP no longer requires a specific json file: it is sufficient to place
certificates and keys in a directory with the appropriate structure (sample in
msp/sampleconfig).

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