Tutorial
GIS Tiling Cluster Creation
SuperMap iManager supports to ‘one-click’ creating GIS Tiling Cluster, please refer to the following steps:
- Open Sites Management on the left navigation bar.
- Clicks on + Create.
-
Fills in the name of the GIS Tiling Cluster environment, and select GIS Tiling Cluster 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.
- iServer-master External Port: Set the port of iServer-master access address, a random port would be used if not set.
- FTP external port: Set the port of FTP access address, a random port would be used if not set.
- FTP data transfer minimum port: Set the minimum port range for FTP data transfering, a random port would be used if not set.
- FTP data transfer maximum port: Set the maximum port range for FTP data transfering, 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. - Clicks on OK.
- Check the status on the GIS Tiling Cluster page, while the status change to ‘Normal’, the GIS Tiling Cluster created successfully.