WO2023138032A1 - 一种地址空间推荐方法、装置及相关设备 - Google Patents

一种地址空间推荐方法、装置及相关设备 Download PDF

Info

Publication number
WO2023138032A1
WO2023138032A1 PCT/CN2022/110403 CN2022110403W WO2023138032A1 WO 2023138032 A1 WO2023138032 A1 WO 2023138032A1 CN 2022110403 W CN2022110403 W CN 2022110403W WO 2023138032 A1 WO2023138032 A1 WO 2023138032A1
Authority
WO
WIPO (PCT)
Prior art keywords
address space
address
vpc
recommendation
relationship
Prior art date
Application number
PCT/CN2022/110403
Other languages
English (en)
French (fr)
Inventor
杨增印
朱小平
Original Assignee
华为云计算技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为云计算技术有限公司 filed Critical 华为云计算技术有限公司
Publication of WO2023138032A1 publication Critical patent/WO2023138032A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/953Querying, e.g. by the use of web search engines
    • G06F16/9535Search customisation based on user profiles and personalisation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5046Resolving address allocation conflicts; Testing of addresses

Definitions

  • the present application relates to the technical field of the Internet, in particular to an address space recommendation method, device and related equipment.
  • VPC virtual private cloud
  • IPV4 Internet Protocol Version 4
  • IPV6 Internet Protocol Version 6
  • Embodiments of the present application provide an address space recommendation method, device, and related equipment to reduce the difficulty of configuring a VPC, improve configuration efficiency, and reduce the possibility of errors in address space configuration.
  • the embodiment of the present application provides an address space recommendation method, which can be performed, for example, by an address space recommendation device.
  • the address space recommendation device when recommending an available address space for a VPC, the address space recommendation device first obtains an address space recommendation request for a first VPC sent by a client.
  • the address space recommendation request includes an identifier of a first alliance relationship, and then responds to the address space recommendation request to determine a first address space that is different from a second address space corresponding to a second VPC.
  • the first VPC and the second VPC have the first alliance relationship, so that the determined first address space and the second address space do not overlap.
  • the address space recommending device outputs the first address space to the client.
  • the address space recommending device can automatically recommend for the VPC the first address space that does not have address conflicts with other VPCs in the alliance relationship, so that the user does not need to manually configure the address space for the VPC. In this way, it not only reduces the difficulty for users to configure VPC and improves configuration efficiency, but also configures VPC based on the automatically recommended first address space, which can effectively reduce the possibility of VPC configuration errors and help establish the interconnection relationship between this VPC and other VPCs.
  • the address space recommendation request further includes an address constraint condition, for example, the address constraint condition can be specified by the user, and the determined first address space satisfies the address constraint condition.
  • the first address space automatically recommended for the user not only does not overlap with the address spaces corresponding to other VPCs in the federation relationship, but also meets the user's requirements, such as meeting the user's requirements in terms of address space size and address prefixes.
  • the address constraint condition is used to indicate the size of the address space
  • the address space recommendation device may specifically determine the first available address space and the second available address space in the first alliance relationship according to the identifier of the first alliance relationship in the address space recommendation request, the size of the first available address space is smaller than the size of the second available address space, and then preferentially determine the first address space from the first available address space according to the address constraint condition in the address space recommendation request.
  • the address space recommendation device can allocate the required address space from the relatively large second available address space, thereby improving the rationality of address space allocation and the utilization rate of the address space.
  • the address space recommending device may further provide a configuration interface, which may be presented to the user through the client, and then, the address space recommending device may respond to the user's configuration operation for the first VPC on the configuration interface, and obtain the identifier of the first alliance relationship and the address constraint condition.
  • the device for recommending address space can support users to flexibly configure VPCs in federation relationships and address constraint conditions, thereby improving user experience.
  • the address space recommendation request further includes the identifier of the second federation relationship, and the first address space determined by the address space recommending device not only does not overlap with the address spaces corresponding to the VPCs in the first federation relationship, but also does not overlap with the address spaces corresponding to the VPCs in the second federation relationship.
  • the address space recommending device is the address space automatically recommended by the VPC, and there may be no address conflict in the two federation relationships in communication.
  • the apparatus for recommending an address space may further provide a recommendation interface, the recommendation interface is presented to the user through the client, and the recommendation interface includes the first address space.
  • the apparatus for recommending an address space may present the determined first address space to the user, so as to improve user experience because the user knows the address space recommended for the VPC.
  • the address space recommendation device may also determine a second address space in response to the user's replacement operation on the first address space.
  • the second address space does not overlap with the first address space, and the second address space does not overlap with the address spaces corresponding to each VPC in the first federation relationship. Then, the address space recommendation device outputs the second address space to the client.
  • the address space recommendation device outputs the second address space to the client. In this way, after the user is dissatisfied with the previously recommended first address space, other available address spaces can be recommended to the user again, so that the re-recommended second address space can meet the user's use requirements, which can further facilitate the user to configure the address space of the VPC and improve user experience.
  • the embodiment of the present application provides an address space recommendation device.
  • the device has functions corresponding to each implementation manner for realizing the above-mentioned first aspect. This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a computing device, including: a processor and a memory; the memory is used to store instructions, and when the computing device is running, the processor executes the instructions stored in the memory, so that the computing device executes the address space recommendation method in the first aspect or any implementation of the first aspect.
  • the memory may be integrated in the processor, or independent of the processor.
  • the device may also include a bus. Wherein, the processor is connected to the memory through the bus.
  • the memory may include a readable memory and a random access memory.
  • the embodiment of the present application also provides a readable storage medium, in which a program or instruction is stored, and when it is run on a computer, the address space recommendation method in the above-mentioned first aspect or any implementation manner of the first aspect is executed.
  • the embodiment of the present application also provides a computer program product containing instructions, which, when run on a computer, cause the computer to execute any address space recommendation method in the first aspect or any implementation manner of the first aspect.
  • FIG. 1 is a schematic structural diagram of an exemplary address space recommendation system provided by an embodiment of the present application
  • FIG. 2 is a schematic flowchart of an address space recommendation method provided in an embodiment of the present application
  • FIG. 3 is a schematic diagram of an exemplary configuration interface provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of the IPV4 address format provided by the embodiment of the present application.
  • FIG. 5 is a schematic diagram of an exemplary recommendation interface provided by the embodiment of the present application.
  • FIG. 6 is a schematic diagram of another exemplary recommendation interface provided by the embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of an address space recommendation device provided in an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a hardware structure of a computing device provided by an embodiment of the present application.
  • an address space recommendation system 100 may include a client 101 and a service platform 102 . Moreover, data interaction can be performed between the client 101 and the service platform 102, such as data communication through Hypertext Transfer Protocol (Hypertext Transfer Protocol, HTTP) or other network protocols.
  • HTTP Hypertext Transfer Protocol
  • the client 101 may be a web browser provided by the service platform 102 for interacting with users; or, the client 101 may be an application program (application) running on a user terminal.
  • the service platform 102 can be constructed by one or more computing devices (such as servers, etc.), and in actual application, the service platform 102 can also include other devices such as storage devices.
  • a service platform 102 is constructed by using multiple servers as an example for illustration, and a user can create a VPC or microservices (microservices) on the service platform 102 through a client 101 .
  • VPC refers to the private network created by the user.
  • the isolated VPCs are not interconnected, and the address space can completely overlap, but there is no overlap in the address space between the interconnected VPCs.
  • Microservices refer to small services that are built based on business and can be deployed independently. One or more microservices can constitute an application.
  • VPC Taking creating a VPC as an example, when a new VPC is created on the service platform 102 and the created VPC is interconnected with other VPCs, the user usually needs to manually configure an address space for the VPC through the client 101, and the configured address space does not overlap with the address space used by other VPCs, so as to avoid address conflicts and affect data communication between VPCs.
  • the newly created VPC there may be many other VPCs interconnected with the newly created VPC. This requires users to know the address spaces corresponding to many VPCs, and manually analyze the address space that does not overlap with the address space used by each VPC, so as to configure the address space for the newly created VPC.
  • This method of manually configuring the available address space for the VPC is not only difficult and inefficient, but also prone to errors in configuring the address space of the VPC, such as overlapping with the address space used by one of the VPCs, which affects the establishment of interconnection relationships between the VPC and other VPCs.
  • an embodiment of the present application provides an address space recommendation method, which can be executed by an address space recommendation device 103 , and the address space recommendation device 103 can be deployed in the service platform 102 .
  • the address space recommendation device 103 may be implemented by software or hardware.
  • the address space recommending device 103 may be a computer program running on a computing device, such as a software development kit (software development kit, SDK).
  • the address space recommending means 103 may be a computing device such as a server, and a computer program runs on the computing device, so that the address space recommending means 103 has the function of automatically recommending an address space.
  • the address space recommending device 103 may be implemented by using an application-specific integrated circuit (application-specific integrated circuit, ASIC), or a device implemented by a programmable logic device (programmable logic device, PLD).
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be implemented by complex programmable logic device (complex programmable logical device, CPLD), field-programmable gate array (field-programmable gate array, FPGA), general array logic (generic array logic, GAL) or any combination thereof.
  • the service platform 102 may receive an address space recommendation request for the VPC sent by the client 101, and the address space recommendation request carries an identifier of the alliance relationship to which the VPC belongs. Then, the service platform 102 can call the address space recommendation device 103 to respond to the address space recommendation request, determine the first address space in the alliance relationship that is different from the second address spaces corresponding to other VPCs, and output the first address space to the client 101, so as to automatically recommend available address spaces for newly created/updated VPCs.
  • the first address space in the consortium relationship that does not conflict with other VPCs can be automatically recommended for the VPC, so that the user does not need to manually configure the address space for the VPC. In this way, it not only reduces the difficulty for users to configure VPC and improves configuration efficiency, but also configures VPC based on the automatically recommended first address space, which can effectively reduce the possibility of VPC configuration errors and help establish the interconnection relationship between this VPC and other VPCs.
  • the address space recommendation device 103 is deployed on the service platform 102 as an example. In actual application, the address space recommendation device 103 may also be deployed independently of the service platform 102, as shown in FIG. 1 .
  • the service platform 102 can generate an address space recommendation request, send it to the address space recommendation device 103, and send the first address space fed back by the address space recommendation device 103 to the client 101, so as to automatically recommend an available address space for the VPC.
  • a database can be configured inside or outside the service platform 102, wherein the database configured inside the service platform 102 can be called a local database, and the database configured outside the service platform 102 can be called a cloud database, and the local database or the cloud database can be used to store data, such as storing VPC information included in each alliance relationship, remaining available address space corresponding to each alliance relationship, and the like.
  • the address space recommendation system 100 may also include more devices with other functions to provide the service platform 102 with more abundant functions, which is not limited in this embodiment.
  • FIG. 2 it is a schematic flowchart of an address space recommendation method in an embodiment of the present application.
  • the method can be applied to the address space recommendation system 100 shown in FIG. 1 and can be executed by the address space recommendation device 103 in the address space recommendation system 100. In actual application, the method can also be applied to other applicable address space recommendation systems.
  • the method is executed by the address space recommending device 103 as an example for illustration below.
  • the method may specifically include:
  • the address space recommendation module 103 acquires an address space recommendation request for the first VPC sent by the client 101, where the address space recommendation request includes an identifier of the first alliance relationship.
  • the service platform 102 can determine an available address space for the VPC through the address space recommendation means 103 .
  • the service platform 102 may provide the client 101 with an operation interface, and present the operation interface to the user through the client 101 .
  • users can apply for creating or updating a VPC on the operation interface.
  • the VPC requested by the user to be created or updated is referred to as the first VPC below.
  • the service platform 102 may provide the client 101 with a configuration interface, so that the interface presented by the client 101 is switched from the above operation interface to the configuration interface.
  • the user can perform a corresponding configuration operation for the first VPC on the configuration interface, and obtain the identity of the alliance relationship to which the first VPC belongs.
  • the configuration interface presented by the client 101 may be as shown in FIG. 3 , on which the user may input the name of the first federation relationship to which the first VPC to be created belongs.
  • the first alliance relationship may include one or more VPCs, and the first alliance relationship may be created by the user, or pre-created by other users.
  • the user can also create the first alliance relationship on the configuration interface, such as creating a new alliance relationship by clicking the "new alliance relationship" control on the configuration interface.
  • the first VPC can be interconnected with other VPCs in the first federation relationship.
  • any VPCs belonging to the same federation relationship can be interconnected, and correspondingly, address spaces used by different VPCs under the federation relationship do not overlap.
  • the address space assigned to the first VPC does not overlap with the second address space of the remaining VPCs in the first federated relationship (hereinafter referred to as the second VPC), so as to avoid affecting communication between the first VPC and the second VPC.
  • the client 101 may send the identifier of the first alliance relationship configured by the user to the service platform 102, and the service platform 102 generates an address space recommendation request including the identifier of the first alliance relationship, and sends it to the address space recommendation device 103, so as to request the address space recommendation device 103 to determine an available address space for the first VPC.
  • the address space refers to one or more IP addresses based on the Internet Protocol (Internet Protocol, IP), which may specifically be an IPV4 address and/or an IPV6 address.
  • IP Internet Protocol
  • the user can also perform basic configuration on the first VPC on the configuration interface, as shown in Figure 3, the user can configure the name of the VPC and the availability zone (availability zone) or region (region) included in the VPC.
  • the user may also input address constraints on the configuration interface to restrict the available address range of the first VPC.
  • the address constraint condition may indicate, for example, the size of the address space, and/or indicate a fixed prefix of the address, and the like.
  • the user may input the address prefix corresponding to the first VPC on the configuration interface shown in FIG. 3 to fix the prefixes of the addresses configured for the first VPC by the service platform 102 .
  • the user can configure the prefix of the IPV4 address corresponding to the first VPC as "192.16.X.X", so that the prefixes of the IPV4 addresses configured by the follow-up service platform 102 for the first VPC are all the same, such as 192.16.0.0 ⁇ 192.16.255.255.
  • the user can also configure other information for the first VPC on the configuration interface, such as the size of the address space, address type (such as IPV4 address, IPV6 address), etc., which is not limited in this embodiment.
  • the address space recommendation module 103 determines a first address space different from a second address space corresponding to a second VPC in response to the address space recommendation request, and the first VPC and the second VPC have the first alliance relationship.
  • S203 The address space recommending device 103 outputs the first address space to the client 101.
  • the address space recommending device 103 may respond to the received address space recommendation request, parse out the identifier of the first alliance relationship, and find out the available address space corresponding to the first alliance relationship.
  • the available address space refers to the address space that does not overlap with the address space used by any VPC in the first confederation relationship. In this way, the address space recommending means 103 can determine the first address space from available addresses, and allocate it to the first VPC.
  • the first federation relationship includes VPC1 and VPC2
  • all the IPV4 address spaces that can be allocated to the first federation relationship are 128.1.0.1 ⁇ 191.254.255.254
  • the IPV4 address space allocated to VPC1 is 128.1.0.1 ⁇ 150.255.255.255
  • the IPV4 address space allocated to VPC2 is 151.0.0. 0 ⁇ 160.255.255.255, at this time, the remaining available IPV4 address space is 161.0.0.0 ⁇ 191.254.255.254.
  • the service platform 102 may allocate 161.0.0.0-165.254.255.254 as the first address space from the remaining available IPV4 address space 161.0.0.0-191.254.255.254 to the first VPC.
  • the first address space determined by the address space recommending device 103 may not overlap with the address space used by each VPC in the first alliance relationship.
  • the different address spaces described in step S202 specifically mean that the first address space and the second address space do not overlap, so as to avoid address conflicts between the first VPC and the second VPC.
  • the available address space corresponding to the first alliance relationship may be stored in a first database (data base, DB), and the first database may be deployed locally on the service platform 102, so that the address space recommendation device 103 may obtain the available address space corresponding to the first alliance relationship by accessing the local database of the data platform 102.
  • the first database may also be deployed independently of the service platform 102, such as deployed on the cloud, which is not limited in this embodiment.
  • the address space recommending means 103 may allocate a fixed-size address space for the VPC, or the address space recommending means 103 may also be specified by the user by configuring address constraints. For example, when the user inputs an address constraint condition on the configuration interface, if the address constraint condition indicates the size of the address space allocated to the first VPC (that is, the number of addresses included), the address space recommending means 103 may determine the first address space of a corresponding size from the available address spaces corresponding to the first alliance relationship.
  • the address space recommending device 103 may also use a greedy algorithm to determine the first address space allocated to the first VPC, so as to reduce the fragmentation rate of the available address space corresponding to the first federation relationship.
  • the available address space corresponding to the first federation relationship may include multiple discontinuous address segments, so that the address space recommending device 103 may preferentially allocate the first address space to the first VPC from smaller address segments.
  • the address space recommending means 103 may preferentially determine the first address space allocated to the first VPC from the first available address space according to the address constraint condition. In this way, when other VPCs subsequently created/updated need to be configured with a larger address space, the address space recommending device 103 can allocate the required address space from the relatively large second available address space, thereby improving the rationality of address space allocation and the utilization rate of the address space.
  • the address constraint condition configured by the user may also indicate the address prefix assigned to the first VPC, so that the address space recommending means 103 may determine the first address space that satisfies the address prefix indicated by the address constraint condition from the available address spaces, so as to meet the user's requirements for the address space.
  • the address prefix specified by the user can be used as the identifier of the user's private network address segment.
  • the address prefix can also identify the AZ or zone that implements the VPC. Taking an IPV4 address as an example, each IPV4 address allocated to the first VPC can be represented by 32 bits, as shown in FIG. 4 .
  • the first digit to the Yth digit is the prefix of the IPV4 address
  • the first digit to the Xth digit (X is a positive integer greater than 1) can be used to identify the user's private network address segment
  • the X+1th digit to the Yth digit can be used to identify the AZ/zone that implements the VPC
  • Y is a positive integer greater than or equal to X.
  • the prefix of each IPV4 address may carry the identification information of AZ or partition; and when Y is equal to X, the prefix of each IPV4 address may not need to identify the AZ or partition.
  • the address space recommending means 103 may also preferentially determine a suitable address space for the first VPC from a smaller address segment based on a greedy algorithm.
  • the address space recommendation device 103 is used as an example to determine the first address space when creating/updating the first VPC in an alliance relationship.
  • the service platform 102 can create/update different VPCs in multiple different alliance relationships for users.
  • the address space recommending means 103 can determine the address space allocated to the VPC in a manner similar to the above, and the allocated address space does not overlap with the address space allocated to other VPCs in the federation relationship. It is worth noting that there may not be interconnection between VPCs in different federation relationships, that is, VPCs in different federation relationships may be isolated from each other.
  • the allocatable address spaces corresponding to each federation relationship may overlap.
  • all available IPV4 address spaces corresponding to alliance relationship 1 may be 128.1.0.1-191.254.255.254
  • all available IPV4 address spaces corresponding to alliance relationship 2 may also be 128.1.0.1-191.254.255.254.
  • the IPV4 address space allocated by the address space recommending device 103 for the VPCa may be 128.1.0.1-150.255.255.255; .
  • VPCs in different federation relationships may be interconnected through some VPCs.
  • the address space recommendation request includes the identifiers of the first federation relationship and the second federation relationship, it indicates that the first VPC belongs to both the first federation relationship and the second federation relationship.
  • the first address space allocated to the first VPC by the address space recommending device 103 not only does not overlap with the address spaces corresponding to the VPCs in the first federation relationship, but also does not overlap with the address spaces corresponding to the VPCs in the second federation relationship.
  • VPCc 1 can interconnect with VPCa 1 and VPCa 2
  • VPCc 2 can interconnect with VPCb 1 and VPCb 2 . In this way, data interaction between two alliance relationships can be realized.
  • the address space allocated by the address space recommending device 103 for the VPCc 1 not only does not overlap with the address spaces allocated to VPCa 1 and VPCa 2 in the federation relationship 1, but also does not overlap with the address spaces allocated to VPCb 1 and VPCb 2 in the federation relationship 1.
  • the address space recommendation system 100 can also manage information of multiple alliance relationships.
  • a second database may also be deployed in the address space recommendation system 100, and the second database may be deployed locally on the service platform 102 or in the cloud, and the second database may be used to store information related to each alliance relationship, such as the identification of the alliance relationship, the identification of each VPC in the alliance relationship, the user to which the VPC belongs, the address space to which the VPC is allocated, etc., so that the address space recommendation system 100 can access the second database to obtain relevant information about the alliance relationship belonging to each user, so as to operate and maintain the VPC belonging to each user according to the information, which is convenient for users Query information about the alliance relationship.
  • the address space recommendation means 103 After the address space recommendation means 103 outputs the first address space, it can feed it back to the service platform 102, so that the service platform 102 can directly configure the address space of the first VPC as the first address space, and present the first address space to the user through the client 101, so that the user can know the address space configured by the service platform 102 for the first VPC.
  • the user before determining to configure the address space for the first VPC, the user may also determine whether the address space of the first VPC is the first address space. Specifically, this embodiment may also include:
  • the service platform 102 provides a recommendation interface, the recommendation interface is presented to the user through the client 101, and the recommendation interface includes the first address space output by the address space recommendation device 103.
  • the service platform 102 may provide a recommendation interface as shown in FIG. 5 , where the recommendation interface includes the first address space recommended to the user. Meanwhile, the recommendation interface may further include a "confirm" control and a "recommend” control.
  • the recommendation interface shown in FIG. 5 and the configuration interface shown in FIG. 3 can be two independent interfaces, or can be combined into one interface.
  • the user can also view the address space automatically recommended by the address space recommendation system 100 when configuring the first VPC to be created/updated on this interface, which is not limited in this embodiment.
  • the service platform 102 determines that the address space of the first VPC is configured as the first address space; and when the user clicks the "recommend" control on the recommendation interface (such as the currently recommended first address space does not meet the user's future planning for the address space, etc.), the service platform 102 can instruct the address space recommendation device 103 to re-determine the address space for the first VPC.
  • the address space recommending device 103 may further perform the following steps:
  • the address space recommendation device 103 determines a second address space in response to the user's replacement operation on the first address space, where the second address space does not overlap with the first address space, and the second address space does not overlap with the address spaces corresponding to the VPCs in the first federation relationship.
  • the address space recommending device 103 outputs the second address space to the client 101.
  • the user's replacement operation for the first address space may be, for example, the above-mentioned operation of clicking "recommend" the space, or other operations that trigger the address space recommendation device 103 to re-recommend the address space, which is not limited in this embodiment.
  • the address space recommending means 103 may re-find a second address space that does not overlap with the first address space from the available address spaces corresponding to the first alliance relationship.
  • the specific implementation manner of determining the second address space by the address space recommending device 103 is similar to the specific implementation manner of the above-mentioned first determination of the target address space, and reference may be made to relevant descriptions in the foregoing embodiments. It should be noted that the rediscovered second address space still needs to meet the basic requirement that there is no overlap with the address spaces allocated by other VPCs in the federation relationship.
  • the user can also input address information (such as address prefix, address space size, address continuity, etc.) to the service platform 102, and the address space recommendation device 103 outputs a second address space that satisfies the address information, so that the re-recommended second address space can meet the user's expectations.
  • address information such as address prefix, address space size, address continuity, etc.
  • the service platform 102 may present the second address space in the recommendation interface shown in FIG. 5 or FIG. 6, so that the user can further determine whether to configure the address space of the first VPC as the second address space.
  • the service platform 102 determines to configure the address space of the first VPC as the second address space; and when the user clicks the "recommend" control on the recommendation interface, the service platform 102 can recommend a new address space for the user again.
  • the address space recommending device 103 may also reclaim the address space, specifically, release the address space allocated to the first VPC, and add it to the first database as an available address space. In this way, when a subsequent user creates or updates a VPC, the address space recommendation means 103 can allocate the address space to the VPC to be created or updated from the first database.
  • the address space recommendation device 103 and the service platform 102 are used as two independent entities to illustrate the implementation process of automatic address space recommendation.
  • the address space recommendation device 103 may also be deployed on the service platform 102. At this time, some or all of the actions performed by the service platform 102 in the above embodiments are specifically performed by the address space recommendation device 103, which is not limited in this embodiment.
  • the address space recommending device 103 is used as an example to automatically recommend available address spaces for a VPC.
  • the address space recommending device 103 may also automatically recommend available address spaces for microservices requested by users to create or update.
  • the specific implementation method is similar to the specific process of automatically recommending available address spaces for a VPC introduced in the above-mentioned embodiments. Refer to the above-mentioned process for understanding, and details will not be repeated here.
  • the embodiment of the present application also provides an address space recommendation device, which can implement the function of the address space recommendation device 103 in the embodiment shown in FIG. 2 above.
  • the address space recommendation device 700 may include:
  • the communication module 701 is configured to obtain an address space recommendation request for the first virtual private cloud VPC sent by the client, where the address space recommendation request includes the identifier of the first alliance relationship;
  • a determining module 702 configured to, in response to the address space recommendation request, determine a first address space different from a second address space corresponding to a second VPC, where the first VPC and the second VPC have the first alliance relationship;
  • the communication module 701 is further configured to output the first address space to the client.
  • the address space recommendation request further includes an address constraint condition, and the first address space satisfies the address constraint condition.
  • the address constraint condition is used to indicate the size of the address space
  • the determining module 701 is configured to:
  • the first address space is determined from the first available address space according to the address constraints in the address space recommendation request.
  • the address space recommending apparatus 700 further includes:
  • the information obtaining module 704 is configured to obtain the identifier of the first federation relationship and the address constraints in response to the user's configuration operation on the configuration interface for the first VPC.
  • the address space recommendation request further includes an identifier of the second alliance relationship
  • the first address space does not overlap with the address spaces corresponding to the VPCs in the first federation relationship, and the first address space does not overlap with the address spaces corresponding to the VPCs in the second federation relationship.
  • the address space recommending apparatus 700 further includes:
  • the providing module 703 is configured to provide a recommendation interface, the recommendation interface is presented to the user through the client, and the recommendation interface includes the first address space.
  • the determination module 702 is further configured to determine a second address space in response to the user's replacement operation on the first address space, the second address space does not overlap with the first address space, and the second address space does not overlap with the address spaces corresponding to the VPCs in the first federation relationship;
  • the communication module 701 is further configured to output the second address space to the client.
  • the address space recommending apparatus 700 in this embodiment corresponds to the address space recommending method shown in FIG. 2 . Therefore, for the specific realization and technical effects of each functional module in the address space recommending apparatus 700 in this embodiment, refer to the relevant descriptions in the embodiment shown in FIG. 2 , and details are not repeated here.
  • the embodiment of the present application further provides a computing device.
  • the computing device 800 may include a communication interface 810 and a processor 820 .
  • the computing device 800 may further include a memory 830 .
  • the memory 830 may be set inside the computing device 800 , and may also be set outside the computing device 800 .
  • each action performed by the address space recommending apparatus 103 in the embodiment shown in FIG. 2 may be implemented by the processor 820 .
  • the processor 820 may obtain the address space recommendation request through the communication interface 810, and use it to implement any method performed in FIG. 2 .
  • each step of the processing flow may implement the method executed in FIG.
  • the program codes executed by the processor 820 to implement the above methods may be stored in the memory 830 .
  • the memory 830 is connected to the processor 820, such as a coupled connection.
  • Some features of the embodiments of the present application may be implemented/supported by the processor 820 executing program instructions or software codes in the memory 830 .
  • the software components being loaded on the memory 830 can be summarized functionally or logically, for example, the determining module 702, the providing module 703, and the information obtaining module 704 shown in FIG. 7 .
  • the function of the communication module 701 can be realized by the communication interface 810 .
  • Any communication interface involved in the embodiments of the present application may be a circuit, a bus, a transceiver, or any other device that can be used for information exchange.
  • the communication interface 810 in the computing device 800 for example, the other device may be a device connected to the computing device 800 .
  • the processors involved in the embodiments of the present application may be general-purpose processors, digital signal processors, application-specific integrated circuits, field programmable gate arrays or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components, and may implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.
  • a general purpose processor may be a microprocessor or any conventional processor or the like.
  • the steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, modules or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, modules or modules.
  • the processor may operate in conjunction with the memory.
  • the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (solid-state drive, SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (random-access memory, RAM).
  • a memory is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the embodiment of the present application does not limit the specific connection medium among the communication interface, the processor, and the memory.
  • the memory, the processor, and the communication interface can be connected through a bus.
  • the bus can be divided into address bus, data bus, control bus and so on.
  • the embodiments of the present application also provide a computer storage medium, in which a software program is stored, and when the software program is read and executed by one or more processors, it can implement the method performed by the address space recommendation device 103 provided in any one or more of the above embodiments.
  • the computer storage medium may include: various media capable of storing program codes such as U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk.
  • an embodiment of the present application further provides a chip, which includes a processor, configured to implement the functions of the address space recommendation device 103 involved in the above embodiments, for example, to implement the method performed by the address space recommendation device 103 in FIG. 2 .
  • the chip further includes a memory for necessary program instructions and data executed by the processor.
  • the chip may consist of chips, or may include chips and other discrete devices.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory capable of directing a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means that implement the functions specified in one or more flows of the flowchart and/or one or more blocks of the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to generate computer-implemented processing, so that the instructions executed on the computer or other programmable equipment provide steps for realizing the functions specified in one flow or multiple flows of the flow chart and/or one or more square blocks of the block diagram.

Abstract

本申请公开了一种地址空间推荐方法,包括:获取客户端发送的针对第一VPC的地址空间推荐请求,该地址空间推荐请求包括第一联盟关系的标识;响应该地址空间推荐请求,确定与第二VPC对应的第二地址空间不同的第一地址空间,该第一VPC与第二VPC具有该第一联盟关系;向客户端输出该第一地址空间。由于可以自动为VPC推荐联盟关系中不与其它VPC存在地址冲突的第一地址空间,从而无需用户手动为该VPC配置地址空间。如此,不仅可以降低用户配置VPC的难度、提高配置效率,而且,基于自动推荐的第一地址空间对VPC进行配置,可以有效降低配置VPC出错的可能性,有助于建立该VPC与其它VPC之间的互联关系。此外,本申请还提供了对应的装置及相关设备。

Description

一种地址空间推荐方法、装置及相关设备
本申请要求于2022年1月24日递交中国国家知识产权局、申请号为202210081617.5,发明名称为“一种地址空间推荐方法、装置及相关设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及互联网技术领域,尤其涉及一种地址空间推荐方法、装置及相关设备。
背景技术
随着云服务部署的增多,越多越多的用户(如企业等)期望在全球范围内的不同虚拟私有云(virtual private cloud,VPC)之间实现互连。以VPC为例,通常情况下,当不同VPC之间相互隔离时(即相互之间不存在数据交互),不同VPC所使用的地址空间可以存在重叠,包括互联网协议版本4(Internet Protocol Version 4,IPV4)地址空间和/或互联网协议版本6(Internet Protocol Version 6,IPV6)地址空间等;而当不同VPC之间进行互连时,需要保证不同VPC所使用的地址空间不存在重叠,以避免数据包因为不同VPC之间的地址空间重叠而无法转发,如出现回环路由等。
目前,用户在创建/更新VPC时,通常会根据与该VPC互连的其它VPC所使用的地址空间,为该VPC手动配置不重叠的地址段,以避免出现地址冲突。但是,实际应用场景中,与该VPC互连的其它VPC的数量可能较多,如包括几十甚至几百个VPC等。此时,由用户为VPC人工配置不与其它VPC存在地址冲突的地址空间,不仅配置难度较大、配置效率较低,而且配置VPC的地址空间容易出现错误,从而影响该VPC与其它VPC之间建立互连关系。
发明内容
本申请实施例提供一种地址空间推荐方法、装置及相关设备,以降低配置VPC的难度、提高配置效率、降低配置地址空间出现错误的可能性。
第一方面,本申请实施例提供一种地址空间推荐方法,该方法例如可以是由地址空间推荐装置执行,具体的,在为VPC推荐可用的地址空间时,地址空间推荐装置先获取客户端发送的针对第一VPC的地址空间推荐请求,该地址空间推荐请求包括第一联盟关系的标识,然后响应该地址空间推荐请求,确定与第二VPC对应的第二地址空间不同的第一地址空间,该第一VPC与第二VPC具有该第一联盟关系,从而所确定的第一地址空间与第二地址空间不存在重叠,最后,地址空间推荐装置向客户端输出该第一地址空间。
由于在创建或者更新VPC时,地址空间推荐装置可以自动为该VPC推荐联盟关系中不与其它VPC存在地址冲突的第一地址空间,从而无需用户手动为该VPC配置地址空间。如此,不仅可以降低用户配置VPC的难度、提高配置效率,而且,基于自动推荐的第一地址空间对VPC进行配置,可以有效降低配置VPC出错的可能性,有助于建立该VPC与其它VPC之间的互联关系。
在一种可能的实施方式中,地址空间推荐请求还包括地址约束条件,如可以由用户指定该地址约束条件等,则所确定的第一地址空间满足该地址约束条件。如此,为用户自动 推荐的第一地址空间不仅与联盟关系中的其它VPC对应的地址空间不存在重叠,而且,该第一地址空间还符合用户的要求,如满足用户在地址空间大小、地址前缀等方面的要求。
在一种可能的实施方式中,地址约束条件用于指示地址空间的大小,则地址空间推荐装置在响应地址空间推荐请求时,具体可以是根据该地址空间推荐请求中的第一联盟关系的标识,确定第一联盟关系中的第一可用地址空间以及第二可用地址空间,该第一可用地址空间的大小小于第二可用地址空间的大小,然后根据该地址空间推荐请求中的地址约束条件,优先从第一可用地址空间中确定第一地址空间。如此,这样,当后续创建/更新的其它VPC需要配置更大的地址空间时,地址空间推荐装置可以从相对较大的第二可用地址空间中为其分配其所需的地址空间,提高地址空间分配的合理性以及地址空间的利用率。
在一种可能的实施方式中,地址空间推荐装置还可以提供配置界面,该配置界面可以通过客户端呈现给用户,然后,地址空间推荐装置可以响应于用户在该配置界面上针对第一VPC的配置操作,获得第一联盟关系的标识以及该地址约束条件。如此,地址空间推荐装置可以支持用户对VPC在联盟关系以及地址约束条件的灵活配置,提高用户体验。
在一种可能的实施方式中,地址空间推荐请求还包括第二联盟关系的标识,则地址空间推荐装置所确定的第一地址空间不仅与第一联盟关系中的各个VPC分别对应的地址空间均不存在重叠,而且,该第一地址空间与第二联盟关系中的各个VPC分别对应的地址空间也均不存在重叠。如此,地址空间推荐装置为VPC所自动推荐的地址空间,可以在存在通信的两个联盟关系中不存在地址冲突。
在一种可能的实施方式中,地址空间推荐装置还可以提供推荐界面,该推荐界面通过客户端呈现给用户,并且,该推荐界面中包括第一地址空间。如此,地址空间推荐装置可以将确定的第一地址空间呈现给用户,以便由于用户获知为VPC推荐的地址空间,提高用户体验。
在一种可能的实施方式中,地址空间推荐装置还可以响应用户针对该第一地址空间的更换操作,确定第二地址空间,该第二地址空间与第一地址空间不重叠,并且,该第二地址空间与第一联盟关系中的各个VPC分别对应的地址空间均不重叠,然后,地址空间推荐装置向客户端输出该第二地址空间。如此,可以在用户不满意之前推荐的第一地址空间后,再次为用户推荐其它可用的地址空间,以使得重新推荐后的第二地址空间能够满足用户的使用需求,从而可以进一步方便用户对VPC进行地址空间的配置,提高用户体验。
第二方面,基于与第一方面的方法实施例同样的发明构思,本申请实施例提供了一种地址空间推荐装置。该装置具有实现上述第一方面的各实施方式对应的功能。该功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第三方面,本申请实施例提供一种计算设备,包括:处理器和存储器;该存储器用于存储指令,当该计算设备运行时,该处理器执行该存储器存储的该指令,以使该计算设备执行上述第一方面或第一方面的任一实现方式中的地址空间推荐方法。需要说明的是,该存储器可以集成于处理器中,也可以是独立于处理器之外。装置还可以包括总线。其中,处理器通过总线连接存储器。其中,存储器可以包括可读存储器以及随机存取存储器。
第四方面,本申请实施例还提供一种可读存储介质,所述可读存储介质中存储有程序 或指令,当其在计算机上运行时,使得上述第一方面或第一方面的任一实现方式中的地址空间推荐方法被执行。
第五方面,本申请实施例还提供一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述第一方面或第一方面的任一实现方式中的任意地址空间推荐方法。
另外,第二方面至五方面中任一种实现方式所带来的技术效果可参见第一方面中不同实现方式所带来的技术效果,或者可参见第二方面中不同实现方式所带来的技术效果,此处不再赘述。
附图说明
为了更清楚地说明本申请实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请中记载的一些实施例,对于本领域普通技术人员来讲,还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一示例性地址空间推荐系统的结构示意图;
图2为本申请实施例提供的地址空间推荐方法的流程示意图;
图3为本申请实施例提供的一示例性配置界面示意图;
图4为本申请实施例提供的IPV4地址格式的示意图;
图5为本申请实施例提供的一示例性推荐界面示意图;
图6为本申请实施例提供的又一示例性推荐界面示意图;
图7为本申请实施例提供的一种地址空间推荐装置的结构示意图;
图8为本申请实施例提供的一种计算设备的硬件结构示意图。
具体实施方式
参见图1,为一示例性地址空间推荐系统的结构示意图。如图1所示,地址空间推荐系统100可以包括客户端101、服务平台102。并且,客户端101以及服务平台102之间可以进行数据交互,如通过超文本传输协议(Hypertext Transfer Protocol,HTTP)或者其他网络协议进行数据通信等。
其中,客户端101,可以是服务平台102对外提供的网络浏览器,用于与用户进行交互;或者,客户端101可以是运行在用户终端上的应用程序(application)等。在地址空间推荐系统100中,客户端101的数量可以是一个或者多个,本实施例对此并不进行限定。服务平台102可以通过一个或者多个计算设备(如服务器等)进行构建,实际应用时,服务平台102还可以包括存储设备等其它设备。图1中以通过多个服务器构建服务平台102为例进行示例性说明,并且用户可以通过客户端101在服务平台102上创建VPC或者微服务(microservices)。其中,VPC,是指用户创建的属于自己的私有网络,相互隔离的VPC之间不互连,地址空间可完全重叠,而互连的VPC之间地址空间不存在重叠。微服务,是指由基于业务构建并且能够独立部署的小服务,一个或者多个微服务可以构成应用程序。
以创建VPC为例,当在服务平台102上创建新的VPC,并且所创建的VPC与其它VPC存在互联时,用户通常需要通过客户端101手动为该VPC配置地址空间,并且所配置的地址空间与其它VPC所使用的地址空间不存在重叠,以避免发生地址冲突而影响VPC之间的数据通信。但是,实际应用时,与该新创建的VPC存在互联的其它VPC的数量可能较 多,这要求用户需要了解众多VPC分别对应的地址空间,并人工分析出不与每个VPC所使用的地址空间存在重叠的地址空间,从而将该地址空间配置给新创建的VPC。这种人工为VPC配置可用的地址空间的方式,不仅配置难度较大、配置效率较低,而且配置VPC的地址空间容易出现错误,如容易与其中一个VPC所使用的地址空间存在部分重叠等,从而影响该VPC与其它VPC之间建立互连关系。
基于此,本申请实施例提供了一种地址空间推荐方法,该地址空间推荐方法可以由地址空间推荐装置103执行,该地址空间推荐装置103可以部署于服务平台102中。示例性地,地址空间推荐装置103可以通过软件或者硬件实现。当通过软件实现时,地址空间推荐装置103可以是运行在计算设备上的计算机程序,如软件开发工具包(software development kit,SDK)等。当通过硬件实现时,地址空间推荐装置103可以是服务器等计算设备,并且该计算设备上运行了计算机程序,以使得地址空间推荐装置103具有自动推荐地址空间的功能。或者,地址空间推荐装置103可以是利用专用集成电路(application-specific integrated circuit,ASIC)实现、或可编程逻辑器件(programmable logic device,PLD)实现的设备等。其中,上述PLD可以是复杂程序逻辑器件(complex programmable logical device,CPLD)、现场可编程门阵列(field-programmable gate array,FPGA)、通用阵列逻辑(generic array logic,GAL)或其任意组合实现。
当用户通过客户端101请求创建或者更新VPC时,服务平台102可以接收客户端101发送的针对VPC的地址空间推荐请求,该地址空间推荐请求中携带有该VPC所属的联盟关系的标识。然后,服务平台102可以调用地址空间推荐装置103响应该地址空间推荐请求,确定该联盟关系中与其它VPC对应的第二地址空间不同的第一地址空间,并向客户端101输出该第一地址空间,实现为新创建/更新的VPC自动推荐可用的地址空间。
由于在创建或者更新VPC时,可以自动为该VPC推荐联盟关系中不与其它VPC存在地址冲突的第一地址空间,从而无需用户手动为该VPC配置地址空间。如此,不仅可以降低用户配置VPC的难度、提高配置效率,而且,基于自动推荐的第一地址空间对VPC进行配置,可以有效降低配置VPC出错的可能性,有助于建立该VPC与其它VPC之间的互联关系。
需要说明的是,上述示例中是以地址空间推荐装置103部署于服务平台102为例,实际应用时,地址空间推荐装置103也可以是独立于服务平台102进行部署,如图1所示。此时,当用户通过客户端101在服务平台102上申请创建/更新VPC时,服务平台102可以生成地址空间推荐请求,将其发送给地址空间推荐装置103,并将地址空间推荐装置103所反馈的第一地址空间发送给客户端101,实现为VPC自动推荐可用的地址空间。并且,在服务平台102内部或者外部可以配置数据库,其中,配置于服务平台102内部的数据库可以称之为本地数据库,配置于服务平台102外部的数据库可以称之为云端数据库,并且,该本地数据库或者云端数据库可以用于存储数据,如存储各个联盟关系所包括的VPC信息、各个联盟关系所对应的剩余可用的地址空间等。
值得注意的是,图1所示的系统架构仅作为一种示例,并不用于限定其具体实现局限于该示例。例如,在其它可能的系统架构中,地址空间推荐系统100还可以包括更多其它功能的装置,以为服务平台102提供更加丰富的功能,本实施例对此并不进行限定。
为使本申请的上述目的、特征和优点能够更加明显易懂,下面将结合附图对本申请实施例中的各种非限定性实施方式进行示例性说明。显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例,都属于本申请保护的范围。
如图2所示,为本申请实施例中一种地址空间推荐方法的流程示意图,该方法可以应用于如图1所示的地址空间推荐系统100中,并可以由该地址空间推荐系统100中的地址空间推荐装置103执行。实际应用时,该方法也可以是应用于其它可适用的地址空间推荐系统中。为便于理解与描述,下面以地址空间推荐装置103执行该方法为例进行示例性说明,该方法具体可以包括:
S201:地址空间推荐装置103获取客户端101发送的针对第一VPC的地址空间推荐请求,该地址空间推荐请求包括第一联盟关系的标识。
本实施例中,当用户通过客户端101在服务平台102上创建/更新VPC时,服务平台102可以通过地址空间推荐装置103为该VPC确定可用的地址空间。
实际应用时,服务平台102可以向客户端101提供操作界面,并通过客户端101向用户呈现该操作界面。这样,用户可以在该操作界面上申请创建或者更新VPC。为便于区分与描述,以下将用户所申请创建或者更新的VPC称之为第一VPC。
然后,基于用户创建/更新第一VPC的请求,服务平台102可以向客户端101提供配置界面,从而客户端101所呈现的界面由上述操作界面切换至该配置界面。这样,用户可以在该配置界面上针对第一VPC执行相应的配置操作,获得第一VPC所属的联盟关系的标识。例如,客户端101所呈现的配置界面可以如图3所示,用户可以在该配置界面上输入所要创建的第一VPC所属的第一联盟关系的名称。其中,在创建第一VPC之前,该第一联盟关系中可以包括一个或者多个VPC,并且,该第一联盟关系可以由用户进行创建,或者由其它用户进行预先创建。当然,当用户之前未创建第一联盟关系时,用户也可以是在该配置界面上新建该第一联盟关系,如通过点击配置界面上的“新建联盟关系”控件来创建新的联盟关系等。当在已创建的第一联盟关系中添加第一VPC时,该第一VPC可以与该第一联盟关系中的其它VPC进行互连。本实施例中,属于同一联盟关系的任意VPC之间可以进行互连,相应的,该联盟关系下的不同VPC之间所使用的地址空间不存在重叠。当在第一联盟关系中创建第一VPC时,分配给该第一VPC的地址空间与该第一联盟关系中的其余VPC(以下称之为第二VPC)所具有的第二地址空间不存在重叠,以避免影响第一VPC与第二VPC之间的通信。
接着,客户端101可以将用户配置的第一联盟关系的标识发送给服务平台102,由服务平台102生成包括该第一联盟关系的标识的地址空间推荐请求,并将其发送给地址空间推荐装置103,以请求地址空间推荐装置103为该第一VPC确定可用的地址空间。本实施例中,地址空间,是指基于互联网协议(Internet Protocol,IP)的一个或者多个IP地址,具体可以是IPV4地址和/或IPV6地址。
进一步地,用户还可以在该配置界面上对第一VPC进行基础配置,如图3中,用户可以配置VPC的名称以及该VPC所包括的可用区(availability zone)或分区(region)等。 另外,用户还可以在配置界面上输入地址约束条件,以约束该第一VPC可用的地址范围。示例性地,该地址约束条件例如可以指示地址空间的大小,和/或指示地址的固定前缀等。例如,用户可以在图3所示的配置界面上输入第一VPC对应的地址前缀,以固定服务平台102为该第一VPC配置的各个地址的前缀。如用户可以配置第一VPC对应的IPV4地址的前缀为“192.16.X.X”,从而后续服务平台102为该第一VPC配置的各个IPV4地址的前缀均相同,如192.16.0.0~192.16.255.255等。实际应用时,用户还可以在配置界面上为第一VPC配置其它信息,如地址空间的大小、地址类型(如IPV4地址、IPV6地址)等,本实施例对此并不进行限定。
S202:地址空间推荐装置103响应地址空间推荐请求,确定与第二VPC对应的第二地址空间不同的第一地址空间,该第一VPC与第二VPC具有该第一联盟关系。
S203:地址空间推荐装置103向客户端101输出第一地址空间。
具体实现时,地址空间推荐装置103可以响应接收到的地址空间推荐请求,从中解析出第一联盟关系的标识,并查找出与该第一联盟关系所对应的可用的地址空间。其中,可用的地址空间是指与该第一联盟关系中的任意VPC所使用的地址空间均不存在重叠的地址空间。如此,地址空间推荐装置103可以从可用的地址中确定出第一地址空间,并将其分配给第一VPC。举例来说,假设第一联盟关系中包括VPC1以及VPC2,第一联盟关系对应的所有可被分配的IPV4地址空间为128.1.0.1~191.254.255.254,并且,VPC1所分配到的IPV4地址空间为128.1.0.1~150.255.255.255,VPC2所分配到的IPV4地址空间为151.0.0.0~160.255.255.255,此时,剩余可用的IPV4地址空间为161.0.0.0~191.254.255.254。当用户申请在该第一联盟关系中新建第一VPC时,服务平台102可以从剩余可用的IPV4地址空间161.0.0.0~191.254.255.254中,将161.0.0.0~165.254.255.254作为第一地址空间分配给第一VPC。如此,地址空间推荐装置103所确定出的第一地址空间可以与第一联盟关系中各个VPC所使用的地址空间均不存在重叠。需要说明的是,步骤S202中所描述的地址空间不同,具体是指第一地址空间与第二地址空间不存在重叠,以此避免第一VPC与第二VPC之间存在地址冲突。
实际应用时,第一联盟关系对应的可用的地址空间,可以存储于第一数据库(data base,DB)中,该第一数据库可以部署于服务平台102本地,从而地址空间推荐装置103可以通过访问数据平台102的本地数据库,获得该第一联盟关系对应的可用地址空间。或者,第一数据库也可以是独立于服务平台102进行部署,如部署于云端等,本实施例对此并不进行限定。
在一些可能的实施方式中,针对所要创建或者更新的每个VPC,地址空间推荐装置103可以为该VPC分配固定大小的地址空间,或者,地址空间推荐装置103也可以由用户通过配置地址约束条件进行指定。比如,当用户在配置界面上输入地址约束条件时,若该地址约束条件指示分配给第一VPC的地址空间大小(即包括的地址的数量),则地址空间推荐装置103可以从第一联盟关系对应的可用的地址空间中,确定出相应大小的第一地址空间。
进一步地,地址空间推荐装置103还可以采用贪心算法确定分配给第一VPC的第一地址空间,以减少第一联盟关系对应的可用地址空间的碎片率。具体地,当第一联盟关系中的多个VPC分配到各自对应的地址空间时,该第一联盟关系对应的可用地址空间可能包括 多个不连续的地址段,从而地址空间推荐装置103可以优先从较小的地址段中为第一VPC分配第一地址空间。例如,假设地址空间推荐装置103根据第一联盟关系的标识,查找到该第一联盟关系对应的可用的地址空间包括不重叠的第一可用地址空间以及第二可用地址空间,并且,该第一可用地址空间的大小小于第二可用地址空间的大小,则地址空间推荐装置103可以根据地址约束条件,优先从第一可用地址空间中确定分配给第一VPC的第一地址空间。这样,当后续创建/更新的其它VPC需要配置更大的地址空间时,地址空间推荐装置103可以从相对较大的第二可用地址空间中为其分配其所需的地址空间,提高地址空间分配的合理性以及地址空间的利用率。
在其它可能的实施方式中,用户所配置的地址约束条件也可以指示分配给第一VPC的地址前缀,从而地址空间推荐装置103可以从可用的地址空间中,确定出满足地址约束条件所指示的地址前缀的第一地址空间,以满足用户对于该地址空间的需求。实际应用时,用户所指定的地址前缀,可以作为用户的私有网络地址段的标识。进一步地,该地址前缀,还可以对实现VPC的AZ或者分区进行标识。以IPV4地址为例,分配给第一VPC的每个IPV4地址可以通过32比特(bit)进行表示,如图4所示。其中,第1位至第Y位即为IPV4地址的前缀,并且第1位至第X位(X为大于1的正整数)可以用于标识用户的私有网络地址段,第X+1位至第Y位可以用于标识实现VPC的AZ/分区,Y为大于等于X的正整数。当Y大于X时,每个IPV4地址的前缀可以携带有AZ或者分区的标识信息;而当Y等于X时,每个IPV4地址的前缀可以无需标识该AZ或者分区。并且,在用户指定地址前缀的情况下,地址空间推荐装置103也可以基于贪心算法优先从较小的地址段中为第一VPC确定合适地址空间。
上述实施方式中,是以地址空间推荐装置103在一个联盟关系中创建/更新第一VPC时确定第一地址空间为例,实际应用时,服务平台102可以为用户在多个不同的联盟关系中创建/更新不同的VPC。此时,在每个联盟关系中创建/更新VPC时,地址空间推荐装置103均可以采用上述类似方式确定分配给该VPC的地址空间,并且所分配的地址空间与该联盟关系中其它VPC所分配到的地址空间不存在重叠。值得注意的是,不同联盟关系中的VPC之间,可以不存在互连,也即不同联盟关系中的VPC可以相互隔离,因此,每个联盟关系对应的可分配的全部地址空间可以存在重叠。比如,针对相互隔离的联盟关系1以及联盟关系2,联盟关系1对应的全部可用的IPV4地址空间可以是128.1.0.1~191.254.255.254,联盟关系2对应的全部可用的IPV4地址空间也可以是128.1.0.1~191.254.255.254。相应的,当在联盟关系1中新建VPCa时,地址空间推荐装置103为该VPCa分配的IPV4地址空间可以是128.1.0.1~150.255.255.255;在联盟关系2中新建VPCb时,地址空间推荐装置103为该VPCb分配的IPV4地址空间也可以是128.1.0.1~150.255.255.255等。
而在其它实施方式中,不同联盟关系中的VPC之间可以通过部分VPC进行互连,具体的,当地址空间推荐请求同时包括第一联盟关系以及第二联盟关系的标识时,表征第一VPC同时属于第一联盟关系以及第二联盟关系,此时,地址空间推荐装置103为第一VPC分配的第一地址空间,不仅与第一联盟关系中的各个VPC分别对应的地址空间均不重叠,而且与所述第二联盟关系中的各个VPC分别对应的地址空间均不重叠。比如,假设用户1 可以创建联盟关系1并且在该联盟关系1中新建VPCa 1和VPCa 2,用户2可以创建联盟关系2并且在该联盟关系2中新建VPCb 1和VPCb 2,当用户1期望联盟关系1中的VPC与联盟关系中2中的VPC可以进行互连时,用户1可以在联盟关系1以及联盟关系2中同时创建VPCc 1。这样,在联盟关系1中,VPCc 1可以与VPCa 1和VPCa 2进行互连,并且,在联盟关系2中,VPCc 1可以与VPCb 1和VPCb 2进行互连。如此,可以实现两个联盟关系之间的数据交互。值得注意的是,在联盟关系1以及联盟关系2中新建VPCc 1时,地址空间推荐装置103为该VPCc 1分配的地址空间,不仅与联盟关系1中的VPCa 1和VPCa 2所分配到的地址空间均不存在重叠,而且,与联盟关系1中的VPCb 1和VPCb 2所分配到的地址空间也不存在重叠。
实际应用时,当地址空间推荐系统100支持多个用户在多个联盟关系中分别进行VPC的创建/更新时,地址空间推荐系统100还可以对多个联盟关系的信息进行管理。具体地,地址空间推荐系统100中还可以部署第二数据库,该第二数据库可以部署于服务平台102本地,也可以部署于云端,并且该第二数据库可以用于存储各个联盟关系的相关信息,如联盟关系的标识、联盟关系中各个VPC的标识、VPC所属用户、VPC所分配到的地址空间等,从而地址空间推荐系统100可以通过访问第二数据库,获取属于各个用户的联盟关系的相关信息,以便根据该信息对属于各个用户的VPC进行运维、方便用户查询联盟关系的信息。
地址空间推荐装置103在输出第一地址空间后,可以将其反馈给服务平台102,从而服务平台102可以直接将第一VPC的地址空间配置为该第一地址空间,并将第一地址空间通过客户端101呈现给用户,以便由用户获知服务平台102为该第一VPC配置的地址空间。在进一步可能的实施方式中,在确定为第一VPC配置地址空间之前,还可以由用户确定该第一VPC的地址空间是否为第一地址空间。具体的,本实施例还可以包括:
S204:服务平台102提供推荐界面,该推荐界面通过客户端101呈现给用户,并且,该推荐界面中包括地址空间推荐装置103输出的第一地址空间。
在一种可能的示例中,服务平台102可以提供如图5所示的推荐界面,该推荐界面中包括向用户推荐的第一地址空间。同时,该推荐界面中还可以包括“确认”控件以及“再次推荐”控件。实际应用时,图5所示的推荐界面与图3所示的配置界面可以为两个独立的界面,也可以是合并为同一界面,如图6所示,用户可以在该界面上对所要创建/更新的第一VPC进行相应的配置时,还可以查看到地址空间推荐系统100自动推荐的地址空间,本实施例对此并不进行限定。当用户在推荐界面上点击该“确认”控件时,服务平台102确定将第一VPC的地址空间配置为第一地址空间;而当用户在该推荐界面上点击“再次推荐”控件时(如当前推荐的第一地址空间不符合用户对于地址空间的未来规划等),服务平台102可以指示地址空间推荐装置103重新为该第一VPC确定地址空间。此时,地址空间推荐装置103还可以进一步执行下述步骤:
S205:地址空间推荐装置103响应用户针对第一地址空间的更换操作,确定第二地址空间,其中,该第二地址空间与所述第一地址空间不重叠,并且,该第二地址空间与第一联盟关系中的各个VPC分别对应的地址空间均不重叠。
S206:地址空间推荐装置103向客户端101输出该第二地址空间。
其中,用户针对该第一地址空间的更换操作,例如可以是上述点击“再次推荐”空间的操作,或者可以是其它触发地址空间推荐装置103重新推荐地址空间的操作等,本实施例对此并不进行限定。
当用户请求重新推荐地址空间时,地址空间推荐装置103可以从第一联盟关系对应的可用地址空间中,重新查找出与第一地址空间不重叠的第二地址空间。其中,地址空间推荐装置103确定第二地址空间的具体实现方式,与上述第一确定目标地址空间的具体实现方式类似,可参见前述实施例的相关之处描述。值得注意的是,重新查找出的第二地址空间仍然需要满足与该联盟关系中的其它VPC所分配到的地址空间不存在重叠的基础要求。实际应用时,在用户请求重新推荐地址空间之前,用户还可以向服务平台102输入地址信息(如地址前缀、地址空间大小、地址连续性等),并由地址空间推荐装置103输出满足该地址信息的第二地址空间,以便于重新推荐的第二地址空间能够符合用户的预期。
在地址空间推荐装置103输出第二地址空间后,服务平台102可以将该第二地址空间呈现在图5或者图6所示的推荐界面中,以便由用户进一步确定是否将第一VPC的地址空间配置为该第二地址空间。当用户在推荐界面中点击“确认”控件后,服务平台102确定将第一VPC的地址空间配置为该第二地址空间;而当用户在推荐界面中点击“再次推荐”控件后,服务平台102可以再次为用户推荐新的地址空间。
进一步地,当用户释放第一联盟关系中的一个或者多个VPC时,地址空间推荐装置103还可以回收地址空间,具体可以是将已分配给该第一VPC的地址空间进行释放,并将其作为可用的地址空间添加至第一数据库中。这样,当后续用户创建或者更新VPC时,地址空间推荐装置103可以从第一数据库中将该地址空间分配给所要创建或者更新的VPC。
值得注意的是,本实施例中,是以地址空间推荐装置103与服务平台102作为两个独立的实体对自动推荐地址空间的实现过程进行示例性说明,在其它实施例中,地址空间推荐装置103也可以部署于服务平台102上,此时,上述实施例中服务平台102所执行的部分或者全部动作,具体由地址空间推荐装置103进行执行,本实施例对此并不进行限定。
并且,本实施例中是以地址空间推荐装置103为VPC自动推荐可用的地址空间为例,在其它可能的实施例中,地址空间推荐装置103也可以是为用户请求创建或者更新的微服务自动推荐可用的地址空间,其具体实现方式与上述实施例中介绍的为VPC自动推荐可用的地址空间的具体过程类似,可参见上述过程进行理解,在此不做赘述。
上文中结合图1至图6,详细描述了本申请所提供的地址空间推荐方法,下面将结合图7至图8,描述根据本申请所提供的装置以及设备。
与上述方法同样的发明构思,本申请实施例还提供一种地址空间推荐装置,该地址空间推荐装置可以实现上述图2所示的实施例中地址空间推荐装置103的功能。参见图7所示,该地址空间推荐装置700可以包括:
通信模块701,用于获取客户端发送的针对第一虚拟私有云VPC的地址空间推荐请求,所述地址空间推荐请求包括第一联盟关系的标识;
确定模块702,用于响应所述地址空间推荐请求,确定与第二VPC对应的第二地址空间不同的第一地址空间,所述第一VPC和所述第二VPC具有所述第一联盟关系;
所述通信模块701,还用于向所述客户端输出所述第一地址空间。
在一种可能的实施方式中,所述地址空间推荐请求还包括地址约束条件,则,所述第一地址空间满足所述地址约束条件。
在一种可能的实施方式中,所述地址约束条件用于指示地址空间的大小,所述确定模块701,用于:
根据所述地址空间推荐请求中的所述第一联盟关系的标识,确定所述第一联盟关系中的第一可用地址空间以及第二可用地址空间,所述第一可用地址空间的大小小于所述第二可用地址空间的大小;
根据所述地址空间推荐请求中的地址约束条件,从所述第一可用地址空间中确定所述第一地址空间。
在一种可能的实施方式中,所述地址空间推荐装置700还包括:
提供模块703,用于提供配置界面,所述配置界面通过所述客户端呈现给用户;
信息获取模块704,用于响应于所述用户在所述配置界面上针对所述第一VPC的配置操作,获得所述第一联盟关系的标识以及所述地址约束条件。
在一种可能的实施方式中,所述地址空间推荐请求还包括第二联盟关系的标识;
则,所述第一地址空间与所述第一联盟关系中的各个VPC分别对应的地址空间均不重叠,且所述第一地址空间与所述第二联盟关系中的各个VPC分别对应的地址空间均不重叠。
在一种可能的实施方式中,所述地址空间推荐装置700还包括:
提供模块703,用于提供推荐界面,所述推荐界面通过客户端呈现给用户,所述推荐界面中包括所述第一地址空间。
在一种可能的实施方式中,所述确定模块702,还用于响应所述用户针对所述第一地址空间的更换操作,确定第二地址空间,所述第二地址空间与所述第一地址空间不重叠,且所述第二地址空间与所述第一联盟关系中的各个VPC分别对应的地址空间均不重叠;
所述通信模块701,还用于向所述客户端输出所述第二地址空间。
本实施例中的地址空间推荐装置700,对应于图2所示的地址空间推荐方法,因此,对于本实施例地址空间推荐装置700中各个功能模块的具体实现及其所具有的技术效果,可以参见图2所示实施例中的相关之处描述,在此不做赘述。
此外,本申请实施例还提供一种计算设备,如图8所示,计算设备800中可以包括通信接口810、处理器820。可选的,计算设备800中还可以包括存储器830。其中,存储器830可以设置于计算设备800内部,还可以设置于计算设备800外部。示例性地,上述图2所示实施例中地址空间推荐装置103所执行的各个动作均可以由处理器820实现。处理器820可以通过通信接口810获取地址空间推荐请求,并用于实现图2中所执行的任一方法。在实现过程中,处理流程的各步骤可以通过处理器820中的硬件的集成逻辑电路或者软件形式的指令完成图2中执行的方法。为了简洁,在此不再赘述。处理器820用于实现上述方法所执行的程序代码可以存储在存储器830中。存储器830和处理器820连接,如耦合连接等。
本申请实施例的一些特征可以由处理器820执行存储器830中的程序指令或者软件代码来完成/支持。存储器830上在加载的软件组件可以从功能或者逻辑上进行概括,例如, 图7所示的确定模块702、提供模块703、信息获取模块704。而通信模块701的功能可以由通信接口810实现。
本申请实施例中涉及到的任一通信接口可以是电路、总线、收发器或者其它任意可以用于进行信息交互的装置。比如计算设备800中的通信接口810,示例性地,该其它装置可以是与该计算设备800相连的设备等。
本申请实施例中涉及的处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件,可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。
本申请实施例中的耦合是装置、模块或模块之间的间接耦合或通信连接,可以是电性,机械或其它的形式,用于装置、模块或模块之间的信息交互。
处理器可能和存储器协同操作。存储器可以是非易失性存储器,比如硬盘(hard disk drive,HDD)或固态硬盘(solid-state drive,SSD)等,还可以是易失性存储器(volatile memory),例如随机存取存储器(random-access memory,RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。
本申请实施例中不限定上述通信接口、处理器以及存储器之间的具体连接介质。比如存储器、处理器以及通信接口之间可以通过总线连接。所述总线可以分为地址总线、数据总线、控制总线等。
基于以上实施例,本申请实施例还提供了一种计算机存储介质,该存储介质中存储软件程序,该软件程序在被一个或多个处理器读取并执行时可实现上述任意一个或多个实施例提供地址空间推荐装置103执行的方法。所述计算机存储介质可以包括:U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
基于以上实施例,本申请实施例还提供了一种芯片,该芯片包括处理器,用于实现上述实施例所涉及的地址空间推荐装置103的功能,例如用于实现图2中地址空间推荐装置103所执行的方法。可选地,所述芯片还包括存储器,所述存储器,用于处理器所执行必要的程序指令和数据。该芯片,可以由芯片构成,也可以包含芯片和其他分立器件。
本领域内的技术人员应明白,本申请的实施例可提供为方法、系统、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于 实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换,这仅仅是描述本申请的实施例中对相同属性的对象在描述时所采用的区分方式。
显然,本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的范围。这样,倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。

Claims (17)

  1. 一种地址空间推荐方法,其特征在于,所述方法包括:
    获取客户端发送的针对第一虚拟私有云VPC的地址空间推荐请求,所述地址空间推荐请求包括第一联盟关系的标识;
    响应所述地址空间推荐请求,确定与第二VPC对应的第二地址空间不同的第一地址空间,所述第一VPC和所述第二VPC具有所述第一联盟关系;
    向所述客户端输出所述第一地址空间。
  2. 根据权利要求1所述的方法,其特征在于,所述地址空间推荐请求还包括地址约束条件,则,所述第一地址空间满足所述地址约束条件。
  3. 根据权利要求2所述的方法,其特征在于,所述地址约束条件用于指示地址空间的大小,所述响应所述地址空间推荐请求,包括:
    根据所述地址空间推荐请求中的所述第一联盟关系的标识,确定所述第一联盟关系中的第一可用地址空间以及第二可用地址空间,所述第一可用地址空间的大小小于所述第二可用地址空间的大小;
    根据所述地址空间推荐请求中的地址约束条件,从所述第一可用地址空间中确定所述第一地址空间。
  4. 根据权利要求2或3所述的方法,其特征在于,所述方法还包括:
    提供配置界面,所述配置界面通过所述客户端呈现给用户;
    响应于所述用户在所述配置界面上针对所述第一VPC的配置操作,获得所述第一联盟关系的标识以及所述地址约束条件。
  5. 根据权利要求1至4任一项所述的方法,其特征在于,所述地址空间推荐请求还包括第二联盟关系的标识;
    则,所述第一地址空间与所述第一联盟关系中的各个VPC分别对应的地址空间均不重叠,且所述第一地址空间与所述第二联盟关系中的各个VPC分别对应的地址空间均不重叠。
  6. 根据权利要求1至5任一项所述的方法,其特征在于,所述方法还包括:
    提供推荐界面,所述推荐界面通过客户端呈现给用户,所述推荐界面中包括所述第一地址空间。
  7. 根据权利要求6所述的方法,其特征在于,所述方法还包括:
    响应所述用户针对所述第一地址空间的更换操作,确定第二地址空间,所述第二地址空间与所述第一地址空间不重叠,且所述第二地址空间与所述第一联盟关系中的各个VPC分别对应的地址空间均不重叠;
    向所述客户端输出所述第二地址空间。
  8. 一种地址空间推荐装置,其特征在于,所述装置包括:
    通信模块,用于获取客户端发送的针对第一虚拟私有云VPC的地址空间推荐请求,所述地址空间推荐请求包括第一联盟关系的标识;
    确定模块,用于响应所述地址空间推荐请求,确定与第二VPC对应的第二地址空间不同的第一地址空间,所述第一VPC和所述第二VPC具有所述第一联盟关系;
    所述通信模块,还用于向所述客户端输出所述第一地址空间。
  9. 根据权利要求8所述的装置,其特征在于,所述地址空间推荐请求还包括地址约束条件,则,所述第一地址空间满足所述地址约束条件。
  10. 根据权利要求9所述的装置,其特征在于,所述地址约束条件用于指示地址空间的大小,所述确定模块,用于:
    根据所述地址空间推荐请求中的所述第一联盟关系的标识,确定所述第一联盟关系中的第一可用地址空间以及第二可用地址空间,所述第一可用地址空间的大小小于所述第二可用地址空间的大小;
    根据所述地址空间推荐请求中的地址约束条件,从所述第一可用地址空间中确定所述第一地址空间。
  11. 根据权利要求9或10所述的装置,其特征在于,所述装置还包括:
    提供模块,用于提供配置界面,所述配置界面通过所述客户端呈现给用户;
    信息获取模块,用于响应于所述用户在所述配置界面上针对所述第一VPC的配置操作,获得所述第一联盟关系的标识以及所述地址约束条件。
  12. 根据权利要求8至11任一项所述的装置,其特征在于,所述地址空间推荐请求还包括第二联盟关系的标识;
    则,所述第一地址空间与所述第一联盟关系中的各个VPC分别对应的地址空间均不重叠,且所述第一地址空间与所述第二联盟关系中的各个VPC分别对应的地址空间均不重叠。
  13. 根据权利要求8至12任一项所述的装置,其特征在于,所述装置还包括:
    提供模块,用于提供推荐界面,所述推荐界面通过客户端呈现给用户,所述推荐界面中包括所述第一地址空间。
  14. 根据权利要求13所述的装置,其特征在于,所述确定模块,还用于响应所述用户针对所述第一地址空间的更换操作,确定第二地址空间,所述第二地址空间与所述第一地址空间不重叠,且所述第二地址空间与所述第一联盟关系中的各个VPC分别对应的地址空间均不重叠;
    所述通信模块,还用于向所述客户端输出所述第二地址空间。
  15. 一种计算设备,其特征在于,所述设备包括处理器和存储器;
    所述处理器用于执行所述存储器中存储的指令,以使得所述计算设备执行权利要求1至7中任一项所述的方法。
  16. 一种计算机可读存储介质,其特征在于,包括指令,所述指令用于实现权利要求1至7中任一项所述的方法。
  17. 一种包含指令的计算机程序产品,当其在计算设备上运行时,使得计算设备执行如权利要求1至7任一项所述的方法。
PCT/CN2022/110403 2022-01-24 2022-08-05 一种地址空间推荐方法、装置及相关设备 WO2023138032A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210081617.5A CN116527639A (zh) 2022-01-24 2022-01-24 一种地址空间推荐方法、装置及相关设备
CN202210081617.5 2022-01-24

Publications (1)

Publication Number Publication Date
WO2023138032A1 true WO2023138032A1 (zh) 2023-07-27

Family

ID=87347722

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/110403 WO2023138032A1 (zh) 2022-01-24 2022-08-05 一种地址空间推荐方法、装置及相关设备

Country Status (2)

Country Link
CN (1) CN116527639A (zh)
WO (1) WO2023138032A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020019839A1 (zh) * 2018-07-25 2020-01-30 华为技术有限公司 一种企业云的创建方法和管理平台
CN111327720A (zh) * 2020-02-21 2020-06-23 北京百度网讯科技有限公司 一种网络地址转换方法、装置、网关设备及存储介质
CN111427662A (zh) * 2020-03-23 2020-07-17 深信服科技股份有限公司 虚拟机的ip地址的分配方法、终端设备及dhcp服务器
CN111629084A (zh) * 2020-07-28 2020-09-04 腾讯科技(深圳)有限公司 数据传输方法和装置、存储介质及电子设备
CN111917893A (zh) * 2019-05-10 2020-11-10 华为技术有限公司 虚拟私有云与云下数据中心通信、配置方法及相关装置
CN113032092A (zh) * 2021-03-05 2021-06-25 北京百度网讯科技有限公司 分布式计算方法、装置及平台
CN113766042A (zh) * 2021-01-20 2021-12-07 北京沃东天骏信息技术有限公司 一种容器地址的配置方法、系统、装置、设备及介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020019839A1 (zh) * 2018-07-25 2020-01-30 华为技术有限公司 一种企业云的创建方法和管理平台
CN111917893A (zh) * 2019-05-10 2020-11-10 华为技术有限公司 虚拟私有云与云下数据中心通信、配置方法及相关装置
CN111327720A (zh) * 2020-02-21 2020-06-23 北京百度网讯科技有限公司 一种网络地址转换方法、装置、网关设备及存储介质
CN111427662A (zh) * 2020-03-23 2020-07-17 深信服科技股份有限公司 虚拟机的ip地址的分配方法、终端设备及dhcp服务器
CN111629084A (zh) * 2020-07-28 2020-09-04 腾讯科技(深圳)有限公司 数据传输方法和装置、存储介质及电子设备
CN113766042A (zh) * 2021-01-20 2021-12-07 北京沃东天骏信息技术有限公司 一种容器地址的配置方法、系统、装置、设备及介质
CN113032092A (zh) * 2021-03-05 2021-06-25 北京百度网讯科技有限公司 分布式计算方法、装置及平台

Also Published As

Publication number Publication date
CN116527639A (zh) 2023-08-01

Similar Documents

Publication Publication Date Title
US11258667B2 (en) Network management method and related device
US20190081921A1 (en) Management of domain name systems in a large-scale processing environment
US9374316B2 (en) Interoperability for distributed overlay virtual environment
WO2019042110A1 (zh) 一种订阅发布方法及服务器
WO2022206229A1 (zh) 数据处理方法、装置、设备和存储介质
CN107113241B (zh) 路由确定方法、网络配置方法以及相关装置
US11625280B2 (en) Cloud-native proxy gateway to cloud resources
CN109417492B (zh) 一种网络功能nf管理方法及nf管理设备
EP3664420A1 (en) Managing address spaces across network elements
US20130297671A1 (en) Method, apparatus and system for processing packets
WO2018218977A1 (zh) 一种编排软件定义网络的方法及sdn控制器
WO2020073908A1 (zh) 一种发送路由信息的方法和装置
EP4109251A1 (en) Vnf instantiation method and device
US20220350637A1 (en) Virtual machine deployment method and related apparatus
CN114095430A (zh) 一种访问报文的处理方法、系统及工作节点
US10608942B1 (en) Reducing routes based on network traffic utilization
US10986065B1 (en) Cell-based distributed service architecture with dynamic cell assignment
WO2023221708A1 (zh) Pdn拨号及配置方法、系统、装置、设备及存储介质
WO2023138032A1 (zh) 一种地址空间推荐方法、装置及相关设备
CN116016448A (zh) 一种服务网络访问方法、装置、设备及存储介质
WO2022257338A1 (zh) 一种存储管理方法、系统、存储介质及设备
US20200127923A1 (en) System and method of performing load balancing over an overlay network
US20230281085A1 (en) Method and system for generating backup of a large file and optimizing resource utilization
WO2022089291A1 (zh) 一种数据流镜像方法及装置
WO2017041509A1 (zh) 一种基于多处理单元的报文采样方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22921461

Country of ref document: EP

Kind code of ref document: A1