广东手机网站制作公司,怎样做网络推广甄选广州豪升网络,个人 网站备案,高端网站建设方案!!!修改内容比较繁琐,预期未来提供模板修改
修改初始配置文件,初始添加3个组织
organizations文件夹
/cryptogen文件夹下创建文件crypto-config-org3.yaml,内容如下:
PeerOrgs:# ---------------------------------------------------------------------------# Org3# ----…!!!修改内容比较繁琐,预期未来提供模板修改
修改初始配置文件,初始添加3个组织
organizations文件夹
/cryptogen文件夹下创建文件crypto-config-org3.yaml,内容如下:
PeerOrgs:# ---------------------------------------------------------------------------# Org3# ---------------------------------------------------------------------------- Name: Org3Domain: org3.example.comEnableNodeOUs: trueTemplate:Count: 1SANS:- localhostUsers:Count: 1
在/fabric-ca/org3文件夹中创建fabric-ca-server-config.yaml,内容如下:
version: 1.2.0
port: 11054
debug: false
crlsizelimit: 512000
tls:enabled: truecertfile:keyfile:clientauth:type: noclientcertcertfiles:
ca:name: Org3CAkeyfile:certfile:chainfile:
crl:expiry: 24h
registry:maxenrollments: -1identities:- name: adminpass: adminpwtype: clientaffiliation: attrs:hf.Registrar.Roles: *hf.Registrar.DelegateRoles: *hf.Revoker: truehf.IntermediateCA: truehf.GenCRL: truehf.Registrar.Attributes: *hf.AffiliationMgr: true
db:type: sqlite3datasource: fabric-ca-server.dbtls:enabled: falsecertfiles:client:certfile:keyfile:
ldap:enabled: falseurl: ldap://adminDN:adminPasswordhost:port/basetls:certfiles:client:certfile:keyfile:attribute:names: [uid,member]converters:- name:value:maps:groups:- name:value:
affiliations:org1:- department1- department2org2:- department1
signing:default:usage:- digital signatureexpiry: 8760hprofiles:ca:usage:- cert sign- crl signexpiry: 43800hcaconstraint:isca: truemaxpathlen: 0tls:usage:- signing- key encipherment- server auth- client auth- key agreementexpiry: 8760h
csr:cn: ca.org3.example.comnames:- C: USST: North CarolinaL: RaleighO: org3.example.comOU:hosts:- localhost- org3.example.comca:expiry: 131400hpathlength: 1
bccsp:default: SWsw:hash: SHA2security: 256filekeystore:keystore: msp/keystore
cacount:
cafiles:
intermediate:parentserver:url:caname:enrollment:hosts:profile:label:tls:certfiles:client:certfile:keyfile:修改/fabric-ca中的registerEnroll.sh,添加如下内容:
function createOrg3() {infoln Enrolling the CA adminmkdir -p organizations/peerOrganizations/org3.example.com/export FABRIC_CA_CLIENT_HOME${PWD}/organizations/peerOrganizations/org3.example.com/set -xfabric-ca-client enroll -u https://admin:adminpwlocalhost:11054 --caname ca-org3 --tls.certfiles ${PWD}/organizations/fabric-ca/org3/ca-cert.pem{ set x; } 2/dev/nullecho NodeOUs:Enable: trueClientOUIdentifier:Certificate: cacerts/localhost-11054-ca-org3.pemOrganizationalUnitIdentifier: clientPeerOUIdentifier:Certificate: cacerts/localhost-11054-ca-org3.pemOrganizationalUnitIdentifier: peerAdminOUIdentifier:Certificate: cacerts/localhost-11054-ca-org3.pemOrganizationalUnitIdentifier: adminOrdererOUIdentifier:Certificate: cacerts/localhost-11054-ca-org3.pemOrganizationalUnitIdentifier: orderer ${PWD}/organizations/peerOrganizations/org3.example.com/msp/config.yaml# Since the CA serves as both the organization CA and TLS CA, copy the orgs root cert that was generated by CA startup into the org level ca and tlsca directories# Copy org3s CA cert to org3s /msp/tlscacerts directory (for use in the channel MSP definition)mkdir -p ${PWD}/organizations/peerOrganizations/org3.example.com/msp/tlscacertscp ${PWD}/organizations/fabric-ca/org3/ca-cert.pem ${PWD}/organizations/peerOrganizations/org3.example.com/msp/tlscacerts/ca.crt# Copy org3s CA cert to org3s /tlsca directory (for use by clients)mkdir -p ${PWD}/organizations/peerOrganizations/org3.example.com/tlscacp ${PWD}/organizations/fabric-ca/org3/ca-cert.pem ${PWD}/organizations/peerOrganizations/org3.example.com/tlsca/tlsca.org3.example.com-cert.pem# Copy org3s CA cert to org3s /ca directory (for use by clients)mkdir -p ${PWD}/organizations/peerOrganizations/org3.example.com/cacp ${PWD}/organizations/fabric-ca/org3/ca-cert.pem ${PWD}/organizations/peerOrganizations/org3.example.com/ca/ca.org3.example.com-cert.peminfoln Registering peer0set -xfabric-ca-client register --caname ca-org3 --id.name peer0 --id.secret peer0pw --id.type peer --tls.certfiles ${PWD}/organizations/fabric-ca/org3/ca-cert.pem{ set x; } 2/dev/nullinfoln Registering userset -xfabric-ca-client register --caname ca-org3 --id.name user1 --id.secret user1pw --id.type client --tls.certfiles ${PWD}/organizations/fabric-ca/org3/ca-cert.pem{ set x; } 2/dev/nullinfoln Registering the org adminset -xfabric-ca-client register --caname ca-org3 --id.name org3admin --id.secret org3adminpw --id.type admin --tls.certfiles ${PWD}/organizations/fabric-ca/org3/ca-cert.pem{ set x; } 2/dev/nullinfoln Generating the peer0 mspset -xfabric-ca-client enroll -u https://peer0:peer0pwlocalhost:11054 --caname ca-org3 -M ${PWD}/organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/msp --tls.certfiles ${PWD}/organizations/fabric-ca/org3/ca-cert.pem{ set x; } 2/dev/nullcp ${PWD}/organizations/peerOrganizations/org3.example.com/msp/config.yaml ${PWD}/organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/msp/config.yamlinfoln Generating the peer0-tls certificates, use --csr.hosts to specify Subject Alternative Namesset -xfabric-ca-client enroll -u https://peer0:peer0pwlocalhost:11054 --caname ca-org3 -M ${PWD}/organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls --enrollment.profile tls --csr.hosts peer0.org3.example.com --csr.hosts localhost --tls.certfiles ${PWD}/organizations/fabric-ca/org3/ca-cert.pem{ set x; } 2/dev/null# Copy the tls CA cert, server cert, server keystore to well known file names in the peers tls directory that are referenced by peer startup configcp ${PWD}/organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/tlscacerts/* ${PWD}/organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/ca.crtcp ${PWD}/organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/signcerts/* ${PWD}/organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/server.crtcp ${PWD}/organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/keystore/* ${PWD}/organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/server.keyinfoln Generating the user mspset -xfabric-ca-client enroll -u https://user1:user1pwlocalhost:11054 --caname ca-org3 -M ${PWD}/organizations/peerOrganizations/org3.example.com/users/User1org3.example.com/msp --tls.certfiles ${PWD}/organizations/fabric-ca/org3/ca-cert.pem{ set x; } 2/dev/nullcp ${PWD}/organizations/peerOrganizations/org3.example.com/msp/config.yaml ${PWD}/organizations/peerOrganizations/org3.example.com/users/User1org3.example.com/msp/config.yamlinfoln Generating the org admin mspset -xfabric-ca-client enroll -u https://org3admin:org3adminpwlocalhost:11054 --caname ca-org3 -M ${PWD}/organizations/peerOrganizations/org3.example.com/users/Adminorg3.example.com/msp --tls.certfiles ${PWD}/organizations/fabric-ca/org3/ca-cert.pem{ set x; } 2/dev/nullcp ${PWD}/organizations/peerOrganizations/org3.example.com/msp/config.yaml ${PWD}/organizations/peerOrganizations/org3.example.com/users/Adminorg3.example.com/msp/config.yaml
}ccp-generate.sh中添加如下代码
ORG3
P0PORT11051
CAPORT11054
PEERPEMorganizations/peerOrganizations/org3.example.com/tlsca/tlsca.org3.example.com-cert.pem
CAPEMorganizations/peerOrganizations/org3.example.com/ca/ca.org3.example.com-cert.pemecho $(json_ccp $ORG $P0PORT $CAPORT $PEERPEM $CAPEM) organizations/peerOrganizations/org3.example.com/connection-org3.json
echo $(yaml_ccp $ORG $P0PORT $CAPORT $PEERPEM $CAPEM) organizations/peerOrganizations/org3.example.com/connection-org3.yamltest-network文件夹
在setOrgEnv.sh中添加如下内容
elif [[ ${ORG,,} org3 ]]; thenCORE_PEER_LOCALMSPIDOrg3MSPCORE_PEER_MSPCONFIGPATH${DIR}/test-network/organizations/peerOrganizations/org3.example.com/users/Adminorg3.example.com/mspCORE_PEER_ADDRESSlocalhost:11051CORE_PEER_TLS_ROOTCERT_FILE${DIR}/test-network/organizations/peerOrganizations/org3.example.com/tlsca/tlsca.org3.example.com-cert.pem
compose文件夹
compose-ca.yaml添加如下内容:
ca_org3:image: hyperledger/fabric-ca:latestlabels:service: hyperledger-fabricenvironment:- FABRIC_CA_HOME/etc/hyperledger/fabric-ca-server- FABRIC_CA_SERVER_CA_NAMEca-org3- FABRIC_CA_SERVER_TLS_ENABLEDtrue- FABRIC_CA_SERVER_PORT11054- FABRIC_CA_SERVER_OPERATIONS_LISTENADDRESS0.0.0.0:19054ports:- 11054:11054- 19054:19054command: sh -c fabric-ca-server start -b admin:adminpw -dvolumes:- ../organizations/fabric-ca/org3:/etc/hyperledger/fabric-ca-servercontainer_name: ca_org3networks:- testcompose-couch.yaml添加如下内容
couchdb2:container_name: couchdb2image: couchdb:3.2.2labels:service: hyperledger-fabric# Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password# for CouchDB. This will prevent CouchDB from operating in an Admin Party mode.environment:- COUCHDB_USERadmin- COUCHDB_PASSWORDadminpw# Comment/Uncomment the port mapping if you want to hide/expose the CouchDB service,# for example map it to utilize Fauxton User Interface in dev environments.ports:- 9984:5984networks:- testpeer0.org3.example.com:environment:- CORE_LEDGER_STATE_STATEDATABASECouchDB- CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESScouchdb4:5984# The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD# provide the credentials for ledger to connect to CouchDB. The username and password must# match the username and password set for the associated CouchDB.- CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAMEadmin- CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORDadminpwdepends_on:- couchdb2compose-test-net.yaml修改以及添加如下内容
volumes:orderer.example.com:peer0.org1.example.com:peer0.org2.example.com:peer0.org3.example.com:peer0.org3.example.com:container_name: peer0.org3.example.comimage: hyperledger/fabric-peer:latestlabels:service: hyperledger-fabricenvironment:- FABRIC_CFG_PATH/etc/hyperledger/peercfg- FABRIC_LOGGING_SPECINFO#- FABRIC_LOGGING_SPECDEBUG- CORE_PEER_TLS_ENABLEDtrue- CORE_PEER_PROFILE_ENABLEDfalse- CORE_PEER_TLS_CERT_FILE/etc/hyperledger/fabric/tls/server.crt- CORE_PEER_TLS_KEY_FILE/etc/hyperledger/fabric/tls/server.key- CORE_PEER_TLS_ROOTCERT_FILE/etc/hyperledger/fabric/tls/ca.crt# Peer specific variables- CORE_PEER_IDpeer0.org3.example.com- CORE_PEER_ADDRESSpeer0.org3.example.com:11051- CORE_PEER_LISTENADDRESS0.0.0.0:11051- CORE_PEER_CHAINCODEADDRESSpeer0.org3.example.com:11052- CORE_PEER_CHAINCODELISTENADDRESS0.0.0.0:11052- CORE_PEER_GOSSIP_EXTERNALENDPOINTpeer0.org3.example.com:11051- CORE_PEER_GOSSIP_BOOTSTRAPpeer0.org3.example.com:11051- CORE_PEER_LOCALMSPIDOrg3MSP- CORE_PEER_MSPCONFIGPATH/etc/hyperledger/fabric/msp - CORE_OPERATIONS_LISTENADDRESSpeer0.org3.example.com:9446- CORE_METRICS_PROVIDERprometheus- CHAINCODE_AS_A_SERVICE_BUILDER_CONFIG{peername:peer0org3}- CORE_CHAINCODE_EXECUTETIMEOUT300svolumes:- ../organizations/peerOrganizations/org3.example.com/peers/peer0.org3.example.com:/etc/hyperledger/fabric - peer0.org3.example.com:/var/hyperledger/productionworking_dir: /rootcommand: peer node startports:- 11051:11051- 9446:9446networks:- test测试
启动测试网络
sudo ./network.sh up创建通道
sudo ./network.sh createChannel安装链码
sudo chmod -R 777 ../test-network
./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-go -ccl go之后按照我这篇博客:小白也能读懂的Fabric测试网络运行以及链码部署进行测试. 可以看到完整结果如下:
链码部署文件修改
/script 中的deployCC.sh修改的地方比较零散,用下面的内容进行覆盖:
#!/bin/bashsource scripts/utils.shCHANNEL_NAME${1:-mychannel}
CC_NAME${2}
CC_SRC_PATH${3}
CC_SRC_LANGUAGE${4}
CC_VERSION${5:-1.0}
CC_SEQUENCE${6:-1}
CC_INIT_FCN${7:-NA}
CC_END_POLICY${8:-NA}
CC_COLL_CONFIG${9:-NA}
DELAY${10:-3}
MAX_RETRY${11:-5}
VERBOSE${12:-false}println executing with the following
println - CHANNEL_NAME: ${C_GREEN}${CHANNEL_NAME}${C_RESET}
println - CC_NAME: ${C_GREEN}${CC_NAME}${C_RESET}
println - CC_SRC_PATH: ${C_GREEN}${CC_SRC_PATH}${C_RESET}
println - CC_SRC_LANGUAGE: ${C_GREEN}${CC_SRC_LANGUAGE}${C_RESET}
println - CC_VERSION: ${C_GREEN}${CC_VERSION}${C_RESET}
println - CC_SEQUENCE: ${C_GREEN}${CC_SEQUENCE}${C_RESET}
println - CC_END_POLICY: ${C_GREEN}${CC_END_POLICY}${C_RESET}
println - CC_COLL_CONFIG: ${C_GREEN}${CC_COLL_CONFIG}${C_RESET}
println - CC_INIT_FCN: ${C_GREEN}${CC_INIT_FCN}${C_RESET}
println - DELAY: ${C_GREEN}${DELAY}${C_RESET}
println - MAX_RETRY: ${C_GREEN}${MAX_RETRY}${C_RESET}
println - VERBOSE: ${C_GREEN}${VERBOSE}${C_RESET}FABRIC_CFG_PATH$PWD/../config/#User has not provided a name
if [ -z $CC_NAME ] || [ $CC_NAME NA ]; thenfatalln No chaincode name was provided. Valid call example: ./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-go -ccl go# User has not provided a path
elif [ -z $CC_SRC_PATH ] || [ $CC_SRC_PATH NA ]; thenfatalln No chaincode path was provided. Valid call example: ./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-go -ccl go# User has not provided a language
elif [ -z $CC_SRC_LANGUAGE ] || [ $CC_SRC_LANGUAGE NA ]; thenfatalln No chaincode language was provided. Valid call example: ./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-go -ccl go## Make sure that the path to the chaincode exists
elif [ ! -d $CC_SRC_PATH ] [ ! -f $CC_SRC_PATH ]; thenfatalln Path to chaincode does not exist. Please provide different path.
fiCC_SRC_LANGUAGE$(echo $CC_SRC_LANGUAGE | tr [:upper:] [:lower:])# do some language specific preparation to the chaincode before packaging
if [ $CC_SRC_LANGUAGE go ]; thenCC_RUNTIME_LANGUAGEgolanginfoln Vendoring Go dependencies at $CC_SRC_PATHpushd $CC_SRC_PATHGO111MODULEon go mod vendorpopdsuccessln Finished vendoring Go dependencieselif [ $CC_SRC_LANGUAGE java ]; thenCC_RUNTIME_LANGUAGEjavarm -rf $CC_SRC_PATH/build/install/infoln Compiling Java code...pushd $CC_SRC_PATH./gradlew installDistpopdsuccessln Finished compiling Java codeCC_SRC_PATH$CC_SRC_PATH/build/install/$CC_NAMEelif [ $CC_SRC_LANGUAGE javascript ]; thenCC_RUNTIME_LANGUAGEnodeelif [ $CC_SRC_LANGUAGE typescript ]; thenCC_RUNTIME_LANGUAGEnodeinfoln Compiling TypeScript code into JavaScript...pushd $CC_SRC_PATHnpm installnpm run buildpopdsuccessln Finished compiling TypeScript code into JavaScriptelsefatalln The chaincode language ${CC_SRC_LANGUAGE} is not supported by this script. Supported chaincode languages are: go, java, javascript, and typescriptexit 1
fiINIT_REQUIRED--init-required
# check if the init fcn should be called
if [ $CC_INIT_FCN NA ]; thenINIT_REQUIRED
fiif [ $CC_END_POLICY NA ]; thenCC_END_POLICY
elseCC_END_POLICY--signature-policy $CC_END_POLICY
fiif [ $CC_COLL_CONFIG NA ]; thenCC_COLL_CONFIG
elseCC_COLL_CONFIG--collections-config $CC_COLL_CONFIG
fi# import utils
. scripts/envVar.sh
. scripts/ccutils.shpackageChaincode() {set -xpeer lifecycle chaincode package ${CC_NAME}.tar.gz --path ${CC_SRC_PATH} --lang ${CC_RUNTIME_LANGUAGE} --label ${CC_NAME}_${CC_VERSION} log.txtres$?PACKAGE_ID$(peer lifecycle chaincode calculatepackageid ${CC_NAME}.tar.gz){ set x; } 2/dev/nullcat log.txtverifyResult $res Chaincode packaging has failedsuccessln Chaincode is packaged
}function checkPrereqs() {jq --version /dev/null 21if [[ $? -ne 0 ]]; thenerrorln jq command not found...errorlnerrorln Follow the instructions in the Fabric docs to install the prereqserrorln https://hyperledger-fabric.readthedocs.io/en/latest/prereqs.htmlexit 1fi
}#check for prerequisites
checkPrereqs## package the chaincode
packageChaincode## Install chaincode on peer0.org1 and peer0.org2
infoln Installing chaincode on peer0.org1...
installChaincode 1
infoln Install chaincode on peer0.org2...
installChaincode 2
infoln Install chaincode on peer0.org3...
installChaincode 3## query whether the chaincode is installed
queryInstalled 1## approve the definition for org1
approveForMyOrg 1## check whether the chaincode definition is ready to be committed
## expect org1 to have approved and org2 not to
checkCommitReadiness 1 \Org1MSP\: true \Org2MSP\: false \Org3MSP\: false
checkCommitReadiness 2 \Org1MSP\: true \Org2MSP\: false \Org3MSP\: false
checkCommitReadiness 3 \Org1MSP\: true \Org2MSP\: false \Org3MSP\: false## now approve also for org2
approveForMyOrg 2## check whether the chaincode definition is ready to be committed
## expect them both to have approved
checkCommitReadiness 1 \Org1MSP\: true \Org2MSP\: true \Org3MSP\: false
checkCommitReadiness 2 \Org1MSP\: true \Org2MSP\: true \Org3MSP\: false
checkCommitReadiness 3 \Org1MSP\: true \Org2MSP\: true \Org3MSP\: false## now approve also for org2
approveForMyOrg 3checkCommitReadiness 3 \Org1MSP\: true \Org2MSP\: true \Org3MSP\: false## now that we know for sure both orgs have approved, commit the definition
commitChaincodeDefinition 1 2 3## query on both orgs to see that the definition committed successfully
queryCommitted 1
queryCommitted 2
queryCommitted 3## Invoke the chaincode - this does require that the chaincode have the initLedger
## method defined
if [ $CC_INIT_FCN NA ]; theninfoln Chaincode initialization is not required
elsechaincodeInvokeInit 1 2 3
fi
exit 0运行
修改上述文件之后再重新启动网络,查看输出结果,可以看到3个组织都同意了.
初始化4个节点,添加addorg5
根据之前的内容定义第四个组织
此处不在赘述
添加org5
之后的博客再写.
