Deployment Essentials¶
Deployment Steps¶
Guance deployment can be initiated by following these steps:
1. Resource Planning and Material Preparation¶
2. Deploying Infrastructure¶
3. Deploy Guance¶
4. Start Exploring Features¶
- 4.1 Get Started
Precautions¶
Domain Names¶
Deployment requires providing a domain name. If you have a real domain, it needs DNS resolution or local hosts binding.
Taking dataflux.cn as an example, the following describes the purpose of each subdomain:
| Subdomain Prefix | Example Domain | Target | Purpose | Required |
|---|---|---|---|---|
| dataflux | dataflux.dataflux.cn | Ingress-Nginx | Guance Console Frontend | Yes |
| df-api | df-api.dataflux.cn | Ingress-Nginx | Guance Console API | Yes |
| df-docs | df-docs.dataflux.cn | Ingress-Nginx | Help Documentation | No |
| df-func | df-func.dataflux.cn | Ingress-Nginx | Guance Compute Service | No |
| df-kodo | df-kodo.dataflux.cn | kodo-nginx | Metrics Data Entry Service | Yes |
| df-management | df-management.dataflux.cn | Ingress-Nginx | Guance Admin Console | Yes |
| df-management-api | df-management-api.dataflux.cn | Ingress-Nginx | Guance Admin API | Yes |
| df-openapi | df-openapi.dataflux.cn | Ingress-Nginx | Guance Data Interface | No |
| df-static-res | df-static-res.dataflux.cn | Ingress-Nginx | Guance Template Resources | Yes |
For more information on Guance components, please refer to: Component Description
Cluster Storage Classes¶
Note
Guance software deployment must use nfs-subdir-external-provisioner.
Deploying Guance services involves deploying two main parts: one is the basic component deployment, and the other is Guance software deployment. The storage classes used in both deployments differ as follows:
| Name | nfs-subdir-external-provisioner | OpenEBS |
|---|---|---|
| Requires Third Party? | NFS required | Not required, local disk sufficient |
| Performance | Network storage, poor IO performance | Local storage, high IO performance |
| Read/Write Type | ReadWriteMany, ReadOnlyMany, ReadWriteOnce | ReadWriteOnce |
| Pros and Cons | Pros: Shared data, multi-node mounting; Cons: Poor IO | Pros: High IO; Cons: No cross-node sharing, no dynamic scheduling support |
| Supported Environments | Basic component deployment, Guance software deployment | Basic component deployment only |
| Remarks | For POC environments, this storage class can be used for deploying basic components and Guance software. For production environments, it is not recommended to use this storage class for basic component deployment | This storage class is not suitable for deploying Guance software |
Please continue translating if there's more content.