2. 程式人生 > >fabric v1.1 自動化部署指令碼

fabric v1.1 自動化部署指令碼

阿新 • • 發佈：2018-12-29

自動部署如下結構：

IP 節點 域名
10.254.186.164 orderer orderer.example.com
10.254.186.164 peer peer0.org1.example.com
10.254.247.165 peer peer1.org1.example.com
10.254.207.154 peer
peer0.org2.example.com

前置環境：

  • go v1.9+
  • fabric v1.1的bin檔案已經放到$PATH
  • 寫好的chaincode
  • docker
  • /etc/hosts 已經配置好上面的域名對映
  • 機器間開通免密登入

啟動環境：

清空環境：

相關檔案：

deploy.sh

path=`pwd`
mychannel=$1

if [ $# -ne 1 ]; then
        echo
 
 "請新增channelID"
        echo $mychannel
	exit
else
        echo "start deploying"
fi

#建立資料夾
if [ ! -d ~/peer  ];then
  mkdir ~/peer
else
  echo dir exist
fi

if [ ! -d ~/orderer  ];then
  mkdir ~/orderer
else
  echo dir exist
fi

echo "##########################################################"
echo "##### Generate certificates using cryptogen tool #########"
 

echo "##########################################################"

cryptogen generate --config=crypto-config.yaml --output ./certs
mkdir orderer.example.com
cp -rf certs/ordererOrganizations/example.com/orderers/orderer.example.com/* orderer.example.com/
cp orderer.yaml orderer.example.com
cp orderer_start.sh orderer.example.com/start.sh
mkdir orderer.example.com/data

mkdir peer0.org1.example.com
cp -rf certs/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/* peer0.org1.example.com/
cp core.yaml peer0.org1.example.com
mkdir peer0.org1.example.com/data
cp -rf peer0.org1.example.com/ peer1.org1.example.com/
rm -rf peer1.org1.example.com/msp/
rm -rf peer1.org1.example.com/tls/
cp -rf certs/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/* peer1.org1.example.com/
sed -i "s/peer0.org1.example.com/peer1.org1.example.com/g" peer1.org1.example.com/core.yaml
cp -rf peer0.org1.example.com/ peer0.org2.example.com/
rm -rf peer0.org2.example.com/msp/
rm -rf peer0.org2.example.com/tls/
cp -rf certs/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/*  peer0.org2.example.com/
sed -i "s/peer0.org1.example.com/peer0.org2.example.com/g" peer0.org2.example.com/core.yaml
sed -i "s/Org1MSP/Org2MSP/g" peer0.org2.example.com/core.yaml

#傳輸peer/orderer
cp peer_start.sh peer0.org1.example.com/start.sh
cp peer_start.sh peer1.org1.example.com/start.sh
cp peer_start.sh peer0.org2.example.com/start.sh

echo "##########################################################"
echo "#########  Generating Orderer Genesis block ##############"
echo "##########################################################"

#生成創世區塊
configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./genesisblock
cp genesisblock ~/orderer

#遠端部署peer
cd $path
ssh [email protected] "mkdir -p ~/peer; rm -rf ~/peer/*"
ssh [email protected] "mkdir -p  ~/peer; rm -rf ~/peer/*"
scp -r orderer.example.com/* ~/orderer/
scp -r peer0.org1.example.com/* ~/peer/
scp -r peer1.org1.example.com/* 10.254.247.165:~/peer/
scp -r peer0.org2.example.com/* 10.254.207.154:~/peer/

echo "##########################################################"
echo "############  start orderer && peers  ####################"
echo "##########################################################"
#啟動本地的peer/orderer
cd ~/orderer
echo "strating orderer ..."
sh start.sh
if [ $? != 0 ]; then
    echo "orderer start  fail"
	exit 1
else
	echo "orderer start success"
fi

cd ~/peer
echo "starting peer ..."
sh start.sh
if [ $? != 0 ]; then
    echo "peer start  fail"
        exit 1
else
        echo "peer start success"
fi

#啟動遠端peer
ssh [email protected] "cd ~/peer; sh start.sh > /dev/null 2>&1 &"
ssh [email protected] "cd ~/peer; sh start.sh > /dev/null 2>&1 &"

echo "##########################################################"
echo "#########  Create Adimn && Users in each ORG #############"
echo "##########################################################"
#建立使用者
#org1 Admin(peer0)
cd $path
mkdir Admin_1
cp -rf certs/peerOrganizations/org1.example.com/users/[email protected]/* Admin_1/
cp peer0.org1.example.com/core.yaml  Admin_1/
cp peer.sh Admin_1/

cd Admin_1
echo `./peer.sh node status`

#org1 user1 (peer1)
cd $path
cp -rf  Admin_1/ User_1/
rm -rf  User_1/msp
rm -rf  User_1/tls
cp -rf  certs/peerOrganizations/org1.example.com/users/[email protected]/* User_1/
sed -i "s/peer0.org1.example/peer1.org1.example/g" User_1/peer.sh

#org2 Admin
cp -rf  Admin_1/ Admin_2/
rm -rf  Admin_2/msp/
rm -rf  Admin_2/tls/
cp -rf certs/peerOrganizations/org2.example.com/users/[email protected]/* Admin_2/
sed -i "s/peer0.org1.example/peer0.org2.example/g" Admin_2/peer.sh
sed -i "s/Org1MSP/Org2MSP/g" Admin_2/peer.sh
sed -i "s/peer0.org1.example.com/peer0\.org2\.example.com/g" Admin_2/core.yaml
sed -i "s/Org1MSP/Org2MSP/g" Admin_2/core.yaml

#複製根證書
#把使用org1的另一個身份控制peer1.org1.example.com
cp -rf Admin_1/ Admin_1_2/
sed -i "s/peer0.org1.example/peer1.org1.example/g" Admin_1_2/peer.sh
cp certs/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem  Admin_1/
cp certs/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem  User_1/
cp certs/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem  Admin_2/
cp certs/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem  Admin_1_2/

echo "##########################################################"
echo "#########  Create Channel && Anchor Peer #################"
echo "##########################################################"
#建立channel
configtxgen -profile TwoOrgsChannel -outputCreateChannelTx $mychannel.tx -channelID $mychannel
configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate Org1MSPanchors.tx -channelID $mychannel -asOrg Org1MSP
configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate Org2MSPanchors.tx -channelID $mychannel -asOrg Org2MSP

cd  Admin_1
./peer.sh channel create -o orderer.example.com:7050 -c $mychannel -f ../$mychannel.tx --tls true --cafile tlsca.example.com-cert.pem
cp $mychannel.block ../Admin_2
cp $mychannel.block ../User_1
cp $mychannel.block ../Admin_1_2


#peer加入channel
./peer.sh channel join -b $mychannel.block

if [ $? != 0 ]; then
    echo "peer0.org1.example join $mychannel fail"
        exit 1
else
        echo "------peer0.org1.example join $mychannel success !!!"
fi

cd ../Admin_1_2/
./peer.sh channel join -b $mychannel.block
if [ $? != 0 ]; then
    echo "peer1.org1.example join $mychannel fail"
        exit 1
else
        echo "------peer1.org1.example join $mychannel success !!!"
fi

cd ../Admin_2/
./peer.sh channel join -b $mychannel.block
if [ $? != 0 ]; then
    echo "peer0.org2.example join $mychannel fail"
        exit 1
else
        echo "------peer0.org2.example join $mychannel success !!!"
fi

cd ../Admin_1/
./peer.sh channel update -o orderer.example.com:7050 -c $mychannel -f ../Org1MSPanchors.tx --tls true --cafile ./tlsca.example.com-cert.pem

cd ../Admin_2/
./peer.sh channel update -o orderer.example.com:7050 -c $mychannel -f ../Org2MSPanchors.tx --tls true --cafile ./tlsca.example.com-cert.pem

echo "##########################################################"
echo "#################### ChainCode install ###################"
echo "##########################################################"
#安裝合約
go get github.com/introclass/hyperledger-fabric-chaincodes/demo
cd $path
cd Admin_1
./peer.sh chaincode package demo-pack.out -n demo -v 0.0.1 -s -S -p github.com/introclass/hyperledger-fabric-chaincodes/demo
./peer.sh chaincode signpackage demo-pack.out signed-demo-pack.out
cp signed-demo-pack.out ../Admin_1_2/
cp signed-demo-pack.out ../Admin_2/
./peer.sh chaincode install ./signed-demo-pack.out

if [ $? != 0 ]; then
    echo "peer0.org1.example.com install $mychannel fail"
        exit 1
else
        echo "------peer0.org1.example.com $mychannel success !!!"
fi


cd ../Admin_1_2
./peer.sh chaincode install ./signed-demo-pack.out
if [ $? != 0 ]; then
    echo "peer1.org1.example.com install $mychannel fail"
        exit 1
else
        echo "------peer1.org1.example.com $mychannel success !!!"
fi

cd ../Admin_2
./peer.sh chaincode install ./signed-demo-pack.out
if [ $? != 0 ]; then
    echo "peer0.org2.example.com install $mychannel fail"
        exit 1
else
        echo "------peer0.org2.example.com $mychannel success !!!"
fi





echo "##########################################################"
echo "#################### ChainCode invoke  ###################"
echo "##########################################################"
cd ../Admin_1
echo "Admin_1 instantiate"
./peer.sh chaincode instantiate -o orderer.example.com:7050 --tls true --cafile ./tlsca.example.com-cert.pem -C $mychannel -n demo -v 0.0.1 -c '{"Args":["init"]}' -P "OR('Org1MSP.member','Org2MSP.member')"
sleep 10
echo "Admin_1 invoke"
./peer.sh chaincode invoke -o orderer.example.com:7050  --tls true --cafile ./tlsca.example.com-cert.pem -C $mychannel -n demo -c '{"Args":["write","key1","key1valueisabc"]}'
sleep 2
cd ../Admin_2
echo "Admin_2 query"
./peer.sh chaincode query -C $mychannel -n demo -c '{"Args":["query","key1"]}'
sleep 2
cd ../User_1
echo "User_1 query"
./peer.sh chaincode query -C $mychannel -n demo -c '{"Args":["query","key1"]}'



echo "deploy finished !!!"

clear.sh

killall -9 orderer
killall -9 peer
rm -rf ~/peer
rm -rf ~/orderer
rm -rf Admin\@org1.example.com/
rm -rf certs/
rm -rf genesisblock
rm -rf orderer.example.com/
rm -rf peer0.org*
rm -rf peer1.org1.example.com/
rm -rf Admin_1
rm -rf Admin_2
rm -rf User_1
rm -rf Admin_1_2
rm -rf *.tx
ssh [email protected] "killall -9 peer;rm -rf ~/peer/*"
ssh [email protected] "killall -9 peer;rm -rf ~/peer/*"

peer.sh

#!/bin/bash
export FABRIC_CFG_PATH=`pwd`

export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_TLS_CERT_FILE=./tls/client.crt
export CORE_PEER_TLS_KEY_FILE=./tls/client.key

export CORE_PEER_MSPCONFIGPATH=./msp
export CORE_PEER_ADDRESS=peer0.org1.example.com:7051
export CORE_PEER_LOCALMSPID=Org1MSP
export CORE_PEER_TLS_ROOTCERT_FILE=./tls/ca.crt
export CORE_PEER_ID=cli
export CORE_LOGGING_LEVEL=INFO

peer $*

orderer_start.sh

nohup orderer start 2>&1 &

peer_start.sh

nohup peer node start 2>&1 &

cryptoconfig.yaml

OrdererOrgs:
  - Name: Orderer
    Domain: example.com
    Specs:
      - Hostname: orderer
PeerOrgs:
  - Name: Org1
    Domain: org1.example.com
    Template:
      Count: 2
    Users:
      Count: 1
  - Name: Org2
    Domain: org2.example.com
    Template:
      Count: 1
    Users:
      Count: 1

configtx.yaml

OrdererOrgs:
  - Name: Orderer
    Domain: example.com
    Specs:
      - Hostname: orderer
PeerOrgs:
  - Name: Org1
    Domain: org1.example.com
    Template:
      Count: 2
    Users:
      Count: 1
  - Name: Org2
    Domain: org2.example.com
    Template:
      Count: 1
    Users:
      Count: 1
bogon:fabric_deploy didi$ cat configtx.yaml
Profiles:
    TwoOrgsOrdererGenesis:
        Orderer:
            <<: *OrdererDefaults
            Organizations:
                - *OrdererOrg
        Consortiums:
            SampleConsortium:
                Organizations:
                    - *Org1
                    - *Org2
    TwoOrgsChannel:
        Consortium: SampleConsortium
        Application:
            <<: *ApplicationDefaults
            Organizations:
                - *Org1
                - *Org2
Organizations:
    - &OrdererOrg
        Name: OrdererOrg
        ID: OrdererMSP
        MSPDir: ./certs/ordererOrganizations/example.com/msp
    - &Org1
        Name: Org1MSP
        ID: Org1MSP
        MSPDir: ./certs/peerOrganizations/org1.example.com/msp
        AnchorPeers:
            - Host: peer0.org1.example.com
              Port: 7051
    - &Org2
        Name: Org2MSP
        ID: Org2MSP
        MSPDir: ./certs/peerOrganizations/org2.example.com/msp
        AnchorPeers:
            - Host: peer0.org2.example.com
              Port: 7051
Orderer: &OrdererDefaults
    OrdererType: solo
    Addresses:
        - orderer.example.com:7050
    BatchTimeout: 2s
    BatchSize:
        MaxMessageCount: 10
        AbsoluteMaxBytes: 99 MB
        PreferredMaxBytes: 512 KB
    Kafka:
        Brokers:
            - 127.0.0.1:9092
    Organizations:
Application: &ApplicationDefaults
    Organizations:

core.yaml

logging:
    peer:       warning
    cauthdsl:   warning
    gossip:     warning
    ledger:     info
    msp:        warning
    policies:   warning
    grpc:       error
    format: '%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}'
peer:
    id: peer0.org1.example.com
    networkId: dev
    listenAddress: 0.0.0.0:7051
    address: 0.0.0.0:7051
    addressAutoDetect: false
    gomaxprocs: -1
    gossip:
        bootstrap: 127.0.0.1:7051
        bootstrap: peer0.org1.example.com:7051
        useLeaderElection: true
        orgLeader: false
        endpoint:
        maxBlockCountToStore: 100
        maxPropagationBurstLatency: 10ms
        maxPropagationBurstSize: 10
        propagateIterations: 1
        propagatePeerNum: 3
        pullInterval: 4s
        pullPeerNum: 3
        requestStateInfoInterval: 4s
        publishStateInfoInterval: 4s
        stateInfoRetentionInterval:
        publishCertPeriod: 10s
        skipBlockVerification: false
        dialTimeout: 3s
        connTimeout: 2s
        recvBuffSize: 20
        sendBuffSize: 200
        digestWaitTime: 1s
        requestWaitTime: 1s
        responseWaitTime: 2s
        aliveTimeInterval: 5s
        aliveExpirationTimeout: 25s
        reconnectInterval: 25s
        externalEndpoint: peer0.org1.example.com:7051
        election:
            startupGracePeriod: 15s
            membershipSampleInterval: 1s
            leaderAliveThreshold: 10s
            leaderElectionDuration: 5s
    events:
        address: 0.0.0.0:7053
        buffersize: 100
        timeout: 10ms
    tls:
        enabled: true
        cert:
            file: ./tls/server.crt
        key:
            file: ./tls/server.key
        rootcert:
            file: ./tls/ca.crt
        serverhostoverride:
    fileSystemPath: ./data
    BCCSP:
        Default: SW
        SW:
            Hash: SHA2
            Security: 256
            FileKeyStore:
                KeyStore:
    mspConfigPath: msp
    localMspId: Org1MSP
    profile:
        enabled:    true
        listenAddress: 0.0.0.0:6060
vm:
    endpoint: unix:///var/run/docker.sock
    docker:
        tls:
            enabled: false
            ca:
                file: docker/ca.crt
            cert:
                file: docker/tls.crt
            key:
                file: docker/tls.key
        attachStdout: false
        hostConfig:
            NetworkMode: host
            Dns:
               # - 192.168.0.1
            LogConfig:
                Type: json-file
                Config:
                    max-size: "50m"
                    max-file: "5"
            Memory: 2147483648
chaincode:
    peerAddress:
    id:
        path:
        name:
    builder: $(DOCKER_NS)/fabric-ccenv:$(ARCH)-$(PROJECT_VERSION)
    golang:
        runtime: $(BASE_DOCKER_NS)/fabric-baseos:$(ARCH)-$(BASE_VERSION)
    car:
        runtime: $(BASE_DOCKER_NS)/fabric-baseos:$(ARCH)-$(BASE_VERSION)
    java:
        Dockerfile:  |
            from $(DOCKER_NS)/fabric-javaenv:$(ARCH)-$(PROJECT_VERSION)
    startuptimeout: 300s
    executetimeout: 30s
    mode: net
    keepalive: 0
    system:
        cscc: enable
        lscc: enable
        escc: enable
        vscc: enable
        qscc: enable
    logging:
      level:  info
      shim:   warning
      format: '%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}'
ledger:
  blockchain:
  state:
    stateDatabase: goleveldb
    couchDBConfig:
       couchDBAddress: 127.0.0.1:5984
       username:
       password:
       maxRetries: 3
       maxRetriesOnStartup: 10
       requestTimeout: 35s
       queryLimit: 10000
  history:
    enableHistoryDatabase: true
bogon:fabric_deploy didi$
bogon:fabric_deploy didi$
bogon:fabric_deploy didi$ cat core.yaml
logging:
    peer:       warning
    cauthdsl:   warning
    gossip:     warning
    ledger:     info
    msp:        warning
    policies:   warning
    grpc:       error
    format: '%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}'
peer:
    id: peer0.org1.example.com
    networkId: dev
    listenAddress: 0.0.0.0:7051
    address: 0.0.0.0:7051
    addressAutoDetect: false
    gomaxprocs: -1
    gossip:
        bootstrap: 127.0.0.1:7051
        bootstrap: peer0.org1.example.com:7051
        useLeaderElection: true
        orgLeader: false
        endpoint:
        maxBlockCountToStore: 100
        maxPropagationBurstLatency: 10ms
        maxPropagationBurstSize: 10
        propagateIterations: 1
        propagatePeerNum: 3
        pullInterval: 4s
        pullPeerNum: 3
        requestStateInfoInterval: 4s
        publishStateInfoInterval: 4s
        stateInfoRetentionInterval:
        publishCertPeriod: 10s
        skipBlockVerification: false
        dialTimeout: 3s
        connTimeout: 2s
        recvBuffSize: 20
        sendBuffSize: 200
        digestWaitTime: 1s
        requestWaitTime: 1s
        responseWaitTime: 2s
        aliveTimeInterval: 5s
        aliveExpirationTimeout: 25s
        reconnectInterval: 25s
        externalEndpoint: peer0.org1.example.com:7051
        election:
            startupGracePeriod: 15s
            membershipSampleInterval: 1s
            leaderAliveThreshold: 10s
            leaderElectionDuration: 5s
    events:
        address: 0.0.0.0:7053
        buffersize: 100
        timeout: 10ms
    tls:
        enabled: true
        cert:
            file: ./tls/server.crt
        key:
            file: ./tls/server.key
        rootcert:
            file: ./tls/ca.crt
        serverhostoverride:
    fileSystemPath: ./data
    BCCSP:
        Default: SW
        SW:
            Hash: SHA2
            Security: 256
            FileKeyStore:
                KeyStore:
    mspConfigPath: msp
    localMspId: Org1MSP
    profile:
        enabled:    true
        listenAddress: 0.0.0.0:6060
vm:
    endpoint: unix:///var/run/docker.sock
    docker:
        tls:
            enabled: false
             
 

            
  

           

              
              

            

            
相關推薦

			   
            
            
            
 

    


    
    
fabric v1.1 自動化部署指令碼

     
  
  
  
 自動部署如下結構： 
  
   
    
    IP 
    節點 
    域名 
    
   
   
    
    10.254.186.164 
    orderer 
    orderer.example.com 
    
    
    10.254.18 



  
 

    


    
    
Installing Hyperledger Fabric v1.1 on Ubuntu 16.04?—?Part I

     
 enter   eight   ecif   into   repos   terminal   rac   ould   imageload    

There is an entire library of Blockchain APIs which you can select according 



  
 

    


    
    
Hyperledger Fabric v1.1 單機多節點叢集環境搭建

     
  
 
  
  
 Fabric v1.1 
 1.環境安裝 
 1).安裝go 1.9.x  下載地址  http://golang.org/dl/ 
 配置環境 
  
  #go的安裝根目錄  export GOROOT=/usr/local/go  #go的工作路徑根目錄  export GOPAT 



  
 

    


    
    
Hyperledger Fabric-v1.1多節點叢集

     
  
 
  
  
 Fabric v1.1 
 1.環境安裝 
 1).安裝go 1.9.x  下載地址  http://golang.org/dl/ 
 配置環境 
  
  #go的安裝根目錄  export GOROOT=/usr/local/go  #go的工作路徑根目錄  export GOPAT 



  
 

    


    
    
fabric V1.1 網路及sdk nodejs搭建手冊

     
 
							
							
							0.許可權
獲取管理員許可權：
$ sudo passwd　#設定root密碼
$ su　#切換到root使用者
1.基礎工具準備
1.1.git
$ apt install git
1.2.curl
$ apt install curl
1.3.pip
$ a 



  
 

    


    
    
自動化部署指令碼(安裝jdk)

     
 
							
							
							1.先得保證每一臺機器都安裝了scp:

如果沒有安裝則進行安裝:
安裝scp:  scp是在安裝ssh的時候安裝的,是在ssh的客戶端軟體裡面的
yum list | grep ssh


安裝的是openssh-clients.x86_64
yum inst 



  
 

    


    
    
Hyperledger Fabric v1.1.0 + Ubuntu 16.04

     
 
							
							
							1、go安裝(v1.9)
①下載並解壓
wget https://storage.googleapis.com/golang/go1.9.linux-amd64.tar.gz
sudo tar -C /usr/local -xzf go1.9.linux-amd 



  
 

    


    
    
自動化部署指令碼詳解

     
 
								
								            
						
                
 當有多臺機器要做相同的部署工作時，為了避免重複勞作，就需要用到自動化部署。自動化部署——簡單來說就是批量的在目標機器上安裝程式。下面我們以安裝JDK來看一下自動化部署是怎麼執行的。
         



  
 

    


    
    
MySQL5.7多例項自動化部署指令碼

     
 一、安裝說明 
------------------------------------------------------ 
mysql5.7.10_onekey_install.sh自動化部署指令碼支援mysql5.7.10初始化安裝，多例項建立，且使用經過優化後的my.cnf配置檔案和mysql.ser 



  
 

    


    
    
nginx+tomcat負載均衡配置+python自動化部署指令碼

     
 
                
nginx+tomcat負載均衡配置
1、網路拓撲
    

2、nginx安裝配置
1.安裝nginx伺服器，實現OSI網路模型第七層（應用層）負載均衡及反向代理：      
安裝nginx 1.6.1 stable version，  stable version版 



  
 

    


    
    
003-Ambari一鍵自動化部署指令碼

     
 
                    微信搜尋公眾號：BearData，關注更多內容。

根據前兩篇 “Ambari大資料平臺搭建利器(一)&(二)”， 我們已經完成大資料平臺的搭建，但是我們發現安裝Ambari的步驟比較繁瑣。我們發現手動部署存在以下的劣勢：

每個節點都要執行重複的命令，我們前 



  
 

    


    
    
HyperLedger Fabric v1.1.0-alpha 版本原始碼編譯及單節點網路搭建

     
 
                本文主要參考：https://blog.csdn.net/honganboy/article/details/78714578 的介紹，十分感謝作者。但是安裝版本和環境不同，安裝過程也遇到了一些小問題，因此也再寫一篇供大家參考。安裝環境：作業系統-64位Centos7.2，F 



  
 

    


    
    
阿里雲容器服務區塊鏈解決方案全新升級 支援Hyperledger Fabric v1.1

     
 
                

作為全球開源區塊鏈領域影響最為廣泛的專案之一，超級賬本近日宣佈了Hyperledger Fabric v1.1的正式釋出。此次升級帶來了一系列豐富的新功能以及在安全性、效能與擴充套件性等諸多方面的顯著提升。更多詳情可參考下述資料：

與此同時，作為對開源區塊鏈生態的支援， 



  
 

    


    
    
Linux：自動化部署指令碼，給每一臺主機裝上JDK，且配好環境變數

     
 
                
centos6.7
當我們有很多臺主機，想在每臺機器上都安裝一樣的某些軟體，當然，一臺機器一臺機器安裝也是可以的，但是如果有一鍵安裝所有機器上的軟體那是不是很激動人心呢！
首先我們需要製作一臺伺服器，並把軟體包放在我們的伺服器上
首先進入 /var/www/html資料夾
 



  
 

    


    
    
Hadoop2.7.1 叢集部署及自動化指令碼

     
                      實驗環境作業系統：ubuntu 14.04 64位                    主機名IPnamenode10.107.12.10datanode110.107.12.20datanode210.107.12.50datanode310.107.12.60j 



  
 

    


    
    
Syncd v1.0.1 釋出，一款 Go 語言開發的自動化部署工具

     
  
    
 
syncd是一款開源的程式碼部署工具，它具有簡單、高效、易用等特點，可以提高團隊的工作效率。
專案地址(Github)   專案地址(Gitee)   下載地址 v1.0.1   使用文件
特性：

 Go語言開 



  
 

    


    
    
【fabric實戰指南二】Fabric v1.0 部署過程原理詳解

     
 fabric區塊鏈兄弟社區，區塊鏈技術專業問答先行者，中國區塊鏈技術愛好者聚集地作者：吳壽鶴來源：區塊鏈兄弟原文鏈接：http://www.blockchainbrother.com/article/18著權歸作者所有。商業轉載請聯系作者獲得授權，非商業轉載請註明出處。編譯fabric tools我們會編譯以 



  
 

    


    
    
SaltStack自動化部署Kubernetes v1.9.3版本----Dashboard

     
 docker   k8s   kubernetes   [root@linux-node1 coredns]# pwd/srv/addons/coredns
[root@linux-node1 srv]# cd addons/[root@linux-node1 addons]# lscoredns  dash 



  
 

    


    
    
Fabric實現自動化部署

     
 word   bsp   python   端口   yum   TE   prompt   .py   class   Fabric實現自動化部署
　　1. 安裝fabric 
　　　　yum install fabric -y
　　2. 編寫腳本來實現自動化部署
　　    註意:env.password 



  
 

    


    
    
docker-compose, docker registry2,Python 指令碼 自動化 部署 spring boot 進銷存系統

     
  
 
 準備環境 
 虛擬機器兩臺 
 centos 7.2 192.168.255.128 
 centos 7.2 192.168.255.129 
 maven 3.0.5 
 java 1.8.0_181 
 git version 1.8.3.1 
 Python 2.7.5 
 docker r