Information processing method, first node, first cluster, storage medium, and product

Abstract

The application discloses an information processing method, which comprises the following steps: in a first node, deploying core components required by a first cluster in the form of a containerized workload hosted in the first cluster. The application also discloses a first node, a first cluster, a computer readable storage medium and a computer program product.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication, and particularly relates to an information processing method, a first node, a first cluster, a computer readable storage medium and a computer program product. BACKGROUND

[0002] A cloud native platform Kubernetes (K8s for short, using 8 to replace the 8 characters "ubernete" in the middle of the name) is an open source system for automatically deploying, scaling and managing containerized applications; components required for running K8s are collectively referred to as a control plane, and containerized workloads hosted in K8s are referred to as a data plane; the main function of K8s can be summarized as: when the control plane is working normally, K8s will automatically ensure that all containerized workloads in the data plane are deployed according to the expected specification and work normally according to the configuration information of the data plane.

[0003] In view of the above background, the control plane multiple replica deployment scheme or the external control cluster scheme is usually used in the related art to ensure the normal work of the control plane. However, in the above scheme, if a node fails, professional operation and maintenance personnel need to intervene in processing, and therefore, at least the problem of complexity exists in the scheme for ensuring the normal operation of the control plane provided in the related art. SUMMARY

[0004] The present application provides an information processing method, a first node, a first cluster, a computer readable storage medium and a computer program product.

[0005] The technical scheme of the present application embodiment is implemented as follows:

[0006] In a first aspect, the present application embodiment provides an information processing method applied to a first node, and the method comprises the following steps.

[0007] In the first node of the first cluster, core components required for running the first cluster are deployed in the form of containerized workloads hosted in the first cluster.

[0008] In a second aspect, the present application embodiment provides an information processing method applied to a first cluster, and the method comprises the following steps.

[0009] The first node of the first cluster is built, and in the first node, core components required for running the first cluster are deployed in the form of containerized workloads hosted in the first cluster;

[0010] N second nodes are added to the first cluster; N is a positive integer.

[0011] re-schedule core components deployed in the form of containerized workloads hosted in the first cluster in the first node to the second node so that core components deployed in the form of containerized workloads hosted in the first cluster are distributed to the second node.

[0012] In a third aspect, an embodiment of the present application provides a first node, comprising:

[0013] a processing module configured to deploy core components required for running the first cluster in the form of containerized workloads hosted in the first cluster.

[0014] In a fourth aspect, an embodiment of the present application provides a first node, comprising:

[0015] a memory configured to store executable instructions;

[0016] a processor configured to execute the executable instructions stored in the memory to implement the information processing method described above.

[0017] In a fifth aspect, an embodiment of the present application provides a first cluster, comprising a first node and N second nodes, wherein N is a positive integer, and the first node and the N second nodes cooperate to implement the information processing method described above.

[0018] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium having one or more computer programs stored thereon, wherein the one or more programs are executable by one or more processors to implement the steps of the information processing method described above.

[0019] In a seventh aspect, an embodiment of the present application provides a computer program product comprising a computer program, wherein the computer program, when executed by a processor, implements the steps of the information processing method described above.

[0020] The present application proposes a new way of deploying cluster core components, that is, deploying cluster core components in the form of original workloads of the cluster. In this way, when a fault occurs, new available core components can be pulled up through the high-availability feature of the original workloads of the cluster, thereby automatically ensuring that the cluster control plane components work normally and have high reliability. When there is a need for expansion / shrinking of the cluster, only the replica number parameter of the workload needs to be modified, which is simpler than the expansion / shrinking scheme in the related art. BRIEF DESCRIPTION OF DRAWINGS

[0021] Figure 1 Flowchart of the information processing method provided by an embodiment of the present application Figure 1

[0022] Figure 2 Flowchart of the information processing method provided by an embodiment of the present application​Figure 2 ;

[0023] Figure 3 A flowchart of a K8s cluster deployment scheme provided by an embodiment of the present application is shown in FIG. 1.

[0024] Figure 4 An architecture diagram of a K8s master node provided by an embodiment of the present application is shown in FIG. 2. Figure 1 ;

[0025] Figure 5 An architecture diagram of a K8s master node provided by an embodiment of the present application is shown in FIG. 3. Figure 2 ;

[0026] Figure 6 An architecture diagram of a K8s master node provided by an embodiment of the present application is shown in FIG. 4. Figure 3 ;

[0027] Figure 7 An architecture diagram of a K8s master node provided by an embodiment of the present application is shown in FIG. 5. Figure 4 ;

[0028] Figure 8 An architecture diagram of a K8s master node provided by an embodiment of the present application is shown in FIG. 6. Figure 5 ;

[0029] Figure 9 An architecture diagram of a K8s master node provided by an embodiment of the present application is shown in FIG. 7. Figure 6 ;

[0030] Figure 10 An architecture diagram of a K8s master node provided by an embodiment of the present application is shown in FIG. 8. Figure 7 ;

[0031] Figure 11 A schematic block diagram of a first node provided by an embodiment of the present application is shown in FIG. 9.

[0032] Figure 12 A schematic block diagram of a first cluster provided by an embodiment of the present application is shown in FIG. 10.

[0033] Figure 13 A schematic structural diagram of a communication device provided by an embodiment of the present application is shown in FIG. 11. DETAILED DESCRIPTION

[0034] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Here, the “another” or “yet another” mentioned in the description of the drawings does not refer to a specific embodiment, and the embodiments of the present application can be combined with each other without conflict.

[0035] It should be understood that the "embodiments of the present application" or "the foregoing embodiments" mentioned throughout the specification mean that the specific features, structures or characteristics related to the embodiments are included in at least one embodiment of the present application. Therefore, "in the embodiments of the present application" or "in the foregoing embodiments" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be applied in one or more embodiments in any suitable manner. In various embodiments of the present application, the size of the sequence number of each process described above does not mean the order of execution, and the execution order of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The sequence number of the embodiments of the present application described above is only for description, not representing the advantages and disadvantages of the embodiments.

[0036] Before explaining the present application, the scheme for ensuring the normal work of the control plane of K8s in the related art is described herein:

[0037] Control plane multi-copy deployment is a high availability scheme recommended by the K8s project. All components of the control plane of K8s are directly deployed on different hosts, which are called master nodes. In design, the components of the control plane themselves support such deployment to achieve high availability, so that as long as the number of failures in the several master nodes is less than half of the total number, the normal work of the entire control plane will not be affected. However, for the control plane multi-copy scheme, after a failure occurs in a certain master node, professional operation and maintenance personnel must intervene to handle it to restore normal work, which cannot be automatically handled by machines in most scenarios. Further, if the failure is a hardware problem, the recovery process will also involve backup machine application, component installation, cluster adjustment, etc. Under the constraints of enterprise IT management processes, it may take a very long time to go through various approvals; without handling the failure for a long time, multiple failures may accumulate, so that the state of the master nodes in the K8s cluster no longer meets the condition that "the number of failures is less than half of the total number", causing the control plane components of the cluster to fail to work normally.

[0038] External control cluster is to deploy another set of K8s (referred to as control cluster), and the control plane of the control cluster manages the components of the control plane of the current cluster, thereby ensuring the normal work of the components of the control plane of the current cluster. However, for the external control cluster scheme, it is mostly used in service multi-tenant cloud computing business scenarios, and professional personnel arranged by the cloud computing service provider maintain the control cluster, so that tenants do not need to care about its availability and only need to focus on their own business scenarios to deploy and schedule data plane workloads. However, from the perspective of tenants, many people do not want to choose this scheme of completely entrusting the control plane of the cluster to the operator due to privacy, convenience and cost. Further, in the scenario of self-built K8s cluster, this scheme cannot be used at all.

[0039] Figure 1 A flowchart of an information processing method according to an embodiment of the present application is shown in FIG. 1. The method is applied to a first node in which all components of a control plane of a first cluster are deployed. The method comprises the following steps. Figure 1

[0040] In step 101, in the first node of the first cluster, core components required by the first cluster are deployed in the form of containerized workloads hosted in the first cluster.

[0041] In the embodiment of the present application, the first node is a node configured to deploy all components of the control plane of the first cluster, also known as the master node.

[0042] In some embodiments, the first cluster is a cluster implemented using K8s, also known as a K8S cluster. A K8S cluster includes a plurality of physical machines or virtual machines, and each physical machine or virtual machine can be regarded as a node. K8S creates containers in the cluster in the form of pods, and a pod can include one or more containers that implement corresponding services.

[0043] In some embodiments, the core components include, but are not limited to, an application programming interface server (apiserver), a scheduler, a controller, and an etcd.

[0044] In the embodiment of the present application, the containerized workloads hosted in the first cluster are connected and interacted through a container network, and are automatically restarted when the containers abnormally exit or when the load fails. Thus, the containerized workloads have high availability. Then, the core components are deployed in the form of the containerized workloads hosted in the first cluster, and through the high availability feature of the containerized workloads, new available core components can be started, thereby automatically ensuring that the cluster control plane components work normally.

[0045] ​The embodiment of the present application provides an information processing method, which comprises the following steps: deploying, in a first node, a core component required by a first cluster in the form of a containerized workload hosted in the first cluster. That is, the present application provides a new way of deploying a cluster core component, i.e., deploying the cluster core component in the form of a workload native to the cluster. In this way, when a fault occurs, a new available core component can be started through the high-availability feature of the workload native to the cluster, thereby automatically ensuring that the cluster control plane component works normally and has high reliability. When there is a need for expansion or contraction of the cluster, only the replica parameter of the workload needs to be modified, which is simpler than the expansion or contraction scheme in the related art.

[0046] It should be noted that, in the scheme provided in the present application, the core component can be distributed on any node, and compared with the technical scheme in the related art, special configuration is not needed for the cluster master node.

[0047] In some embodiments, the step 101 of deploying, in a first node of a first cluster, a core component required by the first cluster in the form of a containerized workload hosted in the first cluster can be implemented through the following steps:

[0048] The step A1 comprises directly deploying a first component in the first node; wherein the first component comprises the core component.

[0049] It should be noted that the first component comprises the core component and a non-core component; wherein the non-core component is running on the first node and is used for maintaining a running container and providing a running environment.

[0050] The step A2 comprises deploying a second component in a data plane of the first cluster in the form of a stateless application deployment or a stateful application deployment or ensuring that all nodes run the same container; wherein the second component comprises the core component.

[0051] In some embodiments, M first data plane workloads are deployed in the data plane in the form of a stateful application deployment (StatefulSet); M is a positive integer; the M first data plane workloads are connected to each other through a headless service.

[0052] Here, M can be pre-set or determined based on an actual running environment, and the present application does not make a specific limitation thereon. Exemplarily, M can be set to 3.

[0053] In the embodiment of the present application, deploying the M first data plane workloads in the form of a StatefulSet can be understood as using a StatefulSet workload controller to manage the M first data plane workloads.

[0054] In some embodiments, the first data plane workload is an etcd component deployed on the cluster data plane.

[0055] On the data plane, the second data plane workload, the third data plane workload and the fourth data plane workload are deployed in the form of a stateless application Deployment.

[0056] In the embodiments of the present application, the second data plane workload, the third data plane workload and the fourth data plane workload are deployed in the form of a Deployment, which can be understood as using a Deployment workload controller to manage the second data plane workload, the third data plane workload and the fourth data plane workload.

[0057] In some embodiments, the second data plane workload is an apiserver component, also known as a kube-apiserver workload, deployed on the cluster data plane; the third data plane workload is a controller component, also known as a kube-controller-manager workload, deployed on the cluster data plane; and the fourth data plane workload is a scheduler component, also known as a kube-scheduler workload, deployed on the cluster data plane.

[0058] On the data plane, the fifth data plane workload is deployed in the form of ensuring that all nodes run the same container (DaemonSet).

[0059] In the embodiments of the present application, the fifth data plane workload is deployed in the form of a DaemonSet, which can be understood as using a DaemonSet workload controller to manage the fifth data plane workload.

[0060] In some embodiments, the fifth data plane workload is a kube-proxy workload / component deployed on the cluster data plane.

[0061] On the data plane, the sixth data plane workload is deployed in the form of a stateless application Deployment; and the second component includes M first data plane workloads, the second data plane workload, the third data plane workload, the fourth data plane workload, the fifth data plane workload and the sixth data plane workload.

[0062] In the embodiments of the present application, the sixth data plane workload is deployed in the form of a Deployment, which can be understood as using a Deployment workload controller to manage the sixth data plane workload.

[0063] In some embodiments, the sixth data plane workload is a coredns load / component deployed on the cluster data plane.

[0064] Step A3, establishing a connection of the first component and the second component.

[0065] In the embodiments of the present application, the first control plane workload and the M first data plane workloads, the first control plane workload and the second control plane workload, the second control plane workload and the third control plane workload, the second control plane workload and the fourth control plane workload, the second control plane workload and the fifth workload, the second control plane workload and the fifth data plane workload, and the second control plane workload and the sixth data plane workload are connected through a network; wherein the first component includes the first control plane workload, the second control plane workload, the third control plane workload, the fourth control plane workload and the fifth workload.

[0066] Here, the network connection through the network can be based on a cloud communication channel, or other wired or wireless communication channels for network communication.

[0067] Here, the network can be a network conforming to the requirements of the 3GPP standard, referred to as a 3GPP network. Generally, the 3GPP network is operated by an operator, including but not limited to the 5th generation mobile communication technology (5G) network (referred to as 5G network), the 4th generation mobile communication technology (4G) network (referred to as 4G network), the 3th generation mobile communication technology (3G) network (referred to as 3G network) and the 2th generation mobile communication technology (2G) network (referred to as 2G network) and the like.

[0068] In the embodiments of the present application, the virtual network protocol address (Cluster IP) provided by the service (Service) function and only accessed within the first cluster is connected with the second data plane workload and the fifth workload, the M first data plane workloads and the second data plane workload, the second data plane workload and the third data plane workload, the second data plane workload and the fourth data plane workload, the second data plane workload and the fifth data plane workload, and the second data plane workload and the sixth data plane workload.

[0069] Step A4, migrating the traffic of the core component in the first component to the core component in the second component.

[0070] Step A5, uninstalling the core component in the first component.

[0071] In the embodiments of the present application, the first control plane workload, the second control plane workload, the third control plane workload and the fourth control plane workload are closed and removed.

[0072] Figure 2 A flowchart of an information processing method provided in the embodiments of the present application is shown in FIG. 1. Figure 2 As shown in FIG. 1, the method is applied to a first cluster, and the method comprises the following steps.

[0073] Step 201, building a first node of the first cluster, and in the first node, deploying core components required for running the first cluster in the form of containerized workloads hosted in the first cluster.

[0074] Step 202, adding N second nodes to the first cluster.

[0075] Wherein, N is a positive integer.

[0076] In the embodiments of the present application, in the second node, a first rule is created; wherein the first rule is used to indicate that a request for accessing a virtual network protocol address only accessed within the first cluster corresponding to the second data plane workload is forwarded to a port of the first node already in the first cluster; in the first node, based on the first rule, the second data plane workload is accessed using the virtual network protocol address only accessed within the first cluster provided by the service function; after the fifth workload is started, the fifth data plane workload is automatically deployed in the data plane corresponding to the second data plane workload, and the update process is taken over by the fifth data plane workload.

[0077] Step 203, rescheduling the core components deployed in the form of containerized workloads hosted in the first cluster in the first node, so that the core components deployed in the form of containerized workloads hosted in the first cluster are distributed to the second node.

[0078] In the embodiment, the affinity configuration of the core component deployed in the first node is modified to distribute the core component to the second node.

[0079] It should be noted that the same steps and the same content in other embodiments will be described with reference to the description of other embodiments, and will not be described here.

[0080] Next, taking the first cluster as an example, the exemplary application of the embodiment in an actual application scenario will be described.

[0081] The present application proposes a method of fusing the control plane and the data plane, converting the control plane components of K8s into the workloads of the data plane, and automatically ensuring the normal work of the control plane components of the cluster through the high availability of the data plane when a fault occurs. Further, the mixed deployment scheme of the control plane and the data plane provides a feasible idea for the full-automatic processing of fault recovery.

[0082] Figure 3 is a flowchart of a K8s cluster deployment scheme provided by the present application, as shown in Figure 3 .

[0083] Step 301, deploy the K8s master node normally.

[0084] In some embodiments, referring to Figure 4 , a single master node of the cluster is first built, and the core components of the control plane (etcd, kube-apiserver, kube-controller-manager, kube-scheduler) and the kubelet component are directly deployed on the host; the kube-proxy workload is deployed in the data plane of K8s in the form of DaemonSet, and the coredns workload is deployed in the form of Deployment, that is, the link for communication between the core components of the control plane, the kubelet component, the kube-proxy workload and the coredns workload in the master node is added.

[0085] Step 302, deploy three storage components in the data plane in the form of StatefulSet, as the slave nodes of the storage components on the master node.

[0086] In some embodiments, referring to Figure 5In the data plane, three etcd workloads such as etcd-0, etcd-1 and etcd-2 are deployed by means of StatefulSet, and the three etcd workloads in the data plane are connected with the etcd component of the control plane of the master node to form a cluster.

[0087] At this time, the three etcd workloads can communicate with each other through the headless service by means of the coredns workload in the data plane, and the three etcd workloads and the etcd component of the control plane can communicate with each other through the host network; because the deployment of the workloads in the StatefulSet is sequential and synchronous, that is, a single workload will start the deployment and initialization process only after the deployment and initialization process of all workloads with a smaller serial number are completed; that is, at any time, there will be no more than one etcd node in the initialization process and not working normally; for an etcd cluster composed of one control plane etcd node and three data plane etcd nodes, at any time, there is at most one node in the initialization process, and the etcd cluster can always work normally.

[0088] Among them, the core components of the control plane, the kubelet component, the kube-proxy workload and the coredns workload are connected with each other through the host network.

[0089] Step 303, using Deployment to deploy the application programming interface server / controller / scheduler component in the data plane, and exposing a new application programming interface server (apiserver) address.

[0090] In some embodiments, referring to Figure 6 In the data plane, the kube-apiserver workload, the kube-controller-manager workload and the kube-scheduler workload are sequentially deployed by means of Deployment; among them, the kube-apiserver workload can be connected to the three nodes of the etcd cluster in the data plane by using the Cluster IP provided by the Service function, by means of the kube-proxy workload in the data plane; the kube-controller-manager workload and the kube-scheduler workload in the data plane can be connected to the kube-apiserver workload in the data plane by using the Cluster IP provided by the Service function.

[0091] It should be noted that the three nodes of the etcd cluster in the data plane, the kube-apiserver workload in the data plane, the kube-controller-manager workload in the data plane, and the kube-scheduler workload in the data plane are connected to each other through a container network.

[0092] Step 304, modify the kube-proxy / coredns / kubelet component configuration to point to the new application programming interface server (apiserver) service using Deployment deployment.

[0093] It should be noted that the control plane traffic is migrated to the newly created workload,

[0094] In some embodiments, referring to Figure 7 In the data plane, the deployed kube-proxy workload and coredns workload are modified to connect to the kube-apiserver workload in the data plane using the Cluster IP provided by the Service function. When the kube-proxy workload is restarted, it will reuse the existing rules and connect to the kube-apiserver workload in the data plane because it will not affect the ipvs rules already configured on the node. After the kube-proxy workload is started, it will reuse the existing rules and connect to the kube-apiserver workload in the data plane. When the coredns workload is restarted, the rolling update mechanism of the Deployment ensures that at least one workload is always working normally, so the restart process will not cause connectivity problems between other workloads.

[0095] In some embodiments, referring to Figure 8 On the current master node, the kubelet configuration file is modified to connect to the kube-apiserver workload in the data plane using the Cluster IP provided by the Service function. When the kubelet is restarted to take effect the new configuration, it will not affect the running containers on the master node, in other words, it will not affect the kube-proxy workload in the data plane. Therefore, after the kubelet is restarted, it can correctly use the Cluster IP provided by the Service function to connect to the kube-apiserver workload in the data plane.

[0096] Step 305, remove the K8s core components such as control plane controllers deployed on the master node.

[0097] In some embodiments, referring to Figure 9On the current master node, the functions provided by the control plane components (etcd, kube-apiserver, kube-controller-manager, kube-scheduler) directly deployed in the host have all been replaced by the corresponding workloads in the data plane, and the etcd, kube-apiserver, kube-controller-manager and kube-scheduler components directly deployed on the master node host can be closed and removed.

[0098] In some embodiments, with reference to Figure 10 In the data plane, the configuration of the etcd workload is modified, and the etcd originally deployed on the master node host is removed from the etcd cluster, and the cluster size is changed to 3 nodes. According to the update rule of the StatefulSet, the 3 etcd workloads in the data plane will be restarted in turn, and no more than 1 node will be unavailable, so that the entire Kubernetes cluster will not be unavailable. At this point, the control plane components of the Kubernetes cluster are all deployed on a single master node, and all run as workloads in the data plane in the cluster.

[0099] It should be noted that the present application designs a component migration deployment method based on the native Kubernetes, and the related components are migrated from the native scheme to the new scheme, and lossless migration can be guaranteed during the migration process.

[0100] Step 306, add new cluster nodes to meet the cluster size requirement.

[0101] Next, a single master node cannot meet the demand for high availability, and more hosts need to be added to the Kubernetes cluster. On any host planned to be added to the cluster, first create a temporary rule in ipvs: requests to access the Cluster IP of the kube-apiserver workload are forwarded to the NodePort of the host already in the cluster. The kubelet on the host can use the Cluster IP provided by the Service to access the kube-apiserver workload through this temporary rule. After the kubelet starts, it will automatically deploy the kube-proxy workload on the data plane corresponding to the host, and the kube-proxy workload will take over the update process of ipvs, including automatically overwriting the temporary rule mentioned earlier. At this point, the new host has been added to the Kubernetes cluster, and repeating this step can add multiple hosts to the cluster until the cluster size requirement is met.

[0102] Further, the K8s core components are rescheduled for the cluster to meet the high-availability requirement of the components.

[0103] In the data plane, the affinity configuration of the deployed etcd workloads is modified to be distributed to different host nodes according to the high-availability requirement. During the modification, according to the update rule of the StatefulSet, the three etcd workloads in the data plane are restarted in sequence, and no more than one node is unavailable, so that the entire Kubernetes cluster is not unavailable.

[0104] In the data plane, the affinity configuration of the deployed kube-apiserver, kube-controller-manager, and kube-scheduler workloads is modified to be distributed to different host nodes according to the high-availability requirement. During the modification, according to the rolling update rule of the Deployment, at least one workload is available at any time, and the availability of the entire Kubernetes cluster is not affected. At this point, the high-availability Kubernetes cluster building work is completed.

[0105] In this way, the core components (etcd, kube-apiserver, kube-controller-manager, and kube-schedule) of the Kubernetes cluster deployed by us are in the form of Kubernetes native workloads (Deployment, StatefulSet). If a certain instance fails and hangs up, the controller of the Kubernetes workload will automatically create a new instance, which has higher reliability than the original Kubernetes control plane node. Moreover, if subsequent expansion of the number of instances of these core components is required, only the number of replicas of the corresponding workloads needs to be modified, and the expansion process is transparent and imperceptible to users and operation and maintenance personnel.

[0106] Embodiments of the present application provide a first node, which can be applied to Figure 1 In the information processing method provided by the corresponding embodiments, reference is made to Figure 11 As shown in the figure, the first node 1100 includes:

[0107] The processing module 1101 is configured to deploy the core components required for running the first cluster in the form of containerized workloads hosted in the first cluster.

[0108] In other embodiments of the present application, the processing module 1101 is configured to directly deploy the first components in the first node; wherein the first components include the core components;

[0109] The processing module 1101 is configured to deploy, in a data plane, a second component in a stateless application deployment manner or a stateful application deployment manner or a manner of ensuring that all nodes run the same container; the second component comprises a core component;

[0110] The processing module 1101 is configured to establish a connection between the first component and the second component.

[0111] The processing module 1101 is configured to migrate traffic of the core component in the first component to the core component in the second component.

[0112] The processing module 1101 is configured to offload the core component in the first component.

[0113] In other embodiments of the present application, the processing module 1101 is configured to deploy, in a data plane, M first data plane workloads in a stateful application deployment manner; M is a positive integer; the M first data plane workloads are connected to each other through a headless service;

[0114] The processing module 1101 is configured to deploy, in a data plane, a second data plane workload, a third data plane workload and a fourth data plane workload in a stateless application deployment manner.

[0115] The processing module 1101 is configured to deploy, in a data plane, a fifth data plane workload in a manner of ensuring that all nodes run the same container.

[0116] The processing module 1101 is configured to deploy, in a data plane, a sixth data plane workload in a stateless application deployment manner; wherein the second component comprises the M first data plane workloads, the second data plane workload, the third data plane workload, the fourth data plane workload, the fifth data plane workload and the sixth data plane workload.

[0117] In other embodiments of the present application, the processing module 1101 is configured to connect, through a network, the first control plane workload and the M first data plane workloads, the first control plane workload and the second control plane workload, the second control plane workload and the third control plane workload, the second control plane workload and the fourth control plane workload, the second control plane workload and the fifth workloads, the second control plane workload and the fifth data plane workload, and the second control plane workload and the sixth data plane workload; wherein the first component comprises the first control plane workload, the second control plane workload, the third control plane workload, the fourth control plane workload and the fifth workloads.

[0118] The processing module 1101 is configured to connect the second data plane workload and the fifth workload, the M first data plane workloads and the second data plane workload, the second data plane workload and the third data plane workload, the second data plane workload and the fourth data plane workload, the second data plane workload and the fifth data plane workload, and the second data plane workload and the sixth data plane workload through the virtual network protocol address of the service function that is only accessible within the first cluster.

[0119] In other embodiments of the present application, the core components include a first control plane workload, a second control plane workload, a third control plane workload, and a fourth control plane workload; and the processing module 1101 is configured to shut down and remove the first control plane workload, the second control plane workload, the third control plane workload, and the fourth control plane workload.

[0120] The above device embodiments are described similarly to the above method embodiments, and have similar beneficial effects to the method embodiments. For technical details not disclosed in the device embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

[0121] It should be noted that, in the embodiments of the present application, if the information processing method described above is realized in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for causing an end device to execute all or part of the method embodiments of the present application. The storage medium described above includes: a U disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk, and various media that can store program codes. Thus, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0122] Embodiments of the present application provide a first cluster, which can be applied to Figure 2 In the information processing method provided by the corresponding embodiments, the first cluster 1200 includes a first node 1201 and N second nodes 1202. Figure 12 As shown in the figure, the first cluster 1200 includes a first node 1201 and N second nodes 1202.

[0123] The first node 1201 and the N second nodes 1202 cooperate to execute the following information processing method:

[0124] build a first node of a first cluster, and in the first node, deploy core components required for running the first cluster in the form of containerized workloads hosted in the first cluster;

[0125] add N second nodes to the first cluster; N is a positive integer;

[0126] reschedule the core components deployed in the first node in the form of containerized workloads hosted in the first cluster, so that the core components deployed in the form of containerized workloads hosted in the first cluster are distributed into the second nodes.

[0127] In other embodiments of the present application, the first node 1201 and the N second nodes 1202 cooperate to perform the following information processing method:

[0128] In the second node, create a first rule; wherein the first rule is used to indicate that a request for accessing a virtual network protocol address that is only accessed within the first cluster corresponding to the second data plane workload is forwarded to a port of the first node that has been in the first cluster;

[0129] In the first node, based on the first rule, access the second data plane workload using the virtual network protocol address that is only accessed within the first cluster based on service function provision;

[0130] After the fifth workload is started, automatically deploy a fifth data plane workload in the data plane corresponding to the second data plane workload, and the update process is taken over by the fifth data plane workload.

[0131] In other embodiments of the present application, the first node 1201 and the N second nodes 1202 cooperate to perform the following information processing method:

[0132] Modify the affinity configuration of the core components already deployed in the first node, so that the core components are distributed into the second nodes.

[0133] The above description of the device embodiments is similar to the description of the above-mentioned method embodiments, and has similar beneficial effects as the method embodiments. For technical details not disclosed in the device embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

[0134] It should be noted that, in the embodiments of this application, if the above-described information processing method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a terminal device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROMs, magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0135] Figure 13 This is a schematic structural diagram of a communication device 1300 provided in an embodiment of this application. The communication device can be a first node, a second node, or a first cluster. Figure 13 The communication device 1300 shown includes a processor 1310, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0136] Optionally, such as Figure 13 As shown, the communication device 1300 may further include a memory 1320. The processor 1310 can retrieve and run computer programs from the memory 1320 to implement the methods described in this embodiment.

[0137] The memory 1320 can be a separate device independent of the processor 1310, or it can be integrated into the processor 1310.

[0138] Optionally, such as Figure 13 As shown, the communication device 1300 may also include a transceiver 1330, and the processor 1310 may control the transceiver 1330 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0139] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0140] Optionally, the communication device 1300 may specifically be the first node / first cluster / second node in the embodiments of this application, and the communication device 1300 may implement the corresponding processes implemented by the first node / first cluster / second node in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0141] In some embodiments, the embodiments of the present application further provide a computer program product comprising a computer program, which can be executed by the processor 1310 of the communication device 1300 to complete any of the foregoing method steps.

[0142] It should be understood that the processor of the embodiments of the present application can be an integrated circuit chip having a signal processing capability. In the implementation process, each step of the foregoing method embodiments can be completed by the integrated logic circuit or the instruction in the form of software in the processor. The processor mentioned above can be a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The disclosed methods, steps and logic block diagrams in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as a hardware code processor to execute, or be executed by a combination of hardware and software modules in the code processor. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.

[0143] As an embodiment, the processor can include one or more general central processing units (CPUs). Each of the processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor herein can refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer-executable instructions).

[0144] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a ROM, a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM) used as an external cache. By way of example, but not limitation, many forms of RAM can be used, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the system and method described herein is intended to include, but not be limited to, these and any other suitable types of memory.

[0145] The embodiments of the present application also provide a computer readable storage medium for storing a computer program.

[0146] Optionally, the computer readable storage medium can be applied to the first node / first cluster in the embodiments of the present application, and the computer program makes the computer execute the corresponding processes realized by the model training device in the various methods of the embodiments of the present application. For the sake of brevity, it will not be repeated here.

[0147] In the above embodiments, all or part can be realized by software, hardware, firmware or any combination thereof. When realized by software, it can be realized in the form of a computer program product, entirely or partially.

[0148] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that the computer can store or be integrated into a data storage device such as a server, data center, etc. containing one or more available media. The available media can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)), etc.

[0149] The information processing method, the first node, the first cluster, the computer readable storage medium and the computer program product provided by the embodiments of the present application are described in detail above, and the principles and implementation manners of the present application are described by applying specific examples. The above description of the embodiments is only used to help understand the method and its core idea of the present application; at the same time, for those skilled in the art, according to the idea of the present application, the specific implementation manner and application range will be changed, and the content of the specification should not be understood as a limitation of the present application.

[0150] It should be understood that the "one embodiment" or "an embodiment" or "the embodiments of the present application" or "the foregoing embodiment" or "some embodiments" or "some embodiments" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiments are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" or "the embodiments of the present application" or "the foregoing embodiment" or "some embodiments" or "some embodiments" appearing throughout the specification do not necessarily mean the same embodiment. In addition, these specific features, structures or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in various embodiments of the present application, the size of the sequence number of the above processes does not mean the execution order, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The above sequence number of the embodiments of the present application is only for description, not representing the advantages and disadvantages of the embodiments.

[0151] Unless otherwise stated, the first node / first cluster performs any step in the embodiments of the present application can be that the processor of the first node / first cluster performs the step. Unless otherwise stated, the embodiments of the present application do not limit the order of the steps performed by the first node / first cluster. In addition, the way of processing data in different embodiments can be the same method or different method.

[0152] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only illustrative. For example, the division of units is only a logical function division. In actual implementation, another division manner can be used, such as: a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed components can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0153] The units described as separate components above can or can not be physically separated, and the components displayed as units can or can not be physical units; they can be located in one place or distributed on multiple network units; and part or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0154] In addition, all the functional units in the embodiments of the present application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be realized in the form of hardware or in the form of hardware plus software functional unit.

[0155] The methods disclosed in the several method embodiments provided in the present application can be combined arbitrarily without conflict to obtain new method embodiments. The features disclosed in the several product embodiments provided in the present application can be combined arbitrarily without conflict to obtain new product embodiments. The features disclosed in the several method or device embodiments provided in the present application can be combined arbitrarily without conflict to obtain new method embodiments or device embodiments.

[0156] Those skilled in the art can understand that all or part of the steps of the above method embodiments can be completed by program instruction related hardware, and the foregoing program can be stored in a computer storage medium. When the program is executed, the steps of the method embodiments are executed. The foregoing storage medium includes: mobile storage equipment, ROM, magnetic disc or optical disc and various storage program codes.

[0157] Alternatively, the above-mentioned integrated unit of the present application, if realized in the form of a software function module and sold or used as an independent product, can also be stored in a computer storage medium. Based on such understanding, the technical solutions of the embodiments of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the embodiments of the method of the present application. The aforementioned storage medium includes: mobile storage devices, ROM, magnetic disks or optical disks, and various media that can store program codes.

[0158] The singular forms "a", "an" and "the" used in the embodiments of the present application and the appended claims are intended to include plural forms, unless the context clearly indicates otherwise.

[0159] It should be noted that in each of the embodiments of the present application, all steps or part of the steps can be performed, as long as a complete technical solution can be formed.

[0160] The above is only an implementation of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. An information processing method, characterized in that, Applied to the first node, the method includes: In the first node of the first cluster, the core components required for the operation of the first cluster are deployed as containerized workloads hosted in the first cluster. Wherein, in the first node of the first cluster, the core components required for the operation of the first cluster are deployed in the form of containerized workloads hosted in the first cluster, including: The first component is deployed directly in the first node; wherein the first component includes the core component; The second component is deployed on the data plane of the first cluster in a stateless application deployment, a stateful application deployment, or by ensuring that all nodes run the same container; wherein the second component includes the core component; Establish a connection between the first component and the second component; Migrate the traffic of the core component in the first component to the core component in the second component; Uninstall the core components in the first component.

2. The method according to claim 1, characterized in that, The method of deploying the second component on the data plane of the first cluster, whether using stateless application deployment, stateful application deployment, or ensuring all nodes run the same container, includes: In the data plane, M first data plane workloads are deployed in a stateful application deployment manner; M is a positive integer; the M first data plane workloads are interconnected through headless services; In the data plane, the second data plane workload, the third data plane workload, and the fourth data plane workload are deployed in a stateless application deployment manner; In the data plane, the fifth data plane workload is deployed in a manner that ensures all nodes run the same container. In the data plane, a sixth data plane workload is deployed in a stateless application deployment manner; wherein, the second component includes the M first data plane workloads, the second data plane workloads, the third data plane workloads, the fourth data plane workloads, the fifth data plane workloads, and the sixth data plane workload.

3. The method according to claim 2, characterized in that, The first component includes a first control plane workload, a second control plane workload, a third control plane workload, a fourth control plane workload, and a fifth workload. Establishing a connection between the first component and the second component includes: The network connects a first control plane workload and M first data plane workloads, a first control plane workload and a second control plane workload, a second control plane workload and a third control plane workload, a second control plane workload and a fourth control plane workload, a second control plane workload and a fifth workload, a second control plane workload and a fifth data plane workload, and a second control plane workload and a sixth data plane workload. The second data plane workload and the fifth workload, the M first data plane workloads and the second data plane workload, the second data plane workload and the third data plane workload, the second data plane workload and the fourth data plane workload, the second data plane workload and the fifth data plane workload, and the second data plane workload and the sixth data plane workload are connected through virtual network protocol addresses provided by the service function that are only accessible within the first cluster.

4. The method according to claim 3, characterized in that, The core components include a first control plane workload, a second control plane workload, a third control plane workload, and a fourth control plane workload. The offloading of directly deployed core components includes: Shut down and remove the first control plane workload, the second control plane workload, the third control plane workload, and the fourth control plane workload.

5. An information processing method, characterized in that, Applied to the first cluster, the method includes: The process involves setting up a first node for the first cluster, and deploying the core components required for the operation of the first cluster as containerized workloads hosted in the first cluster on the first node. This deployment includes: directly deploying a first component on the first node, where the first component includes the core component; deploying a second component on the data plane of the first cluster using a stateless application deployment, a stateful application deployment, or ensuring all nodes run the same container, where the second component includes the core component; establishing a connection between the first component and the second component through the first node, migrating traffic from the core component in the first component to the core component in the second component, and offloading the core component from the first component. Add N second nodes to the first cluster; where N is a positive integer; The core components deployed in the first node as containerized workloads hosted in the first cluster are rescheduled to be distributed to the second node.

6. The method according to claim 5, characterized in that, Adding N second nodes to the first cluster includes: In the second node, a first rule is created; wherein the first rule is used to indicate that requests for accessing virtual network protocol addresses corresponding to the second data plane workload, which are only accessible within the first cluster, are forwarded to the port of the first node already in the first cluster. In the first node, based on the first rule, the second data plane workload is accessed using a virtual network protocol address provided by the service function that is only accessible within the first cluster. After the fifth workload starts, the fifth data plane workload is automatically deployed on the data plane corresponding to the second data plane workload, and the update process is taken over by the fifth data plane workload.

7. The method according to claim 5, characterized in that, The rescheduling of core components deployed in the first node as containerized workloads hosted in the first cluster, so that these core components are distributed across the second node, includes: Modify the affinity configuration of the core components already deployed in the first node to distribute the core components to the second node.

8. A first node, characterized in that, The first node includes: The processing module is used to deploy the core components required for the operation of the first cluster in the form of containerized workloads hosted in the first cluster. The step of deploying the core components required for the operation of the first cluster as containerized workloads hosted in the first cluster includes: The first component is deployed directly in the first node; wherein the first component includes the core component; The second component is deployed on the data plane of the first cluster in a stateless application deployment, a stateful application deployment, or by ensuring that all nodes run the same container; wherein the second component includes the core component; Establish a connection between the first component and the second component; Migrate the traffic of the core component in the first component to the core component in the second component; Uninstall the core components in the first component.

9. A first node, characterized in that, The first node includes: Memory, used to store executable instructions; A processor, when executing executable instructions stored in the memory, implements the information processing method according to any one of claims 1 to 4.

10. A first cluster, characterized in that, The first cluster includes a first node and N second nodes, where N is a positive integer, and the first node and the N second nodes cooperate to perform the information processing method as described in any one of claims 5 to 7.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the information processing method of any one of claims 1 to 4, or the information processing method of any one of claims 5 to 7.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the information processing method of any one of claims 1 to 4, or the information processing method of any one of claims 5 to 7.

Images