Chinese | English | Description |
|---|---|---|
Logical unit | Zone | A unit is called a Zone. There are three types of Zones: RZone, GZone, and CZone. Zones have the following features:
|
Cell-based architecture | - | The application layer follows the same sharding dimension as the data layer. This converges the entire request link into a group of servers. This forms a self-contained unit from the application layer to the data layer. The database only needs to handle requests from the application nodes within its unit. This greatly reduces the number of connections. A unit can be moved as a relatively independent whole. You can even deploy some units to different geographical locations. |
Deployment unit | Cell | A deployment unit (Cell) is a self-contained collection that can perform all business operations. This collection contains all the services required for the business and the data allocated to that unit. A unitized architecture uses a Cell as the basic unit of deployment. Several Cells are deployed across all data centers. The number of Cells in each data center can vary. Each Cell has all the applications required by the system. The data in a Cell is a subset of the full data, partitioned by a specific dimension. |
Application service | Application service | This concept is the same as the application service concept in classic application services. However, because containers have unique characteristics, application services in LHC include extra metadata. This metadata includes container specification configurations, images, scheduling policies, and log configurations. |
Image | Image | An image is an application package. It is a binary package that bundles configurations and related software. It must comply with the Docker Image specification. Images can come from any Image Center that is accessible to the LHC network. For private Image Centers, configure the corresponding access information in LHC. |
Build | Build | A build describes the configuration information for the process of creating an image from application source code. This includes the source code address, branch information, source image access information, target image information, and the Dockerfile location. |
Cluster | Cluster | In LHC, a cluster describes a workload cluster that you create. It consists of multiple nodes. |
Node | Node | A node is a physical server or virtual machine that has Docker and Kubelet installed. It is used to run application workloads. |
Pod | Pod | The smallest deployable and manageable unit in Kubernetes. A pod consists of multiple related containers that share a disk. |
Namespace | Namespace | This concept is consistent with the corresponding concept in Kubernetes. A namespace represents a logically isolated space. It isolates elements such as pods, services, and ReplicaSets. However, the network is usually not isolated. |
In-place upgrade | In-place upgrade | In-place upgrade is a method for updating pods in an application service. After a release, the pod's IP address usually changes, and the node it runs on may also change. This update method does not delete the pod when the image is replaced. |
Label | Label | A native Kubernetes concept. Labels are used to tag resources for aggregation or matching. |
Taint | Taint | A native Kubernetes concept. Taints are used to mark nodes. They are typically used for pod scheduling policies. The corresponding concept is toleration. If a pod has a corresponding toleration mark, it can tolerate the taint on a node and be scheduled to that node. |
Secret | Secret | A native Kubernetes concept. Secrets are used to store a user's encrypted content. |
Application container | Container | An isolated workspace where an application runs. It is usually a Docker container or a sandbox workspace with isolation capabilities that is compatible with the Container Runtime Interface (CRI), such as Pouch. |
Workload | Workload | The carrier for an application's runtime state and its higher-level aggregations. Examples include Pod, Deployment, StatefulSet, DaemonSet, and Job. |
Parameter | ConfigMap | A native Kubernetes concept. ConfigMaps are used to store a user's configuration information. |
Storage Class | StorageClass | A native Kubernetes concept. A StorageClass is usually defined by a system administrator. It is used to specify the supported storage categories. Different categories have different storage Service-level agreements (SLAs), backup policies, and other features. |
Persistent Volume | Persistent Volume | A native Kubernetes concept that represents a storage resource created by a system administrator. |
Persistent Volume Claim | Persistent Volume Claim | A native Kubernetes concept. A persistent volume claim (PVC) binds to a persistent volume. |