Made the following changes to fsblkstorage provider:

* Block numbers start at 0, not 1.

* Blockchain height should be last block number + 1.

* A block's Block.Header.Number should be equal to
  the Blockchain height when AddBlock() is called.

* Updated ledger tests to use random temporary dir.

* Update core endorser tests to generate valid block
  numbers.

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

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



In fixing the orderer docker startup, the orderer.yaml file was modified
to include the LocalMSPDir.  This was required because without the
variable in the yaml, the environment variable would not take effect.
However, this orderer.yaml variable was incorrectly set to ../msp when
it was being set as a default in code to ../msp/sampleconfig.  This CR
fixes that.

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

1. Remove confusing comment on `NewChainCreationTemplate`.
2. Add comments to exported variables.
3. Extend test so that it checks policy name

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

The visibility field in the headers is used to control to what extent the
proposal payload will be visibile in the final tx. The default should be full
visibility.

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

Integrate gossip/gossip/algo/pull with peer/core.yaml, so it's wait
time become configurable.

Change-Id: I1661a959b4b771af9c22cb28e1d43c180e98c807
Signed-off-by: Ray Chen <ray@hyperchain.cn>

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



At the organization level, handlers were being instaniated dynamically,
but, the handlers were only being instructed to begin transactions
statically.  This caused a crash when a dynamically created org handler
would be told to process a config item before begin the config
transaction.

This CR reworks the handler instantiation to be done at the beginning of
a transaction.

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

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



Policy handling is done different from config value handling.  This CR
addresses TODOs in the code to migrate Policies management onto its own
Handler type.

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

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



The FAB-1880 change series picked the name "SAMPLE" when instantiating
the sample MSP config when an ID was added to the GetLocalMspFromDir
function.  This apparently as a side effect breaks other parts fo the
system, so this CR sets this ID back to "DEFAULT" as other pieces of the
system expect.

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

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



The anchor peers are per application organization, so should be stored
at the app org level.

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

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



In order to support organization scoped config (ie AnchorPeers), it's
necessary to introduce the notion of organization config.

This CR only introduces the notion of the organization handler.

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

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



In order to support auditability on who submitted a config update
transaction, the full submitted envelope needs to be embedded into the
configuration, not just the config envelope.  This CR modifies the
configtx proto to accommodate this.

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

We have a defunct configuration key to specify the chaincode
install path, but it is not used.  We also specify a chaincode
specific binary name, which is not really necessary.  Therefore
we remove the defunct config item and implement a generic
binary name to clean this up.

Part of the fix for FAB-2122.

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

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



As a transitional mechanism, the config currently depends on the
WriteSet containing the entire configuration. Instead, the config as
written in the config envelope needs to be utilized.

This CR makes the configtx.Manager utilize the config envelope at
instantiation time, but the orderer multichannel support still needs to
be updated to generate the config envelope based on a WriteSet for
instantiation.

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

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



Moving the configuration around caused the orderer docker image to no
longer resolve the MSP configuration directory.  This CR explicitly sets
the MSPDir and ID, and adds them to the config file so that the env
variables are effective.

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

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



Change-Id: Ifb12f5c9f269bd2bed5ee74d9aa84dee16b4ed4a
Signed-off-by: grapebaba <281165273@qq.com>

We clean up some unecessary logic related to creating
chaincode binaries with a desired name.

This refactor lays the groundwork for FAB-2122 fixes
later in the series.

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

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



LCCC exposes the following "GET" api.
   * getid - gets the name given name (basically "exists")
   * getccdata - gets the record entry for the chaincode given name
   * getdepspec - gets the deployment spec for the chaincode given name

Of these only the later needs the chaincode to be available on the peer.
Other APIs should not look for the existence of the chaincode.

This is needed for TXs to be committed on peer even if the chaincode
is not available on it

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