Available in VPC
Once you've reviewed the Blockchain Service specifications and quickstart, you're ready to start using the service. The first step is to create a network. You can create and manage networks from the NAVER Cloud Platform console.
Here are the topics covered in this guide:
Create network
NAVER Cloud Platform's Blockchain Service manages Hyperledger Fabric nodes within units called networks. To create and manage fabric nodes, you must first create a network.
Required resources and service limits for using Blockchain Service
- Ncloud Kubernetes Service: A cluster created in NAVER Cloud Platform's Ncloud Kubernetes Service (VPC) is required. Hyperledger Fabric nodes are deployed to the Kubernetes cluster.
- We recommend using the Kubernetes cluster exclusively for Blockchain Service.
- There should be no additional rules on the server other than the default ACG inbound/outbound (IN/OUT bound) rules.
- The Kubernetes PSP feature must be disabled.
To create a network:
During the network creation process, you can also create Fabric nodes such as orderer, peer, and CA if needed. These fabric nodes are created and managed in Blockchain Service > Nodes.
- Access the NAVER Cloud Platform console.
- Click Region & Platform at the top right of the console interface.
- Select your region and VPC platform and then click [Apply].
- Click
in the upper left corner of the console interface. - Navigate to Services > Blockchain > Blockchain Service.
- Click [Create network].
- Check the details of the agreement on the collection and use of personal information, check the required consent items, and then click [OK].
- Complete the following steps on the network creation interface:
1. Configure network
Specify the network settings information and click [Next].
- Click Deploy network and specify a Kubernetes cluster node pool to deploy blockchain nodes to the selected node pool. The node affinity labels configured for Ncloud Kubernetes Service appear in the list, and you can specify up to 3 labels.
2. Create orderer
You can create an orderer during the network creation step.
- Click the Create orderer radio button.
- If you do not create an orderer at this step, the process skips peer and channel creation and proceeds directly to the finalize step.
- After configuring the orderer CA, orderer MSP, and ordering service, click [Next].
- The CA user IDs for admin and orderer are created as admin or orderer types in the corresponding network CA, respectively. For details on the CA, see Manage CA user ID.
- In MSP name, enter the MSP ID for the organization that the orderer joins. Use the value generated by the orderer CA for the RootCA public key of the organization being created. For details on creating an MSP, see Create MSP.
- You can select either single (raft 1) or multiple (raft 5) for the Orderer type. This creates 1 or 5 orderer nodes, respectively. Use multiple (raft 5) for production environments that require high availability (recommended).
- Selecting multiple (raft 5) as the orderer type creates 5 orderer nodes. Check the available resources in your Kubernetes cluster beforehand.
- For details on configuring the ordering service, see Create orderer.
- Orderer nodes are deployed to the Kubernetes cluster during the orderer creation process.
3. Configure peer
- ** Click the Create org./peer** radio button.
- If you do not create a peer at this step, the process proceeds directly to the finalize step.
- After configuring the organization CA, organization MSP, and peer, click [Next].
- For details on configuring a peer, see Create peer.
- The CA user IDs for admin and peer are created in their respective network CAs with admin or peer types. For details on the CA, see Manage CA user ID.
- Enter the MSP ID for the organization the peer joins in MSP name. Use the value generated by the orderer CA for the RootCA public key of the organization being created.
- You can select either
LevelDBorCouchDBfor State database, which must be configured with the same database type within the consortium. - If
CouchDBis selected as the state database, a separate CouchDB node is created in addition to the peer node. - During the peer creation process, peer nodes are deployed to the Kubernetes cluster.
4. Create channel
- Click the Create channel radio button.
- If you do not create a channel at this step, the process proceeds directly to the finalize step.
- Specify the channel configuration information and click [Next].
- The peer nodes created in the previous step are automatically added to Peers participating in channel.
- For details on configuring a channel, see Create channel.
5. Finalize
Review the network settings and click [Create network].
- If you are creating orderer, peer, or CA nodes during this process, check the available capacity of your Kubernetes cluster. The network cannot be created if the Kubernetes cluster has insufficient resources.
- It takes a few to several tens of minutes to create a Blockchain Service network. When network creation is complete and operations begin, Running is displayed in the status column of the network list.
If you are using the private subnet network type for your Kubernetes cluster:
- To access Fabric nodes in other users' networks or communicate outside the network, you must configure a NAT Gateway in the VPC where the Kubernetes cluster is installed. Go to NAT Gateway user guide.
Delete network
To delete a network:
- Access the NAVER Cloud Platform console.
- Click Region & Platform at the top right of the console interface.
- Select your region and VPC platform and then click [Apply].
- Click
in the upper left corner of the console interface. - Navigate to Services > Blockchain > Blockchain Service > Networks.
- Select the network you want to delete from the network list and click [Delete network].
- In the confirmation popup, enter the name of the corresponding network and click [Delete].
Deleting the network takes several minutes. Once the deletion is complete, the network disappears from the network list.