Change-Id: I979b8ffbe69b87bf2e93613e4357ba8356f7f037
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

The "peer channel fetch" and "peer chaincode install" commands
currently log their success output message at the debug level.
This can make certain integration/e2e tests fail unexpectedly
if the log level is set to any other level.

It seems natural that the logged success message should be at
the info level.

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

The notion of tying an organization to a specific profile does not make
sense.  An organization may be part of many profiles.  In fact, a
profile is principally defined by which organizations are a part of it,
not the other way around.

There is already a 'world' scoped profile for orderer and for peer
channel.  This CR simply removes the organization scoped one which did
not appear to be doing anything.

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

This adds the test config structure.

Change-Id: Ibfe5d4655461cc4ab1d83017b759b63f5a38578c
Signed-off-by: Latitia M Haskins <latitia.haskins@gmail.com>
Signed-off-by: William Lahti <wtlahti@us.ibm.com>