US2025362950A1PendingUtilityA1

Public Cloud-Based Virtual Instance Configuration Method and Cloud Management Platform

Assignee: HUAWEI CLOUD COMPUTING TECH CO LTDPriority: Feb 9, 2023Filed: Aug 8, 2025Published: Nov 27, 2025
Est. expiryFeb 9, 2043(~16.5 yrs left)· nominal 20-yr term from priority
H04L 2101/668H04L 2101/659H04L 12/4633H04L 12/4641H04L 41/0897G06F 2009/45595H04L 61/5007H04L 41/0895G06F 9/45558H04L 41/0889H04L 41/0894
60
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

This application discloses a public cloud-based virtual instance configuration method and a cloud management platform, to simplify an operation of a tenant, quickly respond to a virtual instance creation requirement and an address management requirement of the tenant, and reduce time costs for the tenant, thereby improving user experience. The method in this application includes: After receiving configuration information that is of a to-be-created virtual instance and that is input by a first tenant, based on the configuration information, the cloud management platform may select a first site from a plurality of sites, select a first physical server from a plurality of physical servers at the first site, create a first virtual instance on the first physical server, and allocate an IPv6-format first network address to the first virtual instance.

Claims

exact text as granted — not AI-modified
1 . A public cloud-based virtual instance configuration method, wherein the method is applied to a cloud management platform, the cloud management platform is configured to manage an infrastructure that provides a public cloud service, the infrastructure comprises a plurality of sites, each site comprises a plurality of physical servers, and the method comprises:
 obtaining, from a virtual instance configuration interface, configuration information that is of a first virtual instance to-be-created and that is input by a first tenant, wherein the configuration information indicates a specification required by the first virtual instance, a first site at which the first virtual instance is located, and a first VPC in which the first virtual instance is located; and   based on the configuration information, selecting the first site from the plurality of sites, selecting, from a plurality of physical servers at the first site, a first physical server capable of providing the specification, creating the first virtual instance having the specification on the first physical server, and allocating an IPv6-format first network address to the first virtual instance, wherein the first virtual instance is deployed in the first VPC, the first network address is used to identify the first virtual instance in the first VPC, and an IPv6 prefix, an identifier of the first site, an identifier of the first physical server, and an identifier of the virtual instance are separately recorded in an IPv6 field of the first network address.   
     
     
         2 . The method according to  claim 1 , wherein the first VPC is located at the first site, and the method further comprises:
 configuring the first VPC to connect to a second VPC, wherein the second VPC is located at a second site in the plurality of sites; and   setting a first routing rule in a router in the second VPC, wherein the first routing rule comprises: forwarding an IPv6-format packet whose destination address comprises the first site to the first VPC.   
     
     
         3 . The method according to  claim 1 , wherein the method further comprises:
 setting a second routing rule in a router in the first VPC, wherein the second routing rule comprises: forwarding an IPv6-format packet whose destination address comprises the second site to the second VPC.   
     
     
         4 . The method according to  claim 1 , wherein the first network address is an IPv6-format ULA address. 
     
     
         5 . The method according to  claim 4 , wherein the method further comprises:
 allocating an IPv6-format second network address to the first virtual instance, wherein the second network address is an IPv6-format GUA address, and the second network address is used to identify the first virtual instance in a public network.   
     
     
         6 . The method according to  claim 1 , wherein the first network address is an IPv6-format GUA address, and the first network address is used to identify the first virtual instance in both the first VPC and a public network. 
     
     
         7 . The method according to  claim 1 , wherein the method further comprises:
 recording a correspondence between an IPv4 address of each physical server at each site and an IPv6 address segment in which the physical server is located, wherein an identifier of the site at which the physical server is located, an identifier of the physical server, and an identifier of a virtual instance running on the physical server are recorded in the IPv6 address segment in which the physical server is located; and   notifying the first physical server to use an IPv4 address of the first physical server as an outer source address of a nested packet, use an IPv4 address of a second physical server as an outer destination address of the nested packet, use the first network address as an inner source address of the nested packet, use a network address of a second virtual instance as an inner destination address of the nested packet, and send the nested packet to the second physical server, wherein an inner packet of the nested packet is an IPv6 packet sent by the first virtual instance to the second virtual instance, and the second virtual instance is deployed on the second physical server.   
     
     
         8 . The method according to  claim 1 , wherein the method further comprises:
 migrating the first virtual instance from the first physical server to the second physical server, and allocating an IPv6-format third network address to the first virtual instance to replace the first network address, wherein an IPv6 prefix, an identifier of a site at which the second physical server is located, an identifier of the second physical server, and the identifier of the first virtual instance are recorded in the third network address.   
     
     
         9 . The method according to  claim 1 , wherein the first virtual instance comprises a virtual machine or a container. 
     
     
         10 . The method according to  claim 1 , wherein the plurality of sites are a plurality of availability zones in a public cloud, a plurality of regions in the public cloud, or at least one edge site and at least one central cloud site. 
     
     
         11 . A computing device cluster, wherein the computing device cluster comprises at least one computing device, and each computing device comprises a processor and a memory, wherein
 the memory is configured to store instructions; and   the processor is configured to enable, according to the instructions, the computing device cluster to:   obtain, from a virtual instance configuration interface, configuration information that is of a to-be-created virtual instance and that is input by a first tenant, wherein the configuration information indicates a specification required by the first virtual instance, a first site at which the first virtual instance is located, and a first VPC in which the first virtual instance is located; and   based on the configuration information, select the first site from the plurality of sites, select, from a plurality of physical servers at the first site, a first physical server capable of providing the specification, create the first virtual instance having the specification on the first physical server, and allocate an IPv6-format first network address to the first virtual instance, wherein the first virtual instance is deployed in the first VPC, the first network address is used to identify the first virtual instance in the first VPC, and an IPv6 prefix, an identifier of the first site, an identifier of the first physical server, and an identifier of the virtual instance are separately recorded in an IPv6 field of the first network address.   
     
     
         12 . The computing device cluster according to  claim 11 , wherein the first VPC is located at the first site, and the processor is configured to enable, according to the instructions, the computing device cluster to:
 configure the first VPC to connect to a second VPC, wherein the second VPC is located at a second site in the plurality of sites; and   set a first routing rule in a router in the second VPC, wherein the first routing rule comprises: forwarding an IPv6-format packet whose destination address comprises the first site to the first VPC.   
     
     
         13 . The computing device cluster according to  claim 11 , wherein the processor is configured to enable, according to the instructions, the computing device cluster to:
 set a second routing rule in a router in the first VPC, wherein the second routing rule comprises: forwarding an IPv6-format packet whose destination address comprises the second site to the second VPC.   
     
     
         14 . The computing device cluster according to  claim 11 , wherein the first network address is an IPv6-format ULA address. 
     
     
         15 . The computing device cluster according to  claim 14 , the processor is configured to enable, according to the instructions, the computing device cluster to:
 allocate an IPv6-format second network address to the first virtual instance, wherein the second network address is an IPv6-format GUA address, and the second network address is used to identify the first virtual instance in a public network.   
     
     
         16 . The cloud management platform according to  claim 11 , wherein the first network address is an IPv6-format GUA address, and the first network address is used to identify the first virtual instance in both the first VPC and a public network. 
     
     
         17 . The computing device cluster according to  claim 11 , wherein the processor is configured to enable, according to the instructions, the computing device cluster to:
 record a correspondence between an IPv4 address of each physical server at each site and an IPv6 address segment in which the physical server is located, wherein an identifier of the site at which the physical server is located, an identifier of the physical server, and an identifier of a virtual instance running on the physical server are recorded in the IPv6 address segment in which the physical server is located; and   notify the first physical server to use an IPv4 address of the first physical server as an outer source address of a nested packet, use an IPv4 address of a second physical server as an outer destination address of the nested packet, use the first network address as an inner source address of the nested packet, use a network address of a second virtual instance as an inner destination address of the nested packet, and send the nested packet to the second physical server, wherein an inner packet of the nested packet is an IPv6 packet sent by the first virtual instance to the second virtual instance, and the second virtual instance is deployed on the second physical server.   
     
     
         18 . The computing device cluster according to  claim 11 , wherein the processor is configured to enable, according to the instructions, the computing device cluster to:
 migrate the first virtual instance from the first physical server to the second physical server, and allocate an IPv6-format third network address to the first virtual instance to replace the first network address, wherein an IPv6 prefix, an identifier of a site at which the second physical server is located, an identifier of the second physical server, and the identifier of the first virtual instance are recorded in the third network address.   
     
     
         19 . The computing device cluster according to  claim 11 , wherein the first virtual instance comprises a virtual machine or a container. 
     
     
         20 . The computing device cluster according to  claim 11 , wherein the plurality of sites are a plurality of availability zones in a public cloud, a plurality of regions in the public cloud, or at least one edge site and at least one central cloud site.

Join the waitlist — get patent alerts

Track US2025362950A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.