CN113645069B - Cluster data processing method and cluster - Google Patents
Cluster data processing method and cluster Download PDFInfo
- Publication number
- CN113645069B CN113645069B CN202110902526.9A CN202110902526A CN113645069B CN 113645069 B CN113645069 B CN 113645069B CN 202110902526 A CN202110902526 A CN 202110902526A CN 113645069 B CN113645069 B CN 113645069B
- Authority
- CN
- China
- Prior art keywords
- signaling
- cluster
- container
- routing information
- slave node
- 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
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
- H04L41/0253—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using browsers or web-pages for accessing management information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0889—Techniques to speed-up the configuration process
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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
Abstract
The application provides a cluster data processing method, which comprises the following steps: a management container in a cluster main node receives a first signaling; the management container sends the first signaling to other containers in a slave node or a master node in the cluster based on the routing information carried by the first signaling; the management container manages the cluster master node and the routing information of the container included by the cluster master node, and/or the management container manages the cluster slave node and the routing information of the container included by the cluster slave node; the application provides a cluster, and the cluster data processing method and the cluster provided by the application can improve the efficiency of data processing in the cluster.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a cluster data processing method and a cluster.
Background
In the related technology, the sending or receiving of data in the cluster can be realized only by manually configuring a kernel interface and then adding a configuration script; different interfaces need to be configured independently, the use is complex, and the efficiency of data transmission or reception is low; therefore, how to improve the efficiency of data processing in the cluster needs to be solved urgently.
Disclosure of Invention
The present application provides a cluster data processing method and a cluster, so as to at least solve the above technical problems in the prior art.
One aspect of the present application provides a cluster processing method, including:
a management container in a cluster main node receives a first signaling;
the management container sends the first signaling to other containers in slave nodes or master nodes in the cluster based on the routing information carried by the first signaling;
the management container manages the cluster master node and the routing information of the container included in the cluster master node, and/or the management container manages the cluster slave node and the routing information of the container included in the cluster slave node.
In the above scheme, the first signaling carries routing information of a corresponding node in a cluster;
and the management container sends the first signaling to a corresponding slave node based on the routing information carried by the first signaling.
In the above solution, before the management container in the cluster receives the first signaling, the method further includes:
a receiving container in the cluster main node receives a first signaling sent by terminal equipment;
determining routing information of the first signaling based on keywords in the first signaling, and adding the routing information to the first signaling;
and the receiving container sends the first signaling added with the routing information to the management container.
In the above solution, before the management container in the cluster receives the first message, the method further includes:
a proxy container in the cluster master node receives a first signaling;
determining routing information of the first signaling based on keywords in the first signaling, and adding the routing information to the first signaling;
and the agent container sends the first signaling added with the routing information to the management container.
In the above solution, before the management container in the cluster receives the first signaling, the method further includes:
a control container included by the cluster master node receives a second signaling;
the control container configuring the first signaling and routing information of the first signaling based on the second signaling;
the control container sends a first signaling added with the routing information to the management container;
wherein the first signaling carries an operation instruction for a container included in a slave node.
In the above solution, the routing information includes at least one of the following: an internet protocol address of a slave node receiving the first signaling, a subnet mask of the slave node receiving the first signaling, an IP address of a first container receiving the first signaling, a first interface name receiving the first signaling, and a next routing address.
In the foregoing solution, the method further includes:
receiving the first signaling from a routing interface of a corresponding slave node;
and sending the first signaling to a corresponding container based on the routing information included in the first signaling.
In the foregoing solution, the first signaling includes at least one of:
service configuration information, network configuration information, and container operation information.
In the above scheme, the method further comprises:
the management container receives a third signaling sent by a cluster slave node, wherein the third signaling carries routing information for receiving the third signaling;
and the management container sends the third signaling to one of a receiving container, a proxy container or a control container of the cluster main node based on the routing information carried by the third signaling.
A second aspect of the present application provides a cluster, the cluster comprising:
a management container for receiving a first signaling; based on the routing information carried by the first signaling, sending the first signaling to other containers in the slave nodes or master nodes in the cluster;
the management container manages the cluster master node and the routing information of the container included in the cluster master node, and/or the management container manages the cluster slave node and the routing information of the container included in the cluster slave node.
According to the cluster data processing method provided by the embodiment of the application, a management container in a cluster main node receives a first signaling; the management container sends the first signaling to other containers in a slave node or a master node in the cluster based on the routing information carried by the first signaling; the management container manages the cluster master node and the routing information of the container included in the cluster master node, and/or the management container manages the cluster slave node and the routing information of the container included in the cluster slave node, so that the efficiency of data processing in a cluster can be improved.
Drawings
Fig. 1 shows a first optional flowchart of a cluster data processing method provided in an embodiment of the present application;
fig. 2 shows a second optional flowchart of the cluster data processing method according to the embodiment of the present application;
fig. 3 shows a third alternative flowchart of a cluster data processing method provided in the embodiment of the present application;
fig. 4 shows a fourth optional flowchart of the cluster data processing method according to the embodiment of the present application;
fig. 5 shows a fifth alternative flowchart of a cluster data processing method according to an embodiment of the present application;
fig. 6 is a schematic diagram illustrating an alternative structure of a cluster provided in an embodiment of the present application;
fig. 7 shows a sixth alternative flowchart of a cluster data processing method provided in an embodiment of the present application;
fig. 8 is a schematic diagram illustrating another alternative structure of a cluster provided in the embodiment of the present application;
fig. 9 is a schematic diagram illustrating a hardware composition structure of a master node or a slave node according to an embodiment of the present application.
Detailed Description
In order to make the objects, features and advantages of the present application more obvious and understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the related technology, data transmission between nodes inside the lightweight platform or data transmission between the lightweight platform and the outside requires manual configuration of routing information of each interface, and the use is complex. Therefore, aiming at the defects in the lightweight platform data transmission method, the application provides a cluster data processing method which can overcome part or all of the defects in the prior art.
Fig. 1 shows a first optional flowchart of a cluster data processing method provided in an embodiment of the present application, and will be described according to various steps.
Step S101, a management container in a cluster receives a first signaling.
In some embodiments, the cluster may be a lightweight operating platform, and the cluster may implement the functions of the cluster through at least one container included in each node in the cluster.
In some embodiments, a management container is included in the cluster, the management container being connected with a receiving container, an agent container, and a control container included in the cluster; the management container is configured to receive first signaling. The management container manages the cluster master node and the routing information of the container included in the cluster master node, and/or the management container manages the cluster slave node and the routing information of the container included in the cluster slave node.
In a specific implementation, the management container may further store routing information of the master node or each slave node in the cluster, for example, an IP address, an interface name, a subnet mask, and the like of the master node or each slave node. Routing information of a container included in the master node or each slave node in the cluster, such as an IP address, an interface name, a subnet mask, and the like of the container, may also be stored.
Wherein the first signaling may be transmitted from the receiving container to the management container; alternatively, the first signaling may be sent by the proxy container to the management container; alternatively, the first signaling may be sent by the control container to the management container; alternatively, the first signaling may be sent by a cluster from a node to the management container. The first signaling comprises at least one of: service configuration information, network configuration information, and container operation information.
Step S102, the management container sends the first signaling to other containers in the corresponding nodes or the main nodes in the cluster based on the routing information carried by the first signaling.
In some embodiments, if the first signaling is sent to the management container by one of the receiving container, the proxy container or the control container, the management container sends the first signaling to a slave node and/or a container in the slave node in the cluster based on the routing information carried by the first signaling.
In other embodiments, if the first signaling is sent from a slave node in the cluster to the management container, the management container sends the first signaling to a corresponding master node in the cluster and/or a container in the master node based on the routing information carried in the first signaling.
The routing information includes at least one of: an internet protocol address of a slave node receiving the first signaling, a subnet mask of the slave node receiving the first signaling, an IP address of a first container receiving the first signaling, a first interface name receiving the first signaling, and a next routing address.
The other containers in the master node include containers other than the receiving container in the master node, such as a proxy container, a control container, and the like, but the present application is not limited to only the proxy container and the control container.
Therefore, according to the cluster data processing method provided by the embodiment of the application, the management container in the cluster master node receives the first signaling; the management container sends the first signaling to other containers in a slave node or a master node in the cluster based on the routing information carried by the first signaling; enabling the management container to manage the cluster master node and the routing information of the containers included by the cluster master node, and/or enabling the management container to manage the cluster slave nodes and the routing information of the containers included by the cluster slave nodes; when data transmission is carried out between each node in the cluster or between the cluster and the outside, the management container is used for carrying out unified management on the interface or routing information of the cluster, and data is forwarded through the management container, so that the efficiency of carrying out data transmission between each node in the cluster or between the cluster and the outside is improved, and meanwhile, the data transmission process is simplified.
Fig. 2 shows a second optional flowchart of the cluster data processing method provided in the embodiment of the present application, which will be described according to various steps.
Step S201, a receiving container in the cluster master node receives a first signaling sent by the terminal device.
In some embodiments, a receiving container in the cluster master node receives the first signaling sent by the terminal device. Wherein, the receiving container may be a container corresponding to a Command-Line Interface (CLI); the terminal device may be a device external to the cluster, and is connected to the cluster master node based on a Secure Shell (SSH) protocol; the first signaling may be service configuration information for performing service configuration on at least one container of the slave node.
Step S202, the receiving container determines the routing information of the first signaling based on the keyword in the first signaling, and adds the routing information to the first signaling.
In some embodiments, the receiving container extracts a keyword in the first signaling, and determines that the first signaling is sent to a first slave node based on the keyword in the first signaling; and/or determining routing information (such as an IP address, an interface name, a subnet mask, and the like) of the first slave node, and adding the routing information of the first slave node and/or the routing information of the receiving container to the first signaling.
In some embodiments, the receiving container sends first signaling adding routing information into the management container.
Step S203, the management container sends the first signaling to the first slave node in the cluster based on the routing information carried by the first signaling.
In some embodiments, the management container confirms the routing information of the first slave node based on the routing information, and sends the first signaling to the first slave node in the cluster.
In some optional embodiments, if the first signaling includes service configuration information, the management container may further perform information configuration on a slave node based on information carried in the first signaling. Wherein the information configuration may include at least one of: network configuration, interface configuration, service configuration, log alarm configuration and service data query configuration.
Step S204, the routing interface of the first slave node receives the first signaling.
In some embodiments, the first slave node receives the first signaling at a routing interface of the first slave node; and sending the first signaling to a corresponding container based on the routing information included in the first signaling.
Therefore, by the cluster data processing method provided by the embodiment of the application, the routing information of the first signaling does not need to be manually configured, and the efficiency of sending the first signaling from the terminal device to the slave node in the cluster can be improved.
Fig. 3 shows a third optional flowchart of the cluster data processing method provided in the embodiment of the present application, which will be described according to each step.
Step S301, the proxy container in the cluster master node receives the first signaling.
In some embodiments, a proxy container in a cluster master node receives first signaling sent by a cluster external network management or Web-UI interface. Wherein the proxy container may be a container of network management interfacing; the first signaling may be service configuration information for performing service configuration on at least one container of the slave node.
Step S302, the agent container determines the routing information of the first signaling based on the keyword in the first signaling, and adds the routing information to the first signaling.
In some embodiments, the proxy container extracts a keyword in the first signaling, and determines that the first signaling is sent to a first slave node based on the keyword in the first signaling; and/or determining routing information (such as an IP address, an interface name, a subnet mask, etc.) of the first slave node, and adding the routing information of the first slave node and/or the routing information of the receiving container to the first signaling.
Step S303, the management container sends the first signaling to the first slave node in the cluster based on the routing information carried in the first signaling.
In some embodiments, the management container confirms the routing information of the first slave node based on the routing information, and sends the first signaling to the first slave node in the cluster.
In some optional embodiments, if the first signaling includes service configuration information, the management container may further perform information configuration on a slave node based on information carried in the first signaling. Wherein the information configuration may include at least one of: network configuration, interface configuration, service configuration, log alarm configuration and service data query configuration.
Step S304, the routing interface of the first slave node receives the first signaling.
In some embodiments, the first slave node receives the first signaling at a routing interface of the first slave node; and sending the first signaling to a corresponding container based on the routing information included in the first signaling.
Therefore, by the cluster data processing method provided by the embodiment of the application, the routing information of the first signaling does not need to be manually configured, and the efficiency of sending the first signaling from the terminal device to the slave node in the cluster can be improved.
Therefore, by the cluster data processing method provided by the embodiment of the application, the routing information of the first signaling does not need to be manually configured, and the efficiency of sending the first signaling to the slave node in the cluster by a network manager or a Web-UI can be improved.
Fig. 4 shows a fourth optional flowchart of the cluster data processing method provided in the embodiment of the present application, which will be described according to each step.
Step S401, the control container included in the cluster master node receives the second signaling.
In some embodiments, the cluster master node includes a control container for at least one of adding a container in the cluster slave nodes, deleting a container in the cluster slave nodes, changing configuration information of a container in the cluster slave nodes, querying configuration information of a container in a slave node in the cluster, and configuring slave nodes in the cluster and/or configuration information of a container in a slave node.
In some embodiments, the control container receives second signaling, where the second signaling is used to instruct the control container to at least one of add a container in a cluster slave node, delete a container in a cluster slave node, change configuration information of a container in a cluster slave node, query configuration information of a container in a slave node in a cluster, and configure configuration information of a slave node in a cluster and/or a container in a slave node.
Step S402, the control container configures the first signaling and the routing information of the first signaling based on the second signaling.
In some embodiments, the control container configures the first signaling and the routing information of the first signaling based on the indication content of the second signaling.
In some embodiments, the control container extracts a key in the second signaling, configures first signaling based on the key in the second signaling, and determines that the first signaling is sent to a first slave node; and/or determining routing information (such as an IP address, an interface name, a subnet mask, etc.) of the first slave node, and adding the routing information of the first slave node and/or the routing information of the receiving container to the first signaling.
Step S403, the management container sends the first signaling to the first slave node in the cluster based on the routing information carried in the first signaling.
In some embodiments, the management container confirms the routing information of the first slave node based on the routing information, and sends the first signaling to the first slave node in the cluster.
In some optional embodiments, the management container may further perform information configuration on a slave node based on information carried in the first signaling. Wherein the information configuration may include at least one of: adding a container in the cluster slave node, deleting the container in the cluster slave node, changing the configuration information of the container in the cluster slave node, inquiring the configuration information of the container in the cluster slave node, and configuring the slave node in the cluster and/or the configuration information of the container in the slave node.
Step S404, the routing interface of the first slave node receives the first signaling.
In some embodiments, the first slave node receives the first signaling at a routing interface of the first slave node; and sending the first signaling to a corresponding container based on the routing information included in the first signaling.
Optionally, the first slave node and/or the response container perform at least one of adding a container in the cluster slave nodes, deleting a container in the cluster slave nodes, changing configuration information of a container in the cluster slave nodes, querying configuration information of a container in the cluster slave nodes, and configuring configuration information of a container in the cluster slave nodes and/or slave nodes based on information carried in the first signaling.
Therefore, by the cluster data processing method provided by the embodiment of the application, the routing information of the first signaling does not need to be configured manually, and the configuration efficiency of the container included by each node in the cluster can be improved.
Fig. 5 shows a fifth alternative flowchart of the cluster data processing method according to the embodiment of the present application, which will be described according to various steps.
Step S501, the second slave node in the cluster receives the third signaling sent by the first container.
In some embodiments, the second slave node in the cluster receives third signaling sent by the first container in the second slave node of the cluster.
The third signaling may be sent to a container in the third slave node, and may also be sent to at least one of a receiving container, a proxy container, and a control container of the cluster master node.
Optionally, if the third signaling is sent to a container in a third slave node, the third signaling is used for communication between containers of different slave nodes; and if the third signaling is sent to at least one of a receiving container, an agent container and a control container of the cluster master node, the third container is used for transmitting feedback information aiming at the first signaling.
Step S502, the second slave node sends the third signaling to the management container based on the routing information of the third signaling.
In some embodiments, the second slave node may extract a key in the third signaling, determine a destination route (e.g., a destination IP address, a destination interface name, a destination subnet mask, etc.) of the third signaling based on the key in the third signaling, and send the third signaling to the management container.
Step S503, the management container sends the third signaling based on the routing information carried by the third signaling.
In some embodiments, the management container sends the third signaling to one of a receiving container, a proxy container, a control container or other slave nodes in the cluster of the cluster master node based on the routing information carried by the third signaling.
If the third signaling is sent from the container included in the second slave node to the containers in other slave nodes in the cluster, the IP addresses of the containers in the cluster are completely different, and the IP addresses of the slave nodes in the cluster and the IP addresses of the containers do not want to hear.
Therefore, by the cluster data processing method provided by the embodiment of the application, the routing information of the third signaling does not need to be configured manually, and the efficiency of data transmission among all nodes and/or containers in the cluster can be improved.
Fig. 6 shows an alternative structural diagram of a cluster provided in an embodiment of the present application, which will be described according to various steps.
In fig. 6, taking the cluster as a K8s cluster as an example, the K8s cluster includes a master node, a first slave node, and a second slave node; the receiving container in the master node may be a Command Line Interface (CLI); the Agent container may be a container (Agent) that interfaces with network management; the control container may be a container in the cluster for managing containers in the slave nodes (if the cluster is a K8s cluster, the control container is a K8 smaster); the management container is connected with a receiving container, an agent container and a control container included in the cluster.
In fig. 6, the terminal SSH may be the terminal device in step S201 to step S204; the network management/Web-UI may be a cluster external network management or Web-UI interface in steps S301 to S304.
In fig. 6, the management container may implement data transmission between the cluster external terminal device and the cluster slave node container (step S201 to step S204); the terminal SSH sends the first signaling to a receiving container through a user management container in the cluster main node; the receiving container determines the routing information of the first signaling based on the keywords in the first signaling; sending a first signaling carrying routing information to the management container; and the management container sends the first signaling to the corresponding cluster slave node based on the routing information of the first signaling.
In fig. 6, the management container may implement the external network management of the cluster or the data transmission between the Web-UI interface and the container in the cluster slave node (steps S301 to S304); the network management or Web-UI interface sends the first signaling to the proxy container. The proxy container determines the routing information of the first signaling based on the keywords in the first signaling; sending a first signaling carrying routing information to the management container; and the management container sends the first signaling to the corresponding cluster slave node based on the routing information of the first signaling.
In fig. 6, the management container may implement the configuration of the container included in each node in the cluster by the control container in the cluster (step S401 to step S404); the control container receives second signaling, and configures the first signaling and the routing information of the first signaling based on the second signaling; sending a first signaling carrying routing information to the management container; the management container sends the first signaling to a first slave node based on the routing information of the first signaling; the first slave node performs at least one of adding a container in the cluster slave node, deleting the container in the cluster slave node, changing the configuration information of the container in the cluster slave node, inquiring the configuration information of the container in the slave node in the cluster and configuring the slave node in the cluster and/or the configuration information of the container in the slave node based on the information carried in the first signaling.
In fig. 6, the management container may implement data transmission between nodes and/or containers inside the cluster (step S501 to step S503); and the second slave node in the cluster receives a third signaling sent by the first container, the second slave node sends the third signaling to a management container based on the routing information of the third signaling, and the management container sends the third signaling to one of a receiving container, an agent container, a control container or other slave nodes in the cluster based on the routing information carried by the third signaling.
Fig. 7 shows a sixth alternative flowchart of the cluster data processing method provided in the embodiment of the present application, which will be described according to various steps.
In step S601, a K8S cluster is installed.
In some embodiments, the cluster is illustrated as a K8s cluster.
In some embodiments, the software package of the K8s cluster is decompressed and the validity of the K8s cluster software package is verified; under the condition that the K8s cluster software package meets the legality, configuring the networking of a K8s cluster, and determining a cluster master node and each cluster slave node in the K8s cluster; after the physical networking configuration of the cluster master node and each cluster slave node is completed, installing K8s software on the cluster master node and each cluster slave node, and starting to operate.
In step S602, the management container receives a first signaling.
In some embodiments, a receiving container in the cluster master node receives the first signaling sent by the terminal device. Wherein, the receiving container can be a container corresponding to a command line interface; the terminal device can be a device outside the cluster and is connected to the cluster main node based on a secure shell protocol; the first signaling may be service configuration information for performing service configuration on at least one container of the slave node.
In other embodiments, in some embodiments, a proxy container in the cluster master node receives first signaling sent by a network management or Web-UI interface outside the cluster. Wherein the proxy container may be a container of network management interfacing; the first signaling may be service configuration information for performing service configuration on at least one container of the slave node.
Step S603, the management container configures a namespace based on the first signaling.
In some embodiments, the management container configures a Namespace (Namespace) based on information carried in the first signaling. Wherein the information configuration may include at least one of: network configuration, interface configuration, service configuration, log alarm configuration and service data query configuration.
The management container configures a 5G core network (5GC) for the container in the slave node based on the first signaling.
In some embodiments, the management container configures namespaces, creating an internal networking based on namespaces, such as configuring CLIs, Sbi bridges. And defaults to specifying an address for Sbi Bridge; alternatively, the available address field may also be configured by entering Sbi Bridge.
In other embodiments, the management container further configures interface routing of at least one of N2, N3, N4, and N6 based on the namespace; and configuring a K8s based network.
Optionally, the management container may configure at least two namespaces based on the first signaling.
In some embodiments, after the configuration is completed, the management container configures 5GC under the namespace, and performs communication configuration between the proxy container and the management container.
Step S604, service is configured based on the name space.
In some embodiments, a first slave node corresponding to the management container or the first signaling configures the service information based on the namespace.
Still take the configuration 5GC as an example for illustration.
In some embodiments, a first slave node corresponding to a management container or first signaling configures 5GC service information based on a namespace. Optionally, the service information configuring the 5GC may at least include: the method comprises the steps of service configuration, log alarm configuration, service data configuration and service data query configuration.
Therefore, the north configuration interface is uniformly provided by designing an interface, a route and a K8s network in the newly added management container centralized control and management K8s cluster through software, a uniform operation maintenance management control interface is provided for products based on K8s, and the usability and the availability of the products are improved.
Fig. 8 shows another alternative structural diagram of a cluster provided in the embodiment of the present application, which will be described according to various parts.
In some embodiments, the cluster 800 includes a master node 810 and at least one slave node, and only a first slave node 820 and a second slave node 830 are shown in fig. 8 for page reasons, but those skilled in the art will know that the number of slave nodes in the cluster 800 may be set according to actual requirements, and is not limited to 2.
In some embodiments, the master node (cluster master node) 810 of the cluster 800 may include a management container 811.
The management container 811 is configured to receive a first signaling;
the management container 811 is configured to send the first signaling to other containers in a slave node (a first slave node 820 or a second slave node 830) or a master node 810 in the cluster based on the routing information carried by the first signaling;
the management container 811 manages the cluster master node 810 and the routing information of the container included in the cluster master node 810, and/or the management container 811 manages the cluster slave node (the first slave node 820 or the second slave node 830) and the routing information of the container included in the cluster slave node.
In some embodiments, the first signaling carries routing information of the slave nodes in the cluster; the management container 811 sends the first signaling to the corresponding slave node based on the routing information carried by the first signaling.
In some embodiments, the master node (cluster master node) 810 of the cluster 800 may include a receiving container 812 in some embodiments.
The receiving container 812 is configured to receive a first signaling sent by a terminal device;
determining routing information of the first signaling based on keywords in the first signaling, and adding the routing information to the first signaling;
the receiving container 812 is further configured to send the first signaling for adding the routing information to the management container 811.
In some embodiments, the master node (cluster master node) 810 of the cluster 800 may include a proxy container 813 in some embodiments.
The proxy container 813 is configured to receive a first signaling;
determining routing information of the first signaling based on keywords in the first signaling, and adding the routing information to the first signaling;
the agent container 813 is further configured to send a first signaling for adding the routing information to the management container 811.
In some embodiments, the master node (cluster master node) 810 of the cluster 800 may include a control container 814 in some embodiments.
The control container 814 is configured to receive a second signaling;
the control container 814, configured to configure the first signaling and the routing information of the first signaling based on the second signaling;
the control container 814 is configured to send the first signaling for adding the routing information to the management container 811;
wherein the first signaling carries an operation instruction for a container included in a slave node.
In some embodiments, the routing information comprises at least one of: an internet protocol, IP, address of the slave node receiving the first signaling, a subnet mask of the slave node receiving the first signaling, an IP address of a first container receiving the first signaling, a first interface name receiving the first signaling, and a next routing address.
In some embodiments, the first signaling is received by a routing interface of the first slave node 820 or the second slave node 830;
and sending the first signaling to a corresponding container based on the routing information included in the first signaling.
In some embodiments, the first signaling comprises at least one of:
service configuration information, network configuration information, and container operation information.
The management container 811 is further configured to receive a third signaling sent by a cluster slave node, where the third signaling carries routing information for receiving the third signaling;
the management container 811 sends the third signaling to one of the receiving container 812, the proxy container 813, the control container 814 or other slave nodes in the cluster of the cluster master node based on the routing information carried by the third signaling.
Fig. 9 is a schematic diagram of a hardware structure of a master node or a slave node provided in an embodiment of the present application, where the master node or the slave node 700 includes: at least one processor 701, memory 702, and at least one network unit 704. The various components within the master or slave node 700 are coupled together by a bus system 705. It is understood that the bus system 705 is used to enable communications among the components. The bus system 705 includes a power bus, a control bus, and a status signal bus in addition to a data bus. But for clarity of illustration the various busses are labeled in figure 9 as the bus system 705.
It will be appreciated that the memory 702 can be either volatile memory or nonvolatile memory, and can include both volatile and nonvolatile memory. The non-volatile Memory may be ROM, Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic random access Memory (FRAM), Flash Memory (Flash Memory), magnetic surface Memory, optical Disc, or Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), Synchronous Dynamic Random Access Memory (SLDRAM), Direct Memory (DRmb Access), and Random Access Memory (DRAM). The memory 702 described in embodiments herein is intended to comprise, without being limited to, these and any other suitable types of memory.
The memory 702 in the embodiments of the present application is used to store various types of data to support the operation of the master or slave node 700. Examples of such data include: any computer program for operating on the master or slave node 700, such as application 722. A program implementing the method of an embodiment of the present application may be included in the application 722.
The method disclosed in the embodiment of the present application may be applied to the processor 701, or implemented by the processor 701. The processor 701 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 701. The Processor 701 may be a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor 701 may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in the memory 702, and the processor 701 may read the information in the memory 702 and perform the steps of the aforementioned methods in conjunction with its hardware.
In an exemplary embodiment, the master or slave node 700 may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), FPGAs, general purpose processors, controllers, MCUs, MPUs, or other electronic components for performing the aforementioned methods.
In addition to the above-described methods and apparatus, embodiments of the present application may also be a computer program product comprising computer program instructions that, when executed by a processor, cause the processor to perform the steps in the methods according to the various embodiments of the present application described in the "exemplary methods" section of this specification, above.
The computer program product may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages, for carrying out operations according to embodiments of the present application. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server.
Furthermore, embodiments of the present application may also be a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, cause the processor to perform steps in a method according to various embodiments of the present application described in the "exemplary methods" section above of this specification.
The computer-readable storage medium may take any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may include, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The foregoing describes the general principles of the present application in conjunction with specific embodiments, however, it is noted that the advantages, effects, etc. mentioned in the present application are merely examples and are not limiting, and they should not be considered essential to the various embodiments of the present application. Furthermore, the foregoing disclosure of specific details is for the purpose of illustration and description and is not intended to be limiting, since the foregoing disclosure is not intended to be exhaustive or to limit the disclosure to the precise details disclosed.
The block diagrams of devices, apparatuses, systems referred to in this application are only given as illustrative examples and are not intended to require or imply that the connections, arrangements, configurations, etc. must be made in the manner shown in the block diagrams. These devices, apparatuses, devices, systems may be connected, arranged, configured in any manner, as will be appreciated by those skilled in the art. Words such as "including," "comprising," "having," and the like are open-ended words that mean "including, but not limited to," and are used interchangeably herein. As used herein, the words "or" and "refer to, and are used interchangeably with, the word" and/or, "unless the context clearly dictates otherwise. The word "such as" is used herein to mean, and is used interchangeably with, the phrase "such as but not limited to".
It should also be noted that in the devices, apparatuses, and methods of the present application, the components or steps may be decomposed and/or recombined. These decompositions and/or recombinations are to be considered as equivalents of the present application.
The previous description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the application. Thus, the present application is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The foregoing description has been presented for purposes of illustration and description. Furthermore, the description is not intended to limit embodiments of the application to the form disclosed herein. While a number of example aspects and embodiments have been discussed above, those of skill in the art will recognize certain variations, modifications, alterations, additions and sub-groups thereof.
Claims (9)
1. A method of cluster data processing, the method comprising:
the control container included by the cluster main node receives a second signaling;
the control container configuring a first signaling and routing information of the first signaling based on the second signaling;
the control container sends the first signaling added with the routing information to a management container;
a management container in a cluster main node receives a first signaling;
the management container sends the first signaling to other containers in slave nodes or master nodes in the cluster based on the routing information carried by the first signaling;
the management container manages the cluster master node and the routing information of the containers included by the cluster master node, and/or the management container manages the cluster slave node and the routing information of the containers included by the cluster slave node; the first signaling carries operating instructions for a container comprised by the slave node.
2. The method as set forth in claim 1, wherein,
the first signaling carries routing information of corresponding nodes in the cluster;
and the management container sends the first signaling to a corresponding slave node based on the routing information carried by the first signaling.
3. The method of claim 1, prior to the management container in the cluster receiving the first signaling, the method further comprising:
a receiving container in the cluster main node receives a first signaling sent by a terminal device;
determining routing information of the first signaling based on keywords in the first signaling, and adding the routing information to the first signaling;
and the receiving container sends the first signaling added with the routing information to the management container.
4. The method of claim 1, prior to the management container in the cluster receiving the first signaling, the method further comprising:
a proxy container in the cluster master node receives a first signaling;
determining routing information of the first signaling based on keywords in the first signaling, and adding the routing information to the first signaling;
and the agent container sends the first signaling added with the routing information to the management container.
5. The method of any of claims 1 to 4, the routing information comprising at least one of: an internet protocol, IP, address of the slave node receiving the first signaling, a subnet mask of the slave node receiving the first signaling, an IP address of a first container receiving the first signaling, a first interface name receiving the first signaling, and a next routing address.
6. The method of claim 1, further comprising:
receiving the first signaling from a routing interface of a corresponding slave node;
and sending the first signaling to a corresponding container based on the routing information included in the first signaling.
7. The method of claim 1, the first signaling comprising at least one of:
service configuration information, network configuration information, and container operation information.
8. The method of claim 1, further comprising:
the management container receives a third signaling sent by a cluster slave node, wherein the third signaling carries routing information for receiving the third signaling;
and the management container sends the third signaling to one of a receiving container, a proxy container, a control container or other slave nodes in the cluster of the cluster main node based on the routing information carried by the third signaling.
9. A cluster, the cluster comprising:
a control container for receiving second signaling; configuring a first signaling and routing information of the first signaling based on the second signaling; sending the first signaling added with the routing information to a management container;
a management container for receiving a first signaling; based on the routing information carried by the first signaling, sending the first signaling to other containers in the slave nodes or master nodes in the cluster;
the management container manages the cluster master node and the routing information of the container included by the cluster master node, and/or the management container manages the cluster slave node and the routing information of the container included by the cluster slave node; the first signaling carries operating instructions for a container comprised by the slave node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110902526.9A CN113645069B (en) | 2021-08-06 | 2021-08-06 | Cluster data processing method and cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110902526.9A CN113645069B (en) | 2021-08-06 | 2021-08-06 | Cluster data processing method and cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113645069A CN113645069A (en) | 2021-11-12 |
| CN113645069B true CN113645069B (en) | 2022-09-23 |
Family
ID=78419944
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110902526.9A Active CN113645069B (en) | 2021-08-06 | 2021-08-06 | Cluster data processing method and cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113645069B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105376303A (en) * | 2015-10-23 | 2016-03-02 | 深圳前海达闼云端智能科技有限公司 | Docker implementation system and communication method thereof |
| CN110647580A (en) * | 2019-09-05 | 2020-01-03 | 南京邮电大学 | Distributed container cluster mirror image management main node, slave node, system and method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110858821B (en) * | 2018-08-23 | 2022-01-07 | 阿里巴巴集团控股有限公司 | Container communication method and device |
| US10778798B2 (en) * | 2018-10-24 | 2020-09-15 | Hewlett Packard Enterprise Development Lp | Remote service access in a container management system |
| CN110457559A (en) * | 2019-08-05 | 2019-11-15 | 深圳乐信软件技术有限公司 | Distributed data crawls system, method and storage medium |
| CN111552543A (en) * | 2020-05-22 | 2020-08-18 | 北京联想软件有限公司 | Container management and control method and processing node |
-
2021
- 2021-08-06 CN CN202110902526.9A patent/CN113645069B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105376303A (en) * | 2015-10-23 | 2016-03-02 | 深圳前海达闼云端智能科技有限公司 | Docker implementation system and communication method thereof |
| CN110647580A (en) * | 2019-09-05 | 2020-01-03 | 南京邮电大学 | Distributed container cluster mirror image management main node, slave node, system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113645069A (en) | 2021-11-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111278031B (en) | PDU type setting method, UE strategy setting method, entity and storage medium | |
| CN108712332B (en) | Communication method, system and device | |
| WO2018006381A1 (en) | Network resource management method, apparatus and system | |
| CN109194559B (en) | Multicast method and VTEP device | |
| CN110049503B (en) | Method and equipment for acquiring data | |
| CN113141405B (en) | Service access method, middleware system, electronic device, and storage medium | |
| CN112654100B (en) | Information processing method and related network equipment | |
| CN111427701A (en) | Workflow engine system and business processing method | |
| CN111382115B (en) | Path creating method and device for network on chip and electronic equipment | |
| EP3174318B1 (en) | Method for realizing resource attribute notification, and common service entity | |
| WO2016149880A1 (en) | Data reading method, equipment and system | |
| CN111885172A (en) | Cross-network platform cascading method, computer storage medium and electronic device | |
| CN111064786B (en) | Account identifier management method and device | |
| CN110896411B (en) | Service processing method and related equipment | |
| CN111726400A (en) | Reverse connection method, device and server-side system | |
| CN113079207B (en) | Method, system, terminal and medium for realizing high availability of port or network | |
| CN111866211B (en) | Network access method, device, terminal and medium applied to terminal | |
| CN113645069B (en) | Cluster data processing method and cluster | |
| CN111510384B (en) | Method, electronic device and computer-readable medium for processing data generated by a service | |
| CN112235378A (en) | Data updating method and device, storage medium and electronic equipment | |
| CN115442129A (en) | Method, device and system for managing cluster access authority | |
| CN115480877A (en) | External exposure method and device of application service in multi-cluster environment | |
| WO2021115464A1 (en) | Network slice selection method and related device | |
| CN110928693B (en) | Computing equipment and resource allocation method | |
| CN113742617A (en) | Cache updating method and device |
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 |