Dynamic cross-resource pool operator deployment method, system, and storage medium

Abstract

The present application relates to the field of information technology, and more particularly to a dynamic cross-resource pool operator deployment method, system and storage medium, the method comprising the following steps: recording the matching relationship of paas component version and operator version; receiving a cloud cluster paas component opening instruction, deploying the matched operator to the cloud cluster; recording the paas component instance of the cloud cluster and the version used; listening to the version release message, issuing an operator version upgrade task to the component instance that needs to upgrade the operator version; listening to the paas component instance logout message, if there is an operator version that is not used by any paas component instance, then uninstalling the operator of the corresponding version from the cloud cluster. The beneficial technical effects of the present application include: realizing the dynamic management of the operator life cycle in the cross-resource pool multi-container cloud cluster.

Description

Technical Field

[0001] This invention relates to the field of information technology, and specifically to a dynamic cross-resource pool operator deployment method, system, and storage medium. Background Technology

[0002] An operator is a method for encapsulating, deploying, and managing Kubernetes applications. Based on application-specific controllers, it extends the functionality of the Kubernetes API to represent Kubernetes users in creating, configuring, and managing instances of complex applications. Operators manage applications and their components using custom resources (CRs), which are API extension mechanisms in Kubernetes. A custom resource definition (CRD) explicitly defines the CR and lists all configurations available to the operator user. The operator monitors the CR type and takes application-specific actions to ensure the current state matches the ideal state of the resource. In PaaS platform application scenarios, cloud-native PaaS components are deployed based on operators. As the number of resource pools and container cloud clusters within them grows, the number and versions of operators in the container cloud clusters also increase. How to manage the entire lifecycle of operators, including automatic installation, upgrades, and uninstallation, becomes a challenge. Therefore, there is an urgent need to research technologies that can improve operator management efficiency. Summary of the Invention

[0003] The technical problem this invention aims to solve is the current lack of an efficient operator management solution. It proposes a dynamic cross-resource pool operator deployment method, system, and storage medium, which can efficiently manage the entire lifecycle of operator installation, upgrades, and uninstallation.

[0004] To solve the above technical problems, the present invention adopts the following technical solution: a dynamic cross-resource pool operator deployment method, comprising the following steps: Record the matching relationship between PaaS component versions and operator versions; Receive the command to enable the PaaS component in the cloud cluster, and deploy an operator that matches the version of the PaaS component to the cloud cluster; Record the PaaS component instances and the operator versions used in the cloud cluster; Listen for new operator version release messages and issue operator version upgrade tasks to component instances that need to upgrade their operator versions; Listen for PaaS component instance deregistration messages. If an operator version exists that is not being used by any PaaS component instance, uninstall the corresponding operator version from the cloud cluster.

[0005] Preferably, the method for recording the matching relationship between PaaS component versions and operator versions includes: establishing a matching table for PaaS component versions and operator versions, wherein the matching table records the operator versions that match the PaaS component versions.

[0006] Preferably, after receiving the PaaS component activation instruction of the cloud cluster, it is determined whether the cloud cluster has deployed an operator that matches the version of the PaaS component. If it has been deployed, no operation is performed. Otherwise, if no operator that matches the version of the PaaS component is deployed, the matching operator version is obtained based on the PaaS component version of the cloud cluster, and the matching operator version is deployed.

[0007] Preferably, the method for determining whether the cloud cluster has deployed an operator that matches the version of the PaaS component includes: Establish an operator version table, which records the operator versions currently used by the cloud cluster; The operator version that matches the PaaS component version is obtained according to the matching table; If the operator version table is not recorded and no operator version matching the PaaS component version is found, it is determined that the cloud cluster has not deployed an operator matching the PaaS component version. Conversely, if the operator version table is recorded and an operator version matching the PaaS component version is found, it is determined that the cloud cluster has deployed an operator matching the PaaS component version. After deploying the matching operator version, update the operator version table.

[0008] Preferably, the method for recording the PaaS component instances and the operator versions used in the cloud cluster includes: Establish a PaaS component version table, which records the currently used PaaS component version and the PaaS component instance set. The PaaS component instance set records the PaaS component instance and the operator version used by the PaaS component instance.

[0009] Preferred methods for obtaining component instances that require operator version upgrades include: Query the PaaS component version table to obtain the set of PaaS component instances corresponding to the old operator version. This set of PaaS component instances that need to be upgraded to the operator version is the PaaS component instance set in the PaaS component instance set.

[0010] Preferred methods for determining whether the operator version is used by the PaaS component instance include: Query the PaaS component version table to obtain the set of PaaS component instances corresponding to the operator version. If the set of PaaS component instances is empty, it is determined that the operator version is not used by any PaaS component instance. Conversely, if the set of PaaS component instances is not empty, it is determined that the operator version is used by a PaaS component instance.

[0011] The dynamic cross-resource pool operator deployment system is used to execute the dynamic cross-resource pool operator deployment method described above, including a version management center, an automatic operator deployment unit, an automatic operator upgrade unit, and an automatic operator uninstallation unit. The version management center records the matching relationship between PaaS component versions and operator versions. The operator auto-deployment unit receives the cloud cluster PaaS component activation instruction and deploys the operator matching the PaaS component version to the cloud cluster. After the PaaS component is activated, the version management center records the PaaS component instances in the cloud cluster and the operator versions used. The operator auto-upgrade unit listens for new operator version release messages and issues operator version upgrade tasks to component instances that need to upgrade their operator versions. The operator auto-uninstallation unit listens for PaaS component instance deregistration messages. If there is an operator version that is not used by any PaaS component instance, the corresponding version of the operator is uninstalled from the cloud cluster.

[0012] Preferably, the version management center establishes a matching table between PaaS component versions and operator versions, and the matching table records the operator versions that match the PaaS component versions.

[0013] Preferably, after receiving the PaaS component activation instruction from the cloud cluster, the operator automatic deployment unit determines whether the cloud cluster has deployed an operator that matches the PaaS component version. If it has, no operation is performed; otherwise, if no operator that matches the PaaS component version is deployed, the matching operator version is obtained based on the PaaS component version of the cloud cluster, and the matching operator version is deployed. The version management center establishes an operator version table, which records the operator versions currently used by the cloud cluster. The operator auto-deployment unit obtains the operator version that matches the PaaS component version based on the matching table. The operator auto-deployment unit queries the operator version table. If the operator version table does not record an operator version that matches the PaaS component version, it is determined that the cloud cluster has not deployed an operator that matches the PaaS component version. Conversely, if the operator version table records an operator version that matches the PaaS component version, it is determined that the cloud cluster has deployed an operator that matches the PaaS component version. After the operator auto-deployment unit deploys the matched operator version, it notifies the version management center to update the operator version table.

[0014] Preferably, the version management center establishes a PaaS component version table, which records the currently used PaaS component version and the PaaS component instance set, and the PaaS component instance set records the PaaS component instance and the operator version used by the PaaS component instance.

[0015] A computer system includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the dynamic cross-resource pool operator deployment method as described above.

[0016] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned dynamic cross-resource pool operator deployment method.

[0017] The beneficial technical effects of this invention include: managing the constraint relationship between component versions and operator versions through a version management center, automatically triggering the deployment, upgrade, and uninstallation of operators when components are activated, new versions of operators are released, or components are deregistered, thereby realizing dynamic management of the operator lifecycle in a multi-container cloud cluster across resource pools.

[0018] Other features and advantages of the present invention will be disclosed in detail in the following detailed description and accompanying drawings. Attached Figure Description

[0019] The invention will be further described below with reference to the accompanying drawings: Figure 1 This is a schematic diagram of the dynamic cross-resource pool operator deployment method according to an embodiment of the present invention.

[0020] Figure 2 This is a schematic diagram of the cloud cluster version matching method according to an embodiment of the present invention.

[0021] Figure 3 This is a schematic diagram of the dynamic cross-resource pool operator deployment system structure according to an embodiment of the present invention.

[0022] Figure 4 This is a schematic diagram of the computer system structure according to an embodiment of the present invention.

[0023] Among them: 10, Version Management Center; 20, Operator Automatic Deployment Unit; 30, Operator Automatic Upgrade Unit; 40, Operator Automatic Uninstallation Unit; 50, Computer System; 51, Memory; 52, Computer Program; 53, Processor. Detailed Implementation

[0024] The technical solutions of the embodiments of the present invention will be explained and described below with reference to the accompanying drawings. However, the following embodiments are only preferred embodiments of the present invention and not all of them. Other embodiments obtained by those skilled in the art based on the embodiments in the implementation methods without creative effort are all within the protection scope of the present invention.

[0025] In the following description, terms such as “inner,” “outer,” “upper,” “lower,” “left,” and “right” are used only to facilitate the description of embodiments and simplify the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the present invention.

[0026] Before introducing the technical solution of this embodiment, the application scenario of this embodiment will be introduced.

[0027] Operators, application-specific controllers, extend the functionality of the Kubernetes API to create, configure, and manage instances of complex applications on behalf of users. Operators manage applications and their components using Custom Resources (CRs), an API extension mechanism in Kubernetes. A Custom Resource Definition (CRD) explicitly defines the CR and lists all configurations available to the Operator user. Operators monitor CR types and take application-specific actions to ensure the current state matches the ideal state for that resource. In PaaS platform application scenarios, cloud-native PaaS components are deployed based on operators. As resource pools and the number of container cloud clusters within those pools grow, the number and versions of operators in those clusters also increase.

[0028] For instructions on dynamic cross-resource pool operator deployment, please refer to the appendix. Figure 1 This includes the following steps: Step A01) Record the matching relationship between the PaaS component version and the operator version; Step A02) Receive the command to enable the PaaS component in the cloud cluster and deploy the operator that matches the version of the PaaS component to the cloud cluster; Step A03) Record the PaaS component instance of the cloud cluster and the operator version used; Step A04) Listen for new operator version release messages and send operator version upgrade tasks to component instances that need to upgrade their operator versions; Step A05) Listen for PaaS component instance deregistration messages. If there is an operator version that is not used by any PaaS component instance, uninstall the corresponding version of the operator from the cloud cluster.

[0029] Methods for recording the matching relationship between PaaS component versions and operator versions include: establishing a matching table for PaaS component versions and operator versions, with the matching table recording the operator versions that match the PaaS component versions.

[0030] In this embodiment, the version management center 10: the public area version management center 10 provides PaaS component version and operator version management functions, and maintains the constraint relationship between PaaS component version and operator version.

[0031] Automatic operator deployment: When a user selects a container cloud cluster in a resource pool to enable a PaaS component, the PaaS component enabling engine first determines whether the container cloud cluster has deployed an operator. If not, it obtains the latest matching operator version based on the PaaS component version that needs to be deployed, and then automatically deploys the operator. It also records the version relationship between the container cloud cluster instance and the component operator in the instance center, providing a basis for automatic operator version upgrades in the future.

[0032] Automatic operator upgrade: When a new operator version is released, a notification message is sent to the operator management and scheduling center after the version is successfully released. The operator management and scheduling center will obtain all container cloud clusters with the operator installed, and generate an operator upgrade task for each container cloud cluster. The operator upgrade task will first obtain the instance version in the container cloud cluster and determine whether they all match the latest operator version. If they match, the operator upgrade chart will be sent to the resource pool container cluster to automatically start the new version operator.

[0033] Operator auto-uninstallation: After the PaaS component instance in a container cloud cluster of a certain resource pool is deregistered, it is determined whether an instance of the component still exists in the container cloud cluster. If it does not exist, the operator is triggered to uninstall.

[0034] After receiving the PaaS component activation command from the cloud cluster, determine whether the cloud cluster has deployed an operator that matches the PaaS component version. If it has, no action is taken. Otherwise, if the operator that matches the PaaS component version has not been deployed, obtain the matching operator version based on the PaaS component version of the cloud cluster and deploy the matching operator version.

[0035] For methods to determine whether an operator matching the PaaS component version has been deployed in the cloud cluster, please refer to the appendix. Figure 2 ,include: Step B01) Establish an operator version table, which records the operator versions currently used by the cloud cluster; Step B02) Obtain the operator version that matches the PaaS component version based on the matching table; Step B03) Query the operator version table. If the operator version table does not record an operator version that matches the PaaS component version, it is determined that the cloud cluster has not deployed an operator that matches the PaaS component version. Conversely, if the operator version table records an operator version that matches the PaaS component version, it is determined that the cloud cluster has deployed an operator that matches the PaaS component version. Step B04) After deploying the matching operator version, update the operator version table.

[0036] Methods for recording PaaS component instances and operator versions used in a cloud cluster include: Create a PaaS component version table. The PaaS component version table records the currently used PaaS component version and the PaaS component instance set. The PaaS component instance set records the PaaS component instance and the operator version used by the PaaS component instance.

[0037] Methods to obtain an instance of the component whose operator version needs to be upgraded include: Query the PaaS component version table to obtain the set of PaaS component instances corresponding to the old operator version. This set of PaaS component instances that need to be upgraded to the operator version is the PaaS component instance set that needs to be upgraded to the operator version.

[0038] Methods for determining whether an operator version is used by a PaaS component instance include: Query the PaaS component version table to obtain the set of PaaS component instances corresponding to the operator version. If the set of PaaS component instances is empty, it is determined that the operator version is not used by any PaaS component instance. Conversely, if the set of PaaS component instances is not empty, it is determined that the operator version exists and is used by PaaS component instances.

[0039] The version management center 10 manages the constraint relationship between component versions and operator versions. When a component is activated, a new version of the operator is released, or a component is deregistered, the deployment, upgrade, and uninstallation of the operator are automatically triggered, realizing dynamic management of the operator lifecycle in a multi-container cloud cluster across resource pools.

[0040] On the other hand, this embodiment provides a dynamic cross-resource pool operator deployment system for executing the aforementioned dynamic cross-resource pool operator deployment method. Please refer to the appendix. Figure 3It includes a version management center 10, an operator automatic deployment unit 20, an operator automatic upgrade unit 30, and an operator automatic uninstallation unit 40. Version Management Center 10 records the matching relationship between PaaS component versions and operator versions. Operator Auto Deployment Unit 20 receives the cloud cluster PaaS component activation instruction and deploys the operator matching the PaaS component version to the cloud cluster. After the PaaS component is activated, Version Management Center 10 records the PaaS component instances in the cloud cluster and the operator versions used. Operator Auto Upgrade Unit 30 listens for new operator version release messages and sends operator version upgrade tasks to component instances that need to upgrade their operator versions. Operator Auto Uninstall Unit 40 listens for PaaS component instance deregistration messages. If there is an operator version that is not used by any PaaS component instance, the corresponding version of the operator is uninstalled from the cloud cluster.

[0041] Version Management Center 10 establishes a matching table between PaaS component versions and operator versions. The matching table records the operator versions that match the PaaS component versions.

[0042] After receiving the PaaS component activation instruction from the cloud cluster, the operator automatic deployment unit 20 determines whether the cloud cluster has deployed an operator that matches the PaaS component version. If it has, no operation is performed; otherwise, if the operator that matches the PaaS component version has not been deployed, the matching operator version is obtained based on the PaaS component version of the cloud cluster, and the matching operator version is deployed. Version Management Center 10 establishes an operator version table, which records the operator versions currently used by the cloud cluster. The operator auto-deployment unit 20 obtains the operator version that matches the PaaS component version based on the matching table. The operator auto-deployment unit 20 queries the operator version table. If the operator version table does not record an operator version that matches the PaaS component version, it is determined that the cloud cluster has not deployed an operator that matches the PaaS component version. Conversely, if the operator version table records an operator version that matches the PaaS component version, it is determined that the cloud cluster has deployed an operator that matches the PaaS component version. After deploying the matched operator version, the operator auto-deployment unit 20 notifies Version Management Center 10 to update the operator version table.

[0043] Version Management Center 10 establishes a PaaS component version table. The PaaS component version table records the currently used PaaS component version and the PaaS component instance set. The PaaS component instance set records the PaaS component instance and the operator version used by the PaaS component instance.

[0044] On the other hand, this application provides a computer system, please refer to the appendix. Figure 4 The computer system 50 includes a memory 51, a processor 53, and a computer program 52 stored in the memory 51 and executable on the processor 53. When the computer program 52 is executed by the processor 53, it implements the dynamic cross-resource pool operator deployment method as described above.

[0045] The computer system can be a general-purpose computer system or a special-purpose computer system. In specific implementations, the computer system can be a server cluster including multiple servers, such as a blockchain system including multiple nodes. Those skilled in the art will understand that... Figure 4 This is merely an example of a computer system and does not constitute a limitation on the computer system. It may include more or fewer components than shown in the figure, or combinations of certain components, or different components, such as input / output devices, network access devices, etc.

[0046] Processor 53 can be a Central Processing Unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processor 53 can be a microprocessor or any conventional processor.

[0047] In some embodiments, memory 51 may be an internal storage unit of a computer system, such as a hard disk or RAM. In other embodiments, memory 51 may be an external storage device of a computer system, such as a plug-in hard disk, smart media card (SMC), secure digital card (SD), flash card, etc. Furthermore, memory 51 may include both internal and external storage units of the computer system. Memory 51 is used to store the operating system, applications, boot loader, data, and other programs. Memory 51 can also be used to temporarily store data that has been output or will be output.

[0048] On the other hand, embodiments of this application provide a computer-readable storage medium storing a computer program 52, which, when executed by a processor 53, implements the aforementioned dynamic cross-resource pool operator deployment method.

[0049] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Those skilled in the art should understand that the present invention includes, but is not limited to, the contents described in the accompanying drawings and the specific embodiments above. Any modifications that do not depart from the functional and structural principles of the present invention will be included within the scope of the claims.

Claims

1. A dynamic cross-resource pool operator deployment method, characterized in that, Includes the following steps: Record the matching relationship between PaaS component versions and operator versions; Receive the command to enable the PaaS component in the cloud cluster, and deploy an operator that matches the version of the PaaS component to the cloud cluster; Establish a PaaS component version table, which records the currently used PaaS component version and the PaaS component instance set. The PaaS component instance set records the PaaS component instance and the operator version used by the PaaS component instance. Listen for new operator version release messages and issue operator version upgrade tasks to component instances that need to upgrade their operator versions; Listen for PaaS component instance deregistration messages. If an operator version exists that is not being used by any PaaS component instance, uninstall the corresponding operator version from the cloud cluster.

2. The dynamic cross-resource pool operator deployment method according to claim 1, characterized in that, The method for recording the matching relationship between PaaS component versions and operator versions includes: establishing a matching table for PaaS component versions and operator versions, wherein the matching table records the operator versions that match the PaaS component versions.

3. The dynamic cross-resource pool operator deployment method according to claim 2, characterized in that, After receiving the PaaS component activation command from the cloud cluster, determine whether the cloud cluster has deployed an operator that matches the version of the PaaS component. If it has, no operation is performed. Otherwise, if no operator that matches the version of the PaaS component is deployed, obtain the matching operator version based on the PaaS component version of the cloud cluster and deploy the matching operator version.

4. The dynamic cross-resource pool operator deployment method according to claim 3, characterized in that, The methods for determining whether the cloud cluster has deployed an operator that matches the version of the PaaS component include: Establish an operator version table, which records the operator versions currently used by the cloud cluster; Obtain the operator version that matches the PaaS component version based on the matching table; If the operator version table is not recorded and no operator version matching the PaaS component version is found, it is determined that the cloud cluster has not deployed an operator matching the PaaS component version. Conversely, if the operator version table is recorded and an operator version matching the PaaS component version is found, it is determined that the cloud cluster has deployed an operator matching the PaaS component version. After deploying the matching operator version, update the operator version table.

5. The dynamic cross-resource pool operator deployment method according to claim 1, characterized in that, Methods to obtain an instance of the component whose operator version needs to be upgraded include: Query the PaaS component version table to obtain the set of PaaS component instances corresponding to the old operator version. This set of PaaS component instances that need to be upgraded to the operator version is the PaaS component instance set in the PaaS component instance set.

6. The dynamic cross-resource pool operator deployment method according to claim 1, characterized in that, Methods for determining whether an operator version is used by a PaaS component instance include: Query the PaaS component version table to obtain the set of PaaS component instances corresponding to the operator version. If the set of PaaS component instances is empty, it is determined that the operator version is not used by any PaaS component instance. Conversely, if the set of PaaS component instances is not empty, it is determined that the operator version is used by a PaaS component instance.

7. A dynamic cross-resource pool operator deployment system, used to execute the dynamic cross-resource pool operator deployment method as described in any one of claims 1 to 6, characterized in that, This includes a version management center, an automatic operator deployment unit, an automatic operator upgrade unit, and an automatic operator uninstallation unit. The version management center records the matching relationship between PaaS component versions and operator versions. The operator auto-deployment unit receives the PaaS component activation instruction from the cloud cluster and deploys the operator matching the PaaS component version to the cloud cluster. After the PaaS component is activated, the version management center establishes a PaaS component version table. The PaaS component version table records the currently used PaaS component version and the set of PaaS component instances. The PaaS component instance set records the PaaS component instances and the operator versions used by the PaaS component instances. The operator auto-upgrade unit listens for new operator version release messages and issues operator version upgrade tasks to component instances that need to upgrade their operator versions. The operator auto-uninstallation unit listens for PaaS component instance deregistration messages. If there is an operator version that is not used by any PaaS component instance, the corresponding version of the operator is uninstalled from the cloud cluster.

8. The dynamic cross-resource pool operator deployment system according to claim 7, characterized in that, The version management center establishes a matching table between PaaS component versions and operator versions, and the matching table records the operator versions that match the PaaS component versions.

9. The dynamic cross-resource pool operator deployment system according to claim 8, characterized in that, After receiving the PaaS component activation instruction from the cloud cluster, the operator automatic deployment unit determines whether the cloud cluster has deployed an operator that matches the PaaS component version. If it has, no operation is performed; otherwise, if no operator that matches the PaaS component version is deployed, the matching operator version is obtained based on the PaaS component version of the cloud cluster, and the matching operator version is deployed. The version management center establishes an operator version table, which records the operator versions currently used by the cloud cluster. The operator auto-deployment unit obtains the operator version that matches the PaaS component version based on the matching table. The operator auto-deployment unit queries the operator version table. If the operator version table does not record an operator version that matches the PaaS component version, it is determined that the cloud cluster has not deployed an operator that matches the PaaS component version. Conversely, if the operator version table records an operator version that matches the PaaS component version, it is determined that the cloud cluster has deployed an operator that matches the PaaS component version. After the operator auto-deployment unit deploys the matched operator version, it notifies the version management center to update the operator version table.

10. A computer system, characterized in that, The computer system includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the dynamic cross-resource pool operator deployment method as described in any one of claims 1 to 6.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the dynamic cross-resource pool operator deployment method as described in any one of claims 1 to 6.

Images