HyperLedger Fabric 1.4.4 ca服务集群搭建（MySQL）

梦里梦外; 2023-02-12 12:29 8阅读 0赞

`Fabric CA`默认使用`SQLite`数据库，这是一种嵌入式的文件数据库，如果需要将在集群中部署`Fabric CA`，那么就需要使用`PostgreSQL`或者`MySQL`数据库，支持的最低版本如下：

`PostgreSQL: 9.5.5`

`MySQL: 5.7（但是使用5.7以上的版本也会有问题，这个后面会详细说明）`

## 单机版搭建 ##

首先创建`ca.yaml`文件（需要注意文件中的一些目录需要根据情况做修改），文件内容如下：

# Copyright IBM Corp. All Rights Reserved.
    #
    # SPDX-License-Identifier: Apache-2.0
    #
    
    version: '2'
    services:
      ca0:
        image: hyperledger/fabric-ca:$IMAGE_TAG
        environment:
          - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
          - FABRIC_CA_SERVER_CA_NAME=ca-org1
          - FABRIC_CA_SERVER_TLS_ENABLED=true
          - FABRIC_CA_SERVER_TLS_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem
          - FABRIC_CA_SERVER_TLS_KEYFILE=/etc/hyperledger/fabric-ca-server-config/7550a33dfd82fb96b16f209cff24eeeedb85a8ee4288bd434fa947d98b90356f_sk
        ports:
          - "7054:7054"
        command: sh -c 'fabric-ca-server start --ca.certfile /etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem --ca.keyfile /etc/hyperledger/fabric-ca-server-config/7550a33dfd82fb96b16f209cff24eeeedb85a8ee4288bd434fa947d98b90356f_sk  -b admin:adminpw -d'
        volumes:
          - ./crypto-config/peerOrganizations/org1.example.com/ca/:/etc/hyperledger/fabric-ca-server-config
          # 将ca服务的目录映射到主机目录中
          - /var/hyperledger/ca/:/etc/hyperledger/fabric-ca-server
        container_name: ca0_peerOrg1

文件创建完成之后就可以启动`ca`服务了，`docker-compose -f ca.yaml up -d`。  
`docker ps -a`命令运行结果如下：  
![在这里插入图片描述][2020052611134975.png]  
这时候可以发现我们映射到的主机目录下生成了一系列文件：

[root@bd226 ca]# tree
    .
    ├── fabric-ca-server-config.yaml
    ├── fabric-ca-server.db
    ├── IssuerPublicKey
    ├── IssuerRevocationPublicKey
    └── msp
        └── keystore
            ├── 7550a33dfd82fb96b16f209cff24eeeedb85a8ee4288bd434fa947d98b90356f_sk
            ├── IssuerRevocationPrivateKey
            └── IssuerSecretKey
    
    2 directories, 7 files

`fabric-ca-server.db`：`SQLite数据库`存储数据的文件。  
`fabric-ca-server-config.yaml`：`CA服务`的配置文件。  
其他文件都是公钥密钥之类的文件。

## 修改配置文件 ##

首先修改`ca.yaml`文件。  
修改后的内容如下：

version: '2'
    services:
      ca0:
        image: hyperledger/fabric-ca:$IMAGE_TAG
        environment:
          - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
          - FABRIC_CA_SERVER_CA_NAME=ca-org1
          - FABRIC_CA_SERVER_TLS_ENABLED=true
          - FABRIC_CA_SERVER_TLS_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem
          - FABRIC_CA_SERVER_TLS_KEYFILE=/etc/hyperledger/fabric-ca-server-config/7550a33dfd82fb96b16f209cff24eeeedb85a8ee4288bd434fa947d98b90356f_sk
        ports:
          - "7054:7054"
        command: sh -c 'fabric-ca-server start --ca.certfile /etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem --ca.keyfile /etc/hyperledger/fabric-ca-server-config/7550a33dfd82fb96b16f209cff24eeeedb85a8ee4288bd434fa947d98b90356f_sk  -b admin:adminpw -d'
        volumes:
          - ./crypto-config/peerOrganizations/org1.example.com/ca/:/etc/hyperledger/fabric-ca-server-config
          - /var/hyperledger/ca/:/etc/hyperledger/fabric-ca-server
        container_name: ca0_peerOrg1
    
      ca1:
        image: hyperledger/fabric-ca:$IMAGE_TAG
        environment:
          - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
          - FABRIC_CA_SERVER_CA_NAME=ca-org1
          - FABRIC_CA_SERVER_TLS_ENABLED=true
          - FABRIC_CA_SERVER_TLS_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem
          - FABRIC_CA_SERVER_TLS_KEYFILE=/etc/hyperledger/fabric-ca-server-config/7550a33dfd82fb96b16f209cff24eeeedb85a8ee4288bd434fa947d98b90356f_sk
        ports:
          - "8054:7054"
        command: sh -c 'fabric-ca-server start --ca.certfile /etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem --ca.keyfile /etc/hyperledger/fabric-ca-server-config/7550a33dfd82fb96b16f209cff24eeeedb85a8ee4288bd434fa947d98b90356f_sk  -b admin:adminpw -d'
        volumes:
          - ./crypto-config/peerOrganizations/org1.example.com/ca/:/etc/hyperledger/fabric-ca-server-config
          - /var/hyperledger/ca/:/etc/hyperledger/fabric-ca-server
        container_name: ca1_peerOrg1

然后是`CA服务`的配置文件`fabric-ca-server-config.yaml`，打开修改`db选项`即可。  
如果需要配置成`MySQL`存储，则需要将如下这段

db:
      type: sqlite3
      datasource: fabric-ca-server.db
      tls:
          enabled: false
          certfiles:
          client:
            certfile:
            keyfile:

替换为

db:
      type: mysql
      datasource: username:password@tcp(***.***.***.***:3306)/fabric_ca?parseTime=true
      tls:
          enabled: false
          certfiles:
          client:
            certfile:
            keyfile:

然后删除主机目录下的所有文件，并将修改好的配置文件复制过去。重新启动`CA服务`即可。

## 问题解决 ##

但是`CA服务`使用`MySQL`的时候有一些bug。不论使用的`MySQL`版本是`5.7`以上还是以下的，都有一些问题出现。  
因为`CA服务`启动的时候会判断数据库和表是否存在，如果不存在则会自动创建，但是建表语句与`MySQL`有些不兼容，所以会导致一些问题的出现。下面是导出的建表语句的`SQL文件`，可以手动创建，然后根据自身`MySQL`的版本做一些相应的修改即可成功启动`CA服务`。

SET NAMES utf8mb4;
    SET FOREIGN_KEY_CHECKS = 0;
    
    -- ----------------------------
    -- Table structure for affiliations
    -- ----------------------------
    DROP TABLE IF EXISTS `affiliations`;
    CREATE TABLE `affiliations`  (
      `id` int(11) NOT NULL AUTO_INCREMENT,
      `name` varchar(1024) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
      `prekey` varchar(1024) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL,
      `level` int(11) NULL DEFAULT 0,
      PRIMARY KEY (`id`) USING BTREE,
      INDEX `name_index`(`name`) USING BTREE
    ) ENGINE = InnoDB AUTO_INCREMENT = 6 CHARACTER SET = utf8 COLLATE = utf8_bin ROW_FORMAT = Compact;
    
    -- ----------------------------
    -- Table structure for certificates
    -- ----------------------------
    DROP TABLE IF EXISTS `certificates`;
    CREATE TABLE `certificates`  (
      `id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL,
      `serial_number` varbinary(128) NOT NULL,
      `authority_key_identifier` varbinary(128) NOT NULL,
      `ca_label` varbinary(128) NULL DEFAULT NULL,
      `status` varbinary(128) NOT NULL,
      `reason` int(11) NULL DEFAULT NULL,
      `expiry` timestamp(0) NOT NULL DEFAULT '0000-00-00 00:00:00',
      `revoked_at` timestamp(0) NOT NULL DEFAULT '0000-00-00 00:00:00',
      `pem` varbinary(4096) NOT NULL,
      `level` int(11) NULL DEFAULT 0,
      PRIMARY KEY (`serial_number`, `authority_key_identifier`) USING BTREE
    ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin ROW_FORMAT = Compact;
    
    -- ----------------------------
    -- Table structure for credentials
    -- ----------------------------
    DROP TABLE IF EXISTS `credentials`;
    CREATE TABLE `credentials`  (
      `id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL,
      `revocation_handle` varbinary(128) NOT NULL,
      `cred` varbinary(4096) NOT NULL,
      `ca_label` varbinary(128) NULL DEFAULT NULL,
      `status` varbinary(128) NOT NULL,
      `reason` int(11) NULL DEFAULT NULL,
      `expiry` timestamp(0) NOT NULL DEFAULT '0000-00-00 00:00:00',
      `revoked_at` timestamp(0) NOT NULL DEFAULT '0000-00-00 00:00:00',
      `level` int(11) NULL DEFAULT 0,
      PRIMARY KEY (`revocation_handle`) USING BTREE
    ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin ROW_FORMAT = Compact;
    
    -- ----------------------------
    -- Table structure for nonces
    -- ----------------------------
    DROP TABLE IF EXISTS `nonces`;
    CREATE TABLE `nonces`  (
      `val` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
      `expiry` timestamp(0) NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP(0),
      `level` int(11) NULL DEFAULT 0,
      PRIMARY KEY (`val`) USING BTREE
    ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin ROW_FORMAT = Compact;
    
    -- ----------------------------
    -- Table structure for properties
    -- ----------------------------
    DROP TABLE IF EXISTS `properties`;
    CREATE TABLE `properties`  (
      `property` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT '',
      `value` varchar(256) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL,
      PRIMARY KEY (`property`) USING BTREE
    ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin ROW_FORMAT = Compact;
    
    -- ----------------------------
    -- Table structure for revocation_authority_info
    -- ----------------------------
    DROP TABLE IF EXISTS `revocation_authority_info`;
    CREATE TABLE `revocation_authority_info`  (
      `epoch` int(11) NOT NULL DEFAULT 0,
      `next_handle` int(11) NULL DEFAULT NULL,
      `lasthandle_in_pool` int(11) NULL DEFAULT NULL,
      `level` int(11) NULL DEFAULT 0,
      PRIMARY KEY (`epoch`) USING BTREE
    ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin ROW_FORMAT = Compact;
    
    -- ----------------------------
    -- Table structure for users
    -- ----------------------------
    DROP TABLE IF EXISTS `users`;
    CREATE TABLE `users`  (
      `id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT '',
      `token` blob NULL,
      `type` varchar(256) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL,
      `affiliation` varchar(1024) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL,
      `attributes` text CHARACTER SET utf8 COLLATE utf8_bin NULL,
      `state` int(11) NULL DEFAULT NULL,
      `max_enrollments` int(11) NULL DEFAULT NULL,
      `level` int(11) NULL DEFAULT 0,
      `incorrect_password_attempts` int(11) NULL DEFAULT 0,
      PRIMARY KEY (`id`) USING BTREE
    ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin ROW_FORMAT = Compact;
    
    SET FOREIGN_KEY_CHECKS = 1;

至此就搭建成功了。

后续会补充`PostgreSQL`的搭建教程。

[2020052611134975.png]: https://img-blog.csdnimg.cn/2020052611134975.png