Deploying a Static Web Application Using CCI

Procedure

Preparations

• Before you start, sign up for a HUAWEI id and complete real-name authentication. For details, see Signing Up for a HUAWEI ID and Enabling Huawei Cloud Services and Getting Authenticated.

Step 1: Build an Image and Upload It to the SWR Image Repository

To deploy an application on CCI, build an image for the application and push it to the image repository. Then you can pull the image when creating a workload on CCI.

For details, see Uploading an Image.

Step 2: Create a Namespace

1. Log in to the CCI console.
2. Choose Namespaces in the navigation pane and then click Create in the General-computing namespace area.
3. Enter a namespace name.
   Select an existing VPC or create one. You must specify a CIDR block for the new VPC. The recommended CIDR blocks are 10.0.0.0/8-22, 172.16.0.0/12-22, and 192.168.0.0/16-22.

   NOTICE:

   The VPC CIDR block and subnet CIDR block cannot be set to 10.247.0.0/16 because this CIDR block is reserved by CCI for workload access. If you use this CIDR block, IP address conflicts may occur, which may result in workload creation failures or service unavailability. If you do not need to access pods through workloads, you can allocate this CIDR block to a VPC.

4. Configure a subnet CIDR block.

   Ensure sufficient available IP addresses to create workloads.

5. Click Create.

Step 3: Create a Workload

1. Log in to the CCI console.
2. In the navigation pane, choose Workloads > Deployments. On the page displayed on the right, click Create from Image.
3. Specify basic information.
   • Workload Name: Enter a workload name, for example, deployment-2048.
   • Namespace: Select an existing namespace.
   • Pods: Change the value to 1 in this example.
   • Pod Specifications: Select the general-computing pod with 0.5-core CPU and 1 GiB of memory.
   • Container Settings

     On the My Images tab page, select the uploaded 2048 image.

     Figure 1 Container settings
     

4. Configure workload access settings.
   Three options are available:

   • Do not use: No entry is provided to allow access from other workloads. This option is ideal for computing scenarios where communication with external systems is not required.
   • Intranet access: There are two ways to allow the workload to be accessed by other workloads over the private network.
   • Internet access: The workload is accessed from public networks through load balancers.

   In this example, set the workload access option to Internet access to allow access to the 2048 workload using the EIP and port of the load balancer.

   Set Service Name to deployment-2048, and select a load balancer. If no load balancer is available, click Create Shared Load Balancer to create one.

   Set Ingress Name to ingress-2048, ELB Protocol to HTTP/HTTPS, and ELB Port to HTTP 8080.

   

   Set Workload Access Port to 80 (or another port) and Container Port to 80. The container port must be set to 80, which is the same port set for the 2048 image in the image repository.

   Set Mapping Path to / and associate it with the workload access port so that you can access the 2048 workload using [Load balancer IP address]:[Port].

   

5. Click Next: Configure Advanced Settings. After you confirm the configuration, click Submit. Then click Back to Deployment List.

   In the workload list, if the workload status is Running, the workload is created successfully.

   

Step 4: Access the Workload

After the 2048 workload is created, you can access it using a browser.

1. Click the workload name to enter its details page.
2. Click in the Public Network Access Address column under Access Settings to copy the public network access address.

   

3. Paste the address in the browser address bar to access it.

Step 5: Clear Resources

1. In the navigation pane, choose Workloads > Deployments. On the Deployments tab, click to delete the 2048 workload.
   NOTE:

   To delete the load balancer used by a Service or ingress, delete the Service or ingress on the CCI console, and then delete load balancer on the ELB console.