CN112702441A - Container-based access data processing method, device and system and storage medium - Google Patents
Container-based access data processing method, device and system and storage medium Download PDFInfo
- Publication number
- CN112702441A CN112702441A CN202110007739.5A CN202110007739A CN112702441A CN 112702441 A CN112702441 A CN 112702441A CN 202110007739 A CN202110007739 A CN 202110007739A CN 112702441 A CN112702441 A CN 112702441A
- Authority
- CN
- China
- Prior art keywords
- container
- direct access
- access data
- group
- container group
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5046—Resolving address allocation conflicts; Testing of addresses
-
- 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
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention discloses a container-based access data processing method, a device, a system and a storage medium, wherein the method comprises the following steps: generating service configuration files corresponding to all nodes in the container arrangement engine; wherein each of the nodes comprises at least one container group; dynamically monitoring each service configuration file through a traffic import gateway; reporting container direct access data of each node content group to a client according to the dynamic monitoring result of the traffic import gateway; wherein the container direct access data comprises a container group IP address. The technical scheme of the embodiment of the invention can avoid the problems of port conflict and service interruption existing in the direct access of the container group, and reduce the configuration cost and the maintenance cost of the direct access of the container group, thereby improving the direct access performance of the container group.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a container-based access data processing method, device and system and a storage medium.
Background
The container group (pod) direct access means that the IP address of the container group is clustered through kubernets (container arrangement engine, K8s for short), and the service container in the container group is directly accessed according to the acquired IP address.
Currently, there are two implementations of the container group direct access method. The first container group direct access method is to map the container group to a service based on the node IP address (ndoe _ IP) plus the node port (node port), and then register the service in the nginx gateway. That is, when the first container group direct access method directly accesses the container group, the mapping relationship between the node IP address and the node port needs to be obtained according to the service, so as to determine the address of the container group according to the mapping relationship between the node IP address and the node port and the mapping relationship between the node port and the container group service port. The second direct access method for the container group is to use a host network mode of Kubernets, and the mode adopts a Kubernets node IP address and a service port of the container group to directly access the container group.
In the process of implementing the invention, the inventor finds that the prior art has the following defects: the first container group direct access method needs a large amount of configuration work on kubernets, and a single node port of kubernets needs to be used for generating a service each time, a large amount of services occupy a large number of node ports, a mapping relationship between the node ports and service ports of a container group needs to be manually maintained, and an external gateway cannot be effectively supported. In the second container group direct access method, a single node can only carry one container group with the same service, and multiple container groups with the same service can cause the problem of port conflict. Meanwhile, because the identity of the container group uses the node IP address, when the container group is restarted to cause the resource to be scheduled to other nodes, the identity of the container group is also changed, and the mapping relationship between the container group and the node IP address needs to be manually maintained, otherwise, the service link is interrupted. Meanwhile, the two methods for directly accessing the container group both need developers to master deep knowledge storage for kubernets, and need to perform more configuration work on the kubernets.
Disclosure of Invention
Embodiments of the present invention provide a method, an apparatus, a system, and a storage medium for processing access data based on a container, so as to avoid port conflicts and service interruption problems in direct access of a container group, and reduce configuration cost and maintenance cost of the direct access of the container group, thereby improving direct access performance of the container group.
In a first aspect, an embodiment of the present invention provides a container-based access data processing method, applied to a container orchestration engine, including:
generating service configuration files corresponding to all nodes in the container arrangement engine; wherein each of the nodes comprises at least one container group;
dynamically monitoring each service configuration file through a traffic import gateway;
reporting container direct access data of each node content group to a client according to the dynamic monitoring result of the traffic import gateway;
wherein the container direct access data comprises a container group IP address.
In a second aspect, an embodiment of the present invention further provides a container-based access data processing method, applied to a client, including:
determining target container direct access data of a target container group according to the local container direct access data;
generating a container group direct access request according to the target container direct access data;
sending the container group direct access request to a container orchestration engine to directly access the target container group through the container group direct access request;
wherein the local container direct access data comprises a target container group IP address.
In a third aspect, an embodiment of the present invention further provides a container-based access data processing apparatus, configured in a container arrangement engine, including:
the configuration file generation module is used for generating service configuration files corresponding to all nodes in the container arrangement engine; wherein each of the nodes comprises at least one container group;
the flow import gateway is used for dynamically monitoring each service configuration file; reporting the container direct access data of each node content group to the client according to the dynamic monitoring result;
wherein the container direct access data comprises a container group IP address.
In a fourth aspect, an embodiment of the present invention further provides a container-based access data processing apparatus, configured at a client, including:
the target container direct access data determining module is used for determining target container direct access data of the target container group according to the local container direct access data;
the container group direct access request generation module is used for generating a container group direct access request according to the target container direct access data;
the container group direct access request sending module is used for sending the container group direct access request to a container arrangement engine so as to directly access the target container group through the container group direct access request;
wherein the local container direct access data comprises a target container group IP address.
In a fifth aspect, an embodiment of the present invention further provides a container-based access data processing system, which includes a container orchestration engine and a client, where the container orchestration engine is communicatively connected to the client; wherein:
the container arrangement engine is used for generating service configuration files corresponding to all nodes in the container arrangement engine; wherein each of the nodes comprises at least one container group; dynamically monitoring each service configuration file through a traffic import gateway; reporting container direct access data of each node content group to a client according to the dynamic monitoring result of the traffic import gateway;
the client is used for determining target container direct access data of the target container group according to the local container direct access data; generating a container group direct access request according to the target container direct access data; sending the container group direct access request to a container orchestration engine to directly access the target container group through the container group direct access request;
wherein the container direct access data comprises a container group IP address; the local container direct access data comprises a target container group IP address.
In a sixth aspect, the present invention further provides a computer storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the container-based access data processing method provided in any embodiment of the present invention.
After the container arrangement engine generates the service configuration files corresponding to the nodes in the container arrangement engine, the embodiment of the invention carries out dynamic monitoring on the service configuration files through the flow import gateway in the container arrangement engine, and reports the container direct connection access data of the content groups of the nodes to the client according to the dynamic monitoring result of the flow import gateway. The client side can determine target container direct access data of a target container group according to the local container direct access data, and generate a container group direct access request according to the target container direct access data so as to send the container group direct access request to the container arrangement engine, so that the target container group can be directly accessed through the container group direct access request, the local container direct access data of the client side can also comprise a target container group IP address as the container direct access data comprises the container group IP address, the client side can directly access the target container group according to the target container direct access data comprising the target container group IP address, the problems of port conflict and service interruption, high configuration cost and maintenance cost and the like of the existing container group direct access method are solved, and the configuration cost and the maintenance cost of the container group direct access are reduced, the direct access performance of the container group is improved.
Drawings
FIG. 1 is a flowchart of a container-based access data processing method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a container group direct connection system according to an embodiment of the present invention;
fig. 3 is a schematic diagram of an update structure of an ingress-nginx configuration file according to an embodiment of the present invention;
fig. 4 is a schematic flowchart of updating an IP address of a container group by an ingress module according to an embodiment of the present invention;
FIG. 5 is a flowchart of a container-based access data processing method according to a second embodiment of the present invention;
fig. 6 is a schematic flowchart of a client accessing a container group according to a second embodiment of the present invention;
fig. 7 is a timing diagram of data flow of a directly connected access container group according to a second embodiment of the present invention;
FIG. 8 is a schematic diagram of a container-based access data processing system according to a third embodiment of the present invention;
fig. 9 is a schematic diagram of a container-based access data processing apparatus according to a fourth embodiment of the present invention;
fig. 10 is a schematic diagram of a container-based access data processing apparatus according to a fifth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention.
It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
Example one
Fig. 1 is a flowchart of a method for processing container-based access data according to an embodiment of the present invention, and fig. 2 is a schematic diagram of an architecture of a container group direct connection system according to an embodiment of the present invention, where this embodiment is applicable to a case where a container arrangement engine reports container direct connection access data including an IP address of a container group to a client, and the method may be executed by a container-based access data processing apparatus, and the apparatus may be implemented by software and/or hardware, and may generally be integrated in the container arrangement engine, and used in cooperation with the client for directly accessing the container group. Accordingly, as shown in fig. 1 and 2, the method comprises the following operations:
s110, generating service configuration files corresponding to the nodes in the container arrangement engine; wherein each of the nodes includes at least one container group.
Wherein the container orchestration engine may be used to manage containers and container groups, a container group may include multiple containers. The service configuration file may be a configuration file generated by the container orchestration engine, and is used to configure the container direct access data, where the number of the service configuration files may be multiple.
In embodiments of the present invention, the container orchestration engine may comprise a plurality of nodes, each node may comprise at least one container group. In a specific example, as shown in fig. 2, the container arrangement engine may be kubernets, and accordingly, the node may be a node device included in the container arrangement engine, and the service profile may be a service file generated by kubernets.
In an optional embodiment of the present invention, the generating a service profile corresponding to each node in the container orchestration engine may include: under the condition that the service port of each container group in the node is detected, acquiring the IP address of the container group of each container group; and generating each service configuration file according to the IP address of the container group.
The container group IP address (pod _ IP), that is, the IP address of the container group, may uniquely identify the identity of the container group.
In an embodiment of the present invention, the service port of each container in the container group is exposed by the container group in which it is located. Correspondingly, if the container arrangement engine detects the service port exposed by each container group in the node, the container group IP address of each container group can be acquired, and a corresponding service configuration file is generated according to the container group IP address.
In a specific example, as shown in fig. 2, after the container group exposes the service port of the container, kubernets may generate a service file, and obtain the IP address of the container group of each container group through the service file. It is understood that, since one container group of exposed service ports may generate one service file, and one node may have at least one container group of exposed service ports, one node may generate one or more service files correspondingly. When a node includes multiple container groups, the service file corresponding to the node may configure the exposed service port of each container group.
In an optional embodiment of the present invention, after generating each service profile according to the container group address, the method may further include: configuring a container group label for each container group IP address through the service configuration file; establishing a mapping relation between the IP address of the container group and the label of the container group; and storing the mapping relation between the IP address of the container group and the label of the container group in the service configuration file.
The container group tag may be a custom tag for identifying the container group IP address. Alternatively, the type of container group label may be a label.
Specifically, after the container arrangement engine generates the service configuration file, the service configuration file may be used to assign a corresponding container group label to each container group IP address, and one container group IP address is correspondingly assigned with one unique container group label. Meanwhile, the service configuration file needs to establish and store the mapping relationship between the IP address of each container group and the label of the container group. Since the container group tag can uniquely identify the container group IP address. Therefore, even when the container group IP address changes, the service configuration file can be matched with the new container group IP address of the container group through the label, and the mapping relation between the new container group IP address and the container group label is updated and stored.
In one specific example, as shown in fig. 2, kubernets may bind each container group IP address through a label according to a service file. In this case, when the container group is restarted, the IP address of the container group changes, and the service file can still find the corresponding container group through the Labels of the Labels, and obtain the new IP address of the container group.
And S120, dynamically monitoring each service configuration file through a traffic import gateway.
The traffic import gateway may be a gateway configured in the container orchestration engine, and is configured to monitor the service configuration file and report the monitored data to the client. The traffic import gateway can be compatible with an external gateway of the container arrangement engine, supports TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) traffic, and has stronger compatibility.
In the embodiment of the invention, the container arrangement engine can be configured with the flow import gateway, and the real-time dynamic monitoring is carried out on each service configuration file through the flow import gateway so as to obtain the IP address information of the container group of each container group in real time.
And S130, reporting the container direct access data of each node content group to the client according to the dynamic monitoring result of the traffic import gateway.
Wherein the container direct access data comprises a container group IP address. The dynamic monitoring result may be the IP address information of the container group of each container group obtained by dynamically monitoring each service configuration file. The container direct access data may be data for direct access to the group of containers.
Correspondingly, after the traffic import gateway dynamically monitors each service configuration file to obtain the container group IP address of each container group, container direct access data can be constructed according to the container group IP address, and the container direct access data of each node content group is reported to the client.
In an optional embodiment of the present invention, the traffic ingress gateway includes a synchronization configuration module; the dynamically monitoring each service configuration file through the traffic import gateway may include: and dynamically monitoring each service configuration file through the synchronous configuration module to obtain the dynamic monitoring result.
The synchronous configuration module can be used for dynamically monitoring the service configuration file. In a specific example, as shown in fig. 2, the synchronization configuration module may be an ingress module.
In an optional embodiment of the present invention, the reporting, to the client, container direct access data of each node content group according to the dynamic monitoring result of the traffic import gateway may include: sending the updated container direct access data to the client under the condition that the synchronous configuration module determines that the dynamic monitoring result comprises the updated container direct access data; and updating the container direct access data, wherein the updating the container direct access data comprises newly added container direct access data and/or changed container direct access data.
The updated container direct access data may be changed container direct access data, the newly added container direct access data may be newly appeared container direct access data, and the changed container direct access data may be new container direct access data formed after the existing container direct access data is changed.
It should be noted that, the update of the information of each container group in the container arrangement engine, such as the restart of a new extender group or a container group, may result in the update of the information of the container group. Correspondingly, when a new compatibilizer set is used, the service configuration file adds configuration information for the new compatibilizer set, and the traffic import gateway can acquire the container set IP address of the new compatibilizer set as the direct access data of the added container. When a restart operation occurs to an existing container group, the container group updates the container group IP address. At this time, the service configuration file may also update the IP address of the container group synchronously, and the traffic import gateway may obtain the IP address of the container group as the direct access data of the changed container. That is, once the traffic import gateway monitors the updated container direct access data, the updated container direct access data can be reported to the client in real time, so that the client can master the latest and most accurate container direct access data in real time.
In an optional embodiment of the present invention, the traffic ingress gateway includes a traffic parsing module; the method may further comprise: acquiring a container group direct connection access request sent by the client; analyzing the container group direct connection access request through the flow analysis module to obtain target container direct connection access data; and directly accessing the target container group according to the target container direct access data.
The traffic analysis module may be configured to analyze a container group direct access request sent by a client. In a specific example, as shown in fig. 2, optionally, the traffic parsing module may be an nginx module. The container group direct access request may be a request for direct access to a container group. The target container direct access data may be access data for direct access to the target group of containers. The target container group is the container group which the client needs to directly access. Optionally, the number of the synchronization configuration module and the number of the traffic analysis module may be at least one, and the numbers of the synchronization configuration module and the traffic analysis module may be kept consistent and applied in pairs.
Correspondingly, the container arrangement engine can report the container direct access data of each container group to the client in real time, so that the client can directly access the target container group through the locally stored container direct access data according to the service requirement. Specifically, the client may send a container group direct access request to the container orchestration engine. After receiving the container group direct access request, the container arrangement engine can analyze the container group direct access request through a flow analysis module in the flow import gateway to obtain target container direct access data corresponding to the target container group. Optionally, the target container direct access data may be a target container group IP address, or may also be a combination of the target container group IP address and a service port of the target container group. Correspondingly, the container arrangement engine can directly access the target container group according to the target container direct-connection access data through the flow analysis module, so that the effect that the client directly accesses the target container group is achieved.
According to the technical scheme, the container group IP address is used as the container direct connection access data, a single node can be compatible with a plurality of container groups with the same service, the problem of port conflict can be effectively avoided, the resource utilization rate is improved, the mapping relation between the service port and the node port does not need to be maintained, and therefore the maintenance cost is reduced. In addition, the configuration work of the container arrangement engine can be reduced by using the IP address of the container group as the direct access data of the container, so that the configuration cost and the learning cost of the container arrangement engine are reduced. Meanwhile, the container arrangement engine can dynamically monitor the service configuration file through the flow import gateway so as to obtain a dynamic monitoring result in real time and report the dynamic monitoring result to the client, so that the automatic synchronization of the IP addresses of the container groups is realized, and the problem of service interruption is effectively avoided. In addition, the traffic import gateway can be compatible with an external gateway of the container arrangement engine, and the compatibility is stronger. Therefore, the container-based access data processing method provided by the embodiment of the invention can effectively improve the direct access performance of the container group.
In a specific example, as shown in fig. 2, the ingress-nginx gateway can be used as a kubernets traffic introduction gateway, and the ingress-nginx gateway is a kubernets gateway which uses a nginx module as a reverse proxy to introduce external traffic into the kubernets. Kubernets can dynamically monitor each service file in real time through an ingress module in an ingress-nginx gateway, so that container group IP address information of each container group is obtained through the service files, container direct connection access data is constructed according to the obtained container group IP address information, and the container direct connection access data are reported to a client. The ingress module can continuously monitor the update condition of the IP address of each container group, and when the IP address of a newly added container group or the IP address of an existing container group changes, the ingress module will report the IP address of the updated container group to the client again.
It should be noted that, if the client has service port information of each container group, the container direct access data reported to the client by kubernets may only include an IP address of the container group. Or, Kubernetes may also report a combination of the container group IP address and the service port corresponding to the container group as container direct access data to the client.
Fig. 3 is a schematic diagram of an update structure of an ingress-nginx configuration file according to an embodiment of the present invention, and fig. 4 is a schematic diagram of a flow of an ingress module updating an IP address of a container group according to an embodiment of the present invention. In the configuration aspect, as shown in fig. 3, an ingress module in the kubernets ingress-nginx gateway simultaneously has an authority to modify a configuration file nginx.conf file of the nginx module, when an ingress module is newly added, the ingress module adds a route entry of a reverse proxy to the nginx.conf file, and after a container group direct connection access request sent by a client, the nginx module can obtain the container group direct connection access request and directly access a target container group through a target container group IP address carried in the container group direct connection access request. As shown in fig. 4, the Ingress module may monitor resources related to kubernets by calling kubernets api (Application Program Interface), and when the resources change, the Ingress module may perform related operations, such as: and modifying the configuration file nginx. conf of the nginx module, sending the latest bound container group IP address (endpoint _ IP) to a client (client), and handing over the client to maintain the container group IP address. The client side can update the mapping relation between the label and the tag (table) according to the latest IP address of the container group, and directly access data as a target container to join a container group direct access request when the container group is directly connected.
After the container arrangement engine generates the service configuration files corresponding to the nodes in the container arrangement engine, the embodiment of the invention carries out dynamic monitoring on the service configuration files through the flow import gateway in the container arrangement engine, and reports the container direct connection access data of the content groups of the nodes to the client according to the dynamic monitoring result of the flow import gateway. The client side can determine target container direct access data of a target container group according to the local container direct access data, and generate a container group direct access request according to the target container direct access data so as to send the container group direct access request to the container arrangement engine, so that the target container group can be directly accessed through the container group direct access request, the local container direct access data of the client side can also comprise a target container group IP address as the container direct access data comprises the container group IP address, the client side can directly access the target container group according to the target container direct access data comprising the target container group IP address, the problems of port conflict and service interruption, high configuration cost and maintenance cost and the like of the existing container group direct access method are solved, and the configuration cost and the maintenance cost of the container group direct access are reduced, the direct access performance of the container group is improved.
Example two
Fig. 5 is a flowchart of a container-based access data processing method according to a second embodiment of the present invention, where the present embodiment is applicable to a case where a client directly accesses a target container group according to local container direct access data including an IP address of the target container group, and the method may be executed by a container-based access data processing apparatus, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in a client device, where the client device may be a computer device, and may also be any type of terminal device, and the like, and is used in cooperation with a container arrangement engine for managing the container group. Accordingly, as shown in fig. 5, the method includes the following operations:
s210, determining target container direct access data of the target container group according to the local container direct access data.
The local container direct access data may be container direct access data locally stored by the client, and may include a target container group IP address. Or, the local container direct access data may also include the IP address of the target container group and the service port corresponding to the target container group. The target container direct access data may be container direct access data for direct access to the target set of containers.
In the embodiment of the invention, after receiving the container direct access data reported by the container arrangement engine, the client can store the container direct access data locally as the local container direct access data. When the client side has a direct connection access requirement, the target container direct connection access data of the target container group can be determined according to the local container direct connection access data, and the target container group is directly accessed according to the target container direct connection access data.
And S220, generating a container group direct access request according to the target container direct access data.
The container group direct access request can be an access request generated by a client, and can carry target container direct access data to perform direct access on a target container group.
Correspondingly, the client side can generate a container group direct access request according to the target container direct access data. Illustratively, the client may generate a URL (Uniform Resource Locator) according to the target container direct access data, and add a direct access identifier to the URL to obtain a final container group direct access request.
S230, sending the container group direct access request to a container arrangement engine so as to directly access the target container group through the container group direct access request.
Correspondingly, after the client generates the container group direct access request, the container group direct access request can be sent to the container arrangement engine, and the container group direct access request includes the target container group IP address or includes both the target container group IP address and the service port corresponding to the target container group, so that the container arrangement engine can determine the target container group to be directly accessed by the client through the container group direct access request and directly access the target container group.
According to the technical scheme, the container group IP address is used as the container direct connection access data, a single node can be compatible with a plurality of container groups with the same service, the problem of port conflict can be effectively avoided, the resource utilization rate is improved, the mapping relation between the service port and the node port does not need to be maintained, and therefore the maintenance cost is reduced. In addition, the configuration work of the container arrangement engine can be reduced by using the IP address of the container group as the direct access data of the container, so that the configuration cost and the learning cost of the container arrangement engine are reduced. Meanwhile, the container arrangement engine can dynamically monitor the service configuration file through the flow import gateway so as to obtain a dynamic monitoring result in real time and report the dynamic monitoring result to the client, so that the automatic synchronization of the IP addresses of the container groups is realized, and the problem of service interruption is effectively avoided. In addition, the traffic import gateway in the container arrangement engine can be compatible with the external gateway of the container arrangement engine, so that the compatibility is stronger. Therefore, the container-based access data processing method provided by the embodiment of the invention can effectively improve the direct access performance of the container group.
Fig. 6 is a schematic flowchart of a client accessing a container group according to a second embodiment of the present invention. In a specific example, as shown in fig. 6, kubernets are used as a container arrangement engine, and an ingress-nginx gateway is used as a traffic import gateway of the kubernets, a user (i.e., a client) may determine a target container group IP address of a target container group and a service port of the target container group according to local container direct access data, so as to generate a container group direct access request in a URL form of the target container group according to the target container group IP address and the service port of the target container group, where the request may carry information such as the target container group IP address, the service port of the target container group, and a direct access identifier. Accordingly, the user sends a container group direct access request to kubernets. The nginx module in the Kubernetes can acquire the direct access identifier in the container group direct access request, and judge whether the container group direct access request is the situation of directly accessing the container group according to the direct access identifier. If the situation that the container group direct-connection access request is the direct-connection access container group is determined according to the direct-connection access identifier, the target container group IP address of the target container group and the service port of the target container group can be obtained through the nginx module according to the container group direct-connection access request combination request parameter, and the target container group is accessed directly according to the target container group IP address and the service port of the target container group. If the situation that the volume group direct access request is not the situation of directly accessing the container group is determined according to the direct access identifier, a corresponding load balancer can be found in a native mode of an ingress-nginx gateway, and the load balancer polls and sends the load balancer to each related container group. If the direct access request of the container group can reach the target container group, the target container group is normally accessed and relevant services are executed; otherwise, returning error information to the user, such as returning "404 page" information.
Fig. 7 is a timing diagram of data flow of a directly connected access container group according to a second embodiment of the present invention. In a specific example, as shown in fig. 7, kubernets are used as a container arrangement engine, and an ingress-nginx gateway is used as a traffic import gateway of the kubernets, and after a container group exposes a service port of a container, the kubernets may generate a service file, and obtain a container group IP address of each container group through the service file. Optionally, kubernets may bind the IP addresses of the respective container groups through Labels tags according to the service file. In this case, when the container group is restarted, the IP address of the container group changes, and the service file can still find the corresponding container group through the Labels of the Labels, and obtain the new IP address of the container group. Specifically, the Kubernetes can dynamically monitor each service file in real time through an ingress module in the ingress-nginx gateway, so as to obtain the container group IP address information of each container group through the service file, and construct container direct connection access data according to the obtained container group IP address information, and report the container direct connection access data to the client. The ingress module can continuously monitor the update condition of the IP address of each container group, and when the IP address of a newly added container group or the IP address of an existing container group changes, the ingress module will report the IP address of the updated container group to the client again. The client can automatically maintain the IP address of the container group and the service port information as the local container to directly access the data.
Correspondingly, the client can determine the target container group IP address of the target container group and the service port of the target container group according to the local container direct access data, so as to generate a container group direct access request in the form of URL of the target container group according to the target container group IP address and the service port of the target container group, wherein the request can carry information such as the target container group IP address, the service port of the target container group, the direct access identifier and the like. The client may send a container group direct access request to kubernets. The nginx module in the Kubernetes can acquire the direct access identifier in the container group direct access request, and judge whether the container group direct access request is the situation of directly accessing the container group according to the direct access identifier. If the situation that the container group direct-connection access request is the direct-connection access container group is determined according to the direct-connection access identifier, a target container group IP address (host) and a service port (port) of the target container group can be obtained through the nginx module according to the container group direct-connection access request combination request parameter, and the target container group IP address and the service port of the target container group are reversely proxied to http:// host: port, so that the effect of directly accessing the target container group is achieved. If the situation that the volume group direct access request is not the situation of directly accessing the container group is determined according to the direct access identifier, a corresponding load balancer can be found in a native mode of an ingress-nginx gateway, and the load balancer polls and sends the load balancer to each related container group. If the direct access request of the container group can reach the target container group, the target container group is normally accessed and relevant services are executed; otherwise, returning error information to the user.
The traffic analysis module may also use other gateway modules such as openness (a high-performance Web platform based on Nginx and Lua) or kong (an API gateway for forwarding API communication).
According to the embodiment of the invention, the client side determines the target container direct access data of the target container group according to the local container direct access data comprising the IP address of the target container group, and generates the container group direct access request according to the target container direct access data, so that the container group direct access request is sent to the container arrangement engine, and the target container group is directly accessed through the container group direct access request, the problems of port conflict, service interruption, high configuration cost and maintenance cost and the like of the existing container group direct access method are solved, the configuration cost and maintenance cost of the container group direct access are reduced, and the direct access performance of the container group is improved.
It should be noted that any permutation and combination between the technical features in the above embodiments also belong to the scope of the present invention.
EXAMPLE III
Fig. 8 is a schematic diagram of a container-based access data processing system according to a third embodiment of the present invention, and as shown in fig. 8, the structure of the container-based access data processing system includes: a container orchestration engine 310 and a client 320, the container orchestration engine and the client being communicatively coupled; wherein:
the container orchestration engine 310 is configured to generate a service configuration file corresponding to each node in the container orchestration engine 310; wherein each node comprises at least one container group; dynamically monitoring each service configuration file through a traffic import gateway; and reporting the container direct access data of each node content group to the client 320 according to the dynamic monitoring result of the traffic import gateway. The client 320 is used for determining target container direct access data of the target container group according to the local container direct access data; generating a container group direct access request according to the target container direct access data; a container group direct access request is sent to the container orchestration engine 310 to directly access the target container group through the container group direct access request.
The container direct connection access data comprises a container group IP address; the local container direct access data includes a target container group IP address.
Optionally, the container orchestration engine 310 is further configured to generate each service configuration file according to a service port of each container group in the node when the service port is detected; and acquiring the IP address of each container group according to the service configuration file.
Optionally, the container orchestration engine 310 is further configured to configure a container group tag for each container group IP address through the service profile; establishing a mapping relation between the IP address of the container group and the label of the container group; and storing the mapping relation between the IP address of the container group and the label of the container group in the service configuration file.
Optionally, the traffic import gateway includes a synchronization configuration module; the container orchestration engine 310 is further configured to perform dynamic monitoring on each service configuration file through the synchronization configuration module, so as to obtain the dynamic monitoring result; sending the updated container direct access data to the client under the condition that the synchronous configuration module determines that the dynamic monitoring result comprises the updated container direct access data; and updating the container direct access data, wherein the updating the container direct access data comprises newly added container direct access data and/or changed container direct access data.
Optionally, the traffic import gateway includes a traffic analysis module; the container orchestration engine 310 is further configured to obtain a container group direct access request sent by the client; analyzing the container group direct connection access request through the flow analysis module to obtain target container direct connection access data; and directly accessing the target container group according to the target container direct access data.
After the container arrangement engine generates the service configuration files corresponding to the nodes in the container arrangement engine, the embodiment of the invention carries out dynamic monitoring on the service configuration files through the flow import gateway in the container arrangement engine, and reports the container direct connection access data of the content groups of the nodes to the client according to the dynamic monitoring result of the flow import gateway. The client side can determine target container direct access data of a target container group according to the local container direct access data, and generate a container group direct access request according to the target container direct access data so as to send the container group direct access request to the container arrangement engine, so that the target container group can be directly accessed through the container group direct access request, the local container direct access data of the client side can also comprise a target container group IP address as the container direct access data comprises the container group IP address, the client side can directly access the target container group according to the target container direct access data comprising the target container group IP address, the problems of port conflict and service interruption, high configuration cost and maintenance cost and the like of the existing container group direct access method are solved, and the configuration cost and the maintenance cost of the container group direct access are reduced, the direct access performance of the container group is improved.
Example four
Fig. 9 is a schematic diagram of a container-based access data processing apparatus according to a fourth embodiment of the present invention, where the container-based access data processing apparatus may be configured in a container orchestration engine, and as shown in fig. 9, the container-based access data processing apparatus includes: a configuration file generation module 410 and a traffic import gateway 420, wherein:
a configuration file generating module 410, configured to generate a service configuration file corresponding to each node in the container arrangement engine; wherein each of the nodes comprises at least one container group;
a traffic import gateway 420, configured to perform dynamic monitoring on each service configuration file; reporting the container direct access data of each node content group to the client according to the dynamic monitoring result; wherein the container direct access data comprises a container group IP address.
After the container arrangement engine generates the service configuration files corresponding to the nodes in the container arrangement engine, the embodiment of the invention carries out dynamic monitoring on the service configuration files through the flow import gateway in the container arrangement engine, and reports the container direct connection access data of the content groups of the nodes to the client according to the dynamic monitoring result of the flow import gateway. The client side can determine target container direct access data of a target container group according to the local container direct access data, and generate a container group direct access request according to the target container direct access data so as to send the container group direct access request to the container arrangement engine, so that the target container group can be directly accessed through the container group direct access request, the local container direct access data of the client side can also comprise a target container group IP address as the container direct access data comprises the container group IP address, the client side can directly access the target container group according to the target container direct access data comprising the target container group IP address, the problems of port conflict and service interruption, high configuration cost and maintenance cost and the like of the existing container group direct access method are solved, and the configuration cost and the maintenance cost of the container group direct access are reduced, the direct access performance of the container group is improved.
Optionally, the configuration file generating module 410 is specifically configured to: under the condition that the service port of each container group in the node is detected, generating each service configuration file according to the service port; and acquiring the IP address of each container group according to the service configuration file.
Optionally, the configuration file generating module 410 is further configured to: configuring a container group label for each container group IP address through the service configuration file; establishing a mapping relation between the IP address of the container group and the label of the container group; and storing the mapping relation between the IP address of the container group and the label of the container group in the service configuration file.
Optionally, the traffic import gateway 420 includes a synchronization configuration module; the synchronous configuration module is used for dynamically monitoring each service configuration file to obtain the dynamic monitoring result; sending the updated container direct access data to the client under the condition that the dynamic monitoring result comprises the updated container direct access data; and updating the container direct access data, wherein the updating the container direct access data comprises newly added container direct access data and/or changed container direct access data.
Optionally, the traffic import gateway 420 includes a traffic parsing module; the flow analysis module is used for acquiring a container group direct connection access request sent by the client; analyzing the container group direct connection access request to obtain target container direct connection access data; and directly accessing the target container group according to the target container direct access data.
The container-based access data processing device can execute the container-based access data processing method provided by the first embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the container-based access data processing method provided in the first embodiment of the present invention.
EXAMPLE five
Fig. 10 is a schematic diagram of a container-based access data processing apparatus according to a fifth embodiment of the present invention, where the container-based access data processing apparatus may be configured at a client, and as shown in fig. 10, the container-based access data processing apparatus includes: a target container direct access data determining module 510, a container group direct access request generating module 520, and a container group direct access request sending module 530, where:
a target container direct access data determining module 510, configured to determine target container direct access data of a target container group according to the local container direct access data;
a container group direct access request generating module 520, configured to generate a container group direct access request according to the target container direct access data;
a container group direct access request sending module 530, configured to send the container group direct access request to a container orchestration engine, so as to directly access the target container group through the container group direct access request; wherein the local container direct access data comprises a target container group IP address.
According to the embodiment of the invention, the client side determines the target container direct access data of the target container group according to the local container direct access data comprising the IP address of the target container group, and generates the container group direct access request according to the target container direct access data, so that the container group direct access request is sent to the container arrangement engine, and the target container group is directly accessed through the container group direct access request, the problems of port conflict, service interruption, high configuration cost and maintenance cost and the like of the existing container group direct access method are solved, the configuration cost and maintenance cost of the container group direct access are reduced, and the direct access performance of the container group is improved.
The container-based access data processing device can execute the container-based access data processing method provided by the second embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. For details of the technique not described in detail in this embodiment, reference may be made to the container-based access data processing method provided in the second embodiment of the present invention.
EXAMPLE six
An embodiment of the present invention further provides a computer storage medium storing a computer program, which when executed by a computer processor is configured to execute the container-based access data processing method according to any one of the above-mentioned embodiments of the present invention. For example, the computer program, when executed by a computer processor, is for performing: generating service configuration files corresponding to all nodes in the container arrangement engine; wherein each of the nodes comprises at least one container group; dynamically monitoring each service configuration file through a traffic import gateway; reporting container direct access data of each node content group to a client according to the dynamic monitoring result of the traffic import gateway; wherein the container direct access data comprises a container group IP address. For another example, the computer program, when executed by a computer processor, is for performing: determining target container direct access data of a target container group according to the local container direct access data; generating a container group direct access request according to the target container direct access data; sending the container group direct access request to a container orchestration engine to directly access the target container group through the container group direct access request; wherein the local container direct access data comprises a target container group IP address.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, 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. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, Radio Frequency (RF), etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A container-based access data processing method is applied to a container arrangement engine and comprises the following steps:
generating service configuration files corresponding to all nodes in the container arrangement engine; wherein each of the nodes comprises at least one container group;
dynamically monitoring each service configuration file through a traffic import gateway;
reporting container direct access data of each node content group to a client according to the dynamic monitoring result of the traffic import gateway;
wherein the container direct access data comprises a container group IP address.
2. The method of claim 1, wherein generating the service profile corresponding to each node in the container orchestration engine comprises:
under the condition that the service port of each container group in the node is detected, generating each service configuration file according to the service port;
after the generating of the service configuration file corresponding to each node in the container orchestration engine, the method further includes:
and acquiring the IP address of each container group according to the service configuration file.
3. The method of claim 2, further comprising, after generating each of the service profiles according to the container group address:
configuring a container group label for each container group IP address through the service configuration file;
establishing a mapping relation between the IP address of the container group and the label of the container group;
and storing the mapping relation between the IP address of the container group and the label of the container group in the service configuration file.
4. The method of claim 1, wherein the traffic ingress gateway comprises a synchronization configuration module;
the dynamic monitoring of each service configuration file through the traffic import gateway includes:
dynamically monitoring each service configuration file through the synchronous configuration module to obtain the dynamic monitoring result;
the reporting of the container direct access data of each node content group to the client according to the dynamic monitoring result of the traffic import gateway includes:
sending the updated container direct access data to the client under the condition that the synchronous configuration module determines that the dynamic monitoring result comprises the updated container direct access data;
and updating the container direct access data, wherein the updating the container direct access data comprises newly added container direct access data and/or changed container direct access data.
5. The method of claim 1, wherein the traffic ingress gateway comprises a traffic resolution module; the method further comprises the following steps:
acquiring a container group direct connection access request sent by the client;
analyzing the container group direct connection access request through the flow analysis module to obtain target container direct connection access data;
and directly accessing the target container group according to the target container direct access data.
6. A container-based access data processing method is applied to a client and comprises the following steps:
determining target container direct access data of a target container group according to the local container direct access data;
generating a container group direct access request according to the target container direct access data;
sending the container group direct access request to a container orchestration engine to directly access the target container group through the container group direct access request;
wherein the local container direct access data comprises a target container group IP address.
7. A container-based access data processing apparatus, configured in a container orchestration engine, comprising:
the configuration file generation module is used for generating service configuration files corresponding to all nodes in the container arrangement engine; wherein each of the nodes comprises at least one container group;
the flow import gateway is used for dynamically monitoring each service configuration file; reporting the container direct access data of each node content group to the client according to the dynamic monitoring result;
wherein the container direct access data comprises a container group IP address.
8. A container-based access data processing apparatus, configured at a client, comprising:
the target container direct access data determining module is used for determining target container direct access data of the target container group according to the local container direct access data;
the container group direct access request generation module is used for generating a container group direct access request according to the target container direct access data;
the container group direct access request sending module is used for sending the container group direct access request to a container arrangement engine so as to directly access the target container group through the container group direct access request;
wherein the local container direct access data comprises a target container group IP address.
9. A container-based access data processing system comprising a container orchestration engine and a client, the container orchestration engine and the client being communicatively coupled; wherein:
the container arrangement engine is used for generating service configuration files corresponding to all nodes in the container arrangement engine; wherein each of the nodes comprises at least one container group; dynamically monitoring each service configuration file through a traffic import gateway; reporting container direct access data of each node content group to a client according to the dynamic monitoring result of the traffic import gateway;
the client is used for determining target container direct access data of the target container group according to the local container direct access data; generating a container group direct access request according to the target container direct access data; sending the container group direct access request to a container orchestration engine to directly access the target container group through the container group direct access request;
wherein the container direct access data comprises a container group IP address; the local container direct access data comprises a target container group IP address.
10. A computer storage medium on which a computer program is stored, which program, when being executed by a processor, carries out a container-based access data processing method according to any one of claims 1 to 5, or carries out a container-based access data processing method according to claim 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110007739.5A CN112702441B (en) | 2021-01-05 | 2021-01-05 | Container-based access data processing method, device, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110007739.5A CN112702441B (en) | 2021-01-05 | 2021-01-05 | Container-based access data processing method, device, system and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112702441A true CN112702441A (en) | 2021-04-23 |
| CN112702441B CN112702441B (en) | 2023-06-30 |
Family
ID=75514730
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110007739.5A Active CN112702441B (en) | 2021-01-05 | 2021-01-05 | Container-based access data processing method, device, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112702441B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113347043A (en) * | 2021-06-25 | 2021-09-03 | 武汉悦学帮网络技术有限公司 | Gateway management method, device, gateway management platform and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110427249A (en) * | 2019-07-26 | 2019-11-08 | 重庆紫光华山智安科技有限公司 | Method for allocating tasks, pod initial method and relevant apparatus |
| CN110457134A (en) * | 2019-08-08 | 2019-11-15 | 杭州阿启视科技有限公司 | The method for establishing the video big data cloud platform based on container cloud and micro services framework |
| CN110912972A (en) * | 2019-11-07 | 2020-03-24 | 北京浪潮数据技术有限公司 | Service processing method, system, electronic equipment and readable storage medium |
| CN111431740A (en) * | 2020-03-16 | 2020-07-17 | 深信服科技股份有限公司 | Data transmission method, device, equipment and computer readable storage medium |
-
2021
- 2021-01-05 CN CN202110007739.5A patent/CN112702441B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110427249A (en) * | 2019-07-26 | 2019-11-08 | 重庆紫光华山智安科技有限公司 | Method for allocating tasks, pod initial method and relevant apparatus |
| CN110457134A (en) * | 2019-08-08 | 2019-11-15 | 杭州阿启视科技有限公司 | The method for establishing the video big data cloud platform based on container cloud and micro services framework |
| CN110912972A (en) * | 2019-11-07 | 2020-03-24 | 北京浪潮数据技术有限公司 | Service processing method, system, electronic equipment and readable storage medium |
| CN111431740A (en) * | 2020-03-16 | 2020-07-17 | 深信服科技股份有限公司 | Data transmission method, device, equipment and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 小咔啦眯: "Kubernetes Ingress的应用", 《HTTPS://BLOG.CSDN.NET/QQ_45631844/ARTICLE/DETAILS/112059235》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113347043A (en) * | 2021-06-25 | 2021-09-03 | 武汉悦学帮网络技术有限公司 | Gateway management method, device, gateway management platform and storage medium |
| CN113347043B (en) * | 2021-06-25 | 2022-11-22 | 武汉悦学帮网络技术有限公司 | Gateway management method, device, gateway management platform and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112702441B (en) | 2023-06-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110247784B (en) | Method and device for determining network topology structure | |
| CN107528862B (en) | Domain name resolution method and device | |
| CN109347998B (en) | Method and system for detecting IP address of DNS (Domain name Server) outlet server | |
| CN102047243A (en) | Request routing based on class | |
| CN107210924B (en) | Method and apparatus for configuring a communication system | |
| US8935377B2 (en) | Dynamic registration of listener resources for cloud services | |
| CN112637332B (en) | Service registration discovery method and system | |
| WO2019052058A1 (en) | Domain name redirecting method and system | |
| CN114301990A (en) | Node scheduling method, device and storage medium based on content distribution network | |
| CN103595743A (en) | Method of downloading application software, apparatus and system thereof | |
| CN112702441B (en) | Container-based access data processing method, device, system and storage medium | |
| CN110740355A (en) | Equipment monitoring method and device, electronic equipment and storage medium | |
| CN112637037B (en) | Cross-region container communication system, method, storage medium and computer equipment | |
| CN110572394B (en) | Access control method and device | |
| CN104955153A (en) | Method, device and appliances for discovering resources | |
| CN116566945A (en) | Access method and device for decentralised application, electronic equipment and storage medium | |
| CN116389599A (en) | Gateway service request processing method and device and cloud native gateway system management method and device | |
| CN112804313B (en) | Data synchronization method, device, equipment and medium based on cross-domain edge node | |
| CN114338279A (en) | Terminal access method and device and server | |
| CN109379453B (en) | Method and system for detecting IP address of DNS (Domain name Server) outlet server | |
| US10313254B1 (en) | Network management interface for a network element with network-wide information | |
| CN114327823A (en) | Method, system, terminal and storage medium for calling resources of micro-service cluster | |
| CN114172965A (en) | User service request and processing method, device and medium | |
| CN113285997B (en) | Data processing method, device, medium and product based on heterogeneous system | |
| CN115250236B (en) | Network element instruction adaptation method, device, system, electronic equipment and 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 |