CN111371685B

CN111371685B - Data processing and IPv6 mounting method and device

Info

Publication number: CN111371685B
Application number: CN202010129743.4A
Authority: CN
Inventors: 雷思源; 姜琳; 周磊
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2020-02-28
Filing date: 2020-02-28
Publication date: 2022-06-17
Anticipated expiration: 2040-02-28
Also published as: CN111371685A

Abstract

The embodiment of the application discloses a data processing method and device and an IPv6 mounting method and device. One embodiment of the data processing method includes: receiving a data processing request, wherein the data processing request comprises traffic data and an IPv6 address; if the IPv6 address is the IPv6 address of the intranet load balancing equipment in the Virtual Private Cloud (VPC), distributing an IPv6 port based on load balancing; and sending the traffic data to an IPv6 cloud server mounted through the IPv6 port for processing. In the embodiment, the virtual machine in the VPC balances the traffic to the IPv6 cloud server mounted at the rear end of the VPC by accessing the IPv6 address of the intranet load balancing equipment, so that the IPv6 load balancing of the intranet traffic is realized.

Description

Data processing and IPv6 mounting method and device

Technical Field

The embodiment of the application relates to the technical field of computers, in particular to a data processing and IPv6 mounting method and device.

Background

Load Balance (LB) can Balance application traffic among a plurality of cloud servers, and deal with a large number of access requests, thereby realizing service expansion. Furthermore, the method is simple. Load balancing can also avoid single point of failure and improve service availability. At present, a common mode is to directly mount a cloud server on a load balancing device, and the load balancing device directly distributes traffic data to the mounted cloud server for processing based on load balancing.

Disclosure of Invention

The embodiment of the application provides a data processing and IPv6 mounting method and device.

In a first aspect, an embodiment of the present application provides a data processing method, including: receiving a data processing request, wherein the data processing request comprises traffic data and an IPv6 address; if the IPv6 address is the IPv6 address of the intranet load balancing equipment in the virtual private cloud VPC, distributing IPv6 ports based on load balancing; and sending the traffic data to an IPv6 cloud server mounted through an IPv6 port for processing.

In some embodiments, the method further comprises: if the IPv6 address is not the IPv6 address of the intranet load balancing equipment in the VPC, sending the flow data to an IPv6 public network gateway in the VPC; and searching a route corresponding to the outer network load balancing equipment corresponding to the IPv6 address in the IPv6 public network gateway, and sending the traffic data to the outer network load balancing equipment based on the route so that the IPv6 cloud server mounted by the outer network load balancing equipment processes the traffic data.

In a second aspect, an embodiment of the present application provides an IPv6 mount method, including: creating a load balancing example in intranet load balancing equipment in a VPC; creating an IPv6 port for the load balancing example, and acquiring information of an IPv6 cloud server mounted on the intranet load balancing equipment; generating forwarding configuration information based on the information of the IPv6 port and the information of the IPv6 cloud server; and issuing the forwarding configuration information to a gateway server in the VPC, and issuing the forwarding configuration information to gateway equipment through the gateway server.

In some embodiments, the method further comprises: newly adding an IPv6 instance interface in an IPv6 public network gateway in the VPC; the forwarding configuration is issued to the address translation server in the VPC through the IPv6 example interface, and the forwarding configuration information is issued to the address forwarding device through the address translation server.

In some embodiments, before adding an IPv6 instance interface in an IPv6 public network gateway in the VPC, the method further includes: creating an IPv6 public network gateway in the VPC; and configuring a route in the IPv6 public network gateway, wherein a source network segment of the route comprises a subnet segment of an IPv6 address of the internal network load balancing equipment, a destination network segment of the route configuration comprises a network segment of an IPv6 address of the external network load balancing equipment, and the next hop of the route is to the IPv6 public network gateway.

In some embodiments, the method further comprises: and collecting the configuration flow of the load balancing example from the gateway server, pushing the configuration flow to the monitoring platform, and displaying the configuration flow to a user.

In a third aspect, an embodiment of the present application provides a data processing apparatus, including: a receiving unit configured to receive a data processing request, wherein the data processing request includes traffic data and an IPv6 address; the distribution unit is configured to distribute IPv6 ports based on load balancing if the IPv6 address is the IPv6 address of the intranet load balancing equipment in the virtual private cloud VPC; and the first sending unit is configured to send the traffic data to an IPv6 cloud server mounted through an IPv6 port for processing.

In some embodiments, the apparatus further comprises: the second sending unit is configured to send the traffic data to an IPv6 public network gateway in the VPC if the IPv6 address is not the IPv6 address of the intranet load balancing equipment in the VPC; and the third sending unit is configured to search a route corresponding to the external network load balancing equipment corresponding to the IPv6 address in the IPv6 public network gateway, and send the traffic data to the external network load balancing equipment based on the route, so that the IPv6 cloud server mounted by the external network load balancing equipment processes the traffic data.

In a fourth aspect, an embodiment of the present application provides an IPv6 mount apparatus, including: the device comprises a first creating unit and a second creating unit, wherein the first creating unit is configured to create a load balancing example in intranet load balancing equipment in the VPC; the second creating unit is configured to create an IPv6 port for the load balancing example and acquire information of an IPv6 cloud server mounted on the intranet load balancing equipment; a generation unit configured to generate forwarding configuration information based on information of the IPv6 port and information of the IPv6 cloud server; and the first issuing unit is configured to issue the forwarding configuration information to a gateway server in the VPC and issue the forwarding configuration information to the gateway equipment through the gateway server.

In some embodiments, the apparatus further comprises: the newly-added unit is configured to newly add an IPv6 instance interface in an IPv6 public network gateway in the VPC; and the second issuing unit is configured to issue the forwarding configuration to the address translation server in the VPC through the IPv6 example interface, and issue the forwarding configuration information to the address forwarding equipment through the address translation server.

In some embodiments, the apparatus further comprises: a third creating unit configured to create an IPv6 public network gateway in the VPC; and the configuration unit is configured to configure a route in the IPv6 public gateway, wherein a source network segment of the route comprises a subnet segment of an IPv6 address of the internal network load balancing device, a destination network segment of the route configuration comprises a network segment of an IPv6 address of the external network load balancing device, and the next hop of the route to the IPv6 public network gateway.

In some embodiments, the apparatus further comprises: and the acquisition unit is configured to acquire the configuration flow of the load balancing example from the gateway server, push the configuration flow to the monitoring platform and display the configuration flow to a user.

In a fifth aspect, an embodiment of the present application provides an electronic device, including: one or more processors; a storage device having one or more programs stored thereon; when executed by one or more processors, cause the one or more processors to implement a method as described in any of the implementations of the first aspect or to implement a method as described in any of the implementations of the second aspect.

In a sixth aspect, the present application provides a computer-readable medium, on which a computer program is stored, which when executed by a processor implements the method described in any of the implementation manners in the first aspect or implements the method described in any of the implementation manners in the second aspect.

According to the data processing and IPv6 mounting method and device provided by the embodiment of the application, when a data processing request is received, whether an IPv6 address in the data processing request is an IPv6 address of an intranet load balancing device in a VPC is determined. If the address is the IPv6 address of the intranet load balancing equipment, the IPv6 port is distributed based on load balancing, and then the flow data are sent to the IPv6 cloud server mounted through the IPv6 port for processing. The virtual machine in the VPC balances the flow to the IPv6 cloud server mounted at the rear end of the VPC through accessing the IPv6 address of the intranet load balancing equipment, and the IPv6 load balancing of the intranet flow is achieved.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments made with reference to the following drawings:

FIG. 1 is an exemplary system architecture to which the present application may be applied;

FIG. 2 is a flow diagram of one embodiment of a data processing method according to the present application;

FIG. 3 is a flow diagram of yet another embodiment of a data processing method according to the present application;

FIG. 4 is a flow diagram for one embodiment of an IPv6 mount method according to the present application;

FIG. 5 is a flow diagram of yet another embodiment of an IPv6 mounting method according to the present application;

FIG. 6 is a schematic block diagram of one embodiment of a data processing apparatus according to the present application;

FIG. 7 is a schematic block diagram illustrating one embodiment of an IPv6 mount device according to the present application;

FIG. 8 is a block diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present application.

Detailed Description

The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.

It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.

Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the data processing, IPv6 mount method or data processing, IPv6 mount apparatus of the present application may be applied.

As shown in fig. 1, VPC 101 may be included in system architecture 100. A variety of devices are created within VPC 101, including but not limited to Console 102, Meta-Server 103, Neutron 104, BCNAT-Server 105, BGW-Server 106, BCNATs 107, 108, BGWs 109, 110, BNC 111, BCM 112, and influxDB 113, among others.

It should be understood that the VPC in FIG. 1, and the number of Console, Meta-Server, Neutron, BCNAT-Server, BGW-Server, BCNAT, BGW, BNC, BCM, and influxD created within the VPC are merely illustrative. There may be any number of VPCs, and Console, Meta-Server, Neutron, BCNAT-Server, BGW-Server, BCNAT, BGW, BNC, BCM, and influxD created within a VPC, as desired for an implementation.

With continued reference to FIG. 2, a flow 200 of one embodiment of a data processing method according to the present application is shown. The data processing method comprises the following steps:

step 201, receiving a data processing request.

In this embodiment, an intranet load balancing device in a VPC (Virtual Private Cloud) may receive a data processing request. Typically, a virtual machine within the VPC may send a data processing request to an intranet load balancing device in the VPC. The load balancing device created in the VPC where the virtual machine is located may be an intranet load balancing device. The load balancing devices created in other VPCs than the VPC in which the virtual machine is located may be extranet load balancing devices. The data processing request may include traffic data and an IPv6 address. The IPv6 address in the data processing request may be an IPv6 address of the intranet load balancing device, or an IPv6 address of the extranet load balancing device. The traffic data can access the load balancing device through overlay, the load balancing device only has an over address of IPv6, and a vip address is not allocated.

Step 202, if the IPv6 address is the IPv6 address of the intranet load balancing device in the virtual private cloud VPC, allocating an IPv6 port based on load balancing.

In this embodiment, the intranet load balancing device in the VPC may determine whether the IPv6 address in the data processing request is its own IPv6 address. If the address of the intranet load balancing device is the IPv6 address, the intranet load balancing device may allocate the IPv6 port based on load balancing. The IPv6 port distributed by the intranet load balancing device based on load balancing may be an IPv6 port corresponding to an IPv6 cloud server mounted at the rear end of the intranet load balancing device. The load balancing device backend usually only mounts the IPv6 cloud server.

And step 203, sending the traffic data to an IPv6 cloud server mounted through an IPv6 port for processing.

In this embodiment, the intranet load balancing device in the VPC may send the traffic data to the IPv6 cloud server mounted through the IPv6 port for processing. Generally, the IPv6 cloud server mounted at the back end of the load balancing device cannot see the IP address of the virtual machine sending the data processing request, and can only see the vtep IP and the bip address of the BGW of the load balancing device.

According to the data processing method and device provided by the embodiment of the application, when the data processing request is received, whether the IPv6 address in the data processing request is the IPv6 address of the intranet load balancing equipment in the VPC is determined. If the address is the IPv6 address of the intranet load balancing equipment, the IPv6 port is distributed based on load balancing, and then the flow data are sent to the IPv6 cloud server mounted through the IPv6 port for processing. The virtual machine in the VPC balances the flow to the IPv6 cloud server mounted at the rear end of the VPC through accessing the IPv6 address of the intranet load balancing equipment, and the IPv6 load balancing of the intranet flow is achieved.

With further reference to FIG. 3, a flow 300 of yet another embodiment of a data processing method according to the present application is shown. The data processing method comprises the following steps:

step 301, a data processing request is received.

And step 302, if the IPv6 address is the IPv6 address of the intranet load balancing equipment in the virtual private cloud VPC, distributing an IPv6 port based on load balancing.

And step 303, sending the traffic data to an IPv6 cloud server mounted through an IPv6 port for processing.

In the present embodiment, the steps 301-303 are already described in the embodiment 201-203 shown in fig. 2, and will not be described herein again.

And step 304, if the IPv6 address is not the IPv6 address of the internal network load balancing equipment in the VPC, sending the flow data to the IPv6 public network gateway in the VPC.

In this embodiment, if the IPv6 address in the data processing request is not the IPv6 address of the intranet load balancing device in the VPC, the intranet load balancing device in the VPC may send the traffic data to the IPv6 public network gateway in the VPC. Usually, an IPv6 public network gateway is created in the VPC, the load balancing equipment only has an over address of IPv6, and the address can carry out external network communication by means of the IPv6 public network gateway.

Step 305, searching a route corresponding to the external network load balancing device corresponding to the IPv6 address in the IPv6 public network gateway, and sending the traffic data to the external network load balancing device based on the route, so that the IPv6 cloud server mounted on the external network load balancing device processes the traffic data.

In this embodiment, the IPv6 public network gateway in the VPC may search for a route corresponding to the external network load balancing device corresponding to the IPv6 address, and send the traffic data to the external network load balancing device based on the route. Subsequently, the external network load balancing device can allocate the IPv6 ports based on load balancing and send the traffic data to the IPv6 cloud server mounted on the external network load balancing device through the IPv6 ports for processing.

As can be seen from fig. 3, compared with the embodiment corresponding to fig. 2, the flow 300 of the data processing method in this embodiment adds a step of balancing the traffic load of the external network. Therefore, in the scheme described in this embodiment, the IPv6 address of the external network load balancing device is assigned to the IPv6 public network gateway through the VPC route, and the IPv6 public network gateway in the VPC accesses the external network load balancing device through the IPv6 address of the external network load balancing device, thereby implementing the IPv6 load balancing of the external network traffic.

With continued reference to FIG. 4, a flow 400 of one embodiment of an IPv6 mounting method according to the present application is shown. The IPv6 mounting method comprises the following steps:

step 401, creating a load balancing instance in the intranet load balancing device in the VPC.

In this embodiment, a Console in the VPC may call the Meta-Server in the VPC to create a load balancing instance in an intranet load balancing device in the VPC. In general, load balancing instances may exist as separate instance types, and load balancing instances of IPv6 can only be created in subnets of IPv 6.

Step 402, creating an IPv6 port for the load balancing instance, and acquiring information of an IPv6 cloud server mounted on the intranet load balancing device.

In this embodiment, the Meta-Server in the VPC may call Neutron in the VPC to create an IPv6 port for the load balancing instance. Meanwhile, the Meta-Server can also acquire the information of the IPv6 cloud Server mounted on the intranet load balancing equipment.

And step 403, generating forwarding configuration information based on the information of the IPv6 port and the information of the IPv6 cloud server.

In this embodiment, the Meta-Server in the VPC may generate forwarding configuration information based on information of the IPv6 port and information of the IPv6 cloud Server. The forwarding configuration information may include information of an IPv6 port and information of an IPv6 cloud server, and the IPv6 port and the IPv6 cloud server are configured in a one-to-one correspondence manner.

Step 404, forwarding configuration information is issued to a gateway server in the VPC, and the forwarding configuration information is issued to the gateway device through the gateway server.

In this embodiment, the Meta-Server in the VPC may issue the forwarding configuration information to the BGW-Server (gateway Server) in the VPC. Subsequently, the BGW-Server may issue the forwarding configuration information to a BGW (gateway device), so as to implement mounting the IPv6 cloud Server on the rear end of the intranet load balancing device through the IPv6 port, and complete intranet access configuration.

It should be noted that the gateway device is not limited to BGW, and may be Nginx. The BGW is public cloud intranet four-layer load equipment and supports four-layer listeners. Nginx is a public cloud intranet seven-layer load device and supports a seven-layer monitor.

In addition, in the BGW-Server, for the load balancing example of IPv6, only the cloud Server of IPv6 is mounted for the first time, and meanwhile, the validity check of the IPv6 address needs to be done when a data processing request is received. And a configuration request is issued to the equipment end through the BGW-Agent, and the configuration form is compatible with IPv 4. The difference is that for the cloud server of IPv6, in both configuration and presentation results, the IPv6 address must be included in its entirety using "[ ]".

In some optional implementation manners of this embodiment, the BNC may further collect configuration traffic of the load balancing instance from the BGW-Server, and push the configuration traffic to a monitoring platform such as a BCM or an influxDB, so as to be displayed to a user. Specifically, the BGW-Server can collect traffic information of the IPv6 cloud Server at regular time and push the traffic information to the BNC. And the BNC collects and gathers the signals and pushes the signals to BCM or InfluxDB.

In addition, health state information of the IPv6 cloud server at the rear end of the load balancing device can be obtained from the BGW, and is stored in Redis, so that the list related interface of Meta can display the state information of the rear end IPv6 cloud server for the Console to use, and the state information of the IPv6 cloud server at the rear end of the load balancing device of the IPv6 type can be adapted.

According to the IPv6 mounting method provided by the embodiment of the application, firstly, a load balancing example is created in intranet load balancing equipment in a VPC; then, an IPv6 port is created for the load balancing example, and information of an IPv6 cloud server mounted on the intranet load balancing equipment is obtained; then, generating forwarding configuration information based on the information of the IPv6 port and the information of the IPv6 cloud server; and finally, transmitting the forwarding configuration information to a gateway server in the VPC, and transmitting the forwarding configuration information to gateway equipment through the gateway server. The load balancing device of the IPv6 is created in the IPv6 subnet, the forwarding configuration information is issued to the gateway device, the IPv6 cloud server is mounted at the rear end of the intranet load balancing device through the IPv6 port, intranet access configuration is completed, and 6-to-6 conversion of intranet flow is achieved.

With further reference to fig. 5, a flow 500 of yet another embodiment of an IPv6 mount method according to the present application is shown. The IPv6 mounting method comprises the following steps:

step 501, creating a load balancing instance in an intranet load balancing device in the VPC.

Step 502, an IPv6 port is created for the load balancing instance, and information of an IPv6 cloud server mounted on the intranet load balancing device is obtained.

Step 504, forwarding configuration information is issued to a gateway server in the VPC, and the forwarding configuration information is issued to the gateway device through the gateway server.

In the present embodiment, the specific operations of steps 501-504 are described in detail in step 401-404 in the embodiment shown in fig. 2, and are not described herein again.

And step 505, newly adding an IPv6 instance interface in an IPv6 public network gateway in the VPC.

In this embodiment, the Meta-Server in the VPC may add an IPv6 instance interface in the IPv6 public network gateway in the VPC. Generally, the IPv6 public network gateway can simultaneously support creation of an IPv6 instance of a cloud server and an IPv6 instance of a load balancing device, and respectively limit the speed of the IPv6 of the two types of instances, and does not distinguish the IPv6 instance types when limiting the speed.

In some optional implementations of this embodiment, an IPv6 public network gateway is created in the VPC. The route needs to be configured in the IPv6 public network gateway. The source network segment of the route may include a subnet segment of an IPv6 address of the intranet load balancing device, the destination network segment of the route configuration may include a network segment of an IPv6 address of the extranet load balancing device, and the next hop of the route is to the IPv6 public network gateway.

Step 506, the forwarding configuration is issued to the address translation server in the VPC through the IPv6 example interface, and the forwarding configuration information is issued to the address forwarding device through the address translation server.

In this embodiment, the Meta-Server in the VPC may issue the forwarding configuration to the bcat nat-Server (address translation Server) in the VPC through the IPv6 instance interface. Subsequently, the BCNAT-Server in the VPC can issue the forwarding configuration information to the BCNAT (address forwarding device) in the VPC to complete the external network access configuration.

The main logic of the Meta-Server is compatible with conventional load balancing, with the main differences as shown in the following table:

as can be seen from fig. 5, compared with the embodiment corresponding to fig. 4, the flow 500 of the IPv6 mount method in this embodiment adds the step of configuring the extranet access. Therefore, in the solution described in this embodiment, the forwarding configuration is issued to the address forwarding device, so that the IPv6 address of the external network load balancing device is assigned to the IPv6 public network gateway through the VPC route, and the external network access configuration is implemented by using the IPv6 public network gateway in the VPC.

With further reference to fig. 6, as an implementation of the method shown in the above figures, the present application provides an embodiment of a data processing apparatus, which corresponds to the embodiment of the method shown in fig. 2, and which is particularly applicable to various electronic devices.

As shown in fig. 6, the data processing apparatus 600 of the present embodiment may include: a receiving unit 601, an assigning unit 602 and a first transmitting unit 603. Wherein, the receiving unit 601 is configured to receive a data processing request, wherein the data processing request includes traffic data and an IPv6 address; the allocation unit 602 is configured to allocate IPv6 ports based on load balancing if the IPv6 address is an IPv6 address of an intranet load balancing device in the virtual private cloud VPC; and a first sending unit 603 configured to send the traffic data to an IPv6 cloud server mounted through an IPv6 port for processing.

In the present embodiment, in the data processing apparatus 600: the detailed processing of the receiving unit 601, the allocating unit 602, and the first sending unit 603 and the technical effects thereof can refer to the related descriptions of step 201 and step 203 in the corresponding embodiment of fig. 4, which are not repeated herein.

In some optional implementations of this embodiment, the data processing apparatus 600 further includes: a second sending unit (not shown in the figure), configured to send the traffic data to an IPv6 public network gateway in the VPC if the IPv6 address is not the IPv6 address of the intranet load balancing device in the VPC; and a third sending unit (not shown in the figure) configured to search a route corresponding to the outer network load balancing device corresponding to the IPv6 address in the IPv6 public network gateway, and send the traffic data to the outer network load balancing device based on the route, so that the IPv6 cloud server mounted by the outer network load balancing device processes the traffic data.

With further reference to fig. 7, as an implementation of the method shown in the above-mentioned figures, the present application provides an embodiment of an IPv6 mount apparatus, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 4, and the apparatus may be applied to various electronic devices.

As shown in fig. 7, the IPv6 mount device 700 of this embodiment may include: a first creating unit 701, a second creating unit 702, a generating unit 703 and a first issuing unit 704. The first creating unit 701 is configured to create a load balancing instance in an intranet load balancing device in the VPC; a second creating unit 702, configured to create an IPv6 port for the load balancing instance, and obtain information of an IPv6 cloud server mounted on the intranet load balancing device; a generating unit 703 configured to generate forwarding configuration information based on information of the IPv6 port and information of the IPv6 cloud server; and a first issuing unit 704 configured to issue the forwarding configuration information to a gateway server in the VPC, and issue the forwarding configuration information to the gateway device through the gateway server.

In this embodiment, in IPv6 mounting apparatus 700: the detailed processing and the technical effects of the first creating unit 701, the second creating unit 702, the generating unit 703 and the first issuing unit 704 can refer to the related descriptions of step 401 and step 404 in the corresponding embodiment of fig. 4, which are not described herein again.

In some optional implementations of this embodiment, the IPv6 mounting apparatus 700 further includes: a newly-added unit (not shown in the figure) configured to newly add an IPv6 instance interface in an IPv6 public network gateway in the VPC; and the second issuing unit (not shown in the figure) is configured to issue the forwarding configuration to the address translation server in the VPC through the IPv6 example interface, and issue the forwarding configuration information to the address forwarding equipment through the address translation server.

In some optional implementations of this embodiment, the IPv6 mounting apparatus 700 further includes: a third creating unit (not shown in the figure) configured to create an IPv6 public network gateway in the VPC; and the configuration unit (not shown in the figure) is configured to configure the route in the IPv6 public network gateway, wherein the source network segment of the route comprises the sub-network segment of the IPv6 address of the internal network load balancing device, the destination network segment of the route configuration comprises the network segment of the IPv6 address of the external network load balancing device, and the next hop of the route is to the IPv6 public network gateway.

In some optional implementations of this embodiment, the IPv6 mounting apparatus 700 further includes: and the acquisition unit (not shown in the figure) is configured to acquire the configuration traffic of the load balancing instance from the gateway server and push the configuration traffic to the monitoring platform for presentation to the user.

Referring now to FIG. 8, shown is a block diagram of a computer system 800 suitable for use in implementing the electronic device of an embodiment of the present application. The electronic device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU)801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data necessary for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program performs the above-described functions defined in the method of the present application when executed by the Central Processing Unit (CPU) 801.

It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or electronic device. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a receiving unit, an assigning unit, and a first transmitting unit. Where the names of these units do not constitute a limitation on the unit itself in this case, for example, a receiving unit may also be described as a "unit receiving a data processing request". As another example, it can be described as: a processor includes a first creation unit, a second creation unit, a generation unit, and a first issue unit. Where the names of these units do not constitute a limitation on the unit itself in this case, for example, the first creation unit may also be described as a "unit that creates a load balancing instance within an intranet load balancing device in a VPC".

As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a data processing request, wherein the data processing request comprises traffic data and an IPv6 address; if the IPv6 address is the IPv6 address of the intranet load balancing equipment in the virtual private cloud VPC, distributing IPv6 ports based on load balancing; and sending the traffic data to an IPv6 cloud server mounted through an IPv6 port for processing. Or cause the electronic device to: creating a load balancing example in intranet load balancing equipment in a VPC; creating an IPv6 port for the load balancing example, and acquiring information of an IPv6 cloud server mounted on the intranet load balancing equipment; generating forwarding configuration information based on the information of the IPv6 port and the information of the IPv6 cloud server; and issuing the forwarding configuration information to a gateway server in the VPC, and issuing the forwarding configuration information to gateway equipment through the gateway server.

The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.

Claims

1. A method of data processing, comprising:

receiving a data processing request, wherein the data processing request comprises traffic data and an IPv6 address;

if the IPv6 address is the IPv6 address of the intranet load balancing equipment in the Virtual Private Cloud (VPC), distributing an IPv6 port based on load balancing;

sending the traffic data to an IPv6 cloud server mounted through the IPv6 port for processing;

if the IPv6 address is not the IPv6 address of the intranet load balancing equipment in the VPC, sending the flow data to an IPv6 public network gateway in the VPC;

searching a route corresponding to the outer network load balancing equipment corresponding to the IPv6 address in the IPv6 public network gateway, and sending the traffic data to the outer network load balancing equipment based on the route, so that the IPv6 cloud server mounted by the outer network load balancing equipment processes the traffic data.

2. An IPv6 mounting method comprises the following steps:

creating a load balancing example in intranet load balancing equipment in a VPC;

creating an IPv6 port for the load balancing example, and acquiring information of an IPv6 cloud server mounted on the intranet load balancing equipment;

generating forwarding configuration information based on the information of the IPv6 port and the information of the IPv6 cloud server;

and issuing the forwarding configuration information to a gateway server in the VPC, and issuing the forwarding configuration information to gateway equipment through the gateway server.

3. The method of claim 2, wherein the method further comprises:

newly adding an IPv6 instance interface in an IPv6 public network gateway in the VPC;

and issuing the forwarding configuration to an address translation server in the VPC through the IPv6 example interface, and issuing the forwarding configuration information to address forwarding equipment through the address translation server.

4. The method of claim 3, wherein before adding the IPv6 instance interface within the IPv6 public network gateway in the VPC, further comprising:

creating the IPv6 public network gateway in the VPC;

and configuring a route in the IPv6 public network gateway, wherein a source network segment of the route comprises a sub-network segment of an IPv6 address of the internal network load balancing equipment, a destination network segment of the route configuration comprises a network segment of an IPv6 address of the external network load balancing equipment, and the next hop of the route to the IPv6 public network gateway.

5. The method of claim 2, wherein the method further comprises:

and collecting the configuration flow of the load balancing example from the gateway server, pushing the configuration flow to a monitoring platform, and displaying the configuration flow to a user.

6. A data processing apparatus comprising:

a receiving unit configured to receive a data processing request, wherein the data processing request includes traffic data and an IPv6 address;

the distribution unit is configured to distribute IPv6 ports based on load balancing if the IPv6 address is the IPv6 address of the intranet load balancing equipment in the Virtual Private Cloud (VPC);

a first sending unit configured to send the traffic data to an IPv6 cloud server mounted through the IPv6 port for processing;

a second sending unit, configured to send the traffic data to an IPv6 public network gateway in the VPC if the IPv6 address is not the IPv6 address of an intranet load balancing device in the VPC;

a third sending unit, configured to search, in the IPv6 public gateway, a route corresponding to an external network load balancing device corresponding to the IPv6 address, and send the traffic data to the external network load balancing device based on the route, so that the IPv6 cloud server mounted by the external network load balancing device processes the traffic data.

7. An IPv6 mounting device, comprising:

the system comprises a first creating unit, a second creating unit and a third creating unit, wherein the first creating unit is configured to create a load balancing example in intranet load balancing equipment in the VPC;

the second creating unit is configured to create an IPv6 port for the load balancing instance and acquire information of an IPv6 cloud server mounted on the intranet load balancing equipment;

a generating unit configured to generate forwarding configuration information based on information of the IPv6 port and information of the IPv6 cloud server;

a first issuing unit configured to issue the forwarding configuration information to a gateway server in the VPC, and issue the forwarding configuration information to a gateway device through the gateway server.

8. The apparatus of claim 7, wherein the apparatus further comprises:

the newly-added unit is configured to newly add an IPv6 instance interface in an IPv6 public network gateway in the VPC;

a second issuing unit configured to issue the forwarding configuration to an address translation server in the VPC through the IPv6 instance interface, and issue the forwarding configuration information to an address forwarding device through the address translation server.

9. The apparatus of claim 8, wherein the apparatus further comprises:

a third creating unit configured to create the IPv6 public network gateway in the VPC;

and the configuration unit is configured to configure a route in the IPv6 public gateway, wherein a source network segment of the route includes a subnet segment of an IPv6 address of the intranet load balancing device, a destination network segment of the route configuration includes a network segment of an IPv6 address of an extranet load balancing device, and a next hop of the route to the IPv6 public gateway.

10. The apparatus of claim 7, wherein the apparatus further comprises:

and the acquisition unit is configured to acquire the configuration flow of the load balancing example from the gateway server, push the configuration flow to the monitoring platform and display the configuration flow to a user.

11. An electronic device, comprising:

one or more processors;

a storage device having one or more programs stored thereon,

when executed by the one or more processors, cause the one or more processors to implement the method of claim 1 or to implement the method of any one of claims 2-5.

12. A computer-readable medium, on which a computer program is stored, wherein the computer program, when being executed by a processor, carries out the method of claim 1 or carries out the method of any one of claims 2-5.