Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.
- Service Overview
- Billing
- Getting Started
-
User Guide
- Overview
- Permissions Management
- Environment Management
- Application Management
- Component Management
- Instance Management
- Component Configurations
- Component O&M
- System Settings
- Key Operations Recorded by CTS
-
Best Practices
- CAE Best Practices
- Using CAE to Host Nginx Static File Servers
- Interconnecting GitLab with Jenkins for Automatic Build and Deployment on CAE
- Deploying Components Based on the Dependency Sequence Using the Jenkins Pipeline
- Deploying Spring Cloud Applications to CAE to Automatically Connect to the Nacos Engine
- Graceful Startup of a Spring Cloud Application
- Health Check
- Lifecycle Management
- Sending Event Alarms to WeCom
-
Connecting to the CodeArts Pipeline to Automatically Upgrade CAE Components
- Overview
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to a CodeArts Release Repo
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to the OBS Bucket
- Upgrading a CAE Component After Uploading an Image Built Using the Pipeline to the SWR Image Repository
- Configuring PromQL to Implement Custom Auto Scaling
- Configuring the Interconnection Between CAE and DEW to Help Applications Obtain Encrypted Secrets from DEW
- Deploying ASP.NET Core Applications to CAE
- Connecting the Network Through Enterprise Routes
- API Reference
-
FAQs
- Component Management FAQs
- Environment Management
-
Component Configuration FAQs
- Is Manual Scaling Still Effective When a Scaling Policy Is Configured?
- Can Components Be Scaled Without a Scaling Policy?
- Why Is My Instance Abnormal After Cloud Storage Is Configured?
- What Do I Do If a Component Becomes Not Ready?
- How Does CAE Support Dark Launch?
- How Do I Provide Prometheus Metrics for a Java Application?
- System Configuration FAQs
- Service Resources FAQs
- General Reference
Copied.
Glossary
Regions and AZs
A region and availability zone (AZ) identify the location of a data center. Created resources have a specific region and AZ.
- Regions have their own geographical location and network latency. Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared in the same region. Regions are either universal or dedicated: universal region provides universal cloud services for common domains while a dedicated region provides services of the same type only or for specific domains.
- An AZ contains one or more physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. An AZ's computing, network, storage, and other resources are logically divided into multiple clusters. AZs within a region are interconnected by high-speed optical fibers for building cross-AZ high-availability systems.
Figure 1 shows the relationship between regions and AZs. For details about how to select regions and AZs, see Region and AZ.
Environment
Environments distinguish service deployment scenarios and means isolation. In CAE, development, test, pre-production, and production environments are tailored to requirements. Networks in an environment intercommunicate, while components and services are managed and deployed within the environment for easier O&M, production, and rollout.
Application
An application is a service system with functions and consists of one or more application components.
Application Component
An application component implements a service feature of an application. It is in the form of code or software package and can be deployed independently.
Component Instance
An instance is the minimum running and deployment unit of a component, and tends to be used for a single application process.
Serverless
Serverless computing is a model of cloud computing. The cloud provider allocates machine resources on demand and manages servers on behalf of the customers, who are not involved in capacity planning, configuration, management, maintenance, fault tolerance, or scaling of containers, VMs, or physical servers.
Data Redundancy Policy
The two data redundancy policies are multi-AZ storage and single-AZ storage. CAE only supports authorization and creation of object storage with policy multi-AZ storage.
- Multi-AZ storage: Data is stored in multiple AZs in the same region for better availability. A file system created in multi-AZ mode stores its data in three different AZs in the same region. This enables data access in case of unavailability of any single AZ, so the multi-AZ mode is useful for storing data that must always be available.
- Single-AZ storage: Data is stored in a single AZ, with lower costs.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot