node0 #节点0的目录 ├── node1 #节点1的目录 ├── nodejs #nodejs相关安装目录 ├── node_manager.sh #节点管理脚本 ├── node.sh #nodejs相关环境变量 ├── register.sh #注册节点入网脚本, 扩容使用 ├── start 扩容时使用 ./register.sh IDX unregister.sh 将指定节点从节点管理合约中删除 ./unregister.sh IDX node_manager.sh 查看当前节点管理合约中的节点信息 ./node_manager.sh all [web3sdk使用说明链接] [https://github.com/FISCO-BCOS/web3sdk] [web3lib、syst 停止第IDX个节点 registerIDX.sh 扩容时使用, 将第IDX个节点注册入节点管理合约, 调用的是 docker中的node_manager.sh脚本, 扩容时使用 unregisterIDX.sh 将IDX个节点从节点管理合约删除, 调用的是 node_manager.sh脚本 启动 在docker目录执行start.sh脚本 注意:要先启动创世块节点所在的服务器上的节点!!! ./start

communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses

communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses

communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses

communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses

communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses

communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses

communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses

版本要求： NodeJS 8 (LTS), 9, 或 10 (LTS)，Caliper尚未在更高的NodeJS版本中进行 过验证。 安装指南： 建议使用nvm(Node Version Manager)安装，nvm的安装方式如下： # 安装nvm curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install $(basename $SHELL)rc # 安装Node.js 8 nvm install 8 # 使用Node.js 8 nvm use 8 # 添加源 sudo yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo # 更新缓存 sudo yum makecache 数据、节点的私钥。 具体的落盘加密介绍，可参考：落盘加密的介绍 第一步. 部署Key Manager 每个机构一个Key Manager，具体的部署步骤，可参考Key Manager README [https://github.com/FISCO-BCOS/key-manager] 重要 若节点为国密版，Key Manager也需是国密版。 第二步. 生成节点 用build_chain.sh脚本，用普通的操作方法，先生成节点。

communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses communication between SDK clients. ; This IP is the same as p2p_ip for the physical host. ; But for virtual host e.g., VPS servers, it is usually different from p2p_ip. ; You can check accessible addresses