Cloud private line arrangement management method and device, electronic equipment and medium

Abstract

The invention discloses a cloud private line arrangement management method and device, electronic equipment and a medium, and relates to the technical field of cloud computing. The method comprises the following steps: dividing a cloud server area into a single subnet area and a multi-subnet area; wherein a virtual expansion local area network is established between the cloud server of the single subnet area and the cloud private line switch; a virtual expansion local area network is established between the cloud server and the virtual gateway of the multi-subnet area, and a virtual expansion local area network is established between the virtual gateway and the cloud private line switch; in response to a request operation of opening a cloud private line service, determining whether the virtual gateway of the plurality of subnet areas can undertake opening of the cloud private line according to the specification performance index information of the virtual gateway; and opening the cloud private line for the cloud private line service in the single subnet area under the condition of determining that the virtual gateway of the multiple subnet areas cannot undertake the opening of the cloud private line. According to the method, the cloud server area is divided into the single subnet area and the multi-subnet area, the cloud private line opening mode can be flexibly selected according to different service requirements, and different requirements of different users are met.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, specifically to a method, apparatus, electronic device, and medium for orchestrating and managing cloud private lines. Background Technology

[0002] A cloud dedicated line is a private line that directly connects an enterprise's or user's internal network to the network of a cloud service provider. It provides a high-performance, low-latency, stable, and secure connection, enabling users to access cloud resources and services more efficiently.

[0003] Currently, the primary approach to cloud private line access is through a cloud private line switch-virtual gateway (VXLAN) architecture. The cloud private line switch and the VXLAN establish a VXLAN, and the VXLAN also establishes a VXLAN with the cloud server. Each network node uses static routing to control traffic forwarding. In this architecture, all private line traffic accesses the VPC (Virtual Private Cloud) through the VXLAN, which is responsible for traffic distribution. The performance of the VXLAN network element significantly impacts the cloud private line's cloud access capability. However, in some single-cloud access scenarios, cloud private line users require a single VPC and a single subnet, without particularly complex scenarios. In these cases, the cloud private line switch-virtual gateway (VXLAN) architecture is often used, with traffic relayed through the VXLAN. If the VXLAN and other network elements reach their performance limits, hardware horizontal expansion is typically implemented. Hardware expansion requires procurement, feasibility studies, design, deployment, and delivery, a process that is very time-consuming. Hardware expansion solutions can significantly impact a customer's cloud migration business. Summary of the Invention

[0004] To solve, or at least partially solve, the above-mentioned technical problems, this application is implemented as follows: In a first aspect, embodiments of this application provide a cloud private line orchestration and management method, including: The cloud server area is divided into single subnet areas and multi-subnet areas; wherein, the cloud server in the single subnet area establishes a virtual extended local area network with the cloud dedicated line switch; the cloud server in the multi-subnet area establishes a virtual extended local area network with the virtual gateway, and the virtual gateway establishes a virtual extended local area network with the cloud dedicated line switch. In response to the request to activate the cloud private line service, the system determines whether the virtual gateway of the multi-subnet area can undertake the cloud private line service based on the specifications and performance indicators of the virtual gateway. If it is determined that the virtual gateway of the multi-subnet area cannot handle the cloud private line service, a cloud private line is opened for the cloud private line service in the single subnet area. If it is determined that the virtual gateway of the multi-subnet area can undertake the cloud private line service, the cloud private line is opened for the cloud private line service in the multi-subnet area.

[0005] In an optional embodiment, the step of activating the cloud private line service in the single subnet area includes: In response to the request to activate the cloud private line service, a virtual private cloud and a virtual routing forwarding policy are created for the cloud private line service in the single subnet area; Based on the Overlay BGP routes published by the cloud server and the Overlay BGP routes published by the cloud dedicated line switch, the cloud server and the cloud dedicated line switch in the single subnet establish a virtual extended local area network to enable the cloud dedicated line service in the single subnet.

[0006] In an optional embodiment, the method further includes: when the cloud private line is opened for the cloud private line service in the single subnet area, generating a first identifier for the subnet, generating a second identifier for the virtual private cloud, generating a third identifier for the virtual network interface of the virtual private cloud, and recording the correspondence between the first identifier, the second identifier and the third identifier.

[0007] In an optional embodiment, the method further includes: after dividing the cloud server area into a single subnet area and multiple subnet areas, the method further includes: pre-creating and allocating resources in the single subnet area according to a unified resource creation and allocation strategy, including pre-creating virtual private clouds, virtual routing and forwarding strategies, and subnets; The step of opening a cloud private line for the cloud private line service in the single subnet area includes: allocating the virtual private cloud, virtual routing forwarding policy and subnet already created in the single subnet area to the cloud private line service.

[0008] In an optional embodiment, the step of opening a cloud private line for the cloud private line service in the multi-subnet area includes: Send the corresponding configuration information to the cloud server controller, virtual gateway controller, and leased line controller respectively, and create virtual routing forwarding policies; The cloud server and virtual gateway in the multi-subnet area establish a virtual extended local area network, the virtual gateway and the cloud dedicated line switch establish a virtual extended local area network, and send uplink static routes to the virtual gateway and downlink static routes to the cloud dedicated line switch, and open the cloud dedicated line service in the multi-subnet area.

[0009] In an optional embodiment, the method further includes: performing resource reclamation in the single subnet area in response to triggering a resource reclamation operation.

[0010] In an optional embodiment, the method further includes: responding to a cross-regional communication requirement of the cloud private line service in the single subnet area, the cross-regional communication requirement instructing the cloud private line service in the single subnet area to communicate with virtual private clouds in the multiple subnet areas, reclaiming resources allocated for the cloud private line service in the single subnet area, and opening a cloud private line for the cloud private line service in the multiple subnet areas, so that the cloud private line service can communicate with virtual private clouds in the multiple subnet areas.

[0011] In an optional embodiment, the method further includes: displaying a cloud dedicated line activation page, the cloud dedicated line activation page including a selection control, the selection control being used to select whether to activate a cloud dedicated line in a single subnet or multiple subnets; in response to detecting a selection operation on the selection control, determining the selected area; if the selected area is the single subnet, activating a cloud dedicated line in the single subnet, or if the selected area is the multiple subnet, activating a cloud dedicated line in the multiple subnets.

[0012] Secondly, embodiments of this application provide a cloud private line orchestration and management device, comprising: The partitioning module is used to divide the cloud server area into a single subnet area and multiple subnet areas; wherein, the cloud server in the single subnet area establishes a virtual extended local area network with the cloud dedicated line switch; the cloud server in the multiple subnet area establishes a virtual extended local area network with a virtual gateway, and the virtual gateway establishes a virtual extended local area network with the cloud dedicated line switch. The judgment module is used to respond to the request operation to activate the cloud private line service and determine whether the virtual gateway of the multi-subnet area can undertake the cloud private line service based on the specification and performance index information of the virtual gateway. The activation module is used to activate the cloud dedicated line for the cloud dedicated line service in a single subnet area when it is determined that the virtual gateway of the multi-subnet area cannot undertake the cloud dedicated line service; and to activate the cloud dedicated line for the cloud dedicated line service in the multi-subnet area when it is determined that the virtual gateway of the multi-subnet area can undertake the cloud dedicated line service.

[0013] In an optional embodiment, the activation module is further configured to: in response to the request operation to activate the cloud dedicated line service, create a virtual private cloud and a virtual routing forwarding policy for the cloud dedicated line service in the single subnet area; and establish a virtual extended local area network between the cloud server and the cloud dedicated line switch in the single subnet area according to the overlay BGP route published by the cloud server and the overlay BGP route of the service end published by the cloud dedicated line switch, so as to activate the cloud dedicated line for the cloud dedicated line service in the single subnet area.

[0014] In an optional embodiment, the activation module is further configured to: when activating the cloud private line service in the single subnet area, generate a first identifier for the subnet, generate a second identifier for the virtual private cloud, generate a third identifier for the virtual network interface of the virtual private cloud, and record the correspondence between the first identifier, the second identifier and the third identifier.

[0015] In an optional embodiment, the activation module is further configured to: send corresponding configuration information to the cloud server controller, virtual gateway controller, and dedicated line controller respectively, and create a virtual routing forwarding policy; establish a virtual extended LAN between the cloud server and the virtual gateway in the multi-subnet area, establish a virtual extended LAN between the virtual gateway and the cloud dedicated line switch, send an uplink static route to the virtual gateway, and send a downlink static route to the cloud dedicated line switch, thereby activating the cloud dedicated line service in the multi-subnet area.

[0016] In an optional embodiment, the activation module is further configured to: perform resource reclamation in the single subnet area in response to triggering a resource reclamation operation.

[0017] In an optional embodiment, the activation module is further configured to: respond to the cross-regional communication requirements of the cloud private line service in the single subnet area, the cross-regional communication requirements instructing the cloud private line service in the single subnet area to communicate with the virtual private clouds in the multiple subnet areas, reclaim the resources allocated for the cloud private line service in the single subnet area, and activate the cloud private line for the cloud private line service in the multiple subnet areas, so that the cloud private line service can communicate with the virtual private clouds in the multiple subnet areas.

[0018] In an optional embodiment, the device further includes an interaction module for displaying a cloud dedicated line activation page, the cloud dedicated line activation page including a selection control for selecting whether to activate a cloud dedicated line in a single subnet or multiple subnets; in response to detecting a selection operation on the selection control, determining the selected area; the activation module is further configured to: if the selected area is the single subnet, activate a cloud dedicated line in the single subnet, or if the selected area is the multiple subnet, activate a cloud dedicated line in the multiple subnets.

[0019] Thirdly, embodiments of this application provide an electronic device, which includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement the cloud private line orchestration and management method provided in any embodiment of this application.

[0020] Fourthly, embodiments of this application provide a readable storage medium on which a program or instruction is stored, and when the program or instruction is executed by a processor, it implements the cloud private line orchestration and management method provided in any embodiment of this application.

[0021] Fifthly, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the cloud private line orchestration and management method provided in any embodiment of this application.

[0022] The technical solution provided in this application has at least the following beneficial effects: The cloud private line orchestration and management method provided in this application divides the cloud server area into single subnet areas and multiple subnet areas, with different areas corresponding to different cloud private line activation methods (i.e., different cloud access methods). Specifically, in a single subnet area, the cloud server establishes a virtual extended LAN with the cloud private line switch; in a multiple subnet area, the cloud server establishes a virtual extended LAN with a virtual gateway, and the virtual gateway establishes a virtual extended LAN with the cloud private line switch. By dividing the cloud server area into single and multiple subnet areas, two methods for activating cloud private lines are provided, improving the flexibility and applicability of cloud access. Flexible switching between single and multiple subnet areas is possible, allowing users to flexibly choose the cloud private line activation method according to different business needs, thus meeting the diverse requirements of different users. Moreover, from a traffic perspective, this application embodiment optimizes traffic by reducing intermediate network nodes and optimizing resource utilization as needed.

[0023] The cloud private line orchestration and management method provided in this application, in response to a request to activate a cloud private line service, determines whether a virtual gateway in a multi-subnet area can handle the activation of a cloud private line based on the specifications and performance indicators of the virtual gateway. If it is determined that the virtual gateway in a multi-subnet area cannot handle the activation of a cloud private line, the cloud private line service is activated in a single subnet area. By detecting the resources of the network elements of the virtual gateway, if the performance resources of the virtual gateway reach a threshold, when a customer activates a service, the new service is automatically switched to a single subnet area, using a cloud private line switch-cloud server activation method. This ensures the realization of the customer's basic cloud access services without affecting the activation of customer services due to insufficient resources, and also ensures the stability of the entire system and improves availability. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0025] Figure 1 A flowchart illustrating a cloud private line orchestration and management method according to an embodiment of this application is shown. Figure 2 A flowchart illustrating a cloud private line orchestration and management method according to another embodiment of this application is shown; Figure 3This illustration shows an application diagram of the cloud private line orchestration and management method according to an embodiment of this application; Figure 4 A flowchart illustrating a cloud private line orchestration and management method according to an embodiment of this application is shown. Figure 5 A block diagram of an electronic device according to an embodiment of this application is shown. Detailed Implementation

[0026] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0027] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0028] Figure 1 This diagram illustrates a flowchart of a cloud dedicated line orchestration and management method according to an embodiment of this application. A cloud dedicated line is a dedicated connection between an enterprise's on-premises data center / office and a Virtual Private Cloud (VPC). It provides a high-speed, low-latency, stable, and secure access channel, enabling users to access cloud resources and services more efficiently. Optionally, this method can be applied to a cloud dedicated line convergence orchestrator. The cloud dedicated line convergence orchestrator is used in cloud-network convergence to uniformly manage network resources. By integrating and optimizing resources, it intelligently combines resources to achieve flexible end-to-end scheduling and efficient service.

[0029] like Figure 1 As shown, the method includes: Step S101: Divide the cloud server region into single subnet regions and multi-subnet regions.

[0030] In this system, a virtual extended LAN is established between the cloud server in a single subnet and the cloud leased line switch. The single subnet connects to the cloud server via the cloud leased line switch (i.e., access to the cloud). Optionally, there can be one or more single subnets; this application does not impose any restrictions. In the case of multiple single subnets, the cloud leased line switch can establish virtual extended LANs with the cloud services in different single subnets.

[0031] A cloud leased line switch is a dedicated network device that connects an enterprise's local network to a cloud service provider, enabling private network interconnection via physical leased lines or virtual interfaces. In this embodiment, the cloud leased line switch is used to carry leased line access and cloud inbound services, serving as the boundary of the cloud resource pool and connecting the Underlay network and the Overlay network. The Underlay network is the physical network infrastructure, including devices such as switches and routers, responsible for data transmission. The Overlay network is a logical virtual network built on top of the Underlay network, achieving logical isolation and cross-physical network communication through encapsulation technology. Within a single subnet, the cloud server establishes a Virtual Extended Local Area Network (VXLAN) connection with the cloud leased line switch, accessing the cloud via the cloud leased line switch-cloud leased line method. The cloud leased line switch is responsible for traffic access and forwarding; it can only forward north-south traffic, not east-west traffic. North-south traffic refers to communication traffic between external networks (such as the Internet) and internal networks (such as data centers), including traffic from users accessing internal services or internal services calling external resources, primarily involving client-server interaction. East-west traffic refers to horizontal communication traffic between servers, microservices, or devices within a data center, such as microservice calls and database interactions.

[0032] Optionally, users can create a single subnet and a single Virtual Private Cloud (VPC) within a single subnet area. Dedicated line traffic enters from the cloud dedicated line switch and is directly forwarded to the cloud server. A single subnet area does not require traffic to pass through a virtual gateway, reducing intermediate network nodes, optimizing resource utilization, and meeting the needs of users with a single VPC and single subnet. A virtual gateway is a network device in cloud computing, primarily used to manage and control communication within a Virtual Private Cloud (VPC), helping users achieve interconnectivity between different networks in the cloud.

[0033] In a multi-subnet zone, multiple subnets and multiple Virtual Private Clouds (VPCs) can be created. Within a multi-subnet zone, cloud servers and virtual gateways establish Virtual Extended LANs (VXLANs), and virtual gateways and cloud leased line switches also establish VXLANs. In a multi-subnet zone, cloud leased lines (i.e., cloud access) are established using a cloud leased line switch-virtual gateway and virtual gateway-cloud server approach. In the architecture where the cloud leased line switch and virtual gateway establish VXLANs, and the virtual gateway and cloud server establish VXLANs, all leased line traffic accesses the VPC through the virtual gateway, which is responsible for distribution within the cloud. Communication between cloud servers in different subnets within the multi-subnet zone is forwarded through the virtual gateway. Optionally, communication between different VPCs can be achieved through VPC peering connections (direct network connections established between virtual private clouds, allowing resource sharing between two VPCs), and traffic from VPC peering connections also needs to be forwarded by the virtual gateway. Optionally, VPCs in multi-subnet zones can communicate with WAN network elements, and the traffic between VPCs and WAN network elements is also forwarded by the virtual gateway.

[0034] Cloud servers with multiple subnets all need to perform traffic relay on a virtual gateway. This is suitable for users who need virtual gateway relay functionality, such as users who need multi-subnet interconnection, VPC peering connection, VPC-WAN interconnection, etc.

[0035] In this embodiment, the cloud server area is divided into single subnet areas and multiple subnet areas, with different areas corresponding to different cloud dedicated line opening methods (i.e. different cloud access methods) to meet the different needs of different customers.

[0036] Step S102: In response to the request to activate the cloud private line service, determine whether the virtual gateway with multiple subnets can undertake the cloud private line service based on the virtual gateway's specification and performance information.

[0037] The request operation for cloud private line service is used to indicate a request to activate the cloud private line. The specifications and performance metrics of the virtual gateway may include, but are not limited to, concurrent connections, throughput, bandwidth, and processing capacity.

[0038] Optionally, the virtual gateway controller can cyclically detect the performance indicators of the virtual gateway. If, based on the performance indicators, it is determined that the virtual gateway in a multi-subnet area cannot handle the cloud private line service, then step S103 is executed to activate the cloud private line service in a single subnet area. If, based on the performance indicators, it is determined that the virtual gateway in a multi-subnet area can handle the activated cloud private line, then step S104 is executed to activate the cloud private line service in the multi-subnet area. As an optional example, the performance indicators of the virtual gateway can be compared with a specified threshold to determine whether the virtual gateway can handle the cloud private line service. If the performance indicators of the virtual gateway are less than the specified threshold, it is determined that the virtual gateway can handle the cloud private line service, and the cloud private line is activated for the multi-subnet area. If the performance indicators of the virtual gateway are greater than or equal to the specified threshold, it is determined that the virtual gateway cannot handle the cloud private line service, and the cloud private line is activated for the single subnet area. For example, the performance indicators reported by the virtual gateway can be used to determine whether it can handle cloud private line services. If the performance indicators reported by the virtual gateway indicate that it cannot handle cloud private line services, then a cloud private line can be enabled for that service in a single subnet.

[0039] In this embodiment of the application, when multiple subnets cannot accommodate new cloud private lines, a cloud private line is opened in a single subnet, thereby ensuring the availability of cloud access for users and preventing the virtual gateway from exceeding its capacity due to the opening of new cloud private line services, which would affect other users.

[0040] Step S103: If it is determined that the virtual gateway in a multi-subnet area cannot handle the opening of the cloud private line, then open the cloud private line service in a single subnet area.

[0041] In an optional embodiment, opening a cloud private line for cloud private line services in a single subnet includes: For requests to activate cloud dedicated line services, create a Virtual Private Cloud (VPC), Virtual Router Forwarding Policy (VRF), and subnet for the cloud dedicated line service in a single subnet area; Based on the Overlay BGP routes published by the cloud server and the service-side Overlay BGP routes published by the cloud leased line switch, a virtual extended LAN is established between the cloud server and the cloud leased line switch in a single subnet to enable cloud leased line services within the single subnet. BGP (Border Gateway Protocol) is a core decentralized autonomous routing protocol on the Internet. Overlay BGP routes are used in the overlay network for exchanging routing information between Autonomous Systems (AS), primarily for route propagation and policy control (such as setting blacklists and whitelists). After the overlay network topology is configured, the system automatically deploys BGP control protocols between sites to propagate overlay network routes. Users can configure blacklists and whitelists to filter and publish or receive overlay WAN-side BGP routes.

[0042] Optionally, a cloud server in a single subnet logically has only a single subnet, with a one-to-one correspondence between the Virtual Private Cloud (VPC) and the subnet. That is, the VPC identifier (denoted as VPC-ID) corresponds one-to-one with the subnet identifier (subnet ID). By establishing the correspondence between VPC-ID and subnet ID, and establishing VXLAN between the cloud server and the dedicated line switch in the single subnet, the logical correspondence between the VPC-ID, subnet ID, and VNI (Virtual Network Identifier, a 24-bit field in the VXLAN protocol used to identify virtual networks, primarily used to distinguish traffic from different tenants or virtual networks) for cloud dedicated line access is determined. Therefore, in this embodiment, when opening a cloud dedicated line service in a single subnet, a first identifier is generated for the subnet, a second identifier is generated for the virtual private cloud, and a third identifier is generated for the virtual network interface of the virtual private cloud. The correspondence between the first, second, and third identifiers is recorded.

[0043] Optionally, when there are multiple subnets, the cloud leased line switch can establish VXLANs with cloud servers in different subnets. The cloud leased line switch identifies different users through VRF (Virtual Routing & Forwarding). If the cloud leased line switch and the cloud server establish an Overlay BGP connection, users can publish subnet segments via BGP when configuring subnet segments.

[0044] Step S104: If it is determined that the virtual gateway of the multi-subnet area can handle the opening of the cloud private line, open the cloud private line for the cloud private line service in the multi-subnet area.

[0045] In an optional embodiment, opening a cloud private line for cloud private line services in a multi-subnet area includes: Send the corresponding configuration information to the cloud server controller, virtual gateway controller, and leased line controller respectively, and create virtual routing forwarding policies; The cloud server and virtual gateway in the multi-subnet area establish a virtual extended LAN, the virtual gateway and the cloud dedicated line switch establish a virtual extended LAN, and send uplink static routes to the virtual gateway and downlink static routes to the cloud dedicated line switch to open the cloud dedicated line service in the multi-subnet area.

[0046] The cloud server controller manages cloud servers across multiple subnets and controls the distribution of cloud server configurations. The virtual gateway controller manages virtual gateways and controls the distribution of virtual gateway configurations. The leased line controller manages cloud leased line switches and controls the distribution of cloud leased line configurations. In this embodiment, after determining that a cloud leased line will be enabled in multiple subnets, corresponding configuration information is sent to the cloud server controller, virtual gateway controller, and leased line controller, respectively. The cloud server controller sends the cloud server configuration information to the cloud server. The virtual gateway controller sends the virtual gateway configuration information to the virtual gateway. The leased line controller sends the cloud leased line switch configuration information to the cloud leased line switch. The cloud leased line switch establishes a VXLAN with the virtual gateway, and the virtual gateway establishes a VXLAN with the cloud server, and issues uplink and downlink static routes respectively to enable the cloud leased line service in multiple subnets.

[0047] The cloud private line orchestration and management method provided in this application divides the cloud server area into single subnet areas and multiple subnet areas, with different areas corresponding to different cloud private line activation methods (i.e., different cloud access methods). Specifically, in a single subnet area, the cloud server establishes a virtual extended LAN with the cloud private line switch; in a multiple subnet area, the cloud server establishes a virtual extended LAN with a virtual gateway, and the virtual gateway establishes a virtual extended LAN with the cloud private line switch. By dividing the cloud server area into single and multiple subnet areas, flexible switching between single and multiple subnet areas can be achieved, allowing for flexible selection of cloud private line activation methods based on different business needs, thus meeting the diverse requirements of different users. Moreover, from a traffic perspective, this application embodiment can optimize traffic flow by reducing intermediate network nodes as needed, thereby optimizing resource utilization.

[0048] The cloud private line orchestration and management method provided in this application, in response to a request to activate a cloud private line service, determines whether a virtual gateway in a multi-subnet area can handle the activation of a cloud private line based on the virtual gateway's specifications and performance indicators. If it is determined that a virtual gateway in a multi-subnet area cannot handle the activation of a cloud private line, the cloud private line service is activated in a single subnet area. By monitoring the specifications and performance indicators of the virtual gateway, if the virtual gateway's performance indicators reach a threshold, when a customer activates a service, the new service is automatically switched to a single subnet area. This utilizes a cloud private line switch-cloud server activation method, ensuring the basic cloud access services of customers are implemented without affecting service activation due to insufficient resources. Furthermore, it guarantees the stability of the entire system and improves availability.

[0049] In an optional embodiment, since each virtual private cloud in a single subnet corresponds one-to-one with a subnet, to improve the timeliness and reduce the complexity of activating cloud private lines in a single subnet, after dividing the cloud server area into single subnets and multiple subnets, resources (such as VRF, VXLAN, BGP, etc.) in the single subnet can be pre-created and allocated according to a unified resource creation and allocation policy. When activating cloud private lines for cloud private line services in a single subnet, the created virtual private clouds, virtual routing forwarding policies, and subnets can be allocated to the cloud private line services.

[0050] In an optional embodiment, the cloud private line orchestration and management method further includes: in response to triggering a resource reclamation operation, performing resource reclamation in a single subnet area to reclaim resources allocated for the cloud private line service and improve resource utilization. The resource reclamation operation can be triggered by a user or by meeting specified conditions. For example, a resource reclamation operation can be triggered when a user terminates the cloud private line service.

[0051] In an optional embodiment, the orchestration and management method for the cloud private line further includes: The page displays a cloud dedicated line activation page, which includes a selection control for selecting whether to activate a cloud dedicated line in a single subnet or multiple subnets. In response to detecting a selection operation on the selection control, the selected area is determined. If the selected area is the single subnet, the cloud dedicated line is activated in the single subnet; or, if the selected area is the multiple subnet, the cloud dedicated line is activated in the multiple subnets.

[0052] For example, when a user activates a dedicated cloud line on the cloud resource management platform, the platform displays a dedicated cloud line activation page. This page includes selection controls to choose between a single subnet or multiple subnets. Users can choose between a single subnet or multiple subnets based on their needs: users requiring only a single subnet and dedicated cloud access can choose a single subnet; users requiring inter-subnet connectivity and VPC peering can choose multiple subnets. If a user selects a single subnet, a one-to-one correspondence is established between the virtual private cloud and the subnet.

[0053] Figure 2 A schematic diagram illustrating a cloud private line orchestration and management method according to another embodiment of this application is shown. Figure 2 As shown, the orchestration and management method for this cloud private line includes: Step S201: Divide the cloud server region into single subnet regions and multi-subnet regions.

[0054] Step S202: In response to the request to activate the cloud private line service, determine whether the virtual gateway in the multi-subnet area can undertake the cloud private line service based on the virtual gateway's specification and performance information.

[0055] Step S203: If it is determined that the virtual gateway in a multi-subnet area cannot handle cloud private line services, then enable cloud private line services in a single subnet area.

[0056] Step S204: In response to the cross-regional communication needs of the cloud private line service in a single subnet, the cross-regional communication needs instruct the cloud private line service in the single subnet to communicate with the virtual private cloud in multiple subnets, reclaim the resources allocated for the cloud private line service in the single subnet, and open the cloud private line for the cloud private line service in multiple subnets so that the cloud private line service can communicate with the virtual private cloud in multiple subnets.

[0057] Steps S201-S203 can be referred to Figure 1 The embodiments shown are not described in detail here to avoid repetition.

[0058] For step S204, when a service that has already opened a cloud private line in a single subnet needs to communicate with other virtual private clouds (VPCs), such as needing to use VPC peering connections, the resources allocated for the cloud private line service in the single subnet can be reclaimed, and a cloud private line can be opened for the cloud private line service in multiple subnets (for example, refer to step S104) so ​​that the cloud private line service can communicate with the virtual private clouds in multiple subnets.

[0059] The cloud private line orchestration and management method provided in this application divides the cloud server area into a single subnet and multiple subnets, providing two ways to open cloud private lines, improving the flexibility and applicability of cloud access, and allowing flexible switching of services between single and multiple subnets to meet different business needs.

[0060] Figure 3 This diagram illustrates the application of the cloud private line orchestration management method according to an embodiment of this application. The cloud private line orchestration management method is applied to a cloud private line converged orchestrator. The cloud private line converged orchestrator is used in cloud-network convergence to uniformly manage network resources, intelligently combine resources through integration and optimization, and achieve flexible end-to-end scheduling and efficient service.

[0061] like Figure 3 As shown, the method in this application embodiment can be mainly divided into: control plane and data plane. Control plane and data plane are two core concepts in network architecture, differing primarily in their functional positioning. The control plane is mainly responsible for decision-making and policy formulation (e.g., routing and traffic management). The control plane mainly includes cloud leased line converged orchestrators, leased line controllers, virtual gateway controllers, cloud server controllers, etc. The data plane is responsible for executing specific data forwarding operations. The data plane mainly includes: cloud leased line switches, virtual gateways, cloud servers, Spine (backbone) switches (…). Figure 3 The Chinese text refers to a switch called Spine or Leaf. Figure 3 Spine switches (referred to as Leaf switches in some regions) are responsible for achieving high availability and fault tolerance in data center networks, implementing load balancing and redundancy through a multi-path network architecture. Leaf switches typically have a large number of ports, supporting connections to multiple servers and devices, and providing high-bandwidth and low-latency data forwarding capabilities. Spine (backbone) switches and Leaf switches constitute the Spine-Leaf architecture. The Spine-Leaf architecture is a data center network architecture design widely used in high-performance, low-latency cloud computing and large-scale data center environments. This architecture provides high bandwidth, scalability, and efficient network traffic processing capabilities through a flat network topology.

[0062] The cloud private line converged orchestrator mainly manages private line controllers, virtual gateway controllers, cloud server controllers, etc. It controls the path of cloud private line traffic by orchestrating the various controllers to achieve different functions.

[0063] The leased line controller is responsible for managing cloud leased line switches and controlling the distribution of configurations for cloud leased line switches.

[0064] The virtual gateway controller is responsible for managing virtual gateways and controlling the distribution of gateway configurations.

[0065] The cloud server controller is responsible for managing cloud servers and controlling the distribution of server configurations.

[0066] The virtual gateway is responsible for the distribution and relay of VPC-related traffic. Cloud dedicated line switches carry dedicated line access and cloud services, serve as the boundary of the cloud resource pool, and connect the Underlay network and the Overlay network.

[0067] In the embodiments of this application, such as Figure 3 As shown, the cloud server is divided into multiple single subnets ( Figure 3 The diagram illustrates two single subnets and multiple subnets. Figure 3 The red dotted lines indicate that the cloud server in a single subnet establishes a virtual extended LAN with the cloud leased line switch, while the red solid lines indicate that the cloud server in a multi-subnet establishes a virtual extended LAN with the virtual gateway, and the virtual gateway establishes a virtual extended LAN with the cloud leased line switch.

[0068] For a single subnet, users can create a single subnet and a single Virtual Private Cloud (VPC). Dedicated line traffic enters through the cloud dedicated line switch and is directly forwarded to the cloud server. A single subnet does not require traffic to pass through a virtual gateway, reducing intermediate network nodes, optimizing resource utilization, and meeting the needs of users with a single VPC and single subnet. Single subnets are suitable for users with a single VPC and single network, eliminating the need for traffic relay through a virtual gateway. Within a single subnet, the cloud server establishes a Virtual Extended Local Area Network (VXLAN) connection with the cloud dedicated line switch, accessing the cloud via the dedicated line switch-cloud dedicated line. The dedicated line switch is responsible for traffic access and forwarding; it can only forward north-south traffic, not east-west traffic.

[0069] For multi-subnet zones, users can create multiple subnets and multiple Virtual Private Clouds (VPCs). Within a multi-subnet zone, cloud servers and virtual gateways establish Virtual Extended LANs (VXLANs), and virtual gateways and cloud leased line switches also establish VXLANs. Cloud leased lines (i.e., cloud access) are established using a cloud leased line switch-virtual gateway and virtual gateway-cloud server configuration. In the architecture where the cloud leased line switch and virtual gateway establish VXLANs, and the virtual gateway and cloud server establish VXLANs, all leased line traffic accesses the VPC through the virtual gateway, which is responsible for distribution within the cloud. Communication between cloud servers in different subnets within the multi-subnet zone is forwarded through the virtual gateway. Optionally, communication between different VPCs can be achieved through VPC peering connections (direct network connections established between virtual private clouds, allowing resource sharing between two VPCs), and traffic from VPC peering connections also needs to be forwarded by the virtual gateway. Optionally, VPCs in multi-subnet zones can communicate with WAN network elements, and the traffic between VPCs and WAN network elements is also forwarded by the virtual gateway.

[0070] Cloud servers with multiple subnets all need to perform traffic relay on a virtual gateway. This is suitable for users who need virtual gateway relay functionality, such as users who need multi-subnet interconnection, VPC peering connection, VPC-WAN interconnection, etc.

[0071] When a user creates a Virtual Private Cloud (VPC) on the cloud resource management platform, the platform displays a dedicated cloud line activation page. This page includes selection controls to choose between a single subnet or multiple subnets. Users can choose between a single subnet or multiple subnets based on their needs: users requiring only a single subnet and dedicated cloud access can choose a single subnet; users requiring inter-subnet connectivity and VPC peering can choose multiple subnets. If a user selects a single subnet, a one-to-one correspondence is established between the VPC and the subnet. When activating a dedicated cloud line, the dedicated cloud line orchestrator obtains relevant information about the VPC to determine whether the cloud server is in a single or multiple subnet.

[0072] The virtual gateway controller continuously monitors the specifications and performance metrics of the virtual gateway. If these metrics exceed a threshold, the controller reports this to the cloud private line convergence orchestrator. When a user activates a cloud private line, the virtual gateway is deemed unsuitable for handling services based on the reported performance metrics. The cloud private line convergence orchestrator then activates the cloud private line for that service within the single subnet, ensuring the availability of the user's cloud private line access and preventing the virtual gateway from exceeding its capacity due to new user service activations, thus impacting other users.

[0073] Optionally, when a service that has already opened a cloud private line in a single subnet needs to communicate with other virtual private clouds (VPCs), such as needing to use VPC peering, the resources allocated for the cloud private line service in the single subnet can be reclaimed, and a cloud private line can be opened for the cloud private line service in multiple subnets (for example, refer to step S104) so ​​that the cloud private line service can communicate with virtual private clouds in multiple subnets.

[0074] In this embodiment, the scope of the cloud leased line converged orchestrator is expanded from virtual gateways and leased line switches to the management of cloud servers; it covers physical networks, overlay networks, servers, and switches, increasing global orchestration capabilities and realizing full-link control, orchestration, and scheduling management, thereby improving management efficiency and system flexibility. Specifically, compared to ordinary cloud leased line orchestrators, the scope of the cloud leased line converged orchestrator provided in this embodiment is expanded from virtual gateways and cloud leased line switches to the management of cloud servers; and it also covers physical networks, overlay networks, servers, and switches.

[0075] This application embodiment divides cloud servers into single subnets and multiple subnets. The cloud private line convergence orchestrator can flexibly switch services between single and multiple subnets, dynamically identify service scenarios, and meet the forwarding needs of different traffic. Traditional network architectures are often static, selecting only one network architecture and not allowing the coexistence of two architectures. This application allows for flexible selection of single and multiple subnets, greatly improving flexibility and applicability.

[0076] In the implementation of a single subnet, the cloud private line converged orchestrator has the functions of resource creation and reclamation. Through unified management and allocation of resource pools such as resources (VRF, VXLAN, BGP), it can quickly realize the activation of cloud private line services, which is more timely than the traditional mode of creating resources while activating them.

[0077] The cloud private line converged orchestrator can detect the specifications and performance of network elements such as virtual gateways. When the specifications and performance exceed the limits, the traditional approach is to wait for the virtual gateway physical server to expand its capacity, which greatly restricts the activation of customer services. However, this invention can flexibly adjust the strategy, allowing cloud private line traffic to bypass the virtual gateway node and communicate directly with the single subnet of the cloud server, ensuring the normal operation of the user's basic services and greatly improving the system's adaptability.

[0078] This application embodiment greatly improves the management efficiency, flexibility, stability and availability of the cloud private line system through unified scheduling of the cloud private line converged orchestrator, flexible single subnet and multi-subnet partitioning, automated traffic resource orchestration and network element node performance monitoring mechanism.

[0079] Figure 4 This application illustrates a cloud private line orchestration and management device provided in an embodiment of the present application. For example... Figure 4 As shown, the orchestration and management device 400 for the cloud private line includes: The partitioning module 401 is used to divide the cloud server area into a single subnet area and a multi-subnet area; wherein, the cloud server in the single subnet area establishes a virtual extended local area network with the cloud dedicated line switch; the cloud server in the multi-subnet area establishes a virtual extended local area network with the virtual gateway, and the virtual gateway establishes a virtual extended local area network with the cloud dedicated line switch. The judgment module 402 is used to respond to the request operation to activate the cloud private line service and determine whether the virtual gateway of the multi-subnet area can undertake the cloud private line service based on the specification and performance index information of the virtual gateway. The activation module 403 is used to activate the cloud dedicated line for the cloud dedicated line service in a single subnet area when it is determined that the virtual gateway of the multi-subnet area cannot undertake the cloud dedicated line service; and to activate the cloud dedicated line for the cloud dedicated line service in the multi-subnet area when it is determined that the virtual gateway of the multi-subnet area can undertake the cloud dedicated line service.

[0080] In an optional embodiment, the activation module is further configured to: in response to the request operation to activate the cloud dedicated line service, create a virtual private cloud and a virtual routing forwarding policy for the cloud dedicated line service in the single subnet area; and establish a virtual extended local area network between the cloud server and the cloud dedicated line switch in the single subnet area according to the overlay BGP route published by the cloud server and the overlay BGP route of the service end published by the cloud dedicated line switch, so as to activate the cloud dedicated line for the cloud dedicated line service in the single subnet area.

[0081] In an optional embodiment, the activation module is further configured to: when activating the cloud private line service in the single subnet area, generate a first identifier for the subnet, generate a second identifier for the virtual private cloud, generate a third identifier for the virtual network interface of the virtual private cloud, and record the correspondence between the first identifier, the second identifier and the third identifier.

[0082] In an optional embodiment, the activation module is further configured to: send corresponding configuration information to the cloud server controller, virtual gateway controller, and dedicated line controller respectively, and create a virtual routing forwarding policy; establish a virtual extended LAN between the cloud server and the virtual gateway in the multi-subnet area, establish a virtual extended LAN between the virtual gateway and the cloud dedicated line switch, send an uplink static route to the virtual gateway, and send a downlink static route to the cloud dedicated line switch, thereby activating the cloud dedicated line service in the multi-subnet area.

[0083] In an optional embodiment, the activation module is further configured to: perform resource reclamation in the single subnet area in response to triggering a resource reclamation operation.

[0084] In an optional embodiment, the activation module is further configured to: respond to the cross-regional communication requirements of the cloud private line service in the single subnet area, the cross-regional communication requirements instructing the cloud private line service in the single subnet area to communicate with the virtual private clouds in the multiple subnet areas, reclaim the resources allocated for the cloud private line service in the single subnet area, and activate the cloud private line for the cloud private line service in the multiple subnet areas, so that the cloud private line service can communicate with the virtual private clouds in the multiple subnet areas.

[0085] In an optional embodiment, the device further includes an interaction module for displaying a cloud dedicated line activation page, the cloud dedicated line activation page including a selection control for selecting whether to activate a cloud dedicated line in a single subnet or multiple subnets; in response to detecting a selection operation on the selection control, determining the selected area; the activation module is further configured to: if the selected area is the single subnet, activate a cloud dedicated line in the single subnet, or if the selected area is the multiple subnet, activate a cloud dedicated line in the multiple subnets.

[0086] The above-described apparatus can execute the method provided in the embodiments of the present invention, and has the corresponding functional modules and beneficial effects for executing the method. Technical details not described in detail in this embodiment can be found in the cloud private line orchestration and management method provided in the embodiments of the present invention.

[0087] Figure 5 A schematic diagram of the structure of an electronic device according to an embodiment of the present invention is shown. Figure 5 As shown, the electronic device includes: The system includes a processor 501, a communication interface 502, a memory 503, and a communication bus 504. The processor 501, communication interface 502, and memory 503 communicate with each other via the communication bus 504. Memory 503 is used to store computer programs; When processor 501 executes the program stored in memory 503, it performs the following steps: The cloud server area is divided into single subnet areas and multi-subnet areas; wherein, the cloud server in the single subnet area establishes a virtual extended local area network with the cloud dedicated line switch; the cloud server in the multi-subnet area establishes a virtual extended local area network with the virtual gateway, and the virtual gateway establishes a virtual extended local area network with the cloud dedicated line switch. In response to the request to activate the cloud private line service, the system determines whether the virtual gateway of the multi-subnet area can undertake the cloud private line service based on the specifications and performance indicators of the virtual gateway. If it is determined that the virtual gateway of the multi-subnet area cannot handle the cloud private line service, the cloud private line is opened for the cloud private line service in the single subnet area.

[0088] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0089] The communication interface is used for communication between the aforementioned terminal and other devices.

[0090] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0091] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0092] In another embodiment of the present invention, a computer-readable storage medium is also provided, which stores instructions that, when executed on a computer, cause the computer to perform the cloud private line orchestration and management method described in any of the above embodiments.

[0093] In another embodiment of the present invention, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute the cloud private line orchestration and management method described in any of the above embodiments.

[0094] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0095] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0096] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0097] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention are included within the scope of protection of the present invention.

Claims

1. A cloud private line orchestration management method, characterized by, The method comprises the following steps: The cloud server area is divided into a single subnet area and a multi-subnet area; wherein the cloud server of the single subnet area establishes a virtual extended local area network with a cloud private line switch; the cloud server and the virtual gateway of the multi-subnet area establish a virtual extended local area network, and the virtual gateway establishes a virtual extended local area network with the cloud private line switch; In response to a request operation of opening a cloud private line service, whether the virtual gateway of the multi-subnet area can undertake the cloud private line service is determined according to the performance index information of the virtual gateway; In the case that the virtual gateway of the multi-subnet area cannot undertake the cloud private line service, a cloud private line is opened for the cloud private line service in the single subnet area; In the case that the virtual gateway of the multi-subnet area can undertake the cloud private line service, a cloud private line is opened for the cloud private line service in the multi-subnet area.

2. The method of claim 1, wherein, The step of opening a cloud private line for the cloud private line service in the single subnet area comprises the following steps: For the request operation of opening a cloud private line service, a virtual private cloud, a virtual routing forwarding policy and a subnet are created for the cloud private line service in the single subnet area; According to the Overlay BGP route published by the cloud server and the Overlay BGP route of the service end published by the cloud private line switch, the cloud server of the single subnet area establishes a virtual extended local area network with the cloud private line switch to open a cloud private line for the cloud private line service in the single subnet area.

3. The method of claim 2, wherein, The method further comprises the following steps: When a cloud private line is opened for the cloud private line service in the single subnet area, a first identifier is generated for the subnet, a second identifier is generated for the virtual private cloud, a third identifier is generated for the virtual network interface of the virtual private cloud, and the correspondence between the first identifier, the second identifier and the third identifier is recorded.

4. The method of claim 1, wherein, After the cloud server area is divided into a single subnet area and a multi-subnet area, the method further comprises the following steps: According to the resource uniform creation and uniform distribution strategy, the resources of the single subnet area are pre-created and distributed, wherein the virtual private cloud, the virtual routing forwarding policy and the subnet are pre-created. The step of opening a cloud private line for the cloud private line service in the single subnet area comprises the following step: the virtual private cloud, the virtual routing forwarding policy and the subnet that have been created in the single subnet area are allocated to the cloud private line service.

5. The method of claim 4, wherein, The step of opening a cloud private line for the cloud private line service in the multi-subnet area comprises the following steps: Respective configuration information is sent to the cloud server controller, the virtual gateway controller and the private line controller, and a virtual routing forwarding policy is created; The cloud server and the virtual gateway of the multi-subnet area establish a virtual extended local area network, the virtual gateway establishes a virtual extended local area network with the cloud private line switch, an uplink static route is sent to the virtual gateway, and a downlink static route is sent to the cloud private line switch, so as to open a cloud private line for the cloud private line service in the multi-subnet area.

6. The method of claim 1, wherein, The method further comprises the following steps: In response to triggering a resource recycling operation, resource recycling is performed in the single subnet area.

7. The method of claim 1, wherein, The method further comprises the following steps: In response to a cross-region communication requirement of the cloud line service of the single-subnet region, the cross-region communication requirement indicating that the cloud line service of the single-subnet region communicates with the virtual private cloud in the multi-subnet region, resources allocated for the cloud line service in the single-subnet region are reclaimed, and a cloud line is opened for the cloud line service in the multi-subnet region, so that the cloud line service communicates with the virtual private cloud in the multi-subnet region.

8. A cloud private line orchestration and management device, characterized in that, Comprise: The division module is used for dividing the cloud server region into a single-subnet region and a multi-subnet region; wherein the cloud server of the single-subnet region establishes a virtual extended local area network with a cloud line switch; the cloud server and the virtual gateway of the multi-subnet region establish a virtual extended local area network, and the virtual gateway establishes a virtual extended local area network with a cloud line switch; The judgment module is used for determining whether the virtual gateway of the multi-subnet region can undertake the cloud line service according to the specification performance index information of the virtual gateway in response to a request operation of opening the cloud line service; The opening module is used for opening a cloud line for the cloud line service in the single-subnet region in the case that the virtual gateway of the multi-subnet region cannot undertake the cloud line service; and opening a cloud line for the cloud line service in the multi-subnet region in the case that the virtual gateway of the multi-subnet region can undertake the cloud line service.

9. An electronic device, comprising: The processor, the memory and the program or the instructions stored on the memory and executable on the processor are included, and the program or the instructions are executed by the processor to implement the method in any one of claims 1-7.

10. A readable storage medium, characterized by, The program or the instructions are stored on the readable storage medium, and the program or the instructions are executed by the processor to implement the method in any one of claims 1-7.

Images