Tutorial

Geo-Blockchain Creation

SuperMap iManager supports to ‘one-click’ creating Geo-Blockchain, please refer to the following steps:

1. Open Sites Management on the left navigation bar.
2. Clicks on + Create.

3. Fills in the name of the Geo-Blockchain environment, and select Geo-Blockchain in the Site type.

   Advanced Options:

   • Namespace: Specifies the namespace for the created site. If not specified, the system will assign a namespace for it. The specified namespace will be created automatically when it does not exist and will be deleted when the site is deleted. The existing namespace will not be deleted.
   • Certification center 1 external port: Set the port for accessing the certification center 1, a random port would be used if not set.
   • Certification center 2 external port: Set the port for accessing the certification center 2, a random port would be used if not set.
   • Certification center 3 external port: Set the port for accessing the certification center 3, a random port would be used if not set.
   • Order node external port: Set the port for accessing the order node, a random port would be used if not set.
   • Certification center 1 Peer node TCP external port: Set the port of the Peer node TCP protocol for accessing certification center 1, a random port would be used if not set.
   • Certification center 1 Peer node Event external port: Set the event port number for accessing the Peer node of certification center 1, a random port would be used if not set.
   • Certification center 1 Peer node CouchDB external port: Set the CouchDB status database port number for accessing the Peer node of certification center 1, a random port would be used if not set.
   • Certification center 2 Peer node TCP external port: Set the port of the Peer node TCP protocol for accessing certification center 2, a random port would be used if not set.
   • Certification center 2 Peer node Event external port: Set the event port number for accessing the Peer node of certification center 2, a random port would be used if not set.
   • Certification center 2 Peer node CouchDB external port: Set the CouchDB status database port number for accessing the Peer node of certification center 2, a random port would be used if not set.
   • Certification center 3 Peer node TCP external port: Set the port of the Peer node TCP protocol for accessing certification center 3, a random port would be used if not set.
   • Certification center 3 Peer node Event external port: Set the event port number for accessing the Peer node of certification center 3, a random port would be used if not set.
   • Certification center 3 Peer node CouchDB external port: Set the CouchDB status database port number for accessing the Peer node of certification center 3, a random port would be used if not set.
   • Distributed version file system Swarm external port: Set the port number for accessing the distributed file system Swarm, a random port would be used if not set.
   • Distributed version file system API external port: Set the port for accessing the backend of the distributed file system, a random port would be used if not set.
   • Distributed version file system Gateway external port: Set the port for accessing the distributed file system gateway, a random port would be used if not set.
   • iServer External Port: Set the port of iServer access address, a random port would be used if not set.
   • Use Service Mesh: Click to open service mesh function, the site is available to achieve service trace and service metrics. Modify the value of deploy_istio_enabled to ‘true’ in the ‘values.yaml’ file of iManager deployment package first if you want to use service mesh, please refer to Guides > Deployment Guide > Install iManager.

   • Resources Allocation: Set the limitation of CPU and Memory of the Site. The CPU/Memory in the Site is different to the CPU/Memory in hardware machine, the CPU/Memory in the Site is the CPU/Memory occupy of a service node in Kubernetes, the total CPU/Memory of the Site is equal to the sum of CPU/Memory of service nodes.

     • CPU(Required): Set the maximum available CPU of the Site.
     • Memory(Required): Set the maximum available Memory of the Site.
     • Pods: Set the maximum number of available pods in the Site.
     • Default container CPU limit: Set the maximum available CPU of a single container when creating.
     • Default container Memory limit: Set the maximum available Memory of a single container when creating.

   Notes:
   If the Site enable Service Mesh, each service node would create a istio-proxy, a istio-proxy occupies 2 core CPU and 1 GB Memory, the total CPU/Memory of the Site equal to the sum of CPU/Memory of service nodes plus the occupy of the istio-proxy.

4. Clicks on OK.
5. Check the status on the Geo-Blockchain page, while the status change to ‘Normal’, the Geo-Blockchain created successfully.

Notes:

1. Geo-Blockchain Site does not support Service Mesh(Istio). Please do not enable service mesh in advanced options, otherwise you can not create the site.
2. The image ‘supermap/fabric-ccenv:2.2’ which is used for creating Geo-Blockchain Site does not support image pull secret, please set the image permission as public.

After creating, clicks on the access address to log in to iServer, you can publish the Geo-Blockchain in iServer. Please refer to SuperMap iServer Documentation for more details.