CN114979076A

CN114979076A - Flat communication network oriented to cross-host container

Info

Publication number: CN114979076A
Application number: CN202210566831.XA
Authority: CN
Inventors: 庄道明; 沈雪良; 宓建栋
Original assignee: Hangzhou Qianjinding Information Technology Co ltd
Current assignee: Zhejiang Wangzhu Information Technology Service Co ltd
Priority date: 2022-05-23
Filing date: 2022-05-23
Publication date: 2022-08-30
Anticipated expiration: 2042-05-23
Also published as: CN114979076B

Abstract

The invention discloses a flat communication network facing a cross-host container, which comprises the following steps: s1: checking whether the IP address field of the network bridge is configured correctly, if so, carrying out the next step, and if not, allocating a sub-network segment; s2: checking whether the iptables forwarding rule is started, if so, clearing the default iptables chain rule, and if not, starting the iptables default forwarding rule first and then clearing the default iptables chain rule; s3: and checking whether the router routing table reaches the routing information of the container address field distributed by the S1, if not, injecting the router into the static routing table, and if so, ending the operation. By providing a flat network environment, the three-layer routing protocol does not need to be repackaged, the unpacking operation in the transmission process is reduced, the resource utilization rate is improved to a great extent, the compatibility of network equipment can be supported, the method is directly realized on the three-layer routing structure, no controller is needed to maintain the node information, and the maintenance is convenient.

Description

Flat communication network oriented to cross-host container

Technical Field

The invention relates to the field of container flattening networks, in particular to a flattening communication network for a cross-host container.

Background

The existing internet technology service architecture design is basically designed in a distributed micro-service architecture, and the design brings obvious advantages in stability, fault tolerance rate, high performance, cooperation and the like. However, in the case of single host deployment, hardware resources are wasted to some extent, so a container technology appears, but in the existing container technology, for example, a do cker can implement interconnection and intercommunication for each container in a single host environment, but interconnection and intercommunication are difficult to implement between containers in each host under the condition of multiple hosts, which brings technical difficulty to the implementation of projects. The necessary breakpoints and direct connection services in the research and development project process of research and development and testing personnel bring great inconvenience. The technical architecture under the registration mechanism is also difficult to implement.

Some existing solutions, such as some OVS network plug-in technologies used after unpacking, can solve a part of problems, the architecture of the existing solutions is also quite complex, a packet forwarding controller center is generally needed, the control center records node information that each destination address of the control center needs to reach, the data packet needs to be encapsulated by an OVS layer protocol before transmitting a three-layer data packet, unpacking operation needs to be performed after the data packet reaches a destination node, and certain consumption is caused to hardware performance consumption. The logic behind such tools is also not very transparent to maintenance personnel, and there is also a certain blind area of knowledge in problem troubleshooting at later maintenance stages. It is also a point that IDC network devices, such as switches and routers, cannot support such plug-ins, and therefore interconnection of containers can only be achieved between the host operating system level.

Disclosure of Invention

The invention aims to overcome the defects of the prior art and provide a flat communication network oriented to a cross-host container.

The purpose of the invention is realized by the following technical scheme: a flat communication network oriented to a cross-host container comprises the following steps:

s1: checking whether the IP address field of the network bridge is configured correctly, if so, carrying out the next step, and if not, allocating a sub-network segment;

s2: checking whether the iptables forwarding rule is started, if so, clearing the default iptables chain rule, and if not, starting the iptables default forwarding rule first and then clearing the default iptables chain rule;

s3: and checking whether the router routing table reaches the routing information of the container address field distributed by the S1, if not, injecting the router into the static routing table, and if so, ending the operation.

Preferably, the step of allocating the subnet segment in S1 is as follows:

a1: comparing the database, distributing a subnet address field of the impractical 24-bit mask and recording;

a2: setting the first host bit IP of the subnet address field as a bridge gateway;

a3: and writing the IP network segment into the container to automatically allocate the DHCP for use when the container is subsequently created.

The invention has the following advantages: the invention provides a flat network environment, does not need to repackage the three-layer routing protocol, reduces the unpacking operation in the transmission process, greatly improves the resource utilization rate, can support the compatibility of network equipment, is directly realized on the three-layer routing structure, does not need any controller to maintain the node information and is convenient to maintain.

Drawings

FIG. 1 is a schematic diagram of a flat communication network state flow;

FIG. 2 is a schematic structural diagram of a basic architecture of a flat communication network;

FIG. 3 is a diagram illustrating the structure of a packet call;

FIG. 4 is a schematic diagram illustrating a micro-service registration mechanism;

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings of the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.

Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.

In addition, the embodiments of the present invention and the features of the embodiments may be combined with each other without conflict.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.

In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc. indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, or orientations or positional relationships that the products of the present invention conventionally lay out when in use, or orientations or positional relationships that are conventionally understood by those skilled in the art, which are merely for convenience of describing the present invention and simplifying the description, but do not indicate or imply that the device or element referred to must have a specific orientation, be constructed in a specific orientation, and be operated, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and the like are used merely to distinguish one description from another, and are not to be construed as indicating or implying relative importance.

In the description of the present invention, it should also be noted that, unless otherwise explicitly specified or limited, the terms "disposed," "mounted," "connected," and "connected" are to be construed broadly and may, for example, be fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.

In this embodiment, as shown in fig. 1, a flat communication network oriented to a cross-host container includes the following steps:

s1: checking whether the IP address field of the network bridge is configured correctly, if so, carrying out the next step, and if not, allocating a sub-network segment; further, the step of allocating the subnet segment in S1 is as follows:

S2: checking whether the iptables forwarding rule is started or not, if so, clearing the default iptables chain rule, and if not, firstly starting the iptables default forwarding rule and then clearing the default iptables chain rule, wherein the main purpose of the step is to realize the function of the router.

S3: and checking whether the router routing table reaches the routing information of the container address field distributed by the S1, if not, injecting the router into a static routing table, and if so, ending the operation. Specifically, as shown in fig. 2, it is necessary to allocate a large segment on a network segment that does not conflict with the address segment of the existing network environment, such as: 10.1.0.0/16, and divide the subnet section to distribute to each host machine to use in this large section, this network segment is the address field in the name space of the network of the docker bridge in each server, wherein each server is equivalent to a router function, its bridge side docks the docker network, eth0 physical network card side docks the outside and builds up, the route of calling the data packet can refer to fig. 3, through offering a flat network environment, do not need to repackage the operation to the protocol of three-layer routing, have reduced the packet and unpack the operation in the transmission process, has promoted the utilization factor of resources, and can support the compatibility of the network equipment, and is equivalent to realizing on the structure of three-layer routing directly, does not need any controller to maintain the node information, easy to maintain; as shown in fig. 4, the service consumer and the service provider of the micro service under the micro service registration mechanism implement the service invocation mechanism by registering themselves to the registration center, and then the registration center informs the service consumer of the information of the service provider to be invoked, and the implementation is performed on the premise that a flat network environment is necessary, otherwise, only a single server system level can be used to deploy the application, which is very resource consuming.

Although the present invention has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that various changes in the embodiments and/or modifications of the invention can be made, and equivalents and modifications of some features of the invention can be made without departing from the spirit and scope of the invention.

Claims

1. A flat communication network oriented to a cross-host container is characterized in that: the method comprises the following steps:

2. The cross-host container oriented flat communication network of claim 1, wherein: the step of allocating the subnet segment in S1 is as follows: