CN115208888A - Communication method and device for cloud instance to cross available areas and electronic equipment - Google Patents

Communication method and device for cloud instance to cross available areas and electronic equipment Download PDF

Info

Publication number
CN115208888A
CN115208888A CN202211110546.3A CN202211110546A CN115208888A CN 115208888 A CN115208888 A CN 115208888A CN 202211110546 A CN202211110546 A CN 202211110546A CN 115208888 A CN115208888 A CN 115208888A
Authority
CN
China
Prior art keywords
lan
cloud
cloud instance
message
vlan
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202211110546.3A
Other languages
Chinese (zh)
Other versions
CN115208888B (en
Inventor
朱丽品
杨其
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou Youyun Technology Co ltd
Original Assignee
Hangzhou Youyun Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou Youyun Technology Co ltd filed Critical Hangzhou Youyun Technology Co ltd
Priority to CN202211110546.3A priority Critical patent/CN115208888B/en
Publication of CN115208888A publication Critical patent/CN115208888A/en
Application granted granted Critical
Publication of CN115208888B publication Critical patent/CN115208888B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4633Interconnection of networks using encapsulation techniques, e.g. tunneling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • H04L45/745Address table lookup; Address filtering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22Parsing or analysis of headers

Abstract

The specification provides a cloud example cross-usable-area communication method and device and electronic equipment. The host machine is applied to the cloud instance, and a neighbor table for cross-available area communication and local available area communication is deployed on the host machine; the method comprises the following steps: after receiving the message sent by the cloud example, the sending end host analyzes the LAN ID, the VLAN ID and the target MAC corresponding to the message; inquiring a neighbor table maintained locally, and determining whether target cloud instance information of a cross-usable-area corresponding to a target MAC exists in the neighbor table; if yes, determining whether the LAN ID and the VLAN ID are matched with the target cloud instance information; if yes, adding a tunnel header and an outer header in the message, filling the LAN ID and the VLAN ID into the tunnel header, and filling the IP of a target host machine crossing an available area in target cloud instance information into the outer header; and sending the processed message to a receiving end host machine corresponding to the IP of the target host machine through a cross-available area special line.

Description

Communication method and device for cloud instance to cross available areas and electronic equipment
Technical Field
Embodiments of the present specification relate to the field of cloud computing, and in particular, to a method and an apparatus for cross-usable-area communication in a cloud embodiment, and an electronic device.
Background
In cloud computing, because some services need higher disaster recovery capability, the disaster recovery services of tenants are distributed in available Areas (AZ) different from the production services, and each available area may be a physical area with independent power and network; therefore, when the available area where the production service is located is abnormal and the service is unavailable, the available area where the disaster recovery service is located can be switched to ensure the availability of the service.
Under normal conditions, the disaster recovery service and the production service need to keep mutual communication to realize data synchronization, so that communication needs to be carried out between cloud instances in two available areas.
In the related art, communication between cloud instances in two different available areas needs to be forwarded through a dedicated forwarding controller, and the communication mode needing to be forwarded through the dedicated forwarding controller is long in forwarding path, so that a message needs to pass through the dedicated forwarding controller at least twice in a cross-available area transmission process, and thus at least two hops of transmission paths are increased. Therefore, the communication of the existing cloud instance across the available area has the problems of long transmission path and low communication transmission efficiency.
Disclosure of Invention
The embodiment of the specification provides a cloud embodiment cross-available-area communication method and device and electronic equipment. The method is used for solving the problems of long transmission path and low communication transmission efficiency of communication crossing available areas.
According to a first aspect of the embodiments of the present specification, a cloud instance cross-usable-area communication method is provided, which is applied to a sending-receiving-end host, where a neighbor table for cross-usable-area communication and a neighbor table for local usable-area communication are deployed in the sending-end host, and cloud instance information of a cloud instance for cross-usable-area is maintained in the neighbor table; the method comprises the following steps:
after receiving the message sent by the cloud example, the sending end host analyzes the LAN ID, the VLAN ID and the target MAC corresponding to the message;
inquiring a locally maintained neighbor table, and determining whether target cloud instance information of a cross-available area corresponding to the target MAC exists in the neighbor table;
if yes, further determining whether the LAN ID and the VLAN ID are matched with the target cloud instance information;
if the matching is carried out, adding a tunnel head and an outer layer head in the message, filling the LAN ID and the VLAN ID into the tunnel head, and filling a target host IP (Internet protocol) of a cross-available area in target cloud example information into the outer layer head to obtain a processed message;
sending the processed message to a receiving end host machine corresponding to the IP of the target host machine through a cross-available area special line; and the receiving end host machine forwards the message to a target cloud instance according to the LAN ID and the VLAN ID in the tunnel header of the message.
Optionally, a collector is deployed in an available area where the sending-end host is located, a flow table is maintained in the collector, and the flow table includes cloud instance information of all cloud instances in each available area; the method further comprises the following steps:
initiating a query request to the aggregator; the query request carries a LAN ID list of cloud instances in the sending end host;
receiving a query result returned by the aggregator, wherein the query result is cloud instance information corresponding to the same LAN ID of the LAN ID list and the flow table;
comparing the LAN ID and VLAN MASK of the cloud instance information in the query result with the LAN ID and VLAN MASK of the network card of the cloud instance on the sending end host;
and when the LAN ID in any cloud instance information is the same as the LAN ID of the network card of the cloud instance and the VLAN MASK in the cloud instance information and the VLAN MASK of the network card have the same VLAN ID, adding the cloud instance information into a neighbor table as neighbor table information.
Optionally, the cloud instance information includes host information of the cloud instance, detailed information of the cloud instance, and network card information of the cloud instance;
the host information may include a host IP;
the cloud instance detailed information can comprise an ID of the cloud instance and an ID of an available area where the cloud instance is located;
the cloud instance network card information may include a network card ID, a LAN ID where the network card is located, a VLAN MASK, and a network card IP.
Optionally, the sending the processed packet to the receiving end host corresponding to the destination host IP through the inter-available area dedicated line includes:
determining whether the destination host IP is located in an available area where the sending end host is located;
if yes, filling the available area IP of the available area into an outer layer Ethernet header of the message, and sending the message to the receiving end host machine through a cross-available area special line in a two-layer mode;
if not, routing to a receiving end host machine from a special line route deployed in the sending end host machine according to the IP of the target host machine, filling the IP of the target host machine to a two-layer Ethernet head of the message, and sending the message to the receiving end host machine through a cross-available area special line in a three-layer mode.
Optionally, the method includes:
after receiving end host machine receives message sent by sending end host machine, analyzing tunnel head of the message, obtaining LAN ID and VLAN ID in the tunnel head;
analyzing an inner layer Ethernet header of the message to obtain a destination network card ID;
inquiring a neighbor table maintained locally, and determining whether a LAN ID and a VLAN MASK corresponding to the ID of the target network card exist or not;
if yes, further determining whether the LAN ID of the destination network card ID is the same as the LAN ID in the tunnel header and whether the VLAN MASK of the network card ID comprises the VLAN ID in the tunnel header;
and if so, forwarding the message to a target cloud instance.
According to a second aspect of the embodiments of the present specification, a cloud example cross-available area communication method is provided, and is applied to a receiving end host, where a neighbor table for cross-available area communication and a neighbor table for local available area communication are deployed in the receiving end host, and cloud example information of a cloud example for cross-available area is maintained in the neighbor table; the method comprises the following steps:
after receiving end host machine receives message sent by sending end host machine through cross-available area special line, analyzing tunnel head of the message, and obtaining LAN ID and VLAN ID in the tunnel head;
analyzing an inner layer Ethernet header of the message to obtain a target network card ID;
inquiring a neighbor table maintained locally, and determining whether a LAN ID and a VLAN MASK corresponding to the ID of the target network card exist or not;
if yes, further determining whether the LAN ID of the destination network card ID is the same as the LAN ID in the tunnel header and whether the VLAN MASK of the network card ID contains the VLAN ID in the tunnel header;
and if so, forwarding the message to a target cloud instance.
Optionally, a collector is deployed in an available area where the receiving-end host is located, a flow table is maintained in the collector, and the flow table includes cloud instance information of all cloud instances in each available area; the method further comprises the following steps:
initiating a query request to the aggregator; wherein the query request carries a LAN ID list of cloud instances in the receiving end host;
receiving a query result returned by the collector, wherein the query result is cloud instance information corresponding to the same LAN ID of the LAN ID list and the flow table;
comparing the LAN ID and VLAN MASK of the cloud instance information in the query result with the LAN ID and VLAN MASK of the network card of the cloud instance on the receiving end host;
and when the LAN ID in any cloud instance information is the same as the LAN ID of the network card of the cloud instance and the VLAN MASK in the cloud instance information and the VLAN MASK of the network card have the same VLAN ID, adding the cloud instance information into the neighbor table as a piece of neighbor table information.
Optionally, the cloud instance information includes host information of the cloud instance, detailed information of the cloud instance, and network card information of the cloud instance;
the host information may include a host IP;
the cloud instance detailed information can comprise an ID of the cloud instance and an ID of an available area where the cloud instance is located;
the cloud instance network card information may include a network card ID, a LAN ID where the network card is located, a VLAN MASK, and a network card IP.
According to a third aspect of the embodiments of the present specification, there is provided a cloud example cross-usable-area communication apparatus, which is applied to a sending-receiving-end host, where a neighbor table for cross-usable-area communication and a neighbor table for local usable-area communication are deployed in the sending-end host, and cloud example information of a cloud example for cross-usable-area is maintained in the neighbor table; the device comprises:
the system comprises an analysis unit and a sending end host machine, wherein the sending end host machine analyzes the LAN ID, the VLAN ID and the target MAC corresponding to the message after receiving the message sent by the cloud instance;
the inquiry unit inquires a local maintained neighbor table and determines whether the neighbor table has the target cloud instance information of the cross-available area corresponding to the target MAC;
a determining unit, if the target cloud instance information exists, further determining whether the LAN ID and the VLAN ID are matched with the target cloud instance information;
if the matching is carried out, adding a tunnel head and an outer layer head in the message, filling the LAN ID and the VLAN ID into the tunnel head, and filling a target host IP (Internet protocol) of a cross-available area in target cloud example information into the outer layer head to obtain a processed message;
the sending unit is used for sending the processed message to a receiving end host machine corresponding to the IP of the target host machine through a cross-available area special line; and the receiving end host machine forwards the message to a target cloud instance according to the LAN ID and the VLAN ID in the tunnel header of the message.
According to a fourth aspect of the embodiments of the present specification, there is provided a communication device for cloud examples across available areas, which is applied to a receiving-end host, where a neighbor table for communicating across available areas and a neighbor table for communicating with the local available area are deployed in the receiving-end host, and cloud example information of cloud examples across available areas is maintained in the neighbor table; the device comprises:
the receiving unit is used for analyzing a tunnel head of a message after a receiving end host machine receives the message sent by a sending end host machine through a cross-available area special line, and acquiring a LAN ID and a VLAN ID in the tunnel head;
the analysis unit is used for analyzing the inner layer Ethernet header of the message to obtain the ID of the target network card;
the inquiry unit inquires a neighbor table maintained locally and determines whether the LAN ID and the VLAN MASK corresponding to the target network card ID exist or not;
a determining unit, if yes, further determining whether the LAN ID of the destination network card ID is the same as the LAN ID in the tunnel header, and whether the VLAN MASK of the network card ID contains the VLAN ID in the tunnel header;
and if so, forwarding the message to a target cloud instance.
According to a fifth aspect of embodiments herein, there is provided an electronic apparatus comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured as any of the cloud embodiments above for communication across available regions.
In the embodiment of the present specification, a communication scheme is provided, in which a neighbor table formed by cloud instance information corresponding to periodically updated cloud instances across an available area is distributed on each host (to replace a dedicated forwarding controller function); therefore, after receiving the message across the available area sent by the cloud instance, the host determines whether the target cloud instance can communicate by inquiring the neighbor table, and directly forwards the message to the target cloud instance across the available area under the condition of communication (without skipping through a special line forwarding controller); therefore, the skipping of the special line forwarding controller is reduced, so that the transmission path is shortened, and the communication transmission efficiency is improved.
Drawings
FIG. 1 is a schematic diagram of a communication manner of an existing cloud instance across available zones provided by an embodiment of the present specification;
FIG. 2 is a flow diagram of a method by which a aggregator generates a neighbor table provided by an embodiment of the present specification;
fig. 3 is a schematic diagram of a communication manner of an improved cloud example across an available area provided by an embodiment of the present specification;
fig. 4 is a flowchart of a cloud example cross-usable-area communication method using a sending-end host as an execution subject according to an embodiment of the present specification;
fig. 5 is a flowchart of a cloud example cross-usable-area communication method with a receiving host as an execution subject according to an embodiment of the present specification;
fig. 6 is a schematic structural diagram of a processed message according to an embodiment of the present specification;
FIG. 7 is a hardware block diagram of a communication device across available zones for a cloud instance as provided by an embodiment of the present specification;
FIG. 8 is a block diagram of a communication device of a cloud instance across available zones provided by an embodiment of the present specification;
fig. 9 is a block diagram of a communication device of a cloud instance across available zones provided by an embodiment of the present specification.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present description. The word "if," as used herein, may be interpreted as "at \8230; \8230when" or "when 8230; \823030when" or "in response to a determination," depending on the context.
In order to more conveniently understand the technical solution described in the present specification, the technical terms and the technical concepts referred to in the specification will be explained below by names:
a Region (Region), which may be an area divided from a geographic location and a network latency dimension; and public services such as flexible computing, block storage, object storage, VPC (virtual private network), flexible public IP (Internet protocol), mirror image and the like can be shared in the same region.
The Availability Zone (AZ) may refer to a physical area within the same geographical area where power and network are independent.
Cloud Instance (Cloud Instance) may refer to a virtual computing environment, which may include underlying computer components such as CPUs, memory, hard disks, systems, networks, and the like. The cloud instance can be a server which is deployed in an available area by a tenant of cloud computing according to own business needs and provides business services or applications based on cloud computing in the form of virtual machines.
Host (Host) may refer to a container running Virtual machines, such as KVM (Kernel-based Virtual Machine), xen, hyper-V, and the like.
The virtual switch may refer to a device that provides ethernet packet forwarding for a virtual machine or other types of virtual devices in cloud computing, and the virtual switch is run on a host.
The LAN ID is one of attributes of a port of the virtual switch in cloud computing, a virtual machine network card corresponds to the equipment ID of the virtual switch, and one tenant only has one LAN ID.
The VLAN MASK is one of the attributes of a cloud computing virtual switch port, and is an unsigned variable of 512Bytes, and each bit corresponds to one VLAN, so that a virtual switch port can have 4096 VLANs at most.
VLAN (Virtual Local Area Network), virtual Local Area Network.
VxLAN (Virtual eXtensible Local Area Network), virtual eXtensible Local Area Network.
A tenant (tenant), in cloud computing, a user using cloud computing needs to rent resources of the cloud computing, and thus the user using cloud computing is referred to as a tenant. The user here may be an individual or an organization or institution.
Multiple cloud instances of the same tenant need to be in the same LAN, so they have the same LAN ID. The plurality here may be two or more, i.e. at least two.
With the continuous development of cloud computing technology, the requirements on a virtualized network in cloud computing are higher and higher, such as requirements on elasticity (scalability), security (security), reliability (reliability), and privacy (privacy), and in addition, a higher requirement on interconnection performance (performance); a wide variety of network virtualization technologies have emerged.
Earlier network virtualization schemes usually merge the network of virtual machines and the physical network to form a flat network architecture, such as a large two-tier network. However, as the size of the virtualized network is increased, the network attacks such as ARP spoofing, broadcast storm, host scanning and the like are more and more serious, and it is difficult for the network virtualization scheme to effectively cope with the network attacks. For this reason, a network isolation technology has been developed, which can be used to completely separate a physical network from a virtual network, so as to effectively avoid the influence caused by network attack.
Among the related network isolation techniques, there is a technique of isolating tenants in cloud computing using a VLAN; however, the traditional VLAN can only isolate 2^12 virtual data centers and cannot support huge user amount of cloud computing, particularly public cloud. As the VxLAN technology is more mature, each cloud computing manufacturer chooses VxLAN for isolation, and the maximum isolation quantity is increased to 2^ 24.
In cloud computing, available areas in different regions are completely isolated, but available areas in one region can be connected by using low-latency links (such as private lines). Part of applications in cloud computing need high disaster tolerance capability, and tenants of the applications can deploy cloud instances in different available areas of the same region, so that the aforementioned requirement for communication across available areas in the same region arises.
In the related art, a communication manner of cloud instances across available areas is shown in fig. 1, and communication between cloud instances on two different available areas needs to be forwarded through a dedicated forwarding controller: for example, the message of the cloud instance in the available area a needs to be sent to the corresponding dedicated line forwarding controller (ZonA dedicated line forwarding controller shown in fig. 1), and then the ZonA dedicated line forwarding controller forwards the message to the dedicated line forwarding controller (ZonB dedicated line forwarding controller shown in fig. 1) corresponding to the available area B, and then the ZonB dedicated line forwarding controller forwards the message to the cloud instance in the available area B.
Therefore, the communication mode needing to pass through the private line forwarding controller has long forwarding path, and the message needs to pass through the private line forwarding controller at least twice in the cross-available area transmission process, so that at least two hops of transmission paths are required. Therefore, the communication of the existing cloud instance across the available area has the problems of long transmission path and low communication transmission efficiency.
In order to solve the above problems, the present specification aims to provide a communication scheme that cloud instances cross available areas and have short transmission paths and a high communication transmission effect, and specifically, a neighbor table formed by periodically updated cloud instance information corresponding to cloud instances that cross available areas is distributed on each host (to replace a dedicated line forwarding controller function); therefore, after receiving the message across the available area issued by the cloud instance, the host determines whether the target cloud instance can communicate by inquiring the neighbor table, and directly forwards the message to the target cloud instance across the available area under the condition of communication (without skipping through a special line forwarding controller); therefore, the transmission path is shortened and the communication transmission efficiency is improved by reducing the skip of the private line forwarding controller.
On the other hand, the neighbor table is stored on each host in a distributed mode, and the abnormal condition of the individual link does not affect the normal communication of other links, so that the overall stability and robustness of cloud computing are enhanced.
On the other hand, the neighbor table is stored in each host in a distributed manner, so that a plurality of hosts can simultaneously forward the message in parallel, and the message forwarding efficiency is higher compared with the case that the dedicated line forwarding controller can only forward the message in series.
In this specification, a transmission process across available areas mainly involves three modules, which are a deployment and collector module, a sending-end host processing message module, and a receiving-end host processing message module; these three modules are described below separately.
The system comprises a deployment and collector module, a message transmission module and a message transmission module, wherein the deployment and collector module is used for ensuring mutual communication among cross-available areas and is a basis for transmitting messages among the cross-available areas.
Generally, before deploying the available area, the following operations need to be performed:
first, an Identity (Identity) of an available area to be communicated is added in a deployment configuration of the available area, the available area ID may uniquely identify a corresponding available area, and there may be a one-to-one correspondence relationship between the available area and the available area ID. The available regions may be connected by a special symbol such as an asterisk.
Second, a consolidated list across the available zones is deployed that records information about the available zones that need to be communicated, such as available zone IDs. Multiple summary lists may also be connected by special symbols such as an asterisk.
After the above operations are completed, routes of available areas needing to be communicated are deployed on the host and the aggregator, and the aggregator can periodically aggregate information of the available areas to form a flow table and send the flow table to other available areas needing to be communicated, so that the aggregator in the other available areas completes the flow table; the aggregator can also receive the flow tables sent by the aggregators of other available areas, and complete the flow tables of the aggregator based on the flow tables of the other available areas, so as to form a neighbor table deployed on the host. That is, each host may include a neighbor table communicating across the available area, or may include a neighbor table communicating in the available area. In some embodiments, the neighbor table communicated across the usable area and the neighbor table communicated with the usable area may be combined into one neighbor table.
The following method for generating the neighbor table in conjunction with the aggregator shown in fig. 2 may be applied to the aggregator deployed in the available area, and the method may include the following steps:
step 210: the collector obtains cloud example information reported by host machines in the available area.
In implementation, all hosts in the available area may report cloud example information on their respective hosts to the aggregator periodically (for example, 4 seconds), that is, the information aggregation traffic in the improved schematic diagram of the communication manner across the available area shown in fig. 3.
The cloud instance information may include host information of the cloud instance, detailed information of the cloud instance, and information of a network card of the cloud instance. In practical application, the cloud instance information may be reported in a form of a structure.
The host information may include an IP (Internet Protocol) of the host;
the cloud instance detailed information can comprise an ID of the cloud instance and an ID of an available area where the cloud instance is located;
the cloud instance network card information may include a network card ID, a LAN ID where the network card is located, a VLAN MASK, and a network card IP.
Step 220: and generating a flow table according to the cloud instance information, and exchanging the respective flow table with the aggregators of other available areas.
As shown in fig. 3, the aggregator in the available area a may generate the flow table of the available area a based on the cloud instance information uploaded by all hosts in the available area a, and forward the flow table of the available area a to the aggregator in the available area B; meanwhile, the flow table of the available area B sent by the collector in the available area B can be received; i.e., cross-usable zone traffic as shown in fig. 3.
The flow table is a set of cloud instance information; after the aggregator receives the flow tables of other areas, the flow table of the current available area and the flow tables of the other areas can be merged into one flow table, and therefore the merged flow table not only contains cloud instance information in the current available area but also contains cloud instance information in the other available areas.
Step 230: acquiring a query request initiated by a host machine in an available area; the query request carries a LAN ID list of cloud instances in the host.
In implementation, all hosts in the available area may periodically (e.g., 4 seconds) collect LAN ids of all cloud instances on their respective hosts to form a LAN id list, and initiate query requests to the aggregator; this process is the neighbor table traffic shown in figure 3.
Step 240: responding to the query request, and comparing the LAN ID in the LAN ID list with the LAN ID contained in the cloud instance information in the flow table; if the same LAN ID exists, cloud instance information corresponding to the same LAN ID is used as a query result and sent to a host initiating a query request; the host machine compares the LAN ID and the VLAN MASK of the cloud instance information in the query result with the LAN ID and the VLAN MASK of the network card of the cloud instance on the host machine; and when the LAN ID in any cloud instance information is the same as the LAN ID of the network card of the cloud instance and the VLAN MASK in the cloud instance information and the VLAN MASK of the network card have the same VLAN ID, adding the cloud instance information into the neighbor table as a piece of neighbor table information.
In implementation, the LAN ID list may be converted into a bitmap value to form a bitmap (bitmap), the flow table in step 220 may be decomposed into a single entry, the LAN ID of each entry may be converted into a bitmap value, and the bitmap value is compared with the aforementioned bitmap, if any LAN ID is true, it indicates that the LAN ID exists in both the LAN ID list and the flow table, which indicates that the cloud instance corresponding to this LAN ID is communicable. Therefore, this LAN id and its associated cloud instance information need to be sent to the host that initiated the query request, otherwise the host is not sent. It should be noted that the bitmap conversion is adopted here for the purpose of reducing the comparison time of the LAN ID to improve the comparison efficiency. In some embodiments, this may not be done, but rather the LAN ID itself is compared directly.
Further, after the summarizer returns the query result to the host, the host can decompose the query result into a single table entry, and compare the LAN ID and the VLAN MASK in the table entry with the LAN ID and the VLAN MASK of the network card of the cloud instance on the host; if the LAN ID in the table entry is the same as the LAN ID of the network card of the cloud instance, and the VLAN MASK in the table entry and the VLAN MASK of the network card have the same VLAN ID, the table entry is a piece of neighbor table information of the host machine, otherwise, the table entry is not the neighbor table information.
The neighbor table formed after processing all the table entries may be used to forward the service traffic (also referred to as tunnel packet) shown in fig. 3, that is, each host may perform communication across available areas based on the neighbor table.
After the foregoing deployment and summarizer module and the generation process of the related neighbor table are introduced, a sending-end host message processing module and a receiving-end host message processing module will be further introduced. In the communication process of the cross-usable area, a host machine where the cloud instance initiating the message is located can be called as a sending end host machine; correspondingly, the host machine where the cloud instance receiving the message is located is called a receiving end host machine.
The message processing module of the sending end host machine is used for processing the message sent by the sending end host machine and sending the processed message to the receiving end host machine; the message processing module of the host machine at the receiving end is used for processing the received message.
Referring to fig. 4, an embodiment of a cloud example cross-usable-area communication method that is described with a sending-end host as an execution subject may be applied to a sending-end host for cloud example cross-usable-area communication in cloud computing; the sending end host machine is provided with a cross-usable area special line route, a cross-usable area communication neighbor table and a local usable area communication neighbor table, and the neighbor table maintains the cross-usable area cloud instance and the cloud instance information of the local usable area cloud instance; the method can comprise the following steps:
step 410: after receiving the message sent by the cloud instance, the sending end host analyzes the LAN ID, the VLAN ID and the destination MAC corresponding to the message.
In an embodiment, the analyzing the LAN ID, the VLAN ID, and the destination MAC corresponding to the packet includes:
analyzing the LAN ID of the network card of the cloud instance which sends the message;
and analyzing the VLAN ID and the destination MAC in the message.
When the message sending method is implemented, the virtual switch of the sending end host machine can analyze the LAN ID of the network card of the cloud instance sending the message according to the private information of the message receiving thread.
The destination MAC is a destination MAC of the packet, and the destination MAC is determined by the cloud instance that initiates the packet when generating the packet.
Step 420: and inquiring a locally maintained neighbor table, and determining whether target cloud instance information crossing an available area corresponding to the target MAC exists in the neighbor table.
When the message is realized, if the target cloud instance information corresponding to the target MAC exists in the neighbor table, the message can be logically sent; and if the neighbor table does not have the destination cloud instance information corresponding to the destination MAC, the message needs to be discarded, and the communication process is also ended.
The cloud instance information has been introduced in the foregoing embodiments, and is not described herein again.
In an embodiment, an aggregator is deployed in an available area where the sending-end host is located, a flow table is maintained in the aggregator, and the flow table contains cloud instance information of all cloud instances in each available area; accordingly, the method further comprises:
initiating a query request to the aggregator; the query request carries a LAN ID list of cloud instances in the sending end host;
receiving a query result returned by the collector, wherein the query result is cloud instance information corresponding to the same LAN ID of the LAN ID list and the flow table;
comparing the LAN ID and VLAN MASK of the cloud instance information in the query result with the LAN ID and VLAN MASK of the network card of the cloud instance on the sending end host;
and when the LAN ID in any cloud instance information is the same as the LAN ID of the network card of the cloud instance and the VLAN MASK in the cloud instance information and the VLAN MASK of the network card have the same VLAN ID, adding the cloud instance information into the neighbor table as a piece of neighbor table information.
The embodiment describes a process of generating a neighbor table by a sending end host, and the content related to the process has been described in detail in the foregoing embodiment, and is not described again here.
Step 430: and if so, further determining whether the LAN ID and the VLAN ID are matched with the target cloud instance information.
When the implementation is performed, if the LAN ID and the VLAN ID match the target cloud instance information, step 440 is continuously performed; and if the LAN ID and the VLAN ID are not matched with the target cloud instance information, the message needs to be discarded, and the communication process is also finished.
Step 440: and if the matching is carried out, adding a Tunnel head and an outer layer head into the message, filling the LAN ID and the VLAN ID into the Tunnel (Tunnel) head, and filling the IP of a target host machine crossing an available area in target cloud instance information into the outer layer head to obtain the processed message.
In an embodiment, the outer header may include an outer UDP header and an outer IP header, that is, the sending host may add the outer UDP header and the outer IP header to the packet, and fill the outer UDP header and the outer IP header with the IP of the destination host.
It should be noted that the operation of adding the tunnel head and the outer layer head may be performed simultaneously or separately; for example, the operation of the tunnel header may also be performed after step 410 and before step 420. The present specification is not particularly limited thereto.
Please refer to the schematic structural diagram of the processed message shown in fig. 6, in which the inner ethernet and the subsequent part are message parts generated by the virtual machine. The outer Tunnel header contains flags such as LAN ID and VLAN ID. The outer Ethernet head, the outer IP head and the outer UDP head are used for transmitting the message in a tunnel and a cross-available area special line, the LAN ID and the VLAN ID can be brought to a target host machine through the mode, and the target host machine determines whether to forward the message to a target cloud example according to the LAN ID, the VLAN ID and a neighbor table of the message.
Step 450: sending the processed message to a receiving end host machine corresponding to the IP of the target host machine through a cross-available area special line; and the receiving end host machine forwards the message to a target cloud example according to the LAN ID and the VLAN ID in the tunnel header of the message.
In an embodiment, the sending the processed packet to the receiving-end host corresponding to the IP of the destination host through a cross-available area dedicated line includes:
determining whether the IP of the destination host is located in an available area where the sending-end host is located;
if yes, filling the available area IP of the available area into an outer layer Ethernet header of the message, and sending the message to the receiving end host machine through a cross-available area special line in a two-layer mode;
if not, according to the destination host machine IP, routing to a receiving end host machine from a special line route deployed in the sending end host machine, filling the destination host machine IP to a two-layer Ethernet header of the message, and sending the message to the receiving end host machine through a cross-available area special line in a three-layer mode.
The embodiment provides two different message sending modes in a targeted manner according to whether the receiving end host is in the same available area with the sending end host.
The steps to be done by a receiving end host are briefly introduced, and the steps comprise that after a message sent by a sending end host is received, a tunnel head of the message is analyzed, and a LAN ID and a VLAN ID in the tunnel head are obtained; analyzing an inner layer Ethernet header of the message to obtain a target network card ID; inquiring a neighbor table maintained locally, and determining whether a LAN ID and a VLAN MASK corresponding to the ID of the target network card exist; if yes, further determining whether the LAN ID of the destination network card ID is the same as the LAN ID in the tunnel header and whether the VLAN MASK of the network card ID comprises the VLAN ID in the tunnel header; and if so, forwarding the message to a target cloud instance. This will be described in detail in the following embodiments, which will be described only briefly.
In this specification, a packet can be transmitted in a tunnel and a cross-available-area dedicated line through an outer header (e.g., an outer UDP header, an outer IP header, etc.), so that a LAN ID and a VLAN ID in the tunnel header are transmitted to a destination host; and the destination host forwards the message to the destination cloud instance according to the LAN ID and the VLAN ID in the tunnel header. Thus, communication transmission across the available area can be realized without the need for the hop of the private line forwarding controller, and by reducing the hop of the private line forwarding controller (at least two hops are reduced), the transmission path is shortened, and the communication transmission efficiency is improved.
Finally, please refer to fig. 5 for the embodiment of the cloud example cross-usable area communication method introduced by using the receiving end host as the execution subject, which can be applied to the receiving end host for cloud example cross-usable area communication in cloud computing; the receiving end host machine is provided with a cross-available area special line route, a cross-available area communication neighbor table and a local available area communication neighbor table, and the neighbor table maintains cloud instance information of the cross-available area cloud instance and the local available area cloud instance; the method can comprise the following steps:
step 510: after receiving end host machine receives message sent by sending end host machine through cross-available area special line, analyzing tunnel head of the message, and obtaining LAN ID and VLAN ID in the tunnel head.
In one embodiment, the receiving host may remove the outer header of the packet, including the outer ethernet header, the outer IP header, and the outer UDP header, and then parse the tunnel header.
Step 520: and analyzing the inner layer Ethernet header of the message to obtain the ID of the target network card.
Step 530: and inquiring a neighbor table maintained locally to determine whether the LAN ID and the VLAN MASK corresponding to the ID of the target network card exist.
The cloud instance information has been introduced in the foregoing embodiments, and is not described herein again.
In an embodiment, an aggregator is deployed in an available area where the receiving end host is located, a flow table is maintained in the aggregator, and the flow table includes cloud instance information of all cloud instances in each available area; the method further comprises the following steps:
initiating a query request to the aggregator; the query request carries a LAN ID list of cloud instances in the receiving end host;
receiving a query result returned by the aggregator, wherein the query result is cloud instance information corresponding to the same LAN ID of the LAN ID list and the flow table;
comparing the LAN ID and VLAN MASK of the cloud instance information in the query result with the LAN ID and VLAN MASK of the network card of the cloud instance on the receiving end host;
and when the LAN ID in any cloud instance information is the same as the LAN ID of the network card of the cloud instance and the VLAN MASK in the cloud instance information and the VLAN MASK of the network card have the same VLAN ID, adding the cloud instance information into a neighbor table as neighbor table information.
The embodiment describes a process of generating a neighbor table by a receiving end host, and the content related to the process has been introduced in detail in the foregoing embodiment, and is not described herein again.
Step 540: if yes, further determining whether the LAN ID of the destination network card ID is the same as the LAN ID in the tunnel header, and whether the VLAN MASK of the network card ID contains the VLAN ID in the tunnel header.
Step 550: and if so, forwarding the message to a target cloud instance.
If the neighbor table has the LAN ID and the VLAN MASK corresponding to the target network card ID, the target cloud instance is communicable and the message is allowed to be forwarded; otherwise, the message is discarded, and the communication process is ended.
Further, if the LAN ID of the destination network card ID is the same as the LAN ID in the tunnel header and the VLAN MASK of the network card ID includes the VLAN ID in the tunnel header, it indicates that the destination cloud instance is indeed located in the receiving-end host, that is, the condition is satisfied, and the packet may be forwarded to the destination cloud instance in the host.
In this specification, a packet can be transmitted in a tunnel and a cross-available-area dedicated line through an outer header (e.g., an outer UDP header, an outer IP header, etc.), so that a LAN ID and a VLAN ID in the tunnel header are transmitted to a destination host; and the destination host forwards the message to the destination cloud instance according to the LAN ID and the VLAN ID in the tunnel header. Thus, communication transmission across the available area can be realized without the need for the hop of the private line forwarding controller, and by reducing the hop of the private line forwarding controller (at least two hops are reduced), the transmission path is shortened, and the communication transmission efficiency is improved.
Corresponding to the foregoing communication method embodiments of the cloud example across available areas, the present specification also provides embodiments of a communication device of the cloud example across available areas. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading a corresponding computer program in the nonvolatile memory into the memory for running through a processor of the device where the software implementation is located as a logical means. From a hardware aspect, as shown in fig. 7, a hardware structure diagram of a device in which a communication apparatus of a cloud example in this specification spans an available area is shown, except for the processor, the network interface, the memory, and the nonvolatile memory shown in fig. 7, the device in which the apparatus is located in the embodiment may also include other hardware according to an actual communication function, which is not described again.
Referring to fig. 8, a block diagram of a communication apparatus of a cloud example across available areas provided for an embodiment of the present specification, where the apparatus corresponds to the embodiment shown in fig. 4, includes:
the analysis unit 810 analyzes the LAN ID, the VLAN ID, and the destination MAC corresponding to the message after the sending-end host receives the message sent by the cloud instance;
a querying unit 820, configured to query a locally maintained neighbor table, and determine whether there is target cloud instance information of a cross-available area corresponding to the target MAC in the neighbor table;
a determining unit 830, if yes, further determining whether the LAN ID and the VLAN ID match the destination cloud instance information;
if the matching is performed, the processing unit 840 adds a tunnel header and an outer header to the packet, fills the LAN ID and the VLAN ID in the tunnel header, and fills the IP of the destination host across the available area in the destination cloud instance information in the outer header to obtain a processed packet;
a sending unit 850, configured to send the processed packet to a receiving-end host corresponding to the destination host IP through a cross-available area dedicated line; and the receiving end host machine forwards the message to a target cloud instance according to the LAN ID and the VLAN ID in the tunnel header of the message.
In an optional embodiment, an aggregator is deployed in an available area where the sending-end host is located, a flow table is maintained in the aggregator, and the flow table contains cloud instance information of all cloud instances in each available area; the device further comprises:
the request unit is used for initiating a query request to the summarizer; the query request carries a LAN ID list of cloud instances in the sending end host;
the comparison unit is used for receiving a query result returned by the collector, wherein the query result is cloud instance information corresponding to the same LAN ID of the LAN ID list and the flow table; comparing the LAN ID and VLAN MASK of the cloud instance information in the query result with the LAN ID and VLAN MASK of the network card of the cloud instance on the sending end host;
and the generation unit is used for adding the cloud instance information into the neighbor table as a piece of neighbor table information when the LAN ID in any cloud instance information is the same as the LAN ID of the network card of the cloud instance and the VLAN MASK in the cloud instance information and the VLAN MASK of the network card have the same VLAN ID.
In an optional embodiment, the cloud instance information includes host information of the cloud instance, detailed information of the cloud instance, and network card information of the cloud instance;
the host information may include a host IP;
the cloud instance detailed information can comprise an ID of the cloud instance and an ID of an available area where the cloud instance is located;
the cloud instance network card information may include a network card ID, a LAN ID where the network card is located, a VLAN MASK, and a network card IP.
In an optional embodiment, the sending unit 850 further includes: determining whether the IP of the destination host is located in an available area where the sending-end host is located; if yes, filling the available area IP of the available area to the outer layer Ethernet head of the message, and sending the message to the receiving end host machine through a cross-available area special line in a two-layer mode; if not, according to the destination host machine IP, routing to a receiving end host machine from a special line route deployed in the sending end host machine, filling the destination host machine IP to a two-layer Ethernet header of the message, and sending the message to the receiving end host machine through a cross-available area special line in a three-layer mode.
In an alternative embodiment, the apparatus comprises:
the receiving subunit, after the receiving end host receives the message sent by the sending end host, analyzes the tunnel head of the message, and obtains the LAN ID and VLAN ID in the tunnel head;
the analysis subunit analyzes the inner layer Ethernet header of the message to acquire the ID of the target network card;
the inquiry subunit inquires a locally maintained neighbor table and determines whether the LAN ID and the VLAN MASK corresponding to the target network card ID exist or not;
a determining subunit, if the destination network card ID exists, further determining whether the LAN ID of the destination network card ID is the same as the LAN ID in the tunnel header, and whether the VLAN MASK of the network card ID includes the VLAN ID in the tunnel header;
and if so, forwarding the message to a target cloud instance.
Referring to fig. 9, a block diagram of a communication apparatus of a cloud example across available areas is provided for an embodiment of the present specification, where the apparatus corresponds to the embodiment shown in fig. 5, and the apparatus includes:
a receiving unit 910, after receiving a message sent by a sending end host through a cross-available area dedicated line, a receiving end host parses a tunnel header of the message, and obtains a LAN ID and a VLAN ID in the tunnel header;
the parsing unit 920 parses the inner ethernet header of the packet to obtain the destination network card ID;
the querying unit 930 queries the locally maintained neighbor table to determine whether the LAN ID and the VLAN MASK corresponding to the destination network card ID exist;
if yes, determining unit 940 further determines whether the LAN ID of the destination network card ID is the same as the LAN ID in the tunnel header, and whether the VLAN MASK of the network card ID includes the VLAN ID in the tunnel header;
and if so, the forwarding unit 950 forwards the message to the destination cloud instance.
In an optional embodiment, an aggregator is deployed in an available area where the receiving end host is located, a flow table is maintained in the aggregator, and the flow table contains cloud instance information of all cloud instances in each available area; the device further comprises:
the request unit is used for initiating a query request to the summarizer; the query request carries a LAN ID list of cloud instances in the receiving end host;
the comparison unit is used for receiving a query result returned by the collector, wherein the query result is cloud instance information corresponding to the same LAN ID of the LAN ID list and the flow table; comparing the LAN ID and VLAN MASK of the cloud instance information in the query result with the LAN ID and VLAN MASK of the network card of the cloud instance on the receiving end host machine;
and the generating unit is used for adding the cloud embodiment information into the neighbor table as a piece of neighbor table information when the LAN ID in any cloud embodiment information is the same as the LAN ID of the network card of the cloud embodiment and the VLAN MASK in the cloud embodiment information and the VLAN MASK of the network card have the same VLAN ID.
In an optional embodiment, the cloud instance information includes host information of the cloud instance, detailed information of the cloud instance, and network card information of the cloud instance;
the host information may include a host IP;
the cloud instance detailed information can comprise an ID of the cloud instance and an ID of an available area where the cloud instance is located;
the cloud instance network card information may include a network card ID, a LAN ID where the network card is located, a VLAN MASK, and a network card IP.
The systems, apparatuses, modules or units described in the above embodiments may be specifically implemented by a computer chip or an entity, or implemented by a product with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, laptop, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.
Fig. 8 and fig. 9 above describe internal functional modules and structural schematic diagrams of a communication device of a cloud example across available areas, and a substantial execution subject of the internal functional modules and structural schematic diagrams may be an electronic device, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform an embodiment of the communication method of any of the cloud instances across the available region.
In the above embodiments of the electronic device, it should be understood that the Processor may be a Central Processing Unit (CPU), other general-purpose processors, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, and the memory may be a read-only memory (ROM), a Random Access Memory (RAM), a flash memory, a hard disk, or a solid state disk. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.
All the embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the embodiment of the electronic device, since it is substantially similar to the embodiment of the method, the description is simple, and for the relevant points, reference may be made to part of the description of the embodiment of the method.
Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following the general principles of the specification and including such departures from the present disclosure as come within known or customary practice in the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.
It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the description is limited only by the appended claims.

Claims (10)

1. A cloud instance cross-usable area communication method is characterized by being applied to a sending end host machine, wherein a neighbor table for cross-usable area communication and a neighbor table for local usable area communication are deployed in the sending end host machine, and cloud instance information of cloud instances of cross-usable areas is maintained in the neighbor table; the method comprises the following steps:
after receiving the message sent by the cloud example, the sending end host analyzes the LAN ID, the VLAN ID and the target MAC corresponding to the message;
inquiring a locally maintained neighbor table, and determining whether target cloud instance information of a cross-available area corresponding to the target MAC exists in the neighbor table;
if yes, further determining whether the LAN ID and the VLAN ID are matched with the target cloud instance information;
if the matching is carried out, adding a tunnel head and an outer layer head in the message, filling the LAN ID and the VLAN ID into the tunnel head, and filling a target host IP (Internet protocol) of a cross-available area in target cloud example information into the outer layer head to obtain a processed message;
sending the processed message to a receiving end host machine corresponding to the IP of the target host machine through a cross-available area special line; and the receiving end host machine forwards the message to a target cloud instance according to the LAN ID and the VLAN ID in the tunnel header of the message.
2. The method according to claim 1, wherein an aggregator is deployed in an available area where the sending end host is located, and a flow table is maintained in the aggregator and contains cloud instance information of all cloud instances in each available area; the method further comprises the following steps:
initiating a query request to the summarizer; the query request carries a LAN ID list of cloud instances in the sending end host;
receiving a query result returned by the collector, wherein the query result is cloud instance information corresponding to the same LAN ID of the LAN ID list and the flow table;
comparing the LAN ID and VLAN MASK of the cloud instance information in the query result with the LAN ID and VLAN MASK of the network card of the cloud instance on the sending end host;
and when the LAN ID in any cloud instance information is the same as the LAN ID of the network card of the cloud instance and the VLAN MASK in the cloud instance information and the VLAN MASK of the network card have the same VLAN ID, adding the cloud instance information into the neighbor table as a piece of neighbor table information.
3. The method according to claim 2, wherein the cloud instance information includes host information of the cloud instance, detailed information of the cloud instance, and network card information of the cloud instance;
the host information comprises a host IP;
the cloud instance detailed information comprises an ID of the cloud instance and an ID of an available area where the cloud instance is located;
the cloud example network card information comprises a network card ID, a LAN ID where the network card is located, a VLAN MASK and a network card IP.
4. The method according to claim 1, wherein said sending the processed packet to a receiving end host corresponding to the destination host IP via a cross-available area dedicated line comprises:
determining whether the IP of the destination host is located in an available area where the sending-end host is located;
if yes, filling the available area IP of the available area to the outer layer Ethernet head of the message, and sending the message to the receiving end host machine through a cross-available area special line in a two-layer mode;
if not, according to the destination host machine IP, routing to a receiving end host machine from a special line route deployed in the sending end host machine, filling the destination host machine IP to a two-layer Ethernet header of the message, and sending the message to the receiving end host machine through a cross-available area special line in a three-layer mode.
5. The method according to claim 1, characterized in that it comprises:
after receiving end host machine receives message sent by sending end host machine, analyzing tunnel head of the message, obtaining LAN ID and VLAN ID in the tunnel head;
analyzing an inner layer Ethernet header of the message to obtain a target network card ID;
inquiring a neighbor table maintained locally, and determining whether a LAN ID and a VLAN MASK corresponding to the ID of the target network card exist or not;
if yes, further determining whether the LAN ID of the destination network card ID is the same as the LAN ID in the tunnel header and whether the VLAN MASK of the network card ID comprises the VLAN ID in the tunnel header;
and if so, forwarding the message to a target cloud instance.
6. A cloud instance cross-usable area communication method is characterized by being applied to a receiving end host machine, wherein a neighbor table for cross-usable area communication and a neighbor table for local usable area communication are deployed in the receiving end host machine, and cloud instance information of cloud instances of the cross-usable area is maintained in the neighbor table; the method comprises the following steps:
after receiving end host machine receives message sent by sending end host machine through cross-available area special line, analyzing tunnel head of the message, and obtaining LAN ID and VLAN ID in the tunnel head;
analyzing an inner layer Ethernet header of the message to obtain a destination network card ID;
inquiring a neighbor table maintained locally, and determining whether a LAN ID and a VLAN MASK corresponding to the ID of the target network card exist or not;
if yes, further determining whether the LAN ID of the destination network card ID is the same as the LAN ID in the tunnel header and whether the VLAN MASK of the network card ID comprises the VLAN ID in the tunnel header;
and if so, forwarding the message to a target cloud instance.
7. The method according to claim 6, wherein an aggregator is deployed in an available area where the receiving end host is located, and a flow table is maintained in the aggregator and contains cloud instance information of all cloud instances in each available area; the method further comprises the following steps:
initiating a query request to the aggregator; the query request carries a LAN ID list of cloud instances in the receiving end host;
receiving a query result returned by the aggregator, wherein the query result is cloud instance information corresponding to the same LAN ID of the LAN ID list and the flow table;
comparing the LAN ID and VLAN MASK of the cloud instance information in the query result with the LAN ID and VLAN MASK of the network card of the cloud instance on the receiving end host;
and when the LAN ID in any cloud instance information is the same as the LAN ID of the network card of the cloud instance and the VLAN MASK in the cloud instance information and the VLAN MASK of the network card have the same VLAN ID, adding the cloud instance information into the neighbor table as a piece of neighbor table information.
8. A communication device for cloud instances crossing an available area is characterized in that the communication device is applied to a sending end host machine, a neighbor table for crossing the available area communication and a neighbor table for local available area communication are deployed in the sending end host machine, and cloud instance information of the cloud instances crossing the available area is maintained in the neighbor table; the device comprises:
the analysis unit is used for analyzing the LAN ID, the VLAN ID and the target MAC corresponding to the message after receiving the message sent by the cloud instance;
the query unit is used for querying a locally maintained neighbor table and determining whether the neighbor table has target cloud instance information of a cross-available area corresponding to the target MAC;
a determining unit, if the target cloud instance information exists, further determining whether the LAN ID and the VLAN ID are matched with the target cloud instance information;
if the matching is carried out, a tunnel head and an outer layer head are added in the message, the LAN ID and the VLAN ID are filled in the tunnel head, and a target host IP (Internet protocol) of a cross-available area in target cloud instance information is filled in the outer layer head, so that a processed message is obtained;
the sending unit sends the processed message to a receiving end host machine corresponding to the IP of the target host machine through a cross-available area special line; and the receiving end host machine forwards the message to a target cloud instance according to the LAN ID and the VLAN ID in the tunnel header of the message.
9. A communication device for cloud examples crossing an available area is characterized in that the communication device is applied to a receiving end host machine, a neighbor table for crossing the available area communication and a neighbor table for local available area communication are deployed in the receiving end host machine, and cloud example information of the cloud examples crossing the available area is maintained in the neighbor table; the device comprises:
the receiving unit is used for analyzing a tunnel head of a message after receiving the message sent by a sending end host machine through a cross-available area special line, and acquiring a LAN ID and a VLAN ID in the tunnel head;
the analysis unit is used for analyzing the inner layer Ethernet header of the message to obtain the ID of the target network card;
the inquiry unit inquires a neighbor table maintained locally and determines whether the LAN ID and the VLAN MASK corresponding to the target network card ID exist or not;
a determining unit, if yes, further determining whether the LAN ID of the destination network card ID is the same as the LAN ID in the tunnel header, and whether the VLAN MASK of the network card ID contains the VLAN ID in the tunnel header;
and if so, forwarding the message to a target cloud instance.
10. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the method of any of the preceding claims 1-7.
CN202211110546.3A 2022-09-13 2022-09-13 Communication method and device for cloud instance to cross available areas and electronic equipment Active CN115208888B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211110546.3A CN115208888B (en) 2022-09-13 2022-09-13 Communication method and device for cloud instance to cross available areas and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211110546.3A CN115208888B (en) 2022-09-13 2022-09-13 Communication method and device for cloud instance to cross available areas and electronic equipment

Publications (2)

Publication Number Publication Date
CN115208888A true CN115208888A (en) 2022-10-18
CN115208888B CN115208888B (en) 2022-12-27

Family

ID=83571985

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211110546.3A Active CN115208888B (en) 2022-09-13 2022-09-13 Communication method and device for cloud instance to cross available areas and electronic equipment

Country Status (1)

Country Link
CN (1) CN115208888B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116094923A (en) * 2023-01-30 2023-05-09 杭州优云科技有限公司 Gateway updating method and device after cloud instance migration and electronic equipment
CN116137585A (en) * 2023-04-20 2023-05-19 武汉绿色网络信息服务有限责任公司 Message forwarding method, device, computer equipment and storage medium
CN116319354A (en) * 2023-01-30 2023-06-23 杭州优云科技有限公司 Network topology updating method based on cloud instance migration

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060233174A1 (en) * 2005-03-28 2006-10-19 Rothman Michael A Method and apparatus for distributing switch/router capability across heterogeneous compute groups
CN104579954A (en) * 2013-10-16 2015-04-29 华为技术有限公司 Message cross-domain forwarding method and device as well as communication device
CN105577548A (en) * 2014-10-10 2016-05-11 杭州华三通信技术有限公司 Software definition network message processing method and device
CN107070691A (en) * 2017-01-12 2017-08-18 阿里巴巴集团控股有限公司 Docker containers across host communication method and system
CN107395781A (en) * 2017-06-29 2017-11-24 北京小度信息科技有限公司 Network communication method and device
CN107453992A (en) * 2016-05-30 2017-12-08 北京京东尚科信息技术有限公司 Data forwarding method and system in a kind of virtual network
CN107547344A (en) * 2017-06-30 2018-01-05 新华三技术有限公司 VXLAN message processing methods and device
CN107770064A (en) * 2016-08-19 2018-03-06 华为技术有限公司 A kind of method of internetwork communication, equipment
CN109639557A (en) * 2019-02-11 2019-04-16 北京百度网讯科技有限公司 Methods, devices and systems for network communication
CN111010329A (en) * 2019-03-20 2020-04-14 新华三技术有限公司 Message transmission method and device
CN112039920A (en) * 2020-09-14 2020-12-04 迈普通信技术股份有限公司 Communication method, communication device, electronic device and storage medium
CN112565047A (en) * 2020-11-19 2021-03-26 浪潮思科网络科技有限公司 Method, device, equipment and medium for constructing network by using VPP in docker
CN114095460A (en) * 2022-01-20 2022-02-25 杭州优云科技有限公司 Message broadcasting method and device
US20220210086A1 (en) * 2020-12-30 2022-06-30 Oracle International Corporation Managing network state for high flow availability within distributed network platform
US20220231944A1 (en) * 2021-01-15 2022-07-21 Vmware, Inc. Direct communication between endpoints across remote sites

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060233174A1 (en) * 2005-03-28 2006-10-19 Rothman Michael A Method and apparatus for distributing switch/router capability across heterogeneous compute groups
CN104579954A (en) * 2013-10-16 2015-04-29 华为技术有限公司 Message cross-domain forwarding method and device as well as communication device
CN105577548A (en) * 2014-10-10 2016-05-11 杭州华三通信技术有限公司 Software definition network message processing method and device
CN107453992A (en) * 2016-05-30 2017-12-08 北京京东尚科信息技术有限公司 Data forwarding method and system in a kind of virtual network
CN107770064A (en) * 2016-08-19 2018-03-06 华为技术有限公司 A kind of method of internetwork communication, equipment
CN107070691A (en) * 2017-01-12 2017-08-18 阿里巴巴集团控股有限公司 Docker containers across host communication method and system
CN107395781A (en) * 2017-06-29 2017-11-24 北京小度信息科技有限公司 Network communication method and device
CN107547344A (en) * 2017-06-30 2018-01-05 新华三技术有限公司 VXLAN message processing methods and device
CN109639557A (en) * 2019-02-11 2019-04-16 北京百度网讯科技有限公司 Methods, devices and systems for network communication
CN111010329A (en) * 2019-03-20 2020-04-14 新华三技术有限公司 Message transmission method and device
CN112039920A (en) * 2020-09-14 2020-12-04 迈普通信技术股份有限公司 Communication method, communication device, electronic device and storage medium
CN112565047A (en) * 2020-11-19 2021-03-26 浪潮思科网络科技有限公司 Method, device, equipment and medium for constructing network by using VPP in docker
US20220210086A1 (en) * 2020-12-30 2022-06-30 Oracle International Corporation Managing network state for high flow availability within distributed network platform
US20220231944A1 (en) * 2021-01-15 2022-07-21 Vmware, Inc. Direct communication between endpoints across remote sites
CN114095460A (en) * 2022-01-20 2022-02-25 杭州优云科技有限公司 Message broadcasting method and device

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
SEBASTIEN VARRETTE等: "On Verifying and Assuring the Cloud SLA by Evaluating the Performance of SaaS Web Services Across Multi-cloud Providers", 《2018 48TH ANNUAL IEEE/IFIP INTERNATIONAL CONFERENCE ON DEPENDABLE SYSTEMS AND NETWORKS WORKSHOPS (DSN-W)》 *
周春华等: "面向虚拟数据中心的云网络资源共享与隔离方法研究", 《中国新通信》 *
韩贞阳等: "基于软件定义网络的IaaS虚拟机通信访问控制方法", 《计算机应用》 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116094923A (en) * 2023-01-30 2023-05-09 杭州优云科技有限公司 Gateway updating method and device after cloud instance migration and electronic equipment
CN116319354A (en) * 2023-01-30 2023-06-23 杭州优云科技有限公司 Network topology updating method based on cloud instance migration
CN116094923B (en) * 2023-01-30 2023-08-25 杭州优云科技有限公司 Gateway updating method and device after cloud instance migration and electronic equipment
CN116319354B (en) * 2023-01-30 2023-11-28 杭州优云科技有限公司 Network topology updating method based on cloud instance migration
CN116137585A (en) * 2023-04-20 2023-05-19 武汉绿色网络信息服务有限责任公司 Message forwarding method, device, computer equipment and storage medium

Also Published As

Publication number Publication date
CN115208888B (en) 2022-12-27

Similar Documents

Publication Publication Date Title
CN115208888B (en) Communication method and device for cloud instance to cross available areas and electronic equipment
CN106789526B (en) method and device for connecting multiple system networks
US9948575B2 (en) Issuing method for forwarding adjacency link
US10749936B1 (en) Managing communications having multiple alternative destinations
US9608841B2 (en) Method for real-time synchronization of ARP record in RSMLT cluster
CN108259304B (en) Forwarding table item synchronization method and device
EP4047888A1 (en) Method for issuing oam configuration information and control node
CN109617816B (en) Data message transmission method and device
CN108306806B (en) Message forwarding method and device
US8713663B2 (en) Method for using extended security system, extended security system and devices
JP5467143B2 (en) Server-to-server connection system, server, and data transfer method
CN111182022A (en) Data transmission method and device, storage medium and electronic device
CN114745255A (en) Hardware chip, DPU, server, communication method and related device
CN110391919B (en) Multicast traffic forwarding method and device, and electronic device
CN113839862B (en) Method, system, terminal and storage medium for synchronizing ARP information between MCLAG neighbors
CN116094923B (en) Gateway updating method and device after cloud instance migration and electronic equipment
US20230353479A1 (en) Edge Computing Data and Service Discovery Using an Interior Gateway Protocol (IGP)
CN114760165A (en) Message transmission method, device and system
CN114389967A (en) Link detection method, device, equipment and storage medium
CN108900422B (en) Multicast forwarding method and device and electronic equipment
CN111600929A (en) Transmission line detection method, route strategy generation method and proxy server
CN108768845B (en) Multi-homing host routing synchronization method and device
EP4294080A1 (en) Route processing method and network device
CN114553707B (en) Method and device for generating topology information of network and delimiting network faults
WO2018028592A1 (en) Method and device for receiving and sending messages

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant