CN117640488A - Route configuration method, device, equipment and storage medium - Google Patents

Abstract

The application provides a route configuration method, a device, equipment and a storage medium. The method comprises the following steps: acquiring a first BGP configuration, a second BGP configuration, a third BGP configuration and a fourth BGP configuration; issuing a first BGP configuration to the access gateway, issuing a second BGP configuration to the first device, wherein the first BGP configuration and the second BGP configuration are used for establishing a first BGP neighbor relation between the access gateway and the first device, and the first BGP neighbor relation is used for sharing routing configuration between the access gateway and the first device; and transmitting a third BGP configuration to the access gateway and transmitting a fourth BGP configuration to the cloud gateway, wherein the third BGP configuration and the fourth BGP configuration are used for establishing a second BGP neighbor relation between the access gateway and the cloud gateway, and the second BGP neighbor relation is used for sharing route configuration between the access gateway and the cloud gateway, so that the route configuration efficiency and the route configuration accuracy can be improved.

Description

Route configuration method, device, equipment and storage medium

Technical Field

The embodiment of the application relates to the field of cloud technology, in particular to a route configuration method, device, equipment and storage medium.

Background

In a hybrid cloud scenario, in order to enable an internet data center (Internet Data Center, IDC) server or customer premise equipment (Customer premises equipment, CPE) on the private cloud side to access a public cloud, as shown in fig. 1, a user needs to send a routing configuration from the private cloud to the public cloud to a cloud controller through an on-cloud console, for example, a network segment route 172.16.0.0/24 of the public cloud is shown in fig. 1, and the cloud controller sends the routing configuration to an access gateway and a cloud gateway. In addition, the user also needs to configure the routing configuration for the IDC server or CPE.

Similarly, in a hybrid cloud scenario, in order to enable a public cloud to access a private cloud, a user needs to send a routing configuration from the public cloud to the private cloud to a cloud controller through a console on the cloud, and the cloud controller sends the routing configuration to an access gateway and a cloud gateway. In addition, the user also needs to configure the routing configuration for the IDC server or CPE.

However, the above routing configuration process is complicated, resulting in lower routing configuration efficiency, and when there are more routing configuration entries, there is also a problem that the routing configuration accuracy is lower.

Disclosure of Invention

The application provides a route configuration method, a device, equipment and a storage medium, which can improve the route configuration efficiency, and particularly, for the case of more route configuration items, the route configuration is configured for only one equipment, so that the situation of configuration errors can be reduced.

In a first aspect, an embodiment of the present application provides a routing configuration method, where the method is applied to a cloud controller, where the cloud controller is connected to an access gateway and a cloud gateway on a public cloud side, and the access gateway is further connected to a first device on a private cloud side and the cloud gateway, and the method includes: acquiring a first BGP configuration, a second BGP configuration, a third BGP configuration and a fourth BGP configuration; issuing a first BGP configuration to the access gateway and issuing a second BGP configuration to the first device, wherein the first BGP configuration and the second BGP configuration are used for establishing a first BGP neighbor relation between the access gateway and the first device, and the first BGP neighbor relation is used for sharing route configuration between the access gateway and the first device; issuing a third BGP configuration to the access gateway and issuing a fourth BGP configuration to the cloud gateway, wherein the third BGP configuration and the fourth BGP configuration are used for establishing a second BGP neighbor relation between the access gateway and the cloud gateway, and the second BGP neighbor relation is used for sharing routing configuration between the access gateway and the cloud gateway; the routing configuration is a first routing configuration from the private cloud to the public cloud or a second routing configuration from the public cloud to the private cloud.

In a second aspect, an embodiment of the present application provides a cloud controller, where the cloud controller is connected to an access gateway and a cloud gateway on a public cloud side, the access gateway is further connected to a first device on a private cloud side and the cloud gateway, and the cloud controller includes: the system comprises an acquisition module and a issuing module, wherein the acquisition module is used for acquiring a first BGP configuration, a second BGP configuration, a third BGP configuration and a fourth BGP configuration; the issuing module is used for: issuing a first BGP configuration to the access gateway and issuing a second BGP configuration to the first device, wherein the first BGP configuration and the second BGP configuration are used for establishing a first BGP neighbor relation between the access gateway and the first device, and the first BGP neighbor relation is used for sharing route configuration between the access gateway and the first device; issuing a third BGP configuration to the access gateway and issuing a fourth BGP configuration to the cloud gateway, wherein the third BGP configuration and the fourth BGP configuration are used for establishing a second BGP neighbor relation between the access gateway and the cloud gateway, and the second BGP neighbor relation is used for sharing routing configuration between the access gateway and the cloud gateway; the routing configuration is a first routing configuration from the private cloud to the public cloud or a second routing configuration from the public cloud to the private cloud.

In a third aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory for performing the method as in the first aspect or in various implementations thereof.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program, the computer program causing a computer to perform a method as in the first aspect or implementations thereof.

In a fifth aspect, embodiments of the present application provide a computer program product comprising computer program instructions for causing a computer to perform the method as in the first aspect or implementations thereof.

In a sixth aspect, embodiments of the present application provide a computer program that causes a computer to perform the method as in the first aspect or implementations thereof.

According to the technical scheme provided by the embodiment of the application, as the cloud controller issues BGP configuration for the first device, the access gateway and the cloud gateway, the access gateway can respectively establish BGP neighbor relation with the first device and the cloud gateway, based on the BGP neighbor relation, after any one of the three devices is configured with the routing configuration between the private cloud and the public cloud, the device can share the routing configuration to the BGP neighbor of the device based on the BGP neighbor relation, and therefore the three devices can all obtain the routing configuration. The route configuration method is simpler, so that the route configuration efficiency can be improved, and particularly, for the case of more route configuration items, the route configuration is only required to be configured for one device, so that the situation of configuration errors can be reduced.

Drawings

Fig. 1 is a diagram of a network structure provided in the related art;

fig. 2 is a network architecture diagram provided in an embodiment of the present application;

fig. 3 is a flowchart of a route configuration method provided in an embodiment of the present application;

fig. 4 is a flowchart of another route configuration method provided in an embodiment of the present application;

fig. 5 is a flowchart of another route configuration method according to an embodiment of the present application;

fig. 6 is a flowchart of another route configuration method according to an embodiment of the present application;

fig. 7 is a flowchart of another route configuration method according to an embodiment of the present application;

fig. 8 is a network architecture diagram provided in an embodiment of the present application;

FIG. 9 is a schematic diagram of a FCR containerized deployment provided by an embodiment of the present application;

fig. 10 is a schematic diagram of a cloud controller 1000 according to an embodiment of the present application;

fig. 11 is a schematic block diagram of an electronic device provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The application relates to the field of Cloud technology, and Cloud technology (Cloud technology) refers to a hosting technology for integrating hardware, software, network and other series resources in a wide area network or a local area network to realize calculation, storage, processing and sharing of data.

Cloud technology (Cloud technology) is based on the general terms of network technology, information technology, integration technology, management platform technology, application technology and the like applied by Cloud computing business models, and can form a resource pool, so that the Cloud computing business model is flexible and convenient as required. Cloud computing technology will become an important support. Background services of technical networking systems require a large amount of computing, storage resources, such as video websites, picture-like websites, and more portals. Along with the high development and application of the internet industry, each article possibly has an own identification mark in the future, the identification mark needs to be transmitted to a background system for logic processing, data with different levels can be processed separately, and various industry data needs strong system rear shield support and can be realized only through cloud computing.

Hybrid clouds (Hybrid clouds) merge Public clouds (Public clouds) and Private clouds (Private clouds), which are the main modes and development directions of Cloud computing in recent years. Private clouds are mainly for enterprise users, and for safety reasons, enterprises prefer to store data in the private clouds, but at the same time wish to obtain computing resources of public clouds, in which case hybrid clouds are increasingly adopted, and mix and match the public clouds and the private clouds to obtain the best effect.

Before introducing the technical solutions of the present application, the following first describes relevant knowledge of the present application:

1. network function virtualization (Network Functions Virtualization, NFV) refers to the implementation of various network functions on standardized universal internet technology (Internet Technology, IT) devices (X86 servers, storage devices and switches) using virtualization technology. The NFV aims to replace private, dedicated and closed network elements in a communication network and realize an open architecture of a unified general hardware platform and business logic software.

NFV builds many types of network devices, such as servers, switches, storage devices, etc., as a data center network, virtually forms Virtual Machines (VMs) by means of IT-borrowing virtualization technology, and then deploys conventional communication technology (Communication Technology, CT) traffic onto the VMs. The special function of the device is realized by special devices before the NFV appears, the control plane of the device is separated from the special device, the control planes of different devices are based on virtual machines, and the virtual machines are based on cloud operating systems, so that when enterprises need to deploy new services, only corresponding virtual machines are needed to be created on an open virtual machine operating platform, and then software packages with corresponding functions are installed on the virtual machines. This approach we call network function virtualization.

The NFV architecture consists of three parts, namely, a basic network function virtualization architecture, virtual network functions, management automation and network arrangement:

the basic network virtualization architecture (Network Functions Virtualization Infrastructure, NFVI), which is just like a mobile phone system that is introduced by each mobile phone manufacturer, gives basic components to hardware devices, and supports software or container management platforms that are required by network applications.

Virtual network functions (Virtual Network Functions, VNF), which are software applications that implement network functions, such as forwarding services, IP configuration, etc., as compared to Applications (APP) on a cell phone. In the NFV architecture, various VNFs are implemented on the basis of NFVI. Since NFVI is a standardized architecture, different VNFs gain versatility and are no longer dependent on the original black box device.

Management automation and network orchestration (Management and orchestration, MANO), which is a unified framework for managing VNFs and NFVI, facilitates traffic orchestration and device management for operation and maintenance personnel.

NFV has many benefits over traditional physical network devices, see table 1:

TABLE 1

2. Proprietary cloud networks, such as virtual private clouds (Virtual Private Cloud, VPC), are an isolated network environment built based on enterprise clouds, with logical complete isolation between proprietary cloud networks. A proprietary cloud network provides two capabilities, one of which is that a user can customize the network topology, including selecting a free IP address range, partitioning segments, configuring routing tables, gateways, and so on. The other capability is that the cloud-on and cloud-off resources use the same network address plan to realize smooth migration and cloud-on of the application by connecting the private line or virtual private network (Virtual Private Network, VPN) with the original data center.

Each private cloud network consists of a private network segment, a router and at least one switch. The router is a hub of the private cloud network, and as an important functional component in the private cloud network, can be connected with each switch in the private cloud network, and is also gateway equipment for connecting the private cloud network and other networks. The switch is basic network equipment forming a proprietary cloud network and is used for connecting different cloud product instances.

3. The border gateway protocol (Border Gateway Protocol, BGP) is a path vector routing protocol that enables routing between autonomous systems (Autonomous System, AS) to be reachable and selects the best route. The purpose of the BGP protocol itself is to communicate routing information.

4. The AS is a collection of internet protocol (Internet Protocal, IP) networks and devices managed by a single organization or organization. There are normally a large number of BGP neighbor relationships between ases. The BGP neighbor relation establishing process is a process in which two parties running BGP protocol find each other and establish connection.

5. The BGP neighbor relation establishment process comprises the following steps:

step 1: some BGP devices, such as BGP routers or BGP gateways, may have some latency after their operation. This period of time defaults to 32s when the BGP device is in an Idle (Idle) state.

It should be appreciated that if the BGP device does not know the routes of the BGP neighbors of the other party at this time, it is always in Idle state, and thus it needs to be ensured that the BGP device and its BGP neighbors can PING with each other.

Step 2: a transport control protocol (Transport control Protocol, TCP) connection needs to be established between the BGP device and its BGP neighbors.

Wherein the BGP device may listen to its 179 ports while attempting to establish a TCP connection with its BGP neighbors. The BGP device is now in a connected (Connect) state. If the TCP connection establishment between the BGP device and its BGP neighbors is complete, the BGP device enters the next state, open send (OpenSent) state. If a TCP connection establishment between the BGP device and its BGP neighbors fails, the BGP device enters an Active (Active) state. If the BGP device enters an Active state, the BGP device waits for the TCP connection of its BGP neighbor and also rolls back to the Connect state at intervals to attempt to establish the TCP connection with the opposite side.

Step 3: the BGP device exchanges and validates parameters with its BGP neighbors.

After the TCP connection between the BGP device and its BGP neighbor is established, an Open (Open) message may be sent between the BGP device and its BGP neighbor next, where the BGP device is in an opencount state. After receiving the Open message sent by its BGP neighbor, some parameters, such AS number, router identification number, authentication password, etc., can be negotiated through the Open message, and if the parameter negotiation fails at this time, the BGP device will fall back to Idle state. If the negotiation is successful, the BGP device may attempt to send keep-alive (keepalive) messages, at which point the BGP device is in an open confirm (OpenConfirm) state. After receiving the keep message sent by its BGP neighbor, the BGP device enters an Establish (Establish) state, which indicates that the BGP device formally establishes a neighbor relationship with its BGP neighbor.

6. Containerization refers to packaging software code and all components needed (e.g., libraries, frameworks, and other dependencies) together, keeping them isolated in their own "container". Based on this, the software or applications within the container can move and run in unison across any environment and any infrastructure, independent of the operating system of that environment or infrastructure. The container is equivalent to a fully functional, portable computing environment.

7. Binary deployment refers to a scheme in which code is written directly on an operating system.

The technical problems and the inventive concepts to be solved by the technical scheme of the present application will be described below:

at present, since public cloud and private cloud belong to different cloud manufacturers, when route configuration is performed from private cloud to public cloud or from public cloud to private cloud, a public cloud side and a private cloud side both need a user to perform route configuration. However, this route configuration process is complicated, resulting in a problem of low route configuration efficiency and accuracy.

In order to solve the technical problems, the method and the device establish a BGP neighbor relation between a first device on a private cloud side and an access gateway and a BGP neighbor relation between the access gateway and a cloud gateway on a public cloud side, so that after the first device, the access gateway or the cloud gateway are configured with route configuration, the route configuration can be shared based on the BGP neighbor relation, the route configuration mode is relatively simple, and therefore the route configuration efficiency and the route configuration accuracy can be improved.

The technical solution of the present application is applicable to the network architecture shown in fig. 2, but is not limited thereto:

fig. 2 is a diagram of a network architecture provided in an embodiment of the present application, and as shown in fig. 2, the network architecture adopts a design idea of separation of forwarding and control (NFV) control, and is divided into a cloud controller 21 for issuing a control command and network devices for performing data forwarding, where the network devices include: the first device 22 on the private cloud side, the cloud gateway 23 on the public cloud side, and the access gateway 24 are not limited thereto.

Alternatively, the cloud controller 21 may be connected to the first device 22, the cloud gateway 23, and the access gateway 24 via a remote procedure scheduler (Remote Procedure Call, RPC), such as a GRPC interface, respectively, and the access gateway 24 may be connected to the first device 22 and the cloud gateway 23, respectively.

Alternatively, the first device 22 may be an IDC server, CPE, or the like, which is not limited in this application.

The cloud gateway 23 is used for the scenes of hybrid cloud private line access, inter-domain intercommunication, public cloud black stone intercommunication and the like, realizes high-performance forwarding, supports multi-tenant access, and supports the characteristics of fragmentation, recombination, speed limitation and the like. The cloud gateway 23 may be a next generation gateway (Next Generation Gate Way, NGW), but is not limited thereto.

The access gateway 24 is also called an intersubnetwork connector and a protocol converter, and the access gateway 24 is used for realizing interconnection of networks with different protocols of two higher layers, namely private cloud and public cloud.

The technical scheme of the application will be described in detail as follows:

fig. 3 is a flowchart of a routing configuration method provided in an embodiment of the present application, where the method may be performed by a cloud controller, a first device on a private cloud side, an access gateway, and a cloud gateway on a public cloud side, where the public cloud may be a private cloud network, where the cloud controller is connected to the access gateway and the cloud gateway, and the access gateway is further connected to the first device and the cloud gateway, and the first device may be an IDC server or a CPE, but is not limited thereto. As shown in fig. 3, the route configuration method may include:

s301: the cloud controller acquires a first BGP configuration, a second BGP configuration, a third BGP configuration and a fourth BGP configuration;

s302: the cloud controller transmits a first BGP configuration to the access gateway;

s303: the cloud controller issues a second BGP configuration to the first device;

s304: the access gateway and the first device establish a first BGP neighbor relation between the access gateway and the first device based on the first BGP configuration and the second BGP configuration, wherein the first BGP neighbor relation is used for sharing route configuration between the access gateway and the first device;

S305: the cloud controller transmits a third BGP configuration to the access gateway;

s306: the cloud controller transmits a fourth BGP configuration to the cloud gateway;

s307: and the access gateway and the cloud gateway establish a second BGP neighbor relation between the access gateway and the cloud gateway based on the third BGP configuration and the fourth BGP configuration, and the second BGP neighbor relation is used for sharing route configuration between the access gateway and the cloud gateway.

It should be understood that the first BGP configuration refers to BGP configuration that the cloud controller issues to the access gateway to establish the first BGP neighbor relationship, and the second BGP configuration refers to BGP configuration that the cloud controller issues to the first device to establish the first BGP neighbor relationship.

Optionally, the first BGP configuration includes at least one of, but is not limited to: the method comprises the steps of carrying out IP address of a cloud controller, IP address of an access gateway, identification of AS to which the access gateway belongs, and identification of BGP neighbor of the access gateway, namely identification of first equipment.

Optionally, the second BGP configuration includes at least one of, but is not limited to: the method comprises the steps of carrying out IP address of a cloud controller, IP address of first equipment, identification of AS to which the first equipment belongs, identification of BGP neighbor of the first equipment, namely identification of an access gateway.

Alternatively, the AS to which the access gateway belongs and the AS to which the first device belongs may be different.

It should be appreciated that, after the access gateway acquires the first BGP configuration and the first device acquires the second BGP configuration, the access gateway and the first device may establish a first BGP neighbor relation between the access gateway and the first device based on a BGP neighbor relation establishment method, where the establishment of the first BGP neighbor relation may be actively initiated by the access gateway or the first device, for example, an exemplary procedure of establishing the first BGP neighbor relation is described below by taking an access gateway actively initiating an establishment procedure of the first BGP neighbor relation as an example:

step 1: the access gateway is in an Idle state.

Step 2: a TCP connection needs to be established between the access gateway and the first device.

Step 3: the exchange and verification of parameters is performed between the access gateway and the first device.

When the access gateway initiates the first BGP neighbor relation, it needs to parse the identity of its BGP neighbor, i.e., the identity of the first device, from the first BGP configuration. In the process of establishing the first BGP neighbor relation, the first device needs to parse the BGP neighbor identifier thereof, that is, the access gateway identifier, from the second BGP configuration, so that the first device establishes TCP connection with the access gateway and performs parameter exchange and verification.

It should be understood that, specifically, the BGP neighbor relation establishment method may refer to the foregoing, which is not repeated herein.

Optionally, after the cloud controller issues the first BGP configuration to the access gateway and issues the second BGP configuration to the first device, the cloud controller may send indication information to the access gateway and the first device to indicate that the access gateway and the first device may establish BGP neighbor relationships with each other.

It should be understood that the third BGP configuration refers to BGP configuration that is issued by the cloud controller to the access gateway to establish the second BGP neighbor relationship, and the fourth BGP configuration refers to BGP configuration that is issued by the cloud controller to the cloud gateway to establish the second BGP neighbor relationship.

Optionally, the third BGP configuration includes at least one of, but is not limited to: the cloud controller comprises an IP address of the cloud controller, an IP address of the access gateway, an identification of an AS to which the access gateway belongs, and an identification of a BGP neighbor of the access gateway, namely an identification of the cloud gateway.

Optionally, the fourth BGP configuration includes at least one of, but is not limited to: the method comprises the steps of IP address of a cloud controller, IP address of a cloud gateway, identification of AS to which the cloud gateway belongs, identification of BGP neighbor of the cloud gateway, namely identification of an access gateway.

Alternatively, the AS to which the access gateway belongs and the AS to which the cloud gateway belongs may be different.

It should be understood that, after the access gateway obtains the third BGP configuration and the cloud gateway obtains the fourth BGP configuration, the access gateway and the cloud gateway may establish a second BGP neighbor relation between the access gateway and the cloud gateway based on a BGP neighbor relation establishment method, where the establishment of the second BGP neighbor relation may be actively initiated by the access gateway or the cloud gateway, for example, an establishment procedure of the access gateway to actively initiate the second BGP neighbor relation is described below as an example:

step 1: the access gateway is in an Idle state.

Step 2: a TCP connection needs to be established between the access gateway and the cloud gateway.

Step 3: and exchanging and verifying parameters between the access gateway and the cloud gateway.

When the access gateway initiates the second BGP neighbor relation, it needs to parse the identity of its BGP neighbor from the third BGP configuration, i.e., the identity of the cloud gateway. In the process of establishing the second BGP neighbor relation, the cloud gateway needs to analyze the BGP neighbor identifier thereof, that is, the access gateway identifier, from the fourth BGP configuration, so that the cloud gateway establishes TCP connection with the access gateway and performs parameter exchange and verification.

It should be understood that, specifically, the BGP neighbor relation establishment method may refer to the foregoing, which is not repeated herein.

Optionally, after the cloud controller issues the third BGP configuration to the access gateway and issues the fourth BGP configuration to the cloud gateway, the cloud controller may send indication information to the access gateway and the cloud gateway to indicate that the access gateway and the cloud gateway may establish BGP neighbor relationships with each other.

Optionally, the cloud controller interfaces with the access gateway and the cloud gateway via a remote procedure scheduler (Remote Procedure Call, RPC), such as a GRPC interface, respectively. Based on this, the cloud controller may issue the first BGP configuration and the third BGP configuration to the access gateway through a GRPC interface between the cloud controller and the access gateway. The cloud controller may issue a fourth BGP configuration to the cloud gateway through a GRPC interface between the cloud controller and the cloud gateway.

Optionally, the routing configuration is a first routing configuration from a private cloud to a public cloud or a second routing configuration from a public cloud to a private cloud.

The routing configuration may be a first routing configuration from the private cloud to the public cloud, for example, the first routing configuration includes a network segment route of the public cloud, or the routing configuration may be a second routing configuration from the public cloud to the private cloud, for example, the second routing configuration includes a network segment route of the private cloud.

According to the technical scheme provided by the embodiment of the application, as the cloud controller issues BGP configuration for the first device, the access gateway and the cloud gateway, the access gateway can respectively establish BGP neighbor relation with the first device and the cloud gateway, based on the BGP neighbor relation, after any one of the three devices is configured with the routing configuration between the private cloud and the public cloud, the device can share the routing configuration to the BGP neighbor of the device based on the BGP neighbor relation, and therefore the three devices can all obtain the routing configuration. Compared with the prior art, the routing configuration process is simpler, so that the routing configuration efficiency can be improved, and particularly, in the case of more routing configuration items, the routing configuration is only needed to be configured for one device, so that the situation of configuration errors can be reduced.

Optionally, the first routing configuration may be a preconfigured routing configuration, or may be configured by the cloud controller to the cloud gateway or the access gateway, and a detailed description will be given below of a routing configuration method in the case where the foregoing routing configuration is the first routing configuration:

fig. 4 is a flowchart of another route configuration method according to an embodiment of the present application, as shown in fig. 4, after S307, the route configuration method further includes:

S401: the cloud controller acquires a first route configuration;

s402: the cloud controller transmits a first route configuration to the cloud gateway;

s403: the cloud gateway shares a first routing configuration to the access gateway based on the second BGP neighbor relation;

s404: the access gateway shares a first routing configuration to the first device based on the first BGP neighbor relation.

Optionally, the user may create the first routing configuration through a web page or command line on the cloud console to send the first routing configuration to the cloud controller.

It should be appreciated that the second BGP neighbor relationship is specifically configured for the cloud gateway to share the first routing configuration to the access gateway; the first BGP neighbor relation is specifically for the access gateway to share the first routing configuration to the first device.

Fig. 5 is a flowchart of another route configuration method according to an embodiment of the present application, as shown in fig. 5, after S307, the route configuration method further includes:

s501: the cloud controller acquires a first route configuration;

s502: the cloud controller transmits a first route configuration to the access gateway;

s503: the access gateway shares the first route configuration to the cloud gateway based on the second BGP neighbor relation;

s504: the access gateway shares a first routing configuration to the first device based on the first BGP neighbor relation.

Optionally, the user may create the first routing configuration through a web page or command line on the cloud console to send the first routing configuration to the cloud controller.

It should be understood that the second BGP neighbor relation is specifically configured for the access gateway to share the first routing configuration to the cloud gateway; the first BGP neighbor relation is specifically for the access gateway to share the first routing configuration to the first device.

According to the technical scheme provided by the embodiment of the application, as the cloud controller issues BGP configuration for the first device, the access gateway and the cloud gateway, the access gateway can respectively establish BGP neighbor relation with the first device and the cloud gateway, and based on the BGP neighbor relation, after the cloud controller issues the first routing configuration to the cloud gateway, the cloud gateway can share the first routing configuration to the access gateway based on the second BGP neighbor relation; the access gateway may share a first routing configuration to the first device based on the first BGP neighbor relation. After the cloud controller issues the first routing configuration to the access gateway, the access gateway may share the first routing configuration to the cloud gateway based on the second BGP neighbor relation and share the first routing configuration to the first device based on the first BGP neighbor relation, respectively. Compared with the prior art, the routing configuration process is simpler, so that the routing configuration efficiency can be improved, and particularly, in the case of more routing configuration items, the configuration error condition can be reduced because only the cloud gateway or the first gateway is required to be configured with the first routing configuration.

It should be understood that, due to the problems of network jitter, time delay, and the like, the first routing configuration actually acquired by the cloud gateway and the access gateway is not necessarily the same as the first routing configuration issued by the cloud controller, that is, the first routing configuration actually acquired by the cloud gateway and/or the access gateway may have an abnormal routing table entry, based on this, the cloud controller may adopt the following realizable manner, but not limited thereto, so that the gateway having the abnormal routing table entry may obtain the correct first routing configuration:

the following realizations may be combined with the embodiments corresponding to fig. 4 or fig. 5, and the routing configuration method is described in detail below in conjunction with the embodiments corresponding to fig. 4:

fig. 6 is a flowchart of another route configuration method according to an embodiment of the present application, as shown in fig. 6, after S404, the route configuration method may further include:

s601: the cloud gateway sends a third route configuration to the cloud controller;

s602: the access gateway sends a fourth routing configuration to the cloud controller;

s603: the cloud controller judges whether the third route configuration is synchronous with the fourth route configuration;

s604: if the third route configuration is not synchronous with the fourth route configuration, the cloud controller determines an abnormal route table entry of at least one of the third route configuration and the fourth route configuration;

S605: if the cloud gateway has an abnormal routing table entry, the cloud controller sends a control command or first routing configuration to the cloud gateway.

S606: if the access gateway has an abnormal routing table entry, the cloud controller sends a control command or first routing configuration to the access gateway.

It should be understood that the third routing configuration refers to the first routing configuration actually acquired by the cloud gateway, and in the case that the network is normal, the third routing configuration should be the same as the first routing configuration. If there is a network or device failure, etc., the third routing configuration may be different from the first routing configuration, for example: the third routing configuration adds, deletes or modifies routing entries with respect to the first routing configuration. Similarly, the fourth routing configuration is the first routing configuration actually obtained by the access gateway, and in the case that the network is normal, the fourth routing configuration should be the same as the first routing configuration. The fourth routing configuration may be different from the first routing configuration if there is a network or device failure, etc., for example: the fourth routing configuration adds, deletes or modifies routing entries with respect to the first routing configuration. In summary, since the first routing configuration is issued by the cloud controller, based on this, the cloud controller determines that the third routing configuration and the fourth routing configuration should be synchronized, but if there is a network or device failure or the like, the third routing configuration and the fourth routing configuration may be different.

It should be understood that the cloud controller determining whether the third routing configuration is synchronized with the fourth routing configuration refers to the cloud controller determining whether the third routing configuration is identical to the fourth routing configuration.

Optionally, if the third routing configuration is not synchronous with the fourth routing configuration, because the first routing configuration is issued by the cloud controller, the cloud controller may match the third routing configuration with the first routing configuration, and determine an abnormal routing table entry in the third routing configuration; and matching the fourth routing configuration with the first routing configuration, and determining an abnormal routing table entry in the fourth routing configuration.

It should be understood that, the control command is used to process an abnormal routing table entry, for example, when a third routing configuration lacks a certain routing table entry, a control command issued by the cloud controller to the cloud gateway may carry the routing table entry, so that the cloud gateway may add the routing table entry on the basis of the third routing configuration. For another example, when the third routing configuration has an excessive condition of a certain routing table entry, a control command issued by the cloud controller to the cloud gateway may be used to delete the routing table entry, so that the cloud gateway may delete the routing table entry according to the control command. For another example, when the third routing configuration has a configuration error condition of a certain routing table entry, the control command issued by the cloud controller to the cloud gateway may carry the correct routing table entry, so that the cloud gateway may update the abnormal routing table entry in the third routing configuration to the correct routing table entry.

Alternatively, the cloud controller may periodically check and process the abnormal routing table entry, for example, the cloud controller may send a request message to the access gateway and the cloud gateway once a day to request the third routing configuration and the fourth routing configuration to be acquired. Alternatively, the access gateway and the cloud gateway may actively periodically report the respective third and fourth routing configurations to the cloud controller.

According to the technical scheme provided by the embodiment of the application, if the conditions such as network or equipment faults exist, the cloud controller can send the control command or the first route configuration to the gateway with the abnormal route table entry, so that the gateway with the abnormal route table entry can acquire the correct first route configuration, and the subsequent data transmission from the private cloud to the public cloud can be ensured.

Alternatively, the second routing configuration may be a preconfigured routing configuration, or may be configured by a user to the first device, and a method of routing configuration in the case where the second routing configuration is the second routing configuration will be described in detail below:

fig. 7 is a flowchart of another route configuration method according to an embodiment of the present application, as shown in fig. 7, after S307, the route configuration method further includes:

S701: the first equipment acquires a second routing configuration;

s702: the first device sharing a second routing configuration to the access gateway based on the first BGP neighbor relation;

s703: the access gateway shares a second routing configuration to the cloud gateway based on the second BGP neighbor relation.

Alternatively, the user may create the second routing configuration via a web page or command line on the first device.

It should be appreciated that the first BGP neighbor relation is specifically used for the first device to share the second routing configuration to the access gateway; the second BGP neighbor relation is specifically configured for the access gateway to share a second routing configuration to the cloud gateway.

According to the technical scheme provided by the embodiment of the application, as the cloud controller issues BGP configuration for the first device, the access gateway and the cloud gateway, the access gateway can respectively establish BGP neighbor relation with the first device and the cloud gateway, and based on the BGP neighbor relation, after the first device acquires the second routing configuration, the first device can share the second routing configuration with the access gateway based on the first BGP neighbor relation; the access gateway may share a second routing configuration to the cloud gateway based on the second BGP neighbor relation. Compared with the prior art, the routing configuration process is simpler, so that the routing configuration efficiency can be improved, and particularly, in the case of more routing configuration items, the configuration error condition can be reduced because only the second routing configuration is required to be configured for the first equipment.

It should be understood that, the gateway device constructed by adopting the NFV concept can be very flexibly deployed and expanded, and in this embodiment of the present application, the first device, the access gateway and the cloud gateway may all adopt the NFV implementation to construct a functional module, where the functional module is suitable for a scenario such as hybrid cloud or hybrid cloud private line access, software defined wide area network (Software-Defined Wide Area Network, SDWAN), and the like, to implement learning and publishing of routing configuration (i.e. implement publishing and obtaining of routing configuration), support BGP complete routing protocol stack, support abundant routing policies and million-level routing management functions, and the like. The functional module may be referred to as, but is not limited to, a fast cloud routing (Fast Cloud Router, FCR) module.

For example, fig. 8 is a network architecture diagram provided in the embodiment of the present application, and as shown in fig. 8, the network architecture adopts a design idea of forwarding control separation (i.e. forwarding and control separation) of NFV, and is divided into a cloud controller 81 for issuing a control command and network devices for performing data forwarding, where the network devices include: the first device 82 on the private cloud side, the cloud gateway 83 on the public cloud side, and the access gateway 84 are not limited thereto.

Wherein the first device 82, the cloud gateway 83, and the access gateway 84 each comprise an FCR module.

Alternatively, the cloud controller 81 may be connected to the FCR module in the first device 82, the FCR module in the cloud gateway 83, and the FCR module in the access gateway 84 through RPC interfaces, such as GRPC interfaces, respectively, and the FCR module in the access gateway 84 may be connected to the FCR module in the first device 82 and the FCR module in the cloud gateway 83, respectively.

Alternatively, the first device 82 may be an IDC server, CPE, or the like, which is not limited in this application.

The cloud gateway 83 is used for mixing the scenes such as cloud private line access, inter-domain intercommunication, public cloud black stone intercommunication and the like, realizing high-performance forwarding, supporting multi-tenant access, supporting characteristics such as fragmentation, recombination and speed limitation. The cloud gateway 83 may be, but is not limited to, NGW.

The access gateway 84 is also called an intersubnetwork connector and a protocol converter, and the access gateway 24 is used for implementing interconnection between two networks with different high-level protocols, i.e. private cloud and public cloud.

Based on this, the route configuration methods provided in the embodiments of the present application may be implemented by the FCR module, that is, the first device in the route configuration method may be replaced by the FCR module of the first device, the access gateway may be replaced by the FCR module of the access gateway, and the cloud gateway may be replaced by the FCR module of the cloud gateway. For example, the route configuration method may include: the cloud controller acquires a first BGP configuration, a second BGP configuration, a third BGP configuration and a fourth BGP configuration; the cloud controller transmits a first BGP configuration to an FCR module in the access gateway; the cloud controller transmits a second BGP configuration to an FCR module in the first device; the FCR module in the access gateway and the FCR module in the first device establish a first BGP neighbor relation between the FCR module in the access gateway and the FCR module in the first device based on the first BGP configuration and the second BGP configuration, and the first BGP neighbor relation is used for sharing route configuration between the FCR module in the access gateway and the FCR module in the first device; the cloud controller transmits a third BGP configuration to an FCR module in the access gateway; the cloud controller transmits a fourth BGP configuration to an FCR module in the cloud gateway; and establishing a second BGP neighbor relation between the FCR module in the access gateway and the FCR module in the cloud gateway based on the third BGP configuration and the fourth BGP configuration, wherein the second BGP neighbor relation is used for sharing route configuration between the FCR module in the access gateway and the FCR module in the cloud gateway.

Alternatively, the FCR module may be deployed in a containerized or two-level system. For example, fig. 9 is a schematic diagram of a FCR container deployment provided by the embodiment of the present application, as shown in fig. 9, a FCR container may be deployed on an access gateway and a cloud gateway in a container deployment manner, and the FCR container may receive a control instruction of the cloud controller through a northbound GRPC interface, and may establish BGP neighbor connection between two FCR containers, and perform routing configuration transfer based on BGP protocol, so that routing configuration interaction between two gateways may be very conveniently implemented. Of course, besides the containerized deployment mode of the FCR container, the containerized deployment mode of the gateway function modules on the access gateway and the cloud gateway can also be adopted.

In this embodiment of the present application, the first device, the access gateway, and the cloud gateway may all deploy the FCR module in a containerized deployment manner or a binary deployment manner, so that when the first device, the access gateway, and the cloud gateway need to be upgraded, the minimum upgrade cost may be paid, for example, only the FCR module needs to be upgraded.

Fig. 10 is a schematic diagram of a cloud controller 1000 provided in an embodiment of the present application, where the cloud controller is connected to an access gateway and a cloud gateway on a public cloud side, and the access gateway is further connected to a first device on a private cloud side and the cloud gateway, and the cloud controller 1000 includes: the system comprises an acquisition module 1010 and a issuing module 1020, wherein the acquisition module 1010 is used for acquiring a first BGP configuration, a second BGP configuration, a third BGP configuration and a fourth BGP configuration; the issuing module 1020 is configured to: issuing a first BGP configuration to the access gateway and issuing a second BGP configuration to the first device, wherein the first BGP configuration and the second BGP configuration are used for establishing a first BGP neighbor relation between the access gateway and the first device, and the first BGP neighbor relation is used for sharing route configuration between the access gateway and the first device; issuing a third BGP configuration to the access gateway and issuing a fourth BGP configuration to the cloud gateway, wherein the third BGP configuration and the fourth BGP configuration are used for establishing a second BGP neighbor relation between the access gateway and the cloud gateway, and the second BGP neighbor relation is used for sharing routing configuration between the access gateway and the cloud gateway; the routing configuration is a first routing configuration from the private cloud to the public cloud or a second routing configuration from the public cloud to the private cloud.

Optionally, when the route configuration is the first route configuration, the obtaining module 1010 is further configured to obtain the first route configuration; the issuing module 1020 is further configured to issue a first routing configuration to the cloud gateway; the second BGP neighbor relation is specifically used for sharing the first route configuration from the cloud gateway to the access gateway; the first BGP neighbor relation is specifically for the access gateway to share the first routing configuration to the first device.

Optionally, when the route configuration is the first route configuration, the obtaining module 1010 is further configured to obtain the first route configuration; the issuing module 1020 is further configured to issue a first routing configuration to the access gateway; the second BGP neighbor relation is specifically used for the access gateway to share the first route configuration with the cloud gateway; the first BGP neighbor relation is specifically for the access gateway to share the first routing configuration to the first device.

Optionally, the second routing configuration is a routing configuration configured by the user for the first device; the first BGP neighbor relation is specifically used for the first device to share the second route configuration with the access gateway; the second BGP neighbor relation is specifically configured for the access gateway to share a second routing configuration to the cloud gateway.

Optionally, the cloud controller 1000 further includes: a decision module 1030 and a determination module 1040. The obtaining module 1010 is further configured to receive a third route configuration sent by the cloud gateway, where the third route configuration is a first route configuration actually obtained by the cloud gateway; receiving a fourth route configuration sent by the access gateway, wherein the fourth route configuration is the first route configuration actually acquired by the access gateway; the judging module 1030 is configured to judge whether the third routing configuration is synchronous with the fourth routing configuration; the determining module 1040 is configured to determine, if the third routing configuration is not synchronous with the fourth routing configuration, an abnormal routing table entry of at least one of the third routing configuration and the fourth routing configuration; the issuing module 1020 is further configured to send a control command or a first routing configuration to a gateway having an abnormal routing table entry in the cloud gateway and the access gateway, where the control command is used to process the abnormal routing table entry.

Optionally, the determining module 1040 is specifically configured to: matching the third route configuration with the first route configuration, and determining an abnormal route table item in the third route configuration; and matching the fourth routing configuration with the first routing configuration, and determining an abnormal routing table entry in the fourth routing configuration.

Optionally, the cloud controller is connected with the access gateway and the cloud gateway through remote procedure call interfaces respectively.

Optionally, the first device is an IDC server or a CPE.

It should be understood that apparatus embodiments and method embodiments may correspond with each other and that similar descriptions may refer to the method embodiments. To avoid repetition, no further description is provided here. Specifically, the cloud controller 1000 shown in fig. 10 may execute the above-mentioned route configuration method embodiment, and the foregoing and other operations and/or functions of each module in the cloud controller 1000 are respectively for implementing corresponding flows in each method in the above-mentioned route configuration method embodiment, which are not repeated herein for brevity.

The cloud controller 1000 of the embodiment of the present application is described above in terms of functional modules in conjunction with the accompanying drawings. It should be understood that the functional module may be implemented in hardware, or may be implemented by instructions in software, or may be implemented by a combination of hardware and software modules. Specifically, each step of the method embodiments in the embodiments of the present application may be implemented by an integrated logic circuit of hardware in a processor and/or an instruction in software form, and the steps of the method disclosed in connection with the embodiments of the present application may be directly implemented as a hardware decoding processor or implemented by a combination of hardware and software modules in the decoding processor. Alternatively, the software modules may be located in a well-established storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, and the like. The storage medium is located in a memory, and the processor reads information in the memory, and in combination with hardware, performs the steps in the above method embodiments.

Fig. 11 is a schematic block diagram of an electronic device provided in an embodiment of the present application.

As shown in fig. 11, the electronic device may include:

a memory 1110 and a processor 1120, the memory 1110 being for storing a computer program and transmitting the program code to the processor 1120. In other words, the processor 1120 may call and run a computer program from the memory 1110 to implement the methods in embodiments of the present application.

For example, the processor 1120 may be configured to perform the above-described method embodiments according to instructions in the computer program.

In some embodiments of the present application, the processor 1120 may include, but is not limited to:

a general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like.

In some embodiments of the present application, the memory 1110 includes, but is not limited to:

volatile memory and/or nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct memory bus RAM (DR RAM).

In some embodiments of the present application, the computer program may be partitioned into one or more modules that are stored in the memory 1110 and executed by the processor 1120 to perform the methods provided herein. The one or more modules may be a series of computer program instruction segments capable of performing the specified functions, which are used to describe the execution of the computer program in the electronic device.

As shown in fig. 11, the electronic device may further include:

a transceiver 1130, the transceiver 1130 may be coupled to the processor 1120 or memory 1110.

Wherein the processor 1120 may control the transceiver 1130 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices. Transceiver 1130 may include a transmitter and a receiver. Transceiver 1130 may further include antennas, the number of which may be one or more.

It will be appreciated that the various components in the electronic device are connected by a bus system that includes, in addition to a data bus, a power bus, a control bus, and a status signal bus.

The present application also provides a computer storage medium having stored thereon a computer program which, when executed by a computer, enables the computer to perform the method of the above-described method embodiments. Alternatively, embodiments of the present application also provide a computer program product comprising instructions which, when executed by a computer, cause the computer to perform the method of the method embodiments described above.

When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces, in whole or in part, a flow or function consistent with embodiments of the present application. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. For example, functional modules in the embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module.

The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (11)

1. The method is applied to a cloud controller, the cloud controller is connected with an access gateway and a cloud gateway on a public cloud side, the access gateway is also connected with first equipment on a private cloud side and the cloud gateway, and the method comprises the following steps:

Acquiring a first Border Gateway Protocol (BGP) configuration, a second BGP configuration, a third BGP configuration and a fourth BGP configuration;

issuing the first BGP configuration to the access gateway, and issuing the second BGP configuration to the first device, wherein the first BGP configuration and the second BGP configuration are used for establishing a first BGP neighbor relation between the access gateway and the first device, and the first BGP neighbor relation is used for sharing route configuration between the access gateway and the first device;

the third BGP configuration is issued to the access gateway, the fourth BGP configuration is issued to the cloud gateway, the third BGP configuration and the fourth BGP configuration are used for establishing a second BGP neighbor relation between the access gateway and the cloud gateway, and the second BGP neighbor relation is used for sharing the routing configuration by the access gateway and the cloud gateway;

the routing configuration is a first routing configuration from the private cloud to the public cloud or a second routing configuration from the public cloud to the private cloud.

2. The method of claim 1, wherein when the routing configuration is the first routing configuration, the method further comprises:

Acquiring the first route configuration;

issuing the first route configuration to the cloud gateway;

the second BGP neighbor relation is specifically configured to share the first routing configuration with the cloud gateway to the access gateway; the first BGP neighbor relation is specifically configured for the access gateway to share the first routing configuration to the first device.

3. The method of claim 1, wherein when the routing configuration is the first routing configuration, the method further comprises:

acquiring the first route configuration;

issuing the first routing configuration to the access gateway;

the second BGP neighbor relation is specifically configured to share the first routing configuration to the cloud gateway by the access gateway; the first BGP neighbor relation is specifically configured for the access gateway to share the first routing configuration to the first device.

4. The method of claim 1, wherein the second routing configuration is a routing configuration configured by a user for the first device;

the first BGP neighbor relation is specifically configured to share the second routing configuration to the access gateway by the first device; the second BGP neighbor relation is specifically configured for the access gateway to share the second routing configuration to the cloud gateway.

5. The method of any one of claims 1-4, further comprising:

receiving a third route configuration sent by the cloud gateway, wherein the third route configuration is the first route configuration actually acquired by the cloud gateway;

receiving a fourth routing configuration sent by the access gateway, wherein the fourth routing configuration is the first routing configuration actually acquired by the access gateway;

judging whether the third route configuration is synchronous with the fourth route configuration or not;

if the third route configuration is not synchronous with the fourth route configuration, determining an abnormal route table item of at least one of the third route configuration and the fourth route configuration;

and sending a control command or the first routing configuration to the gateway with the abnormal routing table entry in the cloud gateway and the access gateway, wherein the control command is used for processing the abnormal routing table entry.

6. The method of claim 5, wherein the determining an exception routing table entry for at least one of the third routing configuration and the fourth routing configuration comprises:

matching the third route configuration with the first route configuration, and determining an abnormal route table item in the third route configuration;

And matching the fourth routing configuration with the first routing configuration, and determining an abnormal routing table entry in the fourth routing configuration.

7. The method of any of claims 1-4, wherein the cloud controller is connected to the access gateway and the cloud gateway via a remote procedure call interface, respectively.

8. The method according to any of claims 1-4, wherein the first device is an internet data center IDC server or a customer premises equipment CPE.

9. A cloud controller, characterized in that the cloud controller is connected with an access gateway and a cloud gateway of a public cloud side, the access gateway is further connected with a first device of a private cloud side and the cloud gateway, the cloud controller comprises:

the acquisition module is used for acquiring the first BGP configuration, the second BGP configuration, the third BGP configuration and the fourth BGP configuration;

a issuing module, configured to:

issuing the first BGP configuration to the access gateway, and issuing the second BGP configuration to the first device, wherein the first BGP configuration and the second BGP configuration are used for establishing a first BGP neighbor relation between the access gateway and the first device, and the first BGP neighbor relation is used for sharing route configuration between the access gateway and the first device;

The third BGP configuration is issued to the access gateway, the fourth BGP configuration is issued to the cloud gateway, the third BGP configuration and the fourth BGP configuration are used for establishing a second BGP neighbor relation between the access gateway and the cloud gateway, and the second BGP neighbor relation is used for sharing the routing configuration by the access gateway and the cloud gateway;

the routing configuration is a first routing configuration from the private cloud to the public cloud or a second routing configuration from the public cloud to the private cloud.

10. An electronic device, comprising:

a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory to perform the method of any of claims 1 to 8.

11. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 8.