Help Center/ Blockchain Service/ User Guide/ Enhanced Hyperledger Fabric BCS Management/ Instance Deployment/ Deployment Using a CCE Cluster
Updated on 2024-06-17 GMT+08:00
View PDF
Share

Deployment Using a CCE Cluster

Enhanced Hyperledger Fabric instances can be deployed in CCE clusters. This section describes how to deploy an enhanced Hyperledger Fabric instance using a CCE cluster.

  • Using a CCE cluster: All the instance and blockchain data are stored on Huawei Cloud. Use your own hardware resources or buy new ones on Huawei Cloud.
    • The BCS instance will use the CCE cluster exclusively. Ensure that the CCE cluster is available before you deploy the BCS instance.
    • When you use BCS for the first time, log in to the CCE console to authorize CCE to access you BCS resources. For details, see Preparations.
    • You can prepare a CCE cluster in advance, and select it when you create an enhanced Hyperledger Fabric instance. Alternatively, you can customize a CCE cluster or select Quick Config to use the default specifications when you create an enhanced Hyperledger Fabric instance.
    • When deploying a BCS instance using a CCE cluster, implement security hardening to ensure that the instance functions properly. For example, you can forbid the root user to remotely log in to the system, disable port 22 in the security group, delete sniffing/development/debugging/compilation tools, set the system session timeout duration (cannot be infinite), and disallow containers to access the management IP of OpenStack (169.254.169.254). Note that access control of 169.254.169.254 will restrict AOM from detecting ICAgent in the cluster, but the data can still be collected and reported. For more security hardening suggestions, see Node Security Configuration.
    • If you deploy your instance using a new cluster, BCS automatically disallows containers to access 169.254.169.254 and deletes port 22 from the security group. If you deploy your instance using an existing cluster, implement security hardening by referring to Node Security Configuration.

Prerequisites

Only IAM users with robust permissions can subscribe to BCS instances. For details, see Permissions Management.

You can create a user group, grant permissions to the user group, and then add the user to the user group. In this way, the user has the permissions of the user group.

Deploying a BCS Instance

After the environment is ready, perform the following steps to purchase a BCS instance:

If your account is in arrears, the instance web disk will be released and the purchased instances will be unavailable.

  1. Go to the page for purchasing enhanced Hyperledger Fabric instances.

  2. Configure basic information about the BCS instance by referring to Table 1.

    Table 1 Basic information parameters

    Parameter

    Description

    Example Setting

    Billing Mode

    BCS instances are billed in pay-per-use mode.

    -

    Region

    Select the region where the blockchain infrastructure is located. You are advised to select the same region as the service application system.

    Retain the default value.

    Enterprise Project

    Select an existing enterprise project, to which the BCS instance will be added.

    NOTE:
    • If the Enterprise Management service is not enabled, this parameter is unavailable.

      For details, see Enabling the Enterprise Project Function.

    • When deploying an instance in an existing CCE cluster, choose the same enterprise project as that used by the cluster to ensure instance performance.

    default

    Instance Name

    An instance name can contain 4 to 24 characters, including letters, digits, and hyphens (-). It cannot start with a hyphen (-).

    NOTE:

    Currently, the name of a created BCS instance cannot be changed. You can only create a new instance with a new name.

    Enter bcs-wh.

    Edition

    BCS provides basic and professional editions.

    NOTE:

    Editions cannot be changed for a deployed BCS instance.

    Select Professional.

    Blockchain Type

    A private blockchain is used only by the tenant that creates it. A consortium blockchain can be used by multiple tenants.

    Select Private.

    Enhanced Hyperledger Fabric Version

    BCS instance version.

    BCS v4.x.x corresponds to Hyperledger Fabric v2.2.

    Select v2.2.

    Consensus Mechanism

    The supported mechanisms for blockchain nodes reaching consensus include:

    Raft (crash fault tolerant) and Fast Byzantine fault tolerance (FBFT).

    NOTE:

    If Raft (CFT) is selected, a basic or professional edition instance has three orderers by default.

    Select FBFT.

    Resource Access Initial Password

    Password of blockchain administration user admin, ECS user root, or CouchDB database user.

    It will be used as such a password if you do not set Blockchain Mgmt. Initial Password, Password of Root User, or Initial Password displayed when NoSQL (CouchDB) is selected for Ledger Storage.

    -

    Confirm Password

    Confirm the resource access initial password.

    -

  3. (Optional) Click Quick Config to allow the system to automatically purchase an instance with the specifications listed in Table 2.

    Table 2 Default specifications

    Item

    Professional Edition

    Enterprise Edition

    Number of ECSs

    1

    2

    ECS specifications

    4 vCPUs | 8 GB

    4 vCPUs | 8 GB

    Note: If the default specifications are sold out, other higher specifications will be purchased by default.

    High availability of the CCE cluster

    Yes

    Yes

    Storage space of SFS Turbo

    1000 GB

    1000 GB

    EIP

    Type: Dynamic BGP; Bandwidth: 5 Mbit/s

  4. Click Next: Configure Resources. Table 3 describes the resource parameters.

    Table 3 Resource parameters

    Parameter

    Description

    Example Setting

    Environment Resources

    Use the default environment or customize your environment resources.

    Select Custom.

    Cluster

    Cluster where the BCS instance will be deployed. You can use an existing cluster or create a new CCE cluster.

    NOTE:
    • CCE clusters of v1.19 or earlier are supported.
    • If the BCS instance uses Fabric v1.4, the CCE cluster must be v1.15 or earlier.
    • The memory usage of instantiated containers varies depending on the chaincode language. On each peer, a Go chaincode container takes up 10 MB for running, and a Java chaincode takes up 110 MB. For example, if 100 Java chaincodes need to be instantiated, a 16 vCPUs and 32 GB CCE node is preferred.

    Select Create a new CCE cluster.

    AZ

    Select the AZ where the ECS is located.

    Select AZ1.

    ECS Specifications

    Specifications of the ECSs in the CCE cluster.

    Select the flavor for 4 vCPUs | 8 GB.

    ECS Quantity

    Enter the required ECS quantity.

    For details, see Edition Differences.

    Enter 2.

    High Availability

    If you have high requirements on system reliability, purchase high-availability ECSs.

    Yes

    VPC

    You can create a new virtual private cloud (VPC), select an existing VPC, or let the system automatically create a VPC.

    Select Automatically create VPC.

    Subnet

    A subnet provides dedicated network resources that are logically isolated from other networks for network security.

    Select Automatically create subnet.

    ECS Login Method

    Either a password or key pair can be used to log in to ECSs.

    Select Password.

    Password of Root User

    Password of the root user for logging in to ECSs.

    If you do not enter a password here, the previously specified resource access initial password will be used.

    -

    Confirm Password

    Confirm the ECS login password of the root user.

    -

    Use EIP of a CCE Node
    • If you select Yes, an EIP bound to the cluster will be used as the blockchain network access address. If the cluster is not bound with any EIP, bind an EIP to the cluster first.
    • If you select No, a private address of the cluster will be used as the blockchain network access address. Ensure that the application can communicate with the internal network of the cluster.

    Select Yes.

    Data Backup

    Whether to back up the management data and ledger data. This parameter is set to Yes by default.

    • Yes: Management data and ledger data of the BCS instance will be backed up in Object Storage Service (OBS) and Cloud Backup and Recovery (CBR). Do not perform any operations on the backup data.
    • No: Data backup is disabled.
    		   

    EIP Billed By

    Pay-per-use has been selected for Billing Mode, so EIPs can be charged by bandwidth or traffic.

    Select Bandwidth.

    EIP Bandwidth

    Select a bandwidth as required.

    Set it to 5 Mbit/s.

  5. Click Next: Configure Blockchain. Table 4 describes the blockchain parameters.

    Table 4 Blockchain parameters

    Parameter

    Description

    Example Setting

    Blockchain Configuration

    Use the default blockchain configurations or customize your own blockchain configurations.

    Select Custom.

    Blockchain Mgmt. Initial Password

    Enter the blockchain management initial password.

    If you do not enter a password here, the previously specified resource access initial password will be used.

    -

    Confirm Password

    Enter the blockchain management initial password again for confirmation.

    -

    Volume Type

    SFS Turbo provides low-latency and high-IOPS file storage.

    Select SFS Turbo.

    Storage Capacity of Peer Organization (GB)

    Stores shared distributed ledger, consensus data, and other intermediate data of the blockchain system.

    Set it to 500 GB.

    Ledger Storage

    File database (GoLevelDB) and NoSQL (CouchDB) are supported.

    • File database (GoLevelDB): The Fabric native storage mode is used. Historical transaction data is stored in the blockchain, and status data is stored in the LevelDB.
    • NoSQL (CouchDB): The CouchDB storage mode supported by the Fabric is used to store transaction data and status data. Each CouchDB database is a collection of independent documents. Each document maintains its own data and self-contained schema.

    Select File database (GoLevelDB).

    Peer Organization

    Peer organizations to be added to the BCS instance.

    • If you use an existing cluster, customize the peer organization name and peer quantity. Automatically create SFS Turbo file system will be displayed in the Network Storage area.
    • If you use a new CCE cluster, customize the peer organization name and peer quantity.

    Add a peer organization named organization with 2 peers.

    Channel Configuration

    Channels isolate business in a consortium blockchain. Business participants (some or all of the organizations in a consortium) are channel members. Each channel can be regarded as a sub-chain and corresponds to one distributed ledger.

    By default, a channel named channel has been created, and the peer organization you just specified has been added to the channel.

    Orderer Quantity

    Number of nodes that order transactions into blocks in the blockchain network.

    When the consensus mechanism is Raft (CFT), the number of orderers is 3.

    Enter 3.

    Security Mechanism

    Encryption algorithm used to ensure data security. ECDSA and OSCCA-published cryptographic algorithms are supported.

    Select ECDSA.

    Configure Block Generation

    The configuration of block generation includes the block generation interval, maximum number of transactions in a block, and maximum size of a block. A new block is generated at the specified interval or when the transaction quantity or size of a block reaches the threshold. Configure these parameters based on the transaction frequency and service volume.

    Select Yes or No as required.

    • Yes: Set the block generation interval, transaction quantity per block, and block size as required.
    • No: You do not need to set parameters. By default, the block generation interval is 2 seconds, the number of transactions per block is 500, and the block size is 2 MB.

    Select No.

    Enable Support for RESTful API

    If you need to use RESTful APIs to invoke chaincodes, select Yes.

    NOTE:

    This function is under OBT.

    Select No.

  6. Click Next: Confirm.
  7. Confirm the configurations, confirm that you have read and agree to the agreement, and click Pay Now.

    Wait for several minutes. After a message is displayed indicating successful installation, check the status of the instance. If it is Normal, the deployment is completed.

    Figure 1 Instance status

Subsequent Operations (Optional)

View the operation records of creating, deleting, and upgrading instances, adding organizations, expanding peers, creating channels, and adding peers to channels. In the left part of the window, you can filter records by status, including In progress, Upgrading, Deleting, Finished, and Failed. The figure is for reference only.

Figure 2 Operation records

The system stores records of the latest three days.

  1. Log in to the BCS console. In the navigation pane, click Instance Management.
  2. Click Task Details.

    Search records by the resource name. You can also view details or delete records.

You can configure an anti-affinity label for the cluster node where the BCS instance is deployed. This label can be used to isolate the instance from other applications in the same cluster to ensure normal running of the system.

  1. Log in to the CCE console.
  2. On the Clusters page, click a target cluster.
  3. On the Nodes tab page, click a node, and click Manage Labels and Taints.
  4. In the Batch Operation area, click Add Operation, and select Add/Update from the drop-down box. Set Key to nodeScope and Value to userApplication for the label to be added.

  5. Click OK.
  6. After the label is added, click Manage Labels and Taints again. In the Node Data area, click Show to view the added labels.
Parent topic: Instance Deployment