CN114172853B - Configuration method and device of traffic forwarding and bare computer server - Google Patents
Configuration method and device of traffic forwarding and bare computer server Download PDFInfo
- Publication number
- CN114172853B CN114172853B CN202111454610.5A CN202111454610A CN114172853B CN 114172853 B CN114172853 B CN 114172853B CN 202111454610 A CN202111454610 A CN 202111454610A CN 114172853 B CN114172853 B CN 114172853B
- Authority
- CN
- China
- Prior art keywords
- virtual
- switch
- target
- server
- virtual switch
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 239000002184 metal Substances 0.000 claims abstract description 108
- 230000004044 response Effects 0.000 claims description 11
- 239000010410 layer Substances 0.000 description 29
- 238000010586 diagram Methods 0.000 description 10
- 238000002955 isolation Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 6
- 230000009471 action Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000000926 separation method Methods 0.000 description 3
- 206010047289 Ventricular extrasystoles Diseases 0.000 description 2
- 230000006399 behavior Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 239000012792 core layer Substances 0.000 description 2
- 239000003999 initiator Substances 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000005641 tunneling Effects 0.000 description 2
- 238000005129 volume perturbation calorimetry Methods 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 206010035148 Plague Diseases 0.000 description 1
- 241000607479 Yersinia pestis Species 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000011217 control strategy Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/70—Virtual switches
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/25—Routing or path finding in a switch fabric
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
One or more embodiments of the present disclosure provide a method and an apparatus for configuring a traffic forwarding and bare metal server, where the traffic forwarding method is applied to a physical switch connected to the bare metal server, and includes: responding to a received virtual switch deployment instruction, and participating in deploying the virtual switch; determining a target bare computer server specified by the virtual switch deployment instruction in bare computer servers connected with the physical switch, and associating the target bare computer server with the virtual switch; and forwarding the target traffic through the virtual switch when the target traffic for the target bare metal server is received.
Description
Technical Field
One or more embodiments of the present disclosure relate to the field of computer networks, and in particular, to a method and apparatus for configuring a traffic forwarding and bare metal server.
Background
In a server hosting scenario, different users rent different servers in the same public cloud, so user isolation needs to be achieved at the cloud, and in related art, user isolation is typically achieved by deploying virtual switches on servers rented by users. However, with the development trend of cloud native technology and distributed cloud and multi-cloud, users start to have a requirement of acquiring bare computer servers from cloud manufacturers, that is, users need to provide servers without installing any irrelevant software by the cloud manufacturers, and this is required to cancel deployment of virtual switches on the servers, so this requirement brings challenges to user isolation of the cloud, and therefore, how to provide bare computer cloud services to clients becomes a problem to be solved urgently.
Disclosure of Invention
In view of this, one or more embodiments of the present disclosure provide a method, an apparatus, an electronic device, and a storage medium for configuring a traffic forwarding and bare metal server.
One or more embodiments of the present disclosure provide the following technical solutions:
according to a first aspect of one or more embodiments of the present disclosure, a traffic forwarding method is provided, applied to a physical switch connected to a bare metal server, including:
responding to a received virtual switch deployment instruction, and participating in deploying the virtual switch;
determining a target bare computer server specified by the virtual switch deployment instruction in bare computer servers connected with the physical switch, and associating the target bare computer server with the virtual switch;
and forwarding the target traffic through the virtual switch when the target traffic for the target bare metal server is received.
According to a second aspect of one or more embodiments of the present disclosure, a configuration method of a bare metal server is provided, which is applied to a management server, and includes:
determining a physical switch connected with a target bare computer server in response to a virtual switch deployment request initiated for the target bare computer server;
And sending a virtual switch deployment instruction to the determined physical switch, enabling the determined physical switch to participate in deploying the virtual switch, and associating the target bare computer server to the virtual switch so that the virtual switch is used for forwarding the target traffic received by the determined physical switch and aiming at the target bare computer server.
According to a third aspect of one or more embodiments of the present specification, there is provided a traffic forwarding apparatus applied to a physical switch connected to a bare metal server, comprising:
the instruction receiving unit is used for responding to the received virtual switch deployment instruction and participating in the deployment of the virtual switch;
a bare metal association unit configured to determine, among bare metal servers connected to the physical switch, a target bare metal server specified by the virtual switch deployment instruction, and associate the target bare metal server to the virtual switch;
and the traffic forwarding unit is used for forwarding the target traffic through the virtual switch under the condition that the target traffic aiming at the target bare computer server is received.
According to a fourth aspect of one or more embodiments of the present specification, there is provided a configuration apparatus of a bare metal server, applied to a management server, including:
A request response unit for determining a physical switch connected with a target bare computer server in response to a virtual switch deployment request initiated for the target bare computer server;
the instruction sending unit is used for sending a virtual switch deployment instruction to the determined physical switch, enabling the determined physical switch to participate in deploying the virtual switch, and associating the target bare computer server to the virtual switch so as to be used by the virtual switch for forwarding the target traffic which is received by the determined physical switch and is aimed at the target bare computer server.
According to a fifth aspect of one or more embodiments of the present specification, there is provided an electronic device, comprising:
a processor; a memory for storing processor-executable instructions; the processor executes the executable instructions to implement the above-mentioned traffic forwarding method or the configuration method of the bare computer server.
According to a sixth aspect of one or more embodiments of the present description, there is provided a computer-readable storage medium having stored thereon executable instructions; and when the instruction is executed by the processor, the method for forwarding the flow or the configuration method of the bare computer server is realized.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and together with the description, serve to explain the principles of the specification.
Fig. 1 is a network architecture diagram of a configuration of a traffic forwarding and bare metal server according to an exemplary embodiment provided in the present specification.
Fig. 2 is a flow chart of a traffic forwarding method provided in the present specification according to an exemplary embodiment.
Fig. 3 is a network architecture schematic diagram of a virtual private cloud VPC according to an exemplary embodiment of the present description.
Fig. 4 is a flowchart of a method for configuring a bare metal server according to an exemplary embodiment provided herein.
Fig. 5 is a schematic diagram of an apparatus according to an exemplary embodiment.
Fig. 6 is a block diagram of a traffic forwarding device provided in accordance with an exemplary embodiment of the present specification.
Fig. 7 is a block diagram of a configuration apparatus of a bare metal server according to an exemplary embodiment provided in the present specification.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with aspects of one or more embodiments of the present description as detailed in the accompanying claims.
It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments.
Fig. 1 is a network architecture diagram of a configuration of a traffic forwarding and bare metal server according to an exemplary embodiment. As shown in fig. 1, the network architecture is specifically a physical network architecture of a bare metal cloud (bare metal cloud), the bare metal cloud according to the embodiment of the present disclosure refers to a lightweight cloud that provides bare metal access and hosting, and is formed by a network formed by a plurality of bare metal servers, in the embodiment of the present disclosure, a plurality of physical servers (only bare metal servers 1 to 6 and 1 management server are shown in fig. 1) and a plurality of physical switches (only physical switches a to D and a core switch that connects them together are shown in fig. 1) are specifically included, wherein the core switch is connected to physical switches a to D, the physical switch a is connected to an Internet public network channel or a cloud service channel, the physical switch B is connected to bare metal servers 1 to 3, the physical switch C is connected to bare metal servers 4 to 6, and the physical switch D is connected to the management server.
The physical switch in this embodiment of the present disclosure may include a core layer physical switch, a convergence layer physical switch, and an access layer physical switch, where the core layer physical switch (e.g. the core switch shown in fig. 1) is used as each convergence layer physical switch or an intermediate network structure between the access layer physical switches, and is used to connect each two-layer subnetwork, so as to implement network accessibility of the whole network, and the access layer physical switch is a physical switch directly connected to a server device or an external network, e.g. the physical switches a-D shown in fig. 1 belong to the access layer physical switch, each physical switch and a device hung below the physical switch together form a two-layer network, devices inside the two-layer network may implement mutual access, and the convergence layer physical switch generally refers to a physical switch hooked between the access layer physical switch and the convergence layer physical switch (the network structure shown in fig. 1 only includes a 2-layer switch structure, so if the physical switches a-D are regarded as access layer physical switches, the convergence layer physical switch is not shown in fig. 1), and the convergence layer physical switch may also be directly hung as a bare device (e.g. a device) so as to be regarded as a service layer physical switch in fig. 1.
The bare metal server (Bare Metal Server) in the embodiment of the present specification is specifically referred to as a bare metal server, which essentially belongs to a physical computer, and does not install any program other than an operating system, and is designed specifically for running a special service uploaded by a user, and is not interrupted for a long time. It has high stability, durability and reliability. Bare computer servers are a single user environment, meaning that the physical resources of a single server may not be shared between two or more users. Because of this physical isolation, bare computer servers do not have a "noisy neighbor" effect that plagues the virtual environment. An important benefit of such isolation is performance predictability. Thus, bare computer servers have the most stable environment, and are well suited for processing large amounts of data. The management server in the embodiment of the present disclosure may manage all other devices in the bare computer cloud, such as a core switch, a physical switch, and a bare computer server, and may obtain their mac information and management IP address (the bare computer cloud may be regarded as an intranet, and the IP addresses in the embodiment of the present disclosure refer to the intranet IP address of the corresponding device in the bare computer cloud), and maintain a global network architecture of the entire bare computer cloud.
Fig. 2 is a flowchart of a traffic forwarding method according to an exemplary embodiment provided in the present specification, which is applied to a physical switch connected to a bare metal server, and includes the steps of:
s202: and responding to the received virtual switch deployment instruction, and participating in the deployment of the virtual switch.
In this embodiment of the present disclosure, the bare metal server may be a bare metal server in the bare metal cloud shown in fig. 1, the virtual switch deployment instruction includes a virtual network identifier, and the participating deployment virtual switch includes: creating virtual edge equipment in a virtual network corresponding to the virtual network identifier; wherein the virtual switch is implemented based on the virtual network.
In an embodiment, the virtual switch deployment instruction only includes information of a physical switch (i.e., a local physical switch) of the received virtual switch deployment instruction, for example, IP address or mac (Medium/Media Access Control) information of the physical switch, after the physical switch receives the virtual switch deployment instruction, the physical switch determines whether the IP address or mac information of the local physical switch matches with information on the virtual switch deployment instruction, if the matching is successful, a virtual edge device in a virtual network corresponding to a virtual network identifier is created, and because the virtual network only includes one virtual edge device created in the local physical switch, the virtual network in this case only includes the virtual edge device itself, which makes the virtual switch participating in deployment unable to implement port number expansion, but only can implement the effect of user isolation, because the virtual network device in the same physical switch can participate in deploying a plurality of virtual switches in different virtual networks (virtual networks corresponding to different virtual network labels), so that the bare machine server under suspension is associated with the virtual network in different bare machine cloud implementation virtual machines.
In another embodiment, the virtual switch deployment instruction includes information of a plurality of physical switches; the virtual network comprises virtual edge devices respectively created by the plurality of physical switches and network tunnels maintained between the virtual edge devices. Specifically, the virtual switch deployment instruction includes at least one IP address of the target physical switch (an intranet IP address of the target physical device in the bare machine cloud), so as to indicate to the physical switch that receives the virtual switch deployment instruction: the IP addresses corresponding to all other virtual edge devices in the virtual network to be created are the IP addresses of the target physical switches except for the IP addresses of the target physical switches in the at least one target physical switch. Therefore, the virtual edge devices created in the physical switch can maintain a broadcast domain, and the broadcast domain includes the IP addresses of all the virtual edge devices in the same virtual network (the virtual network corresponding to the same virtual network identifier), so that the virtual edge devices in the virtual network can realize mutual access according to the broadcast domain maintained by the virtual edge devices, and the virtual network essentially is realized by constructing network tunnels between different virtual edge devices, that is, the virtual network includes all the virtual edge devices and the network tunnels maintained between them, so that the mutual access between the physical switches deployed with different virtual edge devices in the same virtual network can be realized through the virtual network, and based on the fact, the physical switches are not directly connected physically, but realize two-layer intercommunication through network tunneling technology, thus logically forming a large two-layer network, realizing two-layer network isolation in the bare machine cloud, and enabling two-layer intercommunication of bare machine servers hung under different physical switches. In this case, the virtual switches that the physical switches participate in the deployment may logically connect the plurality of physical switches through the network tunneling technique, thereby realizing the port number expansion while realizing the effect of user isolation.
The virtual network according to the embodiments of the present specification may include a VLAN (Virtual Local Area Network ) or VXLAN (Virtual eXtensible Local Area Network, virtual extensible local area network), and the embodiments of the present specification will be described in detail below with reference to the virtual network as VXLAN. After the physical switch receives the virtual switch deployment instruction, firstly, a virtual edge device is created locally, namely a VTEP (VXLAN Tunnel End Point ) in the VXLAN, the VTEP is bound with a virtual network identifier carried in the virtual switch deployment instruction, namely a VNI (VXLAN Network Identifier ) in the VXLAN, the VTEP is virtualized in the physical switch as a virtual device, the same VTEP can acquire IP addresses of other VTEPs in the VXLAN from the virtual switch deployment instruction so as to maintain a broadcast domain corresponding to the VXLAN, and then, the VTEP and other VTEPs bound with the same VNI respectively construct VXLAN tunnels, so that all VTEPs bound with the same VNI and VXLAN tunnels therebetween form a VXLAN together.
The physical switch connected with the bare computer server according to the embodiment of the present disclosure specifically refers to an access layer physical switch or a convergence layer physical switch.
S204: in a bare metal server connected to the physical switch, a target bare metal server specified by the virtual switch deployment instruction is determined, and the target bare metal server is associated to the virtual switch.
In this embodiment of the present disclosure, the virtual switch deployment instruction includes mac information of at least one bare metal server, where the at least one bare metal server is a bare metal server connected to a virtual switch after the virtual switch completes deployment, and the determining a target bare metal server specified by the virtual switch deployment instruction includes: the mac information of the bare computer server connected with the local port and the mac information of the at least one bare computer server are matched, the bare computer server corresponding to the mac information which is successfully matched is determined as the target bare computer server, and the determined target bare computer server is the bare computer server which needs to be associated with the virtual switch.
In the embodiment of the present disclosure, a plurality of physical local ports included in a physical switch may be respectively connected to a plurality of bare metal servers, so that mac information of each bare metal server directly connected to the physical switch may be obtained through the ports, thereby maintaining a device table in the local physical switch, where mac information of all bare metal servers connected to the local physical switch is recorded. Therefore, when the physical switch receives the virtual switch deployment instruction, the device table maintained by the local terminal can be searched according to the mac information of at least one bare computer server contained in the virtual switch deployment instruction, and when the mac information is hit, the bare computer server corresponding to the hit mac information is determined as the target bare computer server.
On the basis of the above embodiment, the virtual switch deployment instruction includes mac information of at least one bare computer server and an IP address of a physical switch to which each of the bare computer server is connected, and the method further includes: determining other bare computer servers except the target bare computer server in the at least one bare computer server; generating route information according to mac information of the other bare computer servers and IP addresses corresponding to the physical switches connected with the mac information, and binding the route information to a virtual network forwarding table corresponding to the virtual network.
In the embodiment of the present disclosure, since the virtual switch deployment instruction includes mac information of at least one bare metal server, the mac information is equivalent to a bare metal server that indicates a virtual switch to be deployed and that needs to be hung down, so that a virtual private network is built in the bare metal cloud, where the virtual private network includes the virtual switch and the bare metal server that is hung down. For virtual edge devices in a virtual network for implementing a virtual switch, only maintaining network tunnels between virtual edge devices inside the virtual network cannot implement mutual access of bare computer server levels, because in a two-layer network, when a physical switch receives a message sent from a bare computer server, a target address designated by the physical switch is mac information instead of an IP address, so that for each virtual edge device, it is required to acquire not only IP addresses of other virtual edge devices in the virtual network, but also mac information of bare computer servers hung under all virtual edge devices to construct routing information from mac information to corresponding IP addresses. Therefore, in the embodiment of the present disclosure, since the virtual switch deployment instruction includes mac information of at least one bare computer server and IP addresses of physical switches connected to the at least one bare computer server, so that the physical switches can learn mac information of the bare computer servers connected to the at least one physical switch, after determining a target bare computer server directly connected to a home terminal, the physical switch can generate routing information according to mac information of other bare computer servers except the target bare computer server and IP addresses corresponding to the physical switches connected to the mac information of the other bare computer servers in the at least one bare computer server, and bind the routing information to a virtual network forwarding table corresponding to the virtual network, where the virtual network forwarding table is maintained in a virtual edge device created on the home terminal physical switch. After receiving the target traffic of the target bare metal switch, the local physical switch sends the target traffic to the virtual edge device created by the local physical switch, so that the virtual edge device forwards the target traffic according to the virtual network forwarding table. Obviously, since the correspondence between mac information and IP addresses is recorded in the virtual network forwarding table, in the embodiment of the present specification, the virtual network forwarding table is a link layer forwarding table.
In this embodiment of the present disclosure, the associating the target bare metal server to the virtual switch includes: and binding the corresponding relation between the mac information of the target bare computer server and the corresponding local port to the mac information of the target bare computer server to a virtual network forwarding table corresponding to the virtual network in the form of routing information. The bare computer server connected with the local port can be obtained by checking the local equipment table, so that mac information of the target bare computer server and route information of the corresponding local port are written in the virtual network forwarding table, and when a message from other virtual edge equipment is sent to the virtual edge equipment, the message can be forwarded to the target bare computer server when the destination mac information of the message is the mac information of the target bare computer server. In addition, the corresponding relation between the mac information of the target bare computer server and the virtual network identifier can be written in the local device table, so that after the target traffic from the target bare computer server is received, the corresponding virtual network can be obtained through the device table, and the virtual edge device to be sent to can be determined.
S206: and forwarding the target traffic through the virtual switch when the target traffic for the target bare metal server is received.
As described above, after the target bare computer server is associated to the virtual router, when receiving the target traffic for the target bare computer server, the target traffic is forwarded based on the virtual network forwarding table through the virtual edge device created in the home physical switch. For example, when a message from a target bare computer server is received, firstly, obtaining that the message is from the target bare computer server according to source mac information of the message, then searching a device table maintained on a local physical switch, searching a virtual network identifier corresponding to the source mac information, determining virtual edge devices created by a virtual network based on the virtual network identifier on the local physical switch, and forwarding target traffic by the virtual edge devices according to a virtual network forwarding table maintained by the virtual edge devices; for another example, when the received message includes a virtual network identifier, the corresponding virtual network is determined based on the network identifier first, and the message is forwarded to a virtual edge device created by the local physical switch for the corresponding virtual network after the virtual network identifier is removed, and if the destination mac information of the message is the mac identifier of the target bare computer server, the message is forwarded to the local port corresponding to the target bare computer server directly based on a virtual network forwarding table in the virtual edge device, so that the message is finally forwarded to the target bare computer server.
In the embodiment of the specification, the virtual switch deployment instruction is issued to the physical switch connected with the bare computer server, so that the virtual switch is only participated in deployment by the physical switch, and then the target bare computer server is associated with the virtual switch constructed based on the physical switch, thereby realizing the process of deploying the bare computer server under the virtual switch. Because the virtual switch is not directly deployed on the bare computer server, the actual deployed bare computer server, namely the bare computer server subsequently delivered to the user, can keep the state of not installing any irrelevant software, meets the requirement of the user on renting the bare computer server, and simultaneously, after the deployment is completed and the target bare computer server is associated with the virtual switch, all target traffic aiming at the target bare computer server is forwarded through the virtual switch instead of forwarding based on a native forwarding table of a physical switch in the bare computer cloud, which is equivalent to building a virtual private network in the bare computer cloud, thereby realizing the separation of the user on the bare computer cloud and providing bare computer cloud services for the user.
In the embodiment of the present specification, the virtual switch and a bare metal server connected to the virtual switch belong to a virtual private cloud VPC corresponding to an initiator user of the virtual switch deployment instruction. In this illustrative embodiment, the virtual switch is managed by a management server in the bare metal cloud, and the virtual router deployment instruction is initiated by the management server in response to a user-implemented virtual router deployment operation. The user identities of different users have binding relation with the virtual network identifier, so that after the user logs in the management server through the client, the user can initiate various configuration operations on the VPC (Virtual Private Cloud ) of the user by a control console on the client, wherein the configuration operations comprise rule configuration operations and virtual router deployment operations. For example, after a user initiates a virtual router deployment operation, a corresponding virtual router deployment request is generated and sent from a client to a management server, the management server further generates a virtual router deployment instruction after receiving the virtual router deployment instruction and sends the virtual router deployment instruction to a corresponding physical switch in the bare computer cloud, and meanwhile, the virtual router deployment instruction carries a virtual network identifier corresponding to a user identity. Through the embodiment of the specification, a user can realize configuration operation on the VPCs held by the user, for example, by initiating virtual switch deployment operation, so that the configuration of any number of bare computer servers is realized, the bare computer servers are added into the VPCs, and the renting function for the bare computer servers is completed.
Fig. 3 is a network architecture schematic diagram of a virtual private cloud VPC according to an exemplary embodiment of the present description. As shown in fig. 3, the VPC of the user includes a virtual router for connecting to the public Internet, a private line or other cloud services, and a virtual router for connecting to the bare metal server 1, the bare metal server 3, the bare metal server 4 and the bare metal server 5, respectively, where the virtual router is essentially implemented by a virtual network, the bare metal server 1 and the bare metal server 3 are physically connected to the physical router B, and the bare metal server 4 and the bare metal server 5 are physically connected to the physical router C, and the physical router B and the physical router C implement two-layer interworking through a network tunnel between virtual edge devices created by the respective routers, so that a logical two-layer network is constructed, and at this time, the bare metal server 1, the bare metal server 3, the bare metal server 4 and the bare metal server 5 can perform two-layer interworking without perception.
Optionally, the method further comprises: and responding to the received rule configuration instruction, and configuring a flow forwarding rule for the virtual switch. In the embodiment of the present disclosure, the rule configuration instruction includes a virtual network identifier, so after the physical switch receives the rule configuration instruction, the physical switch needs to determine a corresponding virtual network according to the virtual network identifier, so as to determine a virtual edge device in the corresponding virtual network deployed by the local end, and then configure the virtual edge device based on a flow table carried in the rule configuration instruction and recorded with a flow forwarding rule of the virtual switch, where the virtual switch is essentially implemented by the virtual network, so that the virtual switch configured in the embodiment of the present disclosure is essentially the virtual switch implemented by the virtual network corresponding to the virtual network identifier, and configuring the virtual edge device is essentially the virtual switch. In embodiments of the present disclosure, the configuration traffic forwarding rules may be for one or more bare metal servers connected to a virtual switch, and the traffic forwarding rules include security groups and/or access control rules. In the embodiment of the specification, the created virtual switch can be configured by sending a rule configuration instruction, so that a user can configure a personalized flow control strategy for the virtual private network in the bare computer cloud held by the user.
FIG. 4 is a flowchart of a bare metal server configuration method provided by the present specification according to an exemplary embodiment, the method being applied to a management server, and comprising the steps of:
s402: in response to a virtual switch deployment request initiated for a target bare metal server, a physical switch connected to the target bare metal server is determined.
In this embodiment of the present disclosure, the management server may be a management server in the bare computer cloud shown in fig. 1, and the virtual switch deployment request may be initiated by a user at a client that has logged into the management server, and the virtual switch deployment request is generated by responding to a virtual switch deployment operation of a console of the user at the client. For example, a user may perform a virtual switch deployment operation at a console interface on a client after logging the client into a management server and assign the number of bare metal servers that the virtual switch needs to be down. After the virtual switch deployment request generated by the client is received by the management server, the management server will automatically allocate a corresponding number of bare metal servers which are not configured at present and are in an idle state as target bare metal servers according to the number of bare metal servers required to be hung by the virtual switch, because the management server can globally manage all devices in the bare metal cloud, and therefore can know the working state, configuration condition and basic information (such as an IP address, mac information and position in a network architecture) of each bare metal server. Meanwhile, the management server determines the physical switches to which the target bare computer server is physically connected, and when the number of the target bare computer servers is plural and the target bare computer servers are respectively connected by different physical switches, the number of the finally determined physical switches is plural, and it should be noted that the physical switches connected with the target bare computer server are not physical switches directly connected with all the target bare computer servers, but are physical switches connected with at least one target bare computer server.
S404: and sending a virtual switch deployment instruction to the determined physical switch, enabling the determined physical switch to participate in deploying the virtual switch, and associating the target bare computer server to the virtual switch so that the virtual switch is used for forwarding the target traffic received by the determined physical switch and aiming at the target bare computer server.
The management server may send a virtual switch deployment instruction to the determined physical switch based on the determined IP address of the physical switch. It should be noted that when the number of the determined physical switches is plural, for each of the determined physical switches, the target bare metal servers to which the virtual switch is associated are not all target bare metal servers but target bare metal servers physically connected to the determined physical switch. Because the local information of the determined physical switches is slightly different, personalized and customized virtual switch deployment instructions can be sent to the different determined physical switches in the stage of sending virtual switch deployment instructions, for example, the virtual switch deployment instructions sent to a certain determined physical switch can only comprise the IP addresses of all the determined physical switches except the determined physical switch, because the IP addresses are known information for the determined physical switch, the IP addresses belong to redundant information for the determined physical switch theoretically, and the redundant information is eliminated in the stage of sending virtual switch deployment instructions, so that invalid traffic can be prevented from being increased in the network and the network load in the cloud can be reduced. As previously described, the virtual network identifier carried in the virtual switch deployment instruction is uniquely determined by the identity of the user initiating the virtual switch deployment operation. The behavior of the physical switch after receiving the virtual switch deployment instruction is described in detail in the foregoing embodiments, and will not be described herein.
In the embodiment of the specification, the virtual switch deployment instruction is issued to the physical switch connected with the bare computer server, so that the virtual switch is only participated in deployment by the physical switch, and then the target bare computer server is associated with the virtual switch constructed based on the physical switch, thereby realizing the process of deploying the bare computer server under the virtual switch. Because the virtual switch is not directly deployed on the bare computer server, the actual deployed bare computer server, namely the bare computer server subsequently delivered to the user, can keep the state of not installing any irrelevant software, meets the requirement of the user on renting the bare computer server, and simultaneously, after the deployment is completed and the target bare computer server is associated with the virtual switch, all target traffic aiming at the target bare computer server is forwarded through the virtual switch instead of forwarding based on a native forwarding table of a physical switch in the bare computer cloud, which is equivalent to building a virtual private network in the bare computer cloud, thereby realizing the separation of the user on the bare computer cloud and providing bare computer cloud services for the user.
Optionally, any physical switch includes a configuration port, where the configuration port is used to enable the management server to manage any physical switch; the sending the virtual switch deployment instruction to the determined physical switch comprises the following steps: and sending a virtual switch deployment instruction to the determined physical switch through the configuration port in the determined physical switch. In this embodiment of the present disclosure, any one of the physical switches may be any one of the physical switches in the bare computer cloud shown in fig. 1, where all the physical switches in the bare computer cloud include at least one configuration port, so that when the management server configures the physical switches, the management server may go away from the dedicated configuration port to enter the physical switch, and meanwhile, may construct a management network implemented based on the physical ports based on the configuration ports of each physical switch, so as to implement link separation between data traffic in the management network and other traffic in the bare computer cloud, and avoid sharing the same link with other traffic in the network, so as to ensure that traffic aiming at configuration behavior of the physical switches is not interfered by overall network load.
Optionally, any bare computer server includes a management port, where the management port is used for the management server to manage the any bare computer server. Similar to the configuration ports on the physical switch, the bare computer server may be any bare computer server in the bare computer cloud shown in fig. 1, and each bare computer server in the bare computer cloud may reserve a management port dedicated to the managed port invoked by the managed server, so as to separate the traffic of the management action from the links of the other network traffic, so as to ensure that the traffic of the management action for the bare computer server is not interfered by the overall network load.
Corresponding to the embodiments of the aforementioned method, the present specification also provides embodiments of an apparatus, an electronic device, and a storage medium.
Fig. 5 is a schematic block diagram of an apparatus according to an exemplary embodiment. Referring to fig. 5, at the hardware level, the device includes a processor 502, an internal bus 504, a network interface 506, a memory 508, and a non-volatile storage 510, although other hardware required for other functions may be included. One or more embodiments of the present description may be implemented in a software-based manner, such as by the processor 502 reading a corresponding computer program from the non-volatile storage 510 into the memory 508 and then running. Of course, in addition to software implementation, one or more embodiments of the present disclosure do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.
As shown in fig. 6, fig. 6 is a block diagram of a traffic forwarding apparatus provided in accordance with an exemplary embodiment of the present specification, which may be applied to an apparatus as shown in fig. 5 to implement a traffic forwarding scheme referred to in the present specification, where the apparatus is applied to a physical switch connected to a bare metal server, may include:
an instruction receiving unit 601, configured to participate in deploying a virtual switch in response to a received virtual switch deployment instruction;
a bare metal association unit 602 configured to determine, among bare metal servers connected to the physical switch, a target bare metal server specified by the virtual switch deployment instruction, and associate the target bare metal server to the virtual switch;
and a traffic forwarding unit 603, configured to forward, when receiving a target traffic for the target bare metal server, the target traffic through the virtual switch.
Optionally, the virtual switch deployment instruction includes a virtual network identifier, and the instruction receiving unit 601 is specifically configured to:
creating virtual edge equipment in a virtual network corresponding to the virtual network identifier;
wherein the virtual switch is implemented based on the virtual network.
Optionally, the virtual switch deployment instruction includes information of a plurality of physical switches; the virtual network comprises virtual edge devices respectively created by the plurality of physical switches and network tunnels maintained between the virtual edge devices.
Optionally, the virtual switch deployment instruction includes mac information of at least one bare computer server and an IP address of a physical switch to which each of the at least one bare computer server is connected, and the apparatus further includes:
a target bare metal determining unit 604 for determining other bare metal servers than the target bare metal server among the at least one bare metal server;
and a routing information binding unit 605, configured to generate routing information according to mac information of the other bare computer servers and IP addresses corresponding to the physical switches connected to the mac information, and bind the routing information to a virtual network forwarding table corresponding to the virtual network.
Optionally, the bare metal association unit 602 is specifically configured to:
and binding the corresponding relation between the mac information of the target bare computer server and the corresponding local port to the mac information of the target bare computer server to a virtual network forwarding table corresponding to the virtual network in the form of routing information.
Optionally, the virtual network forwarding table is a link layer forwarding table.
Optionally, the virtual switch and a bare computer server connected with the virtual switch belong to a virtual private cloud VPC corresponding to an initiator user of the virtual switch deployment instruction.
As shown in fig. 7, fig. 7 is a block diagram of a configuration apparatus of a bare metal server provided in the present specification according to an exemplary embodiment, which may be applied to an apparatus shown in fig. 5 to implement a configuration scheme of a bare metal server related to the present specification, and the apparatus applied to a management server may include:
a request response unit 701 for determining a physical switch connected to a target bare computer server in response to a virtual switch deployment request initiated for the target bare computer server;
an instruction sending unit 702, configured to send a virtual switch deployment instruction to the determined physical switch, so that the determined physical switch participates in deploying a virtual switch, and associate the target bare metal server to the virtual switch, so that the virtual switch is used to forward, for the target traffic received by the determined physical switch and directed to the target bare metal server.
Optionally, any physical switch includes a configuration port, where the configuration port is used to enable the management server to manage any physical switch; the sending the virtual switch deployment instruction to the determined physical switch comprises the following steps:
And sending a virtual switch deployment instruction to the determined physical switch through the configuration port in the determined physical switch.
Correspondingly, the specification also provides a device, which comprises a processor; a memory for storing processor-executable instructions; the processor is configured to implement the traffic forwarding method or the configuration method of the bare computer server provided by all the method embodiments.
Accordingly, the present specification also provides a computer-readable storage medium having stored thereon executable instructions; when the instruction is executed by the processor, the steps of the traffic forwarding method or the configuration method of the bare computer server provided by all the method embodiments are realized.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the modules illustrated as separate components may or may not be physically separate, and the components shown as modules may or may not be physical, i.e., may be located in one place, or may be distributed over a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present description. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments 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 or 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 in one or more embodiments of the present description to describe various information, these 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 one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.
Claims (11)
1. A traffic forwarding method, applied to a physical switch connected to a bare metal server, comprising:
responding to a received virtual switch deployment instruction, and participating in deploying the virtual switch; the virtual switch deployment instruction includes a virtual network identifier, and the participating virtual switch deployment instruction includes: creating virtual edge equipment in a virtual network corresponding to the virtual network identifier; wherein the virtual switch is implemented based on the virtual network;
determining a target bare computer server specified by the virtual switch deployment instruction in bare computer servers connected with the physical switch, and associating the target bare computer server with the virtual switch;
forwarding, by the virtual switch, target traffic for the target bare metal server if the target traffic is received;
The associating the target bare metal server to the virtual switch comprises:
and binding the corresponding relation between the mac information of the target bare computer server and the corresponding local port to the mac information of the target bare computer server to a virtual network forwarding table corresponding to the virtual network in the form of routing information.
2. The method of claim 1, wherein the virtual switch deployment instruction includes information of a plurality of physical switches; the virtual network comprises virtual edge devices respectively created by the plurality of physical switches and network tunnels maintained between the virtual edge devices.
3. The method of claim 2, wherein the virtual switch deployment instruction includes mac information of at least one bare metal server and an IP address of a physical switch to which each is connected, the method further comprising:
determining other bare computer servers except the target bare computer server in the at least one bare computer server;
generating route information according to mac information of the other bare computer servers and IP addresses corresponding to the physical switches connected with the mac information, and binding the route information to a virtual network forwarding table corresponding to the virtual network.
4. The method according to claim 3 or 1, wherein the virtual network forwarding table is a link layer forwarding table.
5. The method of claim 1, wherein the virtual switch and a bare metal server connected to the virtual switch are attributed to a virtual private cloud, VPC, corresponding to an originating user of the virtual switch deployment instruction.
6. A bare metal server configuration method, applied to a management server, comprising:
determining a physical switch connected with a target bare computer server in response to a virtual switch deployment request initiated for the target bare computer server;
sending a virtual switch deployment instruction to the determined physical switch, enabling the determined physical switch to participate in deploying the virtual switch, and associating the target bare computer server to the virtual switch so that the virtual switch is used for forwarding the target traffic received by the determined physical switch and aiming at the target bare computer server;
the virtual switch deployment instruction includes a virtual network identifier, and the participating virtual switch deployment instruction includes: creating virtual edge equipment in a virtual network corresponding to the virtual network identifier; wherein the virtual switch is implemented based on the virtual network;
The associating the target bare metal server to the virtual switch comprises:
and binding the corresponding relation between the mac information of the target bare computer server and the corresponding local port to the mac information of the target bare computer server to a virtual network forwarding table corresponding to the virtual network in the form of routing information.
7. The method of claim 6, wherein any physical switch includes a configuration port, the configuration port being configured to enable the management server to manage the any physical switch; the sending the virtual switch deployment instruction to the determined physical switch comprises the following steps:
and sending a virtual switch deployment instruction to the determined physical switch through the configuration port in the determined physical switch.
8. A traffic forwarding device for use in a physical switch coupled to a bare metal server, comprising:
the instruction receiving unit is used for responding to the received virtual switch deployment instruction and participating in the deployment of the virtual switch; the virtual switch deployment instruction includes a virtual network identifier, and the participating virtual switch deployment instruction includes: creating virtual edge equipment in a virtual network corresponding to the virtual network identifier; wherein the virtual switch is implemented based on the virtual network;
A bare metal association unit configured to determine, among bare metal servers connected to the physical switch, a target bare metal server specified by the virtual switch deployment instruction, and associate the target bare metal server to the virtual switch;
a traffic forwarding unit configured to forward, when receiving a target traffic for the target bare metal server, the target traffic through the virtual switch;
the associating the target bare metal server to the virtual switch comprises:
and binding the corresponding relation between the mac information of the target bare computer server and the corresponding local port to the mac information of the target bare computer server to a virtual network forwarding table corresponding to the virtual network in the form of routing information.
9. A bare metal server configuration apparatus, applied to a management server, comprising:
a request response unit for determining a physical switch connected with a target bare computer server in response to a virtual switch deployment request initiated for the target bare computer server;
the instruction sending unit is used for sending a virtual switch deployment instruction to the determined physical switch, enabling the determined physical switch to participate in deploying the virtual switch, and associating the target bare computer server to the virtual switch so as to be used by the virtual switch for forwarding the target traffic which is received by the determined physical switch and is aimed at the target bare computer server;
The virtual switch deployment instruction includes a virtual network identifier, and the participating virtual switch deployment instruction includes: creating virtual edge equipment in a virtual network corresponding to the virtual network identifier; wherein the virtual switch is implemented based on the virtual network;
the associating the target bare metal server to the virtual switch comprises:
and binding the corresponding relation between the mac information of the target bare computer server and the corresponding local port to the mac information of the target bare computer server to a virtual network forwarding table corresponding to the virtual network in the form of routing information.
10. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to implement the method of any of claims 1-7 by executing the executable instructions.
11. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111454610.5A CN114172853B (en) | 2021-12-01 | 2021-12-01 | Configuration method and device of traffic forwarding and bare computer server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111454610.5A CN114172853B (en) | 2021-12-01 | 2021-12-01 | Configuration method and device of traffic forwarding and bare computer server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114172853A CN114172853A (en) | 2022-03-11 |
| CN114172853B true CN114172853B (en) | 2024-04-16 |
Family
ID=80482112
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111454610.5A Active CN114172853B (en) | 2021-12-01 | 2021-12-01 | Configuration method and device of traffic forwarding and bare computer server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114172853B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114726908A (en) * | 2022-03-23 | 2022-07-08 | 阿里云计算有限公司 | Network communication method and system, electronic device, and computer-readable storage medium |
| CN115225708B (en) * | 2022-07-28 | 2023-08-08 | 天翼云科技有限公司 | Message forwarding method computer equipment and storage medium |
| CN118138552A (en) * | 2022-11-28 | 2024-06-04 | 华为云计算技术有限公司 | Data transmission method and related equipment |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2525532A1 (en) * | 2011-05-19 | 2012-11-21 | Hitachi Ltd. | Method and apparatus of connectivity discovery between network switch and server based on vlan identifiers |
| CN105162674A (en) * | 2015-10-16 | 2015-12-16 | 上海斐讯数据通信技术有限公司 | Method and network card for physical machine to access to virtual network |
| CN106375176A (en) * | 2016-08-29 | 2017-02-01 | 无锡华云数据技术服务有限公司 | Method for accessing physical machine to cloud platform |
| CN107135134A (en) * | 2017-03-29 | 2017-09-05 | 广东网金控股股份有限公司 | Private network cut-in method and system based on virtual switch and SDN technologies |
| WO2020219235A1 (en) * | 2019-04-26 | 2020-10-29 | Microsoft Technology Licensing, Llc | Enabling access to dedicated resources in a virtual network using top of rack switches |
| WO2021000694A1 (en) * | 2019-06-29 | 2021-01-07 | 华为技术有限公司 | Method for deploying services and scheduling apparatus |
| CN112256393A (en) * | 2020-10-22 | 2021-01-22 | 上海云轴信息科技有限公司 | Resource management method and equipment for bare metal server |
| CN112737860A (en) * | 2021-01-06 | 2021-04-30 | 浪潮云信息技术股份公司 | Method for bare metal server VXLAN access and computer readable medium |
| WO2021206790A1 (en) * | 2020-04-06 | 2021-10-14 | Vmware, Inc. | Architecture for stretching logical switches between multiple datacenters |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8923149B2 (en) * | 2012-04-09 | 2014-12-30 | Futurewei Technologies, Inc. | L3 gateway for VXLAN |
| US11102080B2 (en) * | 2019-07-18 | 2021-08-24 | International Business Machines Corporation | Network layer method of configuration of a bare-metal server in a virtual network |
-
2021
- 2021-12-01 CN CN202111454610.5A patent/CN114172853B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2525532A1 (en) * | 2011-05-19 | 2012-11-21 | Hitachi Ltd. | Method and apparatus of connectivity discovery between network switch and server based on vlan identifiers |
| CN105162674A (en) * | 2015-10-16 | 2015-12-16 | 上海斐讯数据通信技术有限公司 | Method and network card for physical machine to access to virtual network |
| CN106375176A (en) * | 2016-08-29 | 2017-02-01 | 无锡华云数据技术服务有限公司 | Method for accessing physical machine to cloud platform |
| CN107135134A (en) * | 2017-03-29 | 2017-09-05 | 广东网金控股股份有限公司 | Private network cut-in method and system based on virtual switch and SDN technologies |
| WO2020219235A1 (en) * | 2019-04-26 | 2020-10-29 | Microsoft Technology Licensing, Llc | Enabling access to dedicated resources in a virtual network using top of rack switches |
| WO2021000694A1 (en) * | 2019-06-29 | 2021-01-07 | 华为技术有限公司 | Method for deploying services and scheduling apparatus |
| WO2021206790A1 (en) * | 2020-04-06 | 2021-10-14 | Vmware, Inc. | Architecture for stretching logical switches between multiple datacenters |
| CN112256393A (en) * | 2020-10-22 | 2021-01-22 | 上海云轴信息科技有限公司 | Resource management method and equipment for bare metal server |
| CN112737860A (en) * | 2021-01-06 | 2021-04-30 | 浪潮云信息技术股份公司 | Method for bare metal server VXLAN access and computer readable medium |
Non-Patent Citations (1)
| Title |
|---|
| VxLAN在云数据中心组网的应用;张届新;傅志仁;吴志明;徐文华;徐海峰;;电信科学(第09期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114172853A (en) | 2022-03-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11265368B2 (en) | Load balancing method, apparatus, and system | |
| CN114172853B (en) | Configuration method and device of traffic forwarding and bare computer server | |
| US11902364B2 (en) | Automatic replacement of computing nodes in a virtual computer network | |
| CN113810230B (en) | Method, device and system for carrying out network configuration on containers in container cluster | |
| CN107547349B (en) | Virtual machine migration method and device | |
| CN107317832B (en) | Message forwarding method and device | |
| CN108718278B (en) | Message transmission method and device | |
| JP2019517168A (en) | Interconnection between physical and virtual networks | |
| US10257086B2 (en) | Source imposition of network routes in computing networks | |
| US10574570B2 (en) | Communication processing method and apparatus | |
| CN111064804B (en) | Network access method and device | |
| CN110213365B (en) | User access request processing method based on user partition and electronic equipment | |
| CN111526223A (en) | Management method of edge service server, service data processing method and device | |
| CN115604272B (en) | Load balancing method, device, system and system establishing method, device and medium | |
| CN113315848B (en) | Access control method, device and equipment | |
| CN104780201A (en) | Data packet processing method and device for use in IPVS (Internet Protocol Virtual Server) cluster | |
| CN118051342A (en) | Method, system and equipment for creating k8s load balance in local area network environment | |
| CN113067824A (en) | Data scheduling method, system, virtual host and computer readable storage medium | |
| CN116055446B (en) | Cross-network message forwarding method, electronic equipment and machine-readable storage medium | |
| CN116208600A (en) | File transfer protocol request processing method, device, equipment and storage medium | |
| CN115834472A (en) | Message processing method, forwarding strategy obtaining method and device | |
| CN116319354B (en) | Network topology updating method based on cloud instance migration | |
| CN115665228B (en) | Cross-node service discovery method and device | |
| CN110740198B (en) | Neighbor table item management method and device, electronic equipment and machine-readable storage medium | |
| JP5780297B2 (en) | Port number identification system, port number identification system control method and control program therefor |
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 |