CN111556110B - Automatic adaptation method for different physical service networks of private cloud system - Google Patents
Automatic adaptation method for different physical service networks of private cloud system Download PDFInfo
- Publication number
- CN111556110B CN111556110B CN202010316917.8A CN202010316917A CN111556110B CN 111556110 B CN111556110 B CN 111556110B CN 202010316917 A CN202010316917 A CN 202010316917A CN 111556110 B CN111556110 B CN 111556110B
- Authority
- CN
- China
- Prior art keywords
- network
- physical
- node
- configuration file
- card
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Abstract
The invention provides an automatic adaptation method of different physical service networks for a private cloud system, which comprises the following steps: s1, binding a plurality of physical network cards of the selected computing nodes into a logic network card; s2, updating the network bridge and the network card configuration file of the computing node, and accessing the logic network card to the set physical service network; s3, updating the private cloud system network configuration file stored by the control node according to the updated network bridge and network card configuration file; s4, restarting the computing node, loading the updated network card and network bridge configuration file, restarting the control node, loading the updated private cloud system network configuration file, and updating the virtual network flow forwarding flow table of the computing node; and S5, configuring the virtual machine of the computing node according to the private cloud system network configuration file, and realizing the login of the virtual machine to the set physical service network.
Description
Technical Field
The invention relates to the technical field of communication, in particular to an automatic adaptation method for different physical service networks of a private cloud system.
Background
In the existing private cloud system based on Openstack, the network is divided into a data network, a management network and an external physical service network according to the use of the network. Fig. 1 and fig. 2 are schematic diagrams of two deployment models of interaction between a virtual network and a physical service network based on neutron.
In the deployment model shown in fig. 1, the computing node serves as a VXLAN subnet of the cloud platform, and the computing node is configured to forward network data according to the flow table rule. The computing nodes comprise a virtual machine VM, a security group bridge, a virtual switch br-int1 and a virtual switch br-tun1 inside a host operating system. The virtual switch br-int1 is used for dividing a VXLAN network in a host machine so as to isolate different virtual machines; the virtual switch br-tun1 is used to establish the VETH tunnel needed for VXLAN network transport.
In the deployment model shown in fig. 1, the data transmission flow when the virtual machine VM accesses the extranet is as follows:
data sent by a virtual machine VM is firstly forwarded to a virtual switch br-int1 through a security group bridge; the virtual switch br-int1 adds an internal VLAN ID for the data, converts the internal VLAN ID into an internal transmission tunnel address, and sends the data to the virtual switch br-tun1 through the virtual switch br-int 1; the virtual switch br-tun1 marks the VXLAN packet of the data packet, sends the marked data to the network node through the VXLAN tunnel, and decapsulates the VXLAN at the network node.
The network node comprises a virtual switch br-tun2, a virtual switch br-int2, an external virtual bridge br-ex and a virtual router. The virtual switch br-tun2 is used for establishing a VETH tunnel required by VXLAN network transmission; the virtual switch br-tun2 unpacks the received data, adds an internal tunnel address to the data, converts the internal tunnel address into an internal Vlan ID, and sends the data to the virtual switch br-int 2; the virtual switch br-int2 deletes the VLAN ID in the data, and then sends the data to the corresponding virtual router. And allocating external gateways by namespace established by the router of the virtual router, and randomly selecting one openstack external network from all the external networks by the external gateway to bind the router gateway. SNAT conversion is carried out on data on namespace, and the source address of the data is converted into an external gateway address from an internal network address. The converted data is forwarded to the external virtual bridge br-ex by the virtual router through the virtual switch br-int2, and the external virtual bridge br-ex is bound with one physical network card in the network node, so as to realize data transmission with the physical service network. The data enters the firewall FW through the physical network card, and the firewall FW converts the source address into the firewall address and then enters the external network for forwarding.
In the deployment model shown in fig. 1, the external network backhaul data reception flow is as follows:
the backhaul data of the extranet enters a firewall FW, a destination address in the data is converted into an intranet gateway address, and after DNAT conversion is carried out, the data is forwarded to enter a network node through a physical service network;
the data is broadcasted from the second virtual bridge br-ex to the virtual switch br-int2 at the network node for vlan conversion, and the step is completed by the flow table; and then the data is broadcasted to namespace by the virtual switch br-int2 to carry out three-layer forwarding, the destination address is converted again before routing forwarding, and the address is converted into the address of the internal virtual machine by the external gateway address for addressing forwarding.
In the deployment model shown in fig. 2, the computing nodes include a virtual machine VM, a security group bridge, a virtual switch br-int, and an external virtual bridge br-ex. The data sending process when the virtual machine VM accesses the external network is as follows:
firstly, data of a virtual machine VM enters a virtual switch br-int through two-layer forwarding, and then is continuously broadcasted to an external virtual bridge br-ex;
after the data arrives at the external virtual bridge br-ex, vlan conversion is carried out according to the intranet vlan tag carried by the message, and the vlan is converted into a vlan identified by an external physical service network;
and then the data reaches a gateway of the physical service network, the source IP is converted into a firewall IP, and then the data enters a public network for forwarding.
In the deployment model shown in fig. 2, the outer network backhaul data reception flow is as follows:
the external network backhaul flow carries out destination address conversion on a firewall, and after the destination address conversion is converted into an external network IP bound by a virtual machine VM, three-layer routing forwarding is carried out;
the backhaul data is forwarded to an external virtual bridge br-ex through a physical service network layer two, and the external virtual bridge br-ex broadcasts back to a virtual switch br-int;
the virtual switch br-int converts the vlan identified by the external network into the vlan identified by the internal network through vlan conversion, and performs traffic broadcast forwarding, thereby forwarding to the virtual machine VM through the second layer.
However, the deployment model in the prior art is deployed only for a single physical service network scenario. As shown in fig. 3, the deployment model of fig. 3 includes a control node, a computing node, and a network node. The control node manages the computing node and the network node through a management network. As shown in fig. 3, the computing nodes and the external virtual bridges br-ex1 and br-ex2 of the network nodes in the private cloud system can only access the first physical service network and cannot establish communication connection with the second physical service network. In actual use, the cloud system is often required to be accessed to different physical service networks to communicate with the different physical service networks.
Disclosure of Invention
The invention aims to provide an automatic adaptation method for different physical service networks of a private cloud system. By updating the computing node, the network card configuration file and the network bridge configuration file in the network node and the private cloud system configuration file in the control node, the virtual machines of the computing node and the network node are connected with the corresponding logic network cards through the newly added network bridge and are connected with the external physical service network through the corresponding logic network cards. The computing nodes and the network nodes are connected with different external physical service networks, the communication redundancy of the virtual machines of the computing nodes and the network nodes and the external physical service networks is realized through the bound logic network cards, and the stability of communication is ensured.
In order to achieve the above object, the present invention provides an automated adaptation method for different physical service networks of a private cloud system, where the private cloud system includes a control node and a plurality of computing nodes, and the computing nodes are connected to an external bridge through a first virtual switch, and the automated adaptation method includes:
s1, acquiring all physical network card information of the computing node, and selecting a plurality of physical network cards to be bound as corresponding logical network cards; physical network cards in one logic network card belong to the same computing node, and the physical network cards do not belong to different logic network cards;
s2, updating the network bridge and the network card configuration file of the computing node, and accessing the logic network card of the computing node to the set physical service network;
s3, updating the private cloud system network configuration file stored by the control node according to the updated network bridge and network card configuration file of the computing node;
s4, restarting a control node and a computing node, wherein the computing node loads the updated network card and network bridge configuration file, and the control node loads the updated private cloud system network configuration file; updating a virtual network flow forwarding flow table of the computing node to ensure that all virtual network flows of the private cloud system are forwarded normally;
s5, configuring the virtual machine of the computing node according to the private cloud system network configuration file, and enabling the virtual machine to log in the set physical service network.
Step S1 specifically includes:
s11, acquiring information of all physical network cards of the computing node, wherein the information of the physical network cards comprises the model, the bandwidth, the IP address and the MAC address of the network cards and whether physical service networks are bound or not;
s12, selecting a plurality of physical network cards of the computing nodes, wherein the physical network cards have the same bandwidth, the same brand and the same model;
s13, inputting redundant configuration information of the logical network card to the computing node, where the redundant configuration information includes: the method comprises the following steps that the name of a physical network card to be bound, the name of a logic network card, and an ip address, a gateway address and a mask address which are required to be configured by the logic network card are obtained;
s14, checking the states of the physical network cards selected from the computing nodes, and if all the selected physical network cards are normal, accessing the selected physical network cards into the set physical service network through the corresponding network cables; adding a corresponding bond configuration file for the computing node according to the redundant configuration information of the computing node logic network card; and binding the physical network card selected from the computing nodes into a corresponding logic network card according to the corresponding bond configuration file.
Step S2 specifically includes:
s21, adding a corresponding first pair of external bridges for the logic network card of the computing node; the first pair of external network bridges are connected with the first virtual switch in the south direction, and are connected with the corresponding logic network cards in the north direction; connecting a physical network card in the logic network card with a set physical service network;
s22, adding configuration information of a first pair of external bridges into a bridge configuration file of the computing node; the configuration information for the first pair of foreign bridges includes: ip address, gateway address, mask address of the first pair of external bridges;
s23, changing the network card type of the physical network card selected from the computing nodes into an OVS interface; and updating the network card configuration file of the computing node according to the network card type after the physical network card is selected and modified, the corresponding redundant configuration information and the name of the first external network bridge.
Step S3 specifically includes:
s31, adding the configuration information of the first external bridge in the private cloud system network configuration file stored by the control node;
and S32, adding a first external virtual network corresponding to the first pair of external bridges at the control node, and setting a vlan id range of the first external virtual network.
Step S5 specifically includes: selecting a virtual machine of the computing node, and configuring the name of an external virtual network which can be accessed by the virtual machine as the name of a first external virtual network.
The present invention further discloses another technical solution, in which the private cloud system further includes a plurality of network nodes, the network nodes are connected to an external bridge through a second virtual switch, and the automated adaptation method further includes, in addition to steps S1 to S5, the steps of:
s6, acquiring all physical network card information of the network node, and selecting a plurality of physical network cards to be bound as corresponding logical network cards; physical network cards in one logic network card belong to the same network node, and the physical network cards do not belong to different logic network cards;
s7, updating the network bridge and the network card configuration file of the network node, and accessing the logic network card of the network node to the set physical service network;
s8, updating the private cloud system network configuration file stored by the control node according to the updated network bridge and network card configuration file of the network node;
s9, restarting a control node and a network node, wherein the network node loads the updated network card and the updated network bridge configuration file, and the control node loads the updated private cloud system network configuration file; updating a virtual network flow forwarding flow table of the network node to ensure that all virtual network flows of the private cloud system are forwarded normally;
s10, configuring the router of the network node according to the private cloud system network configuration file, and realizing the connection of the network node with the set physical service network through the router 。
Step S6 specifically includes the steps of:
s61, acquiring information of all physical network cards of the network nodes, wherein the information of the physical network cards comprises the model, the bandwidth, the IP address and the MAC address of the network cards and whether physical service networks are bound or not;
s62, selecting a plurality of physical network cards of the network nodes, wherein the physical network cards have the same bandwidth, the same brand and the same model;
s63, inputting redundant configuration information of the logical network card to the network node, where the redundant configuration information includes: the method comprises the following steps that the name of a physical network card to be bound, the name of a logic network card, and an ip address, a gateway address and a mask address which are required to be configured by the logic network card are obtained;
s64, checking the states of the physical network cards selected from the network nodes, and if the states of all the selected physical network cards are normal, accessing the selected physical network cards into the set physical service network through the corresponding network cables; according to the redundant configuration information of the network node logic network card, newly adding a corresponding bond configuration file for the network node; and binding the physical network card selected from the network nodes into the corresponding logical network card according to the corresponding bond configuration file.
Step S7 specifically includes:
s71, adding a second external network bridge corresponding to the logic network card of the network node; the second pair of external network bridges are connected with the second virtual switch in the south direction and connected with the corresponding logic network cards in the north direction; connecting a physical network card in the logic network card with a set physical service network;
s72, adding configuration information of a second pair of external bridges into the bridge configuration file of the network node; the configuration information for the second pair of external bridges includes: ip address, gateway address, mask address of the second pair of external bridges;
s73, changing the network card type of the physical network card selected from the network nodes into an OVS interface; and updating the network card configuration file of the network node according to the network card type modified by the selected physical network card, the corresponding redundant configuration information and the name of the second external network bridge.
Step S8 specifically includes:
s81, adding the configuration information of the second external network bridge in the private cloud system network configuration file stored by the control node;
and S82, adding a second external virtual network corresponding to the second pair of external bridges at the control node, and setting a vlan id range of the second external virtual network.
Preferably, the automatic adaptation method is realized by the computing node and the network node through a rest-api port.
Compared with the prior art, the invention has the advantages that:
1) the invention binds different physical network cards of the computing nodes and network nodes deployed in the private cloud system into corresponding logical network cards, and realizes the connection of the logical network cards with corresponding physical service networks through the corresponding external network bridges by newly adding the corresponding external network bridges to the different logical network cards. Therefore, the connection of the computing node and the network node to different physical service networks is realized, and the automatic adaptation of the private cloud system to different physical service networks is realized;
2) communication redundancy, bandwidth expansion and load balance of the computing nodes, the network nodes and the physical service network are realized in a binding mode of the network card, and the reliability of communication between the virtual machines of the computing nodes and the network nodes and the corresponding physical service network is effectively guaranteed;
3) the method is suitable for the private cloud system comprising the network node and not comprising the network node.
Drawings
In order to more clearly illustrate the technical solution of the present invention, the drawings used in the description will be briefly introduced, and it is obvious that the drawings in the following description are an embodiment of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts according to the drawings:
FIG. 1 is a schematic diagram of a first deployment model of a prior art private cloud system interacting with a physical business network;
FIG. 2 is a diagram of a second prior art deployment model of private cloud system interaction with a physical services network;
FIG. 3 is a diagram illustrating a prior art private cloud system connected to a physical service network;
fig. 4 is a schematic diagram illustrating binding of a network card of a computing node as a logical network card according to a first embodiment of the present invention;
fig. 5 is a schematic diagram illustrating an external virtual network bridge established for a logical network card of a compute node according to a first embodiment of the present invention;
fig. 6 is a schematic diagram of a private cloud system connecting two physical service networks according to a second embodiment of the present invention;
FIG. 7 is a flow chart of a method for automated adaptation of different physical service networks for private cloud systems in accordance with the present invention;
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
The invention provides a method for automatically adapting different physical service networks of a private cloud system. As shown in fig. 7, the automatic adaptation method includes the steps of:
s1, acquiring information of all physical network cards of the computing nodes, selecting a plurality of physical network cards and binding the physical network cards into corresponding logical network cards, wherein the physical network cards in one logical network card belong to the same computing node, and the physical network cards do not belong to different logical network cards.
As shown in fig. 4, in the first embodiment of the present invention, the computing nodes include three physical network cards eth0, eth1, eth2, and the physical network cards eth0, eth1 are bound as the logical network card bond0, which specifically includes the following steps:
obtaining the model, bandwidth, IP address and MAC address of eth0, eth1 and eth2, and determining whether a physical service network is bound; selecting eth0 and eth1 with the same bandwidth, brand and model for binding;
inputting redundant configuration information of a logical network card bond0 to a computing node, wherein the redundant configuration information comprises names of physical network cards eth0 and eth1, a name of a logical network card bond0, and an ip address, a gateway address and a mask address which need to be configured by the logical network card bond 0;
s14, checking the states of the physical network cards eth0 and eth1, wherein the state of the physical network card means whether the physical network card can work normally; if all the selected physical network cards are in normal states, accessing the physical network cards eth0 and eth1 to the set physical service network through the corresponding network cables; newly adding a corresponding bond configuration file according to the redundant configuration information of the logical network card bond 0; and binding the physical network cards eth0 and eth1 into corresponding logical network card bond0 according to the bond configuration file. The computing node also feeds back whether the selected physical network card is successfully bound as the logic network card to the client of the private cloud system, and displays the binding result visually through the client.
The compute node completes steps S11 through S14 through the rest-api port.
S2, updating the network bridge and the network card configuration file of the computing node, and accessing the logic network card to the set physical service network;
in the first embodiment of the present invention, as shown in fig. 5, the computing node is connected to the external bridge through the first virtual switch br-int. The physical network card eth2 of the computing node is connected to the virtual switch br-int through the external bridge br-ex 2. On the basis of the original virtual network of the cloud system, a new virtual network is established for the computing node, and the logical network card bond0 is accessed to a set physical service network.
In the first embodiment of the present invention, the step S2 specifically includes:
s21, adding a first pair of external network bridges br-ex1 corresponding to the logical network card bond0 for the computing node, wherein the first pair of external network bridges br-ex1 are connected with the first virtual switch br-int in the south direction, are connected with the logical network card bond0 in the north direction, and are connected with set physical service networks through physical network cards eth0 and eth 1;
s22, adding the configuration information of the first pair of foreign bridges br-ex1 to the bridge configuration file of the compute node, which specifically includes: ip address, gateway address, mask address of the first pair of foreign bridges br-ex 1.
S23, changing the network card types of the physical network cards eth0 and eth1 into OVS interfaces; and updating the network card configuration file of the computing node according to the network card types modified by the physical network cards eth0 and eth1, the redundant configuration information of the logical network card bond0 and the name of the first pair of external network bridges br-ex 1.
S3, updating the private cloud system network configuration file stored by the control node according to the updated network bridge and network card configuration file of the computing node;
in a first embodiment of the present invention, the step S3 specifically includes:
s31, adding the configuration information of the first pair of foreign bridges br-ex1 in the private cloud system network configuration file stored by the control node;
and S32, adding a first external virtual network (external network 1) corresponding to the first pair of external network bridges br-ex1 at the control node, and setting a vlan range of the first external virtual network (external network 1).
S4, restarting a computing node and a control node, wherein the computing node loads the updated network card and network bridge configuration file, and the control node loads the updated private cloud system network configuration file; updating a virtual network traffic forwarding flow table of a computing node to ensure that all virtual network traffic of a private cloud system is forwarded normally (this is the prior art);
s5, selecting a virtual machine of the computing node, and configuring the name of the external virtual network which can be accessed by the virtual machine to be the name of the first external virtual network according to the private cloud system network configuration file, wherein the name of the first external virtual network is the name of the external virtual network 1. The virtual machine logs in the set physical service network through the logical network card bond 0.
Example two
In other cases, the private cloud system also contains several network nodes. As shown in fig. 6, in the second embodiment of the present invention, the private cloud system includes a computing node and a network node. In the second embodiment, the network nodes include a physical network card eth10, a logical network card bond11, and a bond 12. And respectively establishing a second pair of external bridges br-ex11 and br-ex12 connected with a second virtual switch br-int1 for the logical network card bond11 and the bond12, and respectively accessing br-ex11 and br-ex12 to the first physical service network and the second physical service network. The network bridge and the network card configuration file of the network node are updated according to the logical network card bond11 and bond12, and the private cloud system network configuration file stored by the control node and the virtual network traffic forwarding flow table of the network node are updated according to the network bridge and the network card configuration file (this is the prior art). The router (not shown in fig. 6) of the network node is configured according to the private cloud system network configuration file, so that the traffic of the network node enters the first and second physical service networks (this is prior art) through the router by the logical network card bond11 and bond12, respectively.
In the second embodiment, the computing nodes include a physical network card eth20, a logical network card bond21, and a bond 22. And respectively establishing a first pair of external bridges br-ex21 and br-ex22 connected with the virtual switch br-int2 for the logical network card bond21 and the bond22, and respectively accessing br-ex21 and br-ex22 to the first physical service network and the second physical service network. In this embodiment, the compute node includes first to third virtual machines. The first virtual machine is configured to access a first physical service network through a logical network card bond 11; the second virtual machine is configured such that its traffic can access the second physical service network through the logical network card bond 12.
In this embodiment, the VETH tunnel required for VXLAN network transport is established between the virtual switch br-tun1 of the network node and the virtual switch br-tun2 of the compute node. The third virtual machine is configured to access the data network through the virtual switch br-tun2, flow into the network node through the physical network card eth10 of the network node, and access the first physical service network through the network node virtual switch br-int and the second pair of external bridges br-ex11 of the network node.
That is, the compute node and the network node are not in a strongly bound relationship. The flow of the computing node virtual machine can directly flow into the first and second physical service networks, and can also enter the first and second physical service networks through forwarding of the network node.
While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (9)
1. An automated adaptation method for different physical service networks of a private cloud system, the private cloud system comprising a control node and a plurality of computing nodes, the computing nodes being connected to external bridges thereof through a first virtual switch, the automated adaptation method comprising the steps of:
s1, acquiring all physical network card information of the computing node, and selecting a plurality of physical network cards to be bound as corresponding logical network cards; physical network cards in one logic network card belong to the same computing node, and the physical network cards do not belong to different logic network cards;
s2, updating the network bridge and network card configuration file of the computing node, and accessing the logic network card of the computing node to the set physical service network;
s3, updating the private cloud system network configuration file stored by the control node according to the updated network bridge and network card configuration file of the computing node;
s4, restarting a control node and a computing node, wherein the computing node loads the updated network card and the updated network bridge configuration file, and the control node loads the updated private cloud system network configuration file; updating a virtual network flow forwarding flow table of the computing node to ensure that all virtual network flows of the private cloud system are forwarded normally;
s5, configuring the virtual machine of the computing node according to the private cloud system network configuration file, and enabling the virtual machine to log in the set physical service network.
2. The method according to claim 1, wherein the step S1 specifically includes:
s11, acquiring information of all physical network cards of the computing node, wherein the information of the physical network cards comprises the model, the bandwidth, the IP address and the MAC address of the network cards and whether physical service networks are bound or not;
s12, selecting a plurality of physical network cards with the same bandwidth, the same brand and the same model of the computing node;
s13, inputting redundant configuration information of the logical network card to the computing node, where the redundant configuration information includes: the method comprises the following steps that the name of a physical network card to be bound, the name of a logic network card, and an ip address, a gateway address and a mask address which are required to be configured by the logic network card are obtained;
s14, checking the states of the physical network cards selected from the computing nodes, and if all the selected physical network cards are normal, accessing the selected physical network cards into the set physical service network through the corresponding network cables; adding a corresponding bond configuration file for the computing node according to the redundant configuration information of the computing node logic network card; and binding the physical network card selected from the computing nodes into a corresponding logic network card according to the corresponding bond configuration file.
3. The method according to claim 2, wherein the step S2 specifically includes:
s21, adding a corresponding first pair of external bridges for the logic network card of the computing node; the first pair of external network bridges are connected with the first virtual switch in the south direction, and are connected with the corresponding logic network cards in the north direction; connecting a physical network card in the logic network card with a set physical service network;
s22, adding configuration information of a first pair of external bridges into a bridge configuration file of the computing node; the configuration information for the first pair of foreign bridges includes: ip address, gateway address, mask address of the first pair of external bridges;
s23, changing the network card type of the physical network card selected from the computing nodes into an OVS interface; and updating the network card configuration file of the computing node according to the network card type after the physical network card is selected and modified, the corresponding redundant configuration information and the name of the first external network bridge.
4. The method according to claim 3, wherein the step S3 specifically includes:
s31, adding the configuration information of the first external bridge in the private cloud system network configuration file stored by the control node;
and S32, newly adding a first external virtual network corresponding to the first pair of external bridges at the control node, and setting a vlan id range of the first external virtual network.
5. The method according to claim 4, wherein the step S5 specifically includes: selecting a virtual machine of the computing node, and configuring the name of an external virtual network which can be accessed by the virtual machine as the name of a first external virtual network.
6. The method of claim 1, wherein the private cloud system further comprises a plurality of network nodes, the network nodes being connected to external bridges through a second virtual switch, the method further comprising the steps of:
s6, acquiring all physical network card information of the network node, and selecting a plurality of physical network cards to bind as corresponding logical network cards; physical network cards in one logic network card belong to the same network node, and the physical network cards do not belong to different logic network cards;
s7, updating the network bridge and network card configuration file of the network node, and accessing the logic network card of the network node to the set physical service network;
s8, updating the private cloud system network configuration file stored by the control node according to the updated network bridge and network card configuration file of the network node;
s9, restarting a control node and a network node, wherein the network node loads the updated network card and the updated network bridge configuration file, and the control node loads the updated private cloud system network configuration file; updating a virtual network flow forwarding flow table of the network node to ensure that all virtual network flows of the private cloud system are forwarded normally;
s10, configuring the router of the network node according to the private cloud system network configuration file, and realizing the connection of the network node with the set physical service network through the router 。
7. The method according to claim 6, wherein the step S6 specifically includes:
s61, acquiring information of all physical network cards of the network nodes, wherein the information of the physical network cards comprises the model, the bandwidth, the IP address and the MAC address of the network cards and whether physical service networks are bound or not;
s62, selecting a plurality of physical network cards with the same bandwidth, the same brand and the same model of network nodes;
s63, inputting redundant configuration information of the logical network card to the network node, where the redundant configuration information includes: the method comprises the following steps that the name of a physical network card to be bound, the name of a logic network card, and an ip address, a gateway address and a mask address which are required to be configured by the logic network card are obtained;
s64, checking the states of the physical network cards selected from the network nodes, and if the states of all the selected physical network cards are normal, accessing the selected physical network cards into the set physical service network through the corresponding network cables; according to the redundant configuration information of the network node logic network card, newly adding a corresponding bond configuration file for the network node; and binding the physical network card selected from the network nodes into the corresponding logical network card according to the corresponding bond configuration file.
8. The method according to claim 7, wherein the step S7 specifically includes:
s71, adding a corresponding second external network bridge for the logic network card of the network node; the second pair of external network bridges are connected with the second virtual switch in the south direction and connected with the corresponding logic network cards in the north direction; connecting a physical network card in the logic network card with a set physical service network;
s72, adding configuration information of a second pair of external network bridges into the network bridge configuration file of the network node; the configuration information for the second pair of foreign bridges includes: ip address, gateway address, mask address of the second pair of external bridges;
s73, changing the network card type of the physical network card selected from the network nodes into an OVS interface; and updating the network card configuration file of the network node according to the network card type after the physical network card is selected and modified, the corresponding redundant configuration information and the name of the second external network bridge.
9. The method according to claim 8, wherein the step S8 specifically includes:
s81, adding the configuration information of the second external bridge in the private cloud system network configuration file stored by the control node;
and S82, adding a second external virtual network corresponding to the second pair of external bridges at the control node, and setting a vlan id range of the second external virtual network.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010316917.8A CN111556110B (en) | 2020-04-21 | 2020-04-21 | Automatic adaptation method for different physical service networks of private cloud system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010316917.8A CN111556110B (en) | 2020-04-21 | 2020-04-21 | Automatic adaptation method for different physical service networks of private cloud system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111556110A CN111556110A (en) | 2020-08-18 |
| CN111556110B true CN111556110B (en) | 2022-09-06 |
Family
ID=72007508
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010316917.8A Active CN111556110B (en) | 2020-04-21 | 2020-04-21 | Automatic adaptation method for different physical service networks of private cloud system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111556110B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112565357B (en) * | 2020-11-25 | 2023-03-24 | 中国银联股份有限公司 | Method, device and storage medium for connecting service virtual machine and object storage system |
| CN112787913B (en) * | 2021-01-26 | 2023-03-31 | 北京百度网讯科技有限公司 | Intelligent network card assembly, physical machine, cloud service system and message sending method |
| CN112822060B (en) * | 2021-02-22 | 2022-11-22 | 优刻得科技股份有限公司 | Host network construction method, device, system, medium and host |
| CN114006909B (en) * | 2021-11-11 | 2023-05-26 | 四川中电启明星信息技术有限公司 | Method and system for point-to-point unidirectional dynamic private line connection between private cloud tenants |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103139039A (en) * | 2013-02-25 | 2013-06-05 | 汉柏科技有限公司 | Virtual network capable of achieving flow isolation control and construction method |
| CN103634225A (en) * | 2013-12-18 | 2014-03-12 | 武汉朋客云计算有限公司 | Service bandwidth expansion method in cloud computing network virtualization |
| CN103731514A (en) * | 2013-12-29 | 2014-04-16 | 国云科技股份有限公司 | Virtual network management method |
| CN105245504A (en) * | 2015-09-10 | 2016-01-13 | 北京汉柏科技有限公司 | North-south flow safety protection system in cloud computing network |
| CN106375176A (en) * | 2016-08-29 | 2017-02-01 | 无锡华云数据技术服务有限公司 | Method for accessing physical machine to cloud platform |
| CN106612225A (en) * | 2016-12-12 | 2017-05-03 | 武汉烽火信息集成技术有限公司 | Openstack based agent deployment system and method |
| CN107301083A (en) * | 2017-06-16 | 2017-10-27 | 郑州云海信息技术有限公司 | One kind creates OpenStack virtual machines method and OpenStack dummy machine systems |
| CN107547278A (en) * | 2017-09-05 | 2018-01-05 | 郑州云海信息技术有限公司 | A kind of device and method for docking OpenStack with enterprise virtual environment |
| CN108985397A (en) * | 2018-06-15 | 2018-12-11 | 北京信安世纪科技股份有限公司 | A kind of method, apparatus and computer storage medium for inquiring Bond information |
| CN109088768A (en) * | 2018-08-17 | 2018-12-25 | 郑州云海信息技术有限公司 | A kind of method and device of automatic configuration Linux network interface card bonding |
| CN109120494A (en) * | 2018-08-28 | 2019-01-01 | 无锡华云数据技术服务有限公司 | The method of physical machine is accessed in cloud computing system |
| CN109547233A (en) * | 2018-10-10 | 2019-03-29 | 华为技术有限公司 | A kind of method, apparatus and server of the configuration of server network interface |
| CN110838964A (en) * | 2018-08-16 | 2020-02-25 | 上海仪电（集团）有限公司中央研究院 | Network docking system for virtual network and physical network |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4755548B2 (en) * | 2006-08-01 | 2011-08-24 | 株式会社日立製作所 | Operation management method, operation management program, operation management system, and operation management apparatus |
-
2020
- 2020-04-21 CN CN202010316917.8A patent/CN111556110B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103139039A (en) * | 2013-02-25 | 2013-06-05 | 汉柏科技有限公司 | Virtual network capable of achieving flow isolation control and construction method |
| CN103634225A (en) * | 2013-12-18 | 2014-03-12 | 武汉朋客云计算有限公司 | Service bandwidth expansion method in cloud computing network virtualization |
| CN103731514A (en) * | 2013-12-29 | 2014-04-16 | 国云科技股份有限公司 | Virtual network management method |
| CN105245504A (en) * | 2015-09-10 | 2016-01-13 | 北京汉柏科技有限公司 | North-south flow safety protection system in cloud computing network |
| CN106375176A (en) * | 2016-08-29 | 2017-02-01 | 无锡华云数据技术服务有限公司 | Method for accessing physical machine to cloud platform |
| CN106612225A (en) * | 2016-12-12 | 2017-05-03 | 武汉烽火信息集成技术有限公司 | Openstack based agent deployment system and method |
| CN107301083A (en) * | 2017-06-16 | 2017-10-27 | 郑州云海信息技术有限公司 | One kind creates OpenStack virtual machines method and OpenStack dummy machine systems |
| CN107547278A (en) * | 2017-09-05 | 2018-01-05 | 郑州云海信息技术有限公司 | A kind of device and method for docking OpenStack with enterprise virtual environment |
| CN108985397A (en) * | 2018-06-15 | 2018-12-11 | 北京信安世纪科技股份有限公司 | A kind of method, apparatus and computer storage medium for inquiring Bond information |
| CN110838964A (en) * | 2018-08-16 | 2020-02-25 | 上海仪电（集团）有限公司中央研究院 | Network docking system for virtual network and physical network |
| CN109088768A (en) * | 2018-08-17 | 2018-12-25 | 郑州云海信息技术有限公司 | A kind of method and device of automatic configuration Linux network interface card bonding |
| CN109120494A (en) * | 2018-08-28 | 2019-01-01 | 无锡华云数据技术服务有限公司 | The method of physical machine is accessed in cloud computing system |
| CN109547233A (en) * | 2018-10-10 | 2019-03-29 | 华为技术有限公司 | A kind of method, apparatus and server of the configuration of server network interface |
Non-Patent Citations (1)
| Title |
|---|
| 多网卡绑定技术在服务器系统中的应用;唐国军;《计算机光盘软件与应用》;20130115(第02期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111556110A (en) | 2020-08-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111556110B (en) | Automatic adaptation method for different physical service networks of private cloud system | |
| CN106656719B (en) | Inter-cloud communication method and related equipment, inter-cloud communication configuration method and related equipment | |
| EP2832053B1 (en) | L3 gateway for vxlan | |
| US8484353B1 (en) | Resource placement templates for virtual networks | |
| CN103997414B (en) | Generate method and the network control unit of configuration information | |
| CN111698338B (en) | Data transmission method and computer system | |
| CN111092801B (en) | Data transmission method and device | |
| CN106685787B (en) | PowerVM (virtual machine) virtualized network management method and device based on OpenStack | |
| CN107733795B (en) | Ethernet virtual private network EVPN and public network intercommunication method and device | |
| CN116158063A (en) | Multi-edge Ethernet channel (MEEC) creation and management | |
| CN107659484B (en) | Method, device and system for accessing VXLAN network from VLAN network | |
| EP4016928A1 (en) | Layer 2 leased line network system, configuration method, and device | |
| CN107579898B (en) | Method and device for interconnection communication among multiple containers | |
| CN110474829B (en) | Method and device for transmitting message | |
| WO2023165137A1 (en) | Cross-cluster network communication system and method | |
| US20230345273A1 (en) | Fault processing method, control plane network element, steering decision-making network element, and related device | |
| CN112385194B (en) | State packet transmission between remote networks | |
| CN115150224A (en) | Inter-cluster network two-layer communication method, device, equipment and storage medium | |
| CN112929284A (en) | ND message identification method and system under IPv6VXLAN scene | |
| CN113254148A (en) | Virtual machine migration method and cloud management platform | |
| CN113364660A (en) | Data packet processing method and device in LVS load balancing | |
| CN114629844B (en) | Message forwarding method and device and electronic equipment | |
| CN112671811B (en) | Network access method and equipment | |
| CN113472625B (en) | Transparent bridging method, system, equipment and storage medium based on mobile internet | |
| CN114866467A (en) | Cluster communication method, device, system, equipment and readable storage medium |
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 |