Web Cloud Solution. User Guide. Issue 01. Date

Transcription

1 Issue 01 Date

2 Contents Contents 1 Overview What Is Web (CCE+RDS)? Why You Should Choose Web (CCE+RDS) Concept and Principle Required Services Data Planning Procedure Description Operation Guide Uploading an AK/SK File Creating a Key Pair Creating a VPC Creating a Load Balancer Creating a Container Cluster and Node Creating a Component Template Creating a Containerized Application Creating MySQL DB Instances Using RDS Configuring AS Policies Installing the Magento Website Relevant Documents A Change History B Glossary Issue 01 ( ) ii

3 1 Overview 1 Overview 1.1 What Is Web (CCE+RDS)? The Web (CCE+RDS) solution describes how to flexibly and quickly build a secure and scalable Magento e-commerce website using public cloud services. Magento is a professional open-source e-commerce platform with modular architecture and various functions to help retail suppliers succeed in the B2C and B2B industries. Different from website deployment using Elastic Cloud Servers (ECSs) on the public cloud, the Web (CCE+RDS) solution allows you to deploy service nodes using the Cloud Container Engine (CCE) service and data nodes using the relational database service (RDS). The Web (CCE+RDS) solution describes how to use Magento Community Edition to deploy websites on the public cloud without involving the use of Magento. If you need to use the Magento e-commerce website after completing the deployment, visit to access information you need. 1.2 Why You Should Choose Web (CCE+RDS) In website deployment scenarios, a small website is usually deployed on a single server. User access, static and dynamic contents, and database data are all handled on this single server. If the database access traffic of the website increases to the point that a single server cannot meet requirements, deploying databases and website applications on different servers can relieve server loads. Therefore, a deployed website must meet the following requirements: Data nodes must be deployed separately from service nodes. The number of servers must be dynamically adjusted based on service traffic. Service traffic must be automatically distributed to multiple servers. The traditional solution for e-commerce website deployment requires not only purchasing a large number of servers, but also bearing high maintenance costs during peak hours. Therefore, it is best to deploy a website on a public cloud platform, on which virtual resources and supported services can help you complete deployment securely, effectively, and economically. The advantages of using the public cloud platform to deploy an e-commerce website are as follows: Enhancing automation: Applications can be deployed in minutes with lightweight containers, achieving high automatization and improving deployment efficiency. Issue 01 ( ) 3

4 1 Overview Improving system availability and performance: Servers are automatically added or removed based on situation requirements, enhancing access processing capabilities and rapidly responding to service peaks. Reducing costs: Users pay only for the resources to be used. This reduces investment costs. Enhancing security and scalability: Active and standby databases are used in virtual private networks (VPNs) to enhance data security. Database data can be automatically synchronized and copied. 1.3 Concept and Principle Figure 1-1 shows the logical architecture of a Magento e-commerce website deployed by using the Web (CCE+RDS) solution. Figure 1-1 Logical architecture of a Magento e-commerce website deployed by using the Web (CCE+RDS) solution In the Web (CCE+RDS) solution, a website is deployed by using the following procedure: Create a container cluster, run the Magento platform on Docker, and configure the auto scaling policy among containers. Build active and standby MySQL databases using RDS, and set up automatic data synchronization and backup. Configure Elastic Load Balancers for the entire deployment architecture, to achieve automatic access traffic distribution. Issue 01 ( ) 4

5 2.1 Required Services In the Web (CCE+RDS) solution, website deployment schemes using public cloud services are provided based on e-commerce website requirements. Table 2-1 Website deployment schemes and required services Website Requirements Data nodes must be deployed separately from service nodes. The number of servers must be dynamically adjusted based on service traffic. Service traffic must be automatically distributed to multiple servers. Public Cloud Solution Deploying a website: The Virtual Private Cloud (VPC) provides network resources for cloud servers. Traditional servers are replaced with Docker containers in the container cluster created through CCE, and use the Docker containers as basic service nodes of the website. Active and standby data nodes are created using RDS. Configuring features: The auto scaling policy is set based on service requirements. The number of service node instances is dynamically adjusted using the basic service node image, to ensure stable and effective running of services. Configuring features: The Elastic Load Balancing (ELB) service automatically distributes access traffic to multiple service nodes, achieving better fault tolerance performance in applications, and expanding application service capabilities. Required Services VPC CCE RDS CCE ELB Issue 01 ( ) 5

6 The preceding services are described as follows: VPC enables you to provision logically isolated, configurable, and manageable virtual networks for ECSs (that is, Docker containers in this solution). This improves the security of resources in the cloud and simplifies network deployment. You can create security groups and VPNs, assign IP addresses, and specify bandwidth sizes in a VPC. With a VPC, you can manage and configure internal networks and change network configurations, simplifying network management. You can also customize ECS access rules within a security group and between security groups to strengthen ECS security protection. CCE is a high-performance and scalable container service that provides enterprises with lifecycle management of Docker containers, such as rapid application packaging and deployment, and automatic operation and maintenance (O&M). CCE provides a GUI-based application orchestration tool for efficiently creating and deploying applications. RDS is an online relational database service based on the cloud computing platform. RDS is out-of-box, reliable, scalable, and easy to manage. RDS has a sound performance monitoring system and multiple safety measures. It provides a professional database management platform, supporting rapid MySQL database deployment and automatic data synchronization and backup between active and standby databases. ELB is a service that automatically distributes access traffic to multiple cloud servers (that is, Docker containers in this solution) to balance server loads. ELB enables you to achieve better fault tolerance performance in your applications and expand application service capabilities. 2.2 Data Planning For details about how to configure the Web (CCE+RDS) solution, see the following tables. Table 2-2 lists the network configuration information. Table 2-3 lists the parameters of the Elastic Load Balancer. Table 2-4 and Table 2-5 list the cluster and node parameters separately. Table 2-6 lists the parameters of the component template. Table 2-7 lists the Magento parameters. Table 2-8 lists the configuration items of the MySQL database instance. Table 2-2 lists the network configuration information. Table 2-2 Network configuration information Name VPC name. VPC-01 VPC CIDR Classless Inter-Domain Routing (CIDR) block for the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset (for multiple subnets in the VPC) /16 Issue 01 ( ) 6

7 The following CIDR blocks are supported: / / /16 24 Name subnet name. subnet-01 CIDR Gateway subnet address range. This value must be within the VPC subnet. gateway address of the subnet / Table 2-3 lists the parameters of the Elastic Load Balancer. Table 2-3 Parameters of the Elastic Load Balancer Name Elastic Load Balancer name. elb-001 Type VPC Elastic IP Public Network Bandwidth Description network type. Public network: indicates that the load balancer is used in the public network. Private network: indicates that the load balancer is used in the private network. Select Public network for purposes related to this document. VPC to which the load balancer belongs. If you select Public network for Type, you can select an existing IP address or the newly added elastic IP address to create the load balancer. public network bandwidth size when the newly added elastic IP address is used. Provides a description of the load balancer. Public network VPC Node load balancer Table 2-4 and Table 2-5 list the cluster and node parameters separately. Issue 01 ( ) 7

8 Table 2-4 Cluster parameters Name cluster name. magento-cluster VPC Subnet VPC to which the cluster belongs. subnet to which the cluster belongs. VPC-01 subnet /24 Description Provides a description of the cluster. N/A Table 2-5 Node parameters Node Type node type. Computing II Specifications CPU and memory capacity of the node. By default, the operating system uses 340 MB of memory; the node agent on the first node of the container cluster uses 0.71 CPU cores and 170 MB of memory; and the node agent on each of the remaining nodes uses 0.4 CPU cores and 170 MB of memory. Containerized applications will use the remaining CPU and memory resources on the node. The minimum node specifications are 1 vcpu and 2 GB memory. The maximum node specifications are 32 vcpus and 128 GB memory. 2 vcpus 4 GB c2.large Quantity number of nodes. 1 Disk system disk size. 40 GB data disk size. 100 GB Key Pair Selects a key pair. KeyPair-34 Table 2-6 lists the parameters of the component template. Table 2-6 Parameters of the component template Template Name component template name. magento-template Container Image container image, weiyunick/magento Issue 01 ( ) 8

9 including external and internal container images. External images are images in the Docker Hub. Internal images include public or private images. Select External container image for purposes related to this document. Set the container image address in the Docker Hub. To create an image, refer to Cloud Container Engine. Network communication protocol used by the component. TCP Port number of listening ports. 80 Memory CPU Support uncapped CPU Volumes memory size of a container. The unit is MB. CPU specifications of a container (1000 mcores = 1 core). Specifies whether a container supports using uncapped CPU resources. If yes, when the used CPU resources exceed the upper limit, the container occupies other CPU resources on the node where it resides. Retain the default settings. If only one container supports using uncapped CPU resources, the container can use all remaining resources on the node where it resides. If multiple containers support using uncapped CPU resources, these containers allocate the remaining resources of the node according to CPU specifications. For example, if container A has 100 mcores (CPU) and container B has 300 mcores (CPU), containers A and B occupy the remaining resources of the node at 1:3 ratio. Supports a maximum of 10 data volumes. 100 Do not need to configure this parameter in this solution. Retain the default settings. Do not need to configure this parameter in this solution. Environment Variables Supports a maximum of 30 environment variables. Do not need to configure this parameter in this Issue 01 ( ) 9

10 solution. Table 2-7 lists the Magento parameters. Table 2-7 Magento parameters Template Type App template: Created on the graphical orchestration designer. Component template: Created from a container image. When creating a component template from container images, specify the network protocol, communication port, memory capacity, CPU capacity, volume, and environment variables. Component template Container Cluster Selects an existing container cluster. magento-cluster App Name containerized application name. magento-app Template Name Selects an existing template. magento-template Component Name Node component name. The name contains lowercase letters, digits, and hyphens (-), starts with a lowercase letter, and does not exceed 24 characters. node to which the component belongs. Select the node created in Creating a Container Cluster and Node. magento-component magento-node-1 Name subnet name. subnet-01 Instances Service Name Public Service number of component instances. domain name of a containerized application. The containerized application accesses other containers using this domain name. Specifies whether the component supports external accesses. 1 magento-service Select this item. Service Type ELB or node port. LoadBalancer Issue 01 ( ) 10

11 ELB Instance Selects a created ELB instance. elb-001 Table 2-8 lists the configuration items of the MySQL database instance. Table 2-8 Configuration items of the MySQL database instance Configuration Item Parameter Description Example Value Instance Specifications DB Instance Name database instance name. magento-db DB Engine Database Version DB Instance Class Storage database type. database version. database instance type. s1: General-purpo se compute I c2: Compute-opti mized compute II m1: Memory-optim ized compute I storage type and size. MySQL db.s1.medium -1vCPU, 4 GB Common I/O 100 GB Network AZ For details about available AZs, visit ystems.com/en-us/ endpoint/index.ht ml. eu-de-02 VPC Subnet VPC to which the database instance belongs. subnet to which VPC-01 subnet-01 ( /2 Issue 01 ( ) 11

12 Configuration Item Parameter Description Example Value the database instance belongs. 4) Security Group security group. Data can be synchronized between the active and standby databases only when the two databases are in the same security group. Retain the default settings. Database Configuration Administrator Password password of the database administrator. HA HA Specifies whether to enable HA for the database subnet. The standby database improves cluster availability. If you need to create a standby database when creating database instances, enable the HA function. RDS HA instances use floating IP addresses. Backup Policy Automated Backup Specifies whether to enable data backup. The default value is Enabled. Retention Period (Days): period for retaining backup files. Backup Start Time: Test@123 Enabled Enabled 1 01:00 Issue 01 ( ) 12

13 Configuration Item Parameter Description Example Value backup start time. Data backup will begin one hour after the configured backup start time. 2.3 Procedure Description Figure 2-1 shows the process of website deployment on the public cloud platform using the Web (CCE+RDS) solution. Issue 01 ( ) 13

14 Figure 2-1 Website deployment process 2.4 Operation Guide Uploading an AK/SK File Scenarios Before creating a container cluster on the CCE console, upload a valid Access Key ID/Secret Access Key (AK/SK) file. Issue 01 ( ) 14

15 If no AK/SK file is uploaded or the uploaded AK/SK file has expired, the container cluster cannot be authorized to use private container images and Elastic Load Balancing (ELB). To ensure account security and optimal user experience with CCE services, upload your AK/SK file and complete user authentication. Procedure 1. Log in to the management console. 2. Click the account name in the upper right corner, and choose My Credential from the drop-down list. 3. Click Access Keys. 4. Click Add Access Key. The Add Access Key dialog box is displayed. 5. Enter the login password. 6. Enter the verification code received by or mobile phone. For the users created in Identity and Access Management (IAM), if no address or mobile phone is filled during user creation, you need to verify only the login password. MyWorkplace users do not need to verify the login password. If the address or mobile phone information is unavailable, you can create an access password without the verification code. 7. Click OK to download the access key. To prevent the access key from being leaked, keep it secure. 8. Choose Computing > Cloud Container Engine. 9. Upload your AK/SK file to CCE. If you log in to the CCE console for the first time, the Upload Certificate File window is displayed upon successful login. Click Upload. In other situations, choose Dashboard > Update Certificate File. Figure 2-2 Upload a certificate file Creating a Key Pair Scenarios Create a key pair before you create a container cluster. Key pairs are used for identity authentication at the time of node login. If you have already created a key pair, you do not need to create it again. Issue 01 ( ) 15

16 Procedure 1. Log in to the management console. 2. Under Computing, click Elastic Cloud Server. 3. In the navigation pane, select Key Pair. 4. On the Key Pair page, click Create Key Pair. 5. Specify the key pair name. 6. Click OK. 7. In the displayed dialog box, click OK. You can view and save the private key according to the prompts. To ensure ECS security, the private key can be downloaded only once Creating a VPC Scenarios To provide a secure and isolated network environment for CCE, create a VPC before creating a cluster. If you already have a VPC, you do not need to create it again. Procedure 1. Log in to the management console. 2. Under Network, click Virtual Private Cloud. 3. On the Dashboard page, click Create VPC. 4. On the Create VPC page, set parameters as prompted. Table 2-9 Network configuration information Name VPC name. VPC-01 VPC CIDR Classless Inter-Domain Routing (CIDR) block for the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset (for multiple subnets in the VPC). The following CIDR blocks are supported: / / / /16 Name subnet name. subnet-01 CIDR Gateway subnet address range. This value must be within the VPC subnet. gateway address of the subnet / Issue 01 ( ) 16

17 5. Click Create Creating a Load Balancer Scenarios Create a load balancer to automatically distribute access traffic to multiple Docker nodes. Procedure 1. Log in to the management console. 2. Under Network, click Elastic Load Balancing. 3. On the displayed Elastic Load Balancing console, click Create Load Balancer. 4. On the displayed Create Load Balancer page, configure parameters as prompted. Table 2-10 Parameters of the Elastic Load Balancer Name Elastic Load Balancer name. elb-001 Type VPC Elastic IP Public Network Bandwidth Description network type. Public network: indicates that the load balancer is used in the public network. Private network: indicates that the load balancer is used in the private network. Select Public network for purposes related to this document. VPC to which the load balancer belongs. If you select Public network for Type, you can select an existing IP address or the newly added elastic IP address to create the load balancer. public network bandwidth size when the newly added elastic IP address is used. Provides a description of the load balancer. Public network VPC Node load balancer 5. Click Create Now. 6. Confirm the configuration and click Submit. Issue 01 ( ) 17

18 2.4.5 Creating a Container Cluster and Node Scenarios A container cluster consists of one or more nodes and is used for node management. Nodes are used for creating applications. Nodes in a container cluster are used to run containers. Every node is an ECS server with two Elastic Volume Service (EVS) disks and one elastic IP address (EIP). One disk is a 40-GB system data disk and the other disk is a user data disk. Prerequisites Procedure Your valid AK/SK file has been uploaded to CCE. For details about how to upload an AK/SK file, see Uploading an AK/SK File. A VPC has been created. For details about how to create a VPC, see Creating a VPC. An SSH key has been created. For details about how to create an SSH key, see Creating a Key Pair. 1. Log in to the management console. 2. Choose Computing > Cloud Container Engine. 3. In the left navigation pane, click Cluster Manager. 4. Click Create Container Cluster. 5. On the Create Container Cluster page, specify the parameters of the container cluster. Table 2-11 Cluster parameters Name cluster name. magento-cluster VPC Subnet VPC to which the cluster belongs. subnet to which the cluster belongs. VPC-01 subnet /24 Description Provides a description of the cluster. N/A 6. Click OK. If a tab with the name of the newly created container cluster is displayed, as shown in Figure 2-3, the container cluster has been successfully created. Issue 01 ( ) 18

19 Figure 2-3 Container cluster information 7. Click Add Node to add a node to the container cluster. 8. On the Add Node page, specify the parameters of the node to be added. Table 2-12 Node parameters Node Type node type. Computing II Specifications CPU and memory capacity of the node. By default, the operating system uses 340 MB of memory; the node agent on the first node of the container cluster uses 0.71 CPU cores and 170 MB of memory; and the node agent on each of the remaining nodes uses 0.4 CPU cores and 170 MB of memory. Containerized applications will use the remaining CPU and memory resources on the node. The minimum node specifications are 1 vcpu and 2 GB memory. The maximum node specifications are 32 vcpus and 128 GB memory. 2 vcpus 4 GB c2.large Quantity number of nodes. 1 Disk system disk size. 40 GB data disk size. 100 GB Key Pair Selects a key pair. KeyPair Click Add Now. 10. Confirm the specifications and click Submit. It takes 20 to 30 minutes to create a node. If the node status is Available, the node has been created successfully. Issue 01 ( ) 19

20 2.4.6 Creating a Component Template Scenarios A single containerized application consists of one or more components. Each component has one or more containers. After container images are uploaded, you can use the images to create a component template. When creating a component template from container images, specify the following: Network protocol Communications port Memory capacity CPU capacity Volume Environment variables Procedure 1. On the CCE console, choose Component Template > Create Component Template. The Create Component Template page is displayed. 2. On the Create Component Template page, specify the parameters of the component template to be created. Table 2-13 Parameters of the component template Template Name Container Image Network component template name. container image, including external and internal container images. External images are images in the Docker Hub. Internal images include public or private images. Select External container image for purposes related to this document. Set the container image address in the Docker Hub. To create an image, refer to Cloud Container Engine. communication protocol used by the component. magento-template weiyunick/magento TCP Port number of listening ports. 80 Memory memory size of a container. The unit is MB. 100 CPU CPU specifications of a Do not need to configure this Issue 01 ( ) 20

21 container (1000 mcores = 1 core). parameter in this solution. Support uncapped CPU Volumes Specifies whether a container supports using uncapped CPU resources. If yes, when the used CPU resources exceed the upper limit, the container occupies other CPU resources on the node where it resides. Retain the default settings. If only one container supports using uncapped CPU resources, the container can use all remaining resources on the node where it resides. If multiple containers support using uncapped CPU resources, these containers allocate the remaining resources of the node according to CPU specifications. For example, if container A has 100 mcores (CPU) and container B has 300 mcores (CPU), containers A and B occupy the remaining resources of the node at 1:3 ratio. Supports a maximum of 10 data volumes. Retain the default settings. Do not need to configure this parameter in this solution. Environment Variables Supports a maximum of 30 environment variables. Do not need to configure this parameter in this solution. 3. Click OK to complete the creation Creating a Containerized Application Scenarios A containerized application is created using a component template. Procedure 1. On the CCE console, choose App Manager > Create Containerized App. 2. On the Create Containerized App page, select Component template as the template type. 3. Select the container cluster name, and specify the containerized application name. The name magento-app is used as an example in this procedure. 4. Click Create Component. Issue 01 ( ) 21

22 5. On the Create Component page, specify component parameters. Table 2-14 Magento parameters Template Type App template: Created on the graphical orchestration designer. Component template: Created from a container image. When creating a component template from container images, specify the network protocol, communication port, memory capacity, CPU capacity, volume, and environment variables. Component template Container Cluster Selects an existing container cluster. magento-cluster App Name containerized application name. magento-app Template Name Selects an existing template. magento-template Component Name Node component name. The name contains lowercase letters, digits, and hyphens (-), starts with a lowercase letter, and does not exceed 24 characters. node to which the component belongs. Select the node created in Creating a Container Cluster and Node. magento-component magento-node-1 Name subnet name. subnet-01 Instances Service Name Public Service number of component instances. domain name of a containerized application. The containerized application accesses other containers using this domain name. Specifies whether the component supports external accesses. 1 magento-service Select this item. Service Type ELB or node port. LoadBalancer ELB Instance Selects a created ELB instance. elb Click OK to complete component creation. 7. Click OK to complete containerized application creation. Issue 01 ( ) 22

23 It takes about 3 to 5 minutes to create a containerized application. On the App Manager page, if the Status of the application magento-app is Running, the application has been created successfully. 8. On the list of containerized applications, click the name of magento-app or click Manage for magento-app. 9. On the Components tab page, click the icon next to any component of magento-app to show the component information. Click the Basic Info tab to view the service address, in which Public IP Address indicates the IP address of the created node Creating MySQL DB Instances Using RDS Scenarios Use RDS to create out-of-the-box, reliable, and scalable MySQL DB instances for your Magento e-commerce website. Create MySQL DB Instances Enable HA and set an automated backup policy. 1. Log in to the management console. 2. Under Database, click Relational Database Service. 3. Click Create DB Instance. 4. On the displayed Create DB Instance page, configure parameters as prompted. Table 2-15 Configuration items of the MySQL database instance Configuration Item Parameter Description Example Value Instance Specifications DB Instance Name database instance name. magento-db DB Engine Database Version DB Instance Class database type. database version. database instance type. s1: General-purpo se compute I c2: Compute-opti mized compute II m1: MySQL db.s1.medium -1vCPU, 4 GB Issue 01 ( ) 23

24 Configuration Item Parameter Description Example Value Memory-optim ized compute I Storage storage type and size. Common I/O 100 GB Network AZ For details about available AZs, visit ystems.com/en-us/ endpoint/index.ht ml. eu-de-02 VPC Subnet Security Group VPC to which the database instance belongs. subnet to which the database instance belongs. security group. Data can be synchronized between the active and standby databases only when the two databases are in the same security group. VPC-01 subnet-01 ( /2 4) Retain the default settings. Database Configuration Administrator Password password of the database administrator. HA HA Specifies whether to enable HA for the database subnet. The standby database improves cluster availability. If you need to create a standby database when creating Test@123 Enabled Issue 01 ( ) 24

25 Configuration Item Parameter Description Example Value database instances, enable the HA function. RDS HA instances use floating IP addresses. Backup Policy Automated Backup Specifies whether to enable data backup. The default value is Enabled. Retention Period (Days): period for retaining backup files. Backup Start Time: backup start time. Data backup will begin one hour after the configured backup start time. Enabled 1 01:00 5. Click Create Now. 6. Confirm the specifications and click Submit. After DB instances are created, you can view the DB instance information in the DB Instance List area on the Instance Mgmt page. Connection Address indicates the IP address and port number used to connect to the DB instances. Connecting to DB Instances and Creating a Magento Database 1. Create an ECS in the same VPC. For details on how to create an ECS and related operations, see the Elastic Cloud Server. 2. Log in to the ECS created in 1 and run the following command to connect to DB instances: mysql -u root -p -h DB instance IP address -P Port number Issue 01 ( ) 25

26 Obtain the DB instance IP address and port number from the DB instance information in step 6 in Create MySQL DB Instances. Sample command: mysql -u root -p -h P Run the following command to create a Magento database: create database magento 4. Run the following command to create user magento for the Magento database: create user 'magento'@'private IP address of the node where the application magento resides' identified by 'User password'; Obtain the private IP address of the node where the application magento resides as follows: a. On the CCE console, choose Cluster Manager. On the displayed page, click Nodes. b. Locate magento-node-1 and click to expand the node information to obtain Private IP Address. You are advised to set a user password different from Administrator Password set in 4 in Create MySQL DB Instances. Sample command: create user 'magento'@' ' identified by 'F#f123456'; 5. Run the following command to set RDS access permissions for the node where the application magento resides: grant all on magento.* to 'magento'@'private IP address of the node where the application magento resides'; 6. Run the following command to put the permissions into effect: flush privileges; Configuring AS Policies Scenarios Configure different AS policies for different Magento applications to suit different service requirements. Procedure 1. On the CCE console, click App Manager. 2. Click the name of the target Magento application. 3. Click the icon next to a component of the selected Magento application. 4. Choose Auto Scaling > Auto Scaling Policy. Configure parameters. For details, see Table Table 2-16 AS parameters Category Parameter Description Basic settings Minimum Instances Value range: 1 to N, where N is the total number of Issue 01 ( ) 26

27 Category Parameter Description instances that the Magento application has. Resource policy Maximum Instances Policy Name Value range: N to 100, where N is the total number of instances that the Magento application has. Name of the AS policy. The policy name must begin with a letter and contain only letters, digits, and underscores (_). Trigger Type If the parameter value is CPU, configure the number of instances for scaling based on service requirements. If the CPU usage is higher than 50 mcores, one instance will be automatically added. If the CPU usage is lower than 1 mcore, one instance will be automatically deleted. If the parameter value is Memory, configure the number of instances for scaling based on service requirements. If the memory usage is higher than 50 MB, one instance will be automatically added. If the memory usage is lower than 1 MB, one instance will be automatically deleted. Advanced settings Measurement Period Resource Adjustment Period Scale-Out Cool-Down Period Scale-In Cool-Down Period Measurement period over which resource usage is averaged. Value range: 30 to 1800 seconds. Period of time for which the average resource usage must remain above the upper limit or below the lower limit before the AS policy is triggered. This can reduce the number of scaling attempts when resource usage fluctuates. Value range: 60 to 3600 seconds. The cool-down period ensures that no new scale-out will be initiated while the current scale-out is underway. Value range: 600 to 3600 seconds. The cool-down period ensures that no new scale-in will be initiated while the current scale-in is underway. Value range: 600 to 3600 seconds. CCE measures resource usage every 10 seconds. For example, consider a scenario in which the measurement period is 60 seconds, the resource adjustment period is 300 seconds, the cool-down period between scale-outs is 1000 seconds, and the cool-down period between scale-ins is 2000 seconds. Every 10 seconds, the CCE measures the average resource usage over the previous 60 seconds. If the average resource usage remains above the upper limit or below the lower limit for Issue 01 ( ) 27

28 300 seconds, the AS policy is triggered. For 1000 seconds after a scale-out occurs, no additional scale-out will be triggered. For 2000 seconds after a scale-in occurs, no additional scale-in will be triggered. 5. Click Save Installing the Magento Website Scenarios After completing database and application creation, you can access the application node bound to an elastic IP address through the browser to complete the installation of your Magento website. Procedure 1. In the browser address bar, enter the elastic IP address from Creating a Load Balancer, and click Enter. 2. Complete the installation of your Magento website with reference to "Installing Magento CE or EE" in Installing and Verifying Magento Community Edition (CE) and Enterprise Edition (EE) at After the installation is complete, your Magento website homepage should look similar to the following figure. Figure 2-4 Magento website homepage Issue 01 ( ) 28

29 3 Relevant Documents 3 Relevant Documents When using the Web (CCE+RDS) solution, you can refer to the following documents: Virtual Private Cloud Cloud Container Engine Relational Database Service Elastic Load Balancing Elastic Cloud Server To configure your Magento website, refer to Installing and Verifying Magento Community Edition (CE) and Enterprise Edition (EE) and other related documentation at Issue 01 ( ) 29

30 A Change History A Change History Release Date What's New This issue is the first official release. Issue 01 ( ) 30

31 B Glossary B Glossary For details about the terms involved in this document, see Glossary. Issue 01 ( ) 31