WO2021212950A1

WO2021212950A1 - Private cloud task management system and method, and storage medium

Info

Publication number: WO2021212950A1
Application number: PCT/CN2021/074030
Authority: WO
Inventors: 陈海钊; 罗平; 季统凯; 贺忠堂
Original assignee: 国云科技股份有限公司
Priority date: 2020-04-22
Filing date: 2021-01-28
Publication date: 2021-10-28
Also published as: CN111654534A; CN111654534B

Abstract

Disclosed in embodiments of the present application are a private cloud task management system and method, and a storage medium. The private cloud task management system provided by the embodiments of the present application comprises a central management module, a client module, and a task service module; the client module and the task service module are deployed in a private cloud. Information interaction is achieved by providing a three-layer architecture comprising a central management module, a client module, and a task service module; by means of the three-layer architecture, tasks of multiple private clouds can be managed uniformly, task distribution is performed globally, a uniform basic task framework is provided for update, operation and maintenance, and service configuration of the multiple private clouds, and function development and operation and maintenance in a scenario of management of multiple private clouds are simplified. Moreover, the task service module is independent in function, and can operate normally even under the condition of no central management module and client module.

Description

Private cloud task management system, method and storage medium

Technical field

The embodiments of the present application relate to the field of cloud computing technology, and in particular, to a private cloud task management system, method, and storage medium.

Background technique

At present, the core feature of private cloud is that cloud resources are only used by employees in an enterprise and public institution, and other people and organizations have no right to lease and use cloud computing resources. As for where the cloud is deployed, who owns the ownership, and who is responsible for daily management, there are no strict rules. There are two possibilities. One is to deploy in the unit, such as the computer room, which is called a local private cloud; the other is to be hosted elsewhere, such as Alibaba Cloud, which is called a managed private cloud. For the local private cloud, the maintenance is relatively simple, and the information management personnel in the enterprise can directly manage it. But for a host, that is, a private cloud provider, when managing a specific private cloud, that is, when managing isolated private clouds, it is usually necessary to build a corresponding one for each private cloud. Management platform for corresponding management, or operation and maintenance personnel need to remotely log in to the private cloud for operation, although this method will provide more comprehensive management services for the serviced enterprise. However, with the increase in environment deployment, the management of private clouds will greatly increase the cost of private cloud providers. Private cloud management here includes upgrades to private clouds, service configuration, and unified management of mirroring. Therefore, designing a task system that can uniformly perform private cloud management services has become an urgent technical problem to be solved by those skilled in the art.

Summary of the invention

The embodiments of the present application provide a private cloud task management system, method, and storage medium, which adopts a three-tier architecture of a central management module, a client module, and a task service module to realize information interaction, and the above-mentioned three-tier architecture can manage multiple data in a unified manner. The tasks of a private cloud are distributed globally, which simplifies the function development and operation and maintenance in multiple private cloud management scenarios.

In the first aspect, an embodiment of the present application provides a private cloud task management system, including: a central management module, a client module, and a task service module:

The central management module is used to provide centralized task management for a preset number of private clouds; the central management module communicates with the client module through the network;

The client module and the task service module are deployed in the private cloud, and the client module is used to pull tasks from the central management module, convert the pulled tasks, and publish the converted tasks to the tasks Service module; the client module is also used to pull tasks and/or mark tasks from the task service module, and report tasks to the central management module according to the pull tasks and/or mark tasks;

The task service module is used to publish tasks to the cloud service in the corresponding private cloud and monitor the task progress of the cloud service, and is also used to maintain the cloud service list of the private cloud; the cloud service includes an upgrade service and a container service , Mirroring service, physical machine service and monitoring service.

Further, the number of the private cloud is multiple.

In the second aspect, the embodiments of the present application provide a private cloud task management method, including:

When it is detected that the task service module interacts with the cloud service through the message queue, pull the interaction result between the task service module and the cloud service;

Sending the interaction result to the central management module so that the central management module updates the corresponding cloud service list;

Perform a task pull operation to the central management module to pull the task created in the queue to be processed;

Transform the pulled task to obtain the cloud service task, and send the cloud service task to the task service module so that the task service module transmits the cloud service task to the cloud service through the request queue and executes the corresponding Cloud service tasks.

Further, the data structure of the queue to be processed includes a data structure in the form of key-value, where key is a private cloud id, and value is a task queue.

Further, the performing task pull operation to the central management module to pull the tasks created in the queue for processing includes:

A task pull operation is performed to the central management module at a preset time interval to pull the tasks created in the queue to be processed.

Further, the message queue includes a reply queue, and the task service module interacts with cloud services through the message queue, including:

The task service module performs a subscription operation on the reply queue to monitor the registration message of the cloud service, and the cloud service sends the registration information to the reply queue;

The task service module updates its cloud service list according to the registration information of the cloud service, and sets the task execution status of the cloud service to connected mode;

Correspondingly, the pulling the interaction result between the task service module and the cloud service includes:

Pull the cloud service list of the task service module;

The sending the interaction result to the central management module includes:

The cloud service list is sent to the central management module so that the central management module updates the cloud service list corresponding to the private cloud received.

Further, the message queue includes a request queue, and the task service module interacts with cloud services through the message queue, including:

When the task service module detects the unsubscribe event of the request queue, it sets the execution state of the cloud service task in the cloud service list to the disconnected state.

Further, the unsubscription event includes a private cloud network abnormal event and/or a cloud service stop event.

Further, in the process of transforming the pulled task to obtain a cloud service task, and sending the cloud service task to the task service module, the task service module transmits the cloud service task to the task service module through the request queue. After cloud service and execution of corresponding cloud service tasks, it also includes:

Pull the first task to be synchronized in the task service module;

Performing compression processing and/or encryption processing on the first task to be synchronized;

The task to be synchronized after compression and/or encryption is sent to the central management module for decompression and/or decryption to obtain a second task to be synchronized, and the central management module is based on the second task to be synchronized Update the task list;

Send a mark modification request to the task service module to modify the task to be synchronized in the cloud service list to a synchronized task.

In the third aspect, embodiments of the present application provide a storage medium containing computer-executable instructions, which are used to execute the private cloud task management method described in the second aspect when the computer-executable instructions are executed by a computer processor .

The embodiment of the present application implements information interaction by setting a three-tier architecture of a central management module, a client module, and a task service module. Through the foregoing three-tier architecture, multiple private cloud tasks can be managed uniformly, and tasks can be distributed globally. The upgrade, operation and maintenance, and service configuration of multiple private clouds provide a unified basic task framework, which simplifies the function development and operation and maintenance in multiple private cloud management scenarios. In addition, the task service module has independent functions, and it can operate normally even without a central management module and a client module.

Description of the drawings

Fig. 1 is a flowchart of a private cloud task management method provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a process of cloud service registration provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of a task information synchronization process provided by an embodiment of the present application;

FIG. 4 is a structural block diagram of a private cloud task management system provided by an embodiment of the present application;

Fig. 5 is a schematic diagram of specific interactions of a private cloud task management system provided by an embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present application clearer, specific embodiments of the present application will be described in further detail below with reference to the accompanying drawings. It can be understood that the specific embodiments described here are only used to explain the application, but not to limit the application. In addition, it should be noted that, for ease of description, the drawings only show part of the content related to the present application, but not all of the content. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowchart describes various operations (or steps) as sequential processing, many of the operations can be implemented in parallel, concurrently, or simultaneously. In addition, the order of operations can be rearranged. The processing may be terminated when its operation is completed, but may also have additional steps not included in the drawings. The processing may correspond to methods, functions, procedures, subroutines, subroutines, and so on.

Existing solutions require operation and maintenance personnel to remotely log in to the private cloud to perform operations or build a single management platform corresponding to the private cloud when performing private cloud management. The above method will greatly increase the operation and maintenance cost of the enterprise. Therefore, for function development and operation and maintenance in multiple private cloud management scenarios, task distribution and unified management need to be considered. Otherwise, the operation and maintenance personnel need to remotely log in to the private cloud for operation, or related functions need to handle tasks by themselves, so a unified A basic, independent task framework. Based on this, this application provides a three-tier architecture of a central management module, a client module, and a task service module to achieve information interaction. The central management module is responsible for the centralized management of a unified private cloud, which can be used for multiple private clouds. Task publishing; the client module and task service module run inside the corresponding private cloud to obtain the status information of the cloud service in the private cloud. The solution of this application provides a unified basic task framework for the upgrade, operation and maintenance, and service configuration of multiple private clouds, which simplifies the function development and operation and maintenance in multiple private cloud management scenarios, thereby reducing the operation and maintenance costs of enterprises, making Enterprises can focus more on specific private cloud services and improve service quality.

Figure 1 shows a flow chart of a private cloud task management method provided by an embodiment of the application. The private cloud task management method provided in this embodiment can be executed by a private cloud task management device, which can pass Realized by software and/or hardware, the private cloud task management device may be composed of two or more physical entities, or may be composed of one physical entity. Generally speaking, the private cloud task management device can be a computer, a mobile phone, a tablet, or a server.

In the following description, the server is a device that executes the private cloud task management method as an example. Referring to Figure 1, the private cloud task management method specifically includes:

S101: After detecting that the task service module interacts with the cloud service through the message queue, pull the interaction result between the task service module and the cloud service.

In the description of the solution in this embodiment, Task-Server refers to the task service module, Task-Client refers to the client module, and Task-Center refers to the central management module. When it is detected that the task service module interacts with the cloud service through the message queue, that is, when information exchange occurs between the two, the client module is required to pull the interaction result, and the client module can understand in time through the information pull To the status of the cloud service in the private cloud.

Specifically, as shown in Figure 2, Figure 2 is a schematic flow diagram of cloud service registration provided by an embodiment of the present application; in this embodiment, the message queue includes a reply queue and a request queue, and the task service module communicates with Cloud services interact, including:

S1011: The task service module performs a subscription operation on the response queue to monitor the registration message of the cloud service, and the cloud service sends registration information to the response queue.

Specifically, when the cloud service starts, it subscribes to the message queue request queue, and sends a registration message to the message queue reply queue. In this embodiment, request queue refers to the request queue, and reply queue refers to the reply queue; in the cloud After the service sends the registration message to the reply queue, the task service module can subscribe to the reply queue to monitor the registration message of the cloud service. Realize the timely acquisition of registration messages through the above operations.

S1012: The task service module updates its cloud service list according to the registration information of the cloud service, and sets the task execution state of the cloud service to the connected mode.

Specifically, the task service module adds or updates the monitored cloud service registration information to the cloud service list maintained by itself, and sets the task execution status of the cloud service to Idle, thereby realizing the cloud service registration information in the task service module Update.

Pull the cloud service list of the task service module.

Task-Client regularly pulls the list of cloud services from Task-Server and reports to Task-Center. That is, Task-Client acts as a bridge connecting Task-Center and Task-Server, and is responsible for task pull, release, synchronization and other functions.

The sending the interaction result to the central management module includes:

In this embodiment, Task-Center provides centralized management of private cloud tasks on a global scale. Task-Center receives the cloud service list of the private cloud and updates it to the corresponding database and cache.

In addition to the above-mentioned registered information interaction, the interactive operation of this embodiment also includes the interactive operation of cloud service offline. The message queue includes a request queue, and the task service module interacts with cloud services through the message queue, including:

In this embodiment, the unsubscription event includes a private cloud network abnormal event and/or a cloud service stop event. An abnormal event of a private cloud network refers to a problem with the network at the private cloud, and there is no way to connect to the Internet, and a cloud service stop event refers to a user corresponding to the private cloud canceling the corresponding cloud service content. Specifically, the subscription status of a cloud service will be automatically cancelled when the network is abnormal or out of operation, thereby automatically triggering the offline of the cloud service, and the corresponding cloud service at the private cloud can be offlined without manual operation and maintenance. Specifically, Task-Server monitors the unsubscribe event of the request queue. When the cloud service cancels the subscription, it triggers the offline process of the Task-Server cloud service. The Task-Server sets the task execution status of the cloud service in the cloud service list to Disconnected. .

In this embodiment, the task service module is a task management program that runs inside a single private cloud. It is expected to be responsible for the task management of the entire private cloud. It has independent functions and can operate normally even without Task-Center and Task-Client. This guarantees The independence of the operation of the private cloud ensures that the operation of the cloud service will not be disturbed by the status of Task-Center and Task-Client.

S102: Send the interaction result to the central management module so that the central management module updates the corresponding cloud service list.

Task-Client regularly pulls the list of cloud services from Task-Server and reports to Task-Center. That is, Task-Client acts as a bridge connecting Task-Center and Task-Server, and is responsible for task pull, release, synchronization and other functions. The client module is used to transfer and synchronize the information released by the cloud service and the central management module.

S103: Perform a task pull operation to the central management module to pull the task created in the queue to be processed.

Specifically, Task-Center receives the task created by the operation and maintenance personnel, saves the task in the database, and sets the status to Waiting, then adds it to the pending queue, and adds it to the pending queue for Task-Client to perform the task. Pull, Task-Client can only pull the corresponding to-be-processed tasks of the private cloud. For example, Task-Client is a client module of private cloud a, so it cannot pull the corresponding to-be-processed tasks of private cloud b. Task-Center retrieves the task list from the pending queue corresponding to the private cloud where Task-Client is located, and returns it to Task-Client.

A task pull operation is performed to the central management module at a preset time interval to pull the tasks created in the queue to be processed. That is, the task pull is performed every preset time, and the pull operation of the information can be better automatically completed through the client module.

More preferably, the data structure of the queue to be processed in this embodiment includes a data structure in the form of key-value, where key is a private cloud id and value is a task queue. This data structure is used to represent a queue of to-be-processed tasks corresponding to a certain private cloud. The key is used to identify the corresponding private cloud, and the value is used to identify the specific task.

S104: Transform the pulled task to obtain a cloud service task, and send the cloud service task to the task service module so that the task service module transmits the cloud service task to the cloud service through the request queue and executes it The corresponding cloud service task.

Specifically, after the Task-Client receives the task, it transforms it and sends the task to the Task-Server. The Task-Server receives the task, saves the task in the database, and sets the state to the running state; Task-Server When the task is posted to the request queue, the cloud service obtains the task from the request queue, the cloud service executes the task, publishes the task result to the reply queue, and the Task-Server obtains the task result and updates it to the database. The task distribution is realized through the above steps. When the cloud service interacts with the task service module, the interaction is mainly carried out through the request queue and reply queue.

As shown in FIG. 3, FIG. 3 is a schematic diagram of a task information synchronization process provided by an embodiment of the present application. After step S104, it further includes:

S104a: Pull the first task to be synchronized in the task service module.

Specifically, the task stored in the database by the Task-Server has a synchronization mark, and the synchronization mark includes a synchronized state and a pending synchronization state. It is judged whether the task has been synchronized by the above synchronization mark method, and the Task-Client regularly pulls the synchronization mark as the task to be synchronized from the Task-Server. Through this step, all the tasks to be synchronized can be pulled.

S104b: Perform compression processing and/or encryption processing on the first task to be synchronized.

Specifically, the Task-Client periodically pulls the tasks that are marked for synchronization from the Task-Server, compresses and encrypts them in the form of a list, and reports to the Task-Center. Task-Center receives the task list and returns success to Task-Client. Because the client module and the central management module exchange information through the Internet, the security of information transmission can be improved by compressing and encrypting the transmitted content.

S104c: Send the task to be synchronized after compression and/or encryption to the central management module for decompression and/or decryption to obtain a second task to be synchronized, and the central management module according to the second task to be synchronized Synchronize tasks to update the task list.

Specifically, Task-Center decrypts and decompresses the task list corresponding to the private cloud stored in it, and updates it to the database; Task-Client sends a request to Task-Server to set the synchronization flag of the task in the task list to Synchronized.

S104d: Send a mark modification request to the task service module to modify the task to be synchronized in the cloud service list to a synchronized task.

Specifically, when Task-Server adds a task to the database, the synchronization flag is set to be synchronized; when Task-Server obtains the task result and updates to the database, the synchronization flag is set to be synchronized; Task-Client synchronizes the task information to the Task After -Center, send a request to Task-Server to change the synchronization mark of the task in the task list to synchronized. In this embodiment, the synchronization mark interaction is used to make the information mark at the central management module and the task service module the same, that is, the information in the service list maintained by the two is consistent, and then the upgrade, operation and maintenance and service configuration of the private cloud are completed. Unity.

The private cloud task management method provided by the embodiments of the present application can uniformly manage the tasks of multiple private clouds, distribute tasks globally, and provide unified functions for the upgrade, operation and maintenance, and service configuration of multiple private clouds. , The basic independent task framework simplifies the function development and operation and maintenance in multiple private cloud management scenarios.

As shown in Figures 4 and 5, Figure 4 is a structural block diagram of a private cloud task management system provided by an embodiment of the present application, and Figure 5 is a specific interaction schematic diagram of a private cloud task management system provided by an embodiment of the present application. The above-mentioned private cloud task management method of this embodiment runs on a private cloud task management system. The private cloud task management system includes a central management module, a client module, and a task service module; the central management module is deployed at the management server; The management module will not be deployed in the private cloud.

The management server includes a central management module 21, which is used to provide centralized task management for a preset number of private clouds; the central management module 21 communicates with the client module 22 through a network.

The client module 22 and the task service module 23 are deployed in a private cloud. The client module 22 is used to pull tasks from the central management module 21, and convert the pulled tasks, and convert the converted tasks. The task is issued to the task service module 23; the client module 22 is also used to pull tasks and/or mark tasks from the task service module 23, and send to the central management module according to the pull tasks and/or mark tasks 21 Carry out task report.

The task service module 23 is used to publish tasks to the cloud service in the corresponding private cloud and monitor the task progress of the cloud service, and is also used to maintain the cloud service list of the private cloud; the cloud service includes upgrade services and containers. Services, mirroring services, physical machine services and monitoring services. Both the task service module 23 and the client module 22 of this embodiment run inside the private cloud. In this embodiment, the private cloud may be configured in a single server, or multiple servers may jointly construct a private cloud, or even a server may contain multiple private clouds.

In addition, the task service module of this embodiment is a task management program running in a single private cloud, responsible for task management of the entire private cloud, and has independent functions. Even without a central management module and a client module, the task service module can operate normally. The client module is a bridge connecting the center management module and the task service module, and is mainly responsible for the functions of task pull, release and synchronization.

Further, the number of the private cloud is multiple. That is, the management of multiple private clouds can be realized through a single central management module.

An embodiment of the present application also provides a storage medium containing computer-executable instructions, which are used to execute a private cloud task management method when executed by a computer processor, and the private cloud task management method includes:

Storage medium-any of various types of storage devices or storage devices. The term "storage medium" is intended to include: installation media, such as CD-ROM, floppy disk or tape device; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc. ; Non-volatile memory, such as flash memory, magnetic media (such as hard disk or optical storage); registers or other similar types of memory elements. The storage medium may further include other types of memory or a combination thereof. In addition, the storage medium may be located in the first computer system in which the program is executed, or may be located in a different second computer system connected to the first computer system through a network (such as the Internet). The second computer system can provide the program instructions to the first computer for execution. The term "storage medium" may include two or more storage media residing in different locations (for example, in different computer systems connected through a network). The storage medium may store program instructions (for example, embodied as a computer program) executable by one or more processors.

Of course, the storage medium containing computer-executable instructions provided by the embodiments of the present application is not limited to the private cloud task management method described above, and can also execute the private cloud provided by any embodiment of the present application. Related operations in task management methods.

The storage medium provided in the above embodiment can execute the private cloud task management method provided by any embodiment of this application. For technical details not described in detail in the above embodiment, please refer to the private cloud task management provided by any embodiment of this application. method.

The embodiment of the present application implements information interaction by setting a three-tier architecture of a central management module, a client module, and a task service module. Through the foregoing three-tier architecture, multiple private cloud tasks can be managed uniformly, and tasks can be distributed globally. The upgrade, operation and maintenance, and service configuration of multiple private clouds provide a unified basic task framework, which simplifies the function development and operation and maintenance in multiple private cloud management scenarios. In addition, the task service module functions independently, and it can operate normally even without a central management module and a client module.

The above are only the preferred embodiments of this application and the technical principles used. The application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions that can be made by those skilled in the art will not depart from the protection scope of the application. Therefore, although the application has been described in more detail through the above embodiments, the application is not limited to the above embodiments, and can also include more other equivalent embodiments without departing from the concept of the application. The scope of is determined by the scope of the claims.

Claims

A private cloud task management system, which is characterized by comprising a central management module, a client module, and a task service module;

The central management module is used to provide centralized task management for a preset number of private clouds; the central management module communicates with the client module through the network;

The client module and the task service module are deployed in the private cloud, and the client module is used to pull tasks from the central management module, convert the pulled tasks, and publish the converted tasks to the tasks Service module; the client module is also used to pull tasks and/or mark tasks from the task service module, and report tasks to the central management module according to the pull tasks and/or mark tasks;

The task service module is used to publish tasks to the cloud service in the corresponding private cloud and monitor the task progress of the cloud service, and is also used to maintain the cloud service list of the private cloud; the cloud service includes an upgrade service and a container service , Mirroring service, physical machine service and monitoring service.
The private cloud task management system according to claim 1, wherein the number of the private cloud is multiple.
A private cloud task management method, which is characterized in that it includes:

When it is detected that the task service module interacts with the cloud service through the message queue, pull the interaction result between the task service module and the cloud service;

Sending the interaction result to the central management module so that the central management module updates the corresponding cloud service list;

Perform a task pull operation to the central management module to pull the task created in the queue to be processed;

Transform the pulled task to obtain the cloud service task, and send the cloud service task to the task service module so that the task service module transmits the cloud service task to the cloud service through the request queue and executes the corresponding Cloud service tasks.
A private cloud task management method according to claim 3, wherein the data structure of the queue to be processed comprises a data structure in the form of key-value, wherein the key is the private cloud id and the value is the task queue.
The method for managing tasks in a private cloud according to claim 3, wherein the task pull operation to the central management module to pull the tasks created in the queue to be processed comprises:

A task pull operation is performed to the central management module at a preset time interval to pull the tasks created in the queue to be processed.
A private cloud task management method according to claim 3, wherein the message queue comprises a reply queue, and the task service module interacts with the cloud service through the message queue, comprising:

The task service module performs a subscription operation on the reply queue to monitor the registration message of the cloud service, and the cloud service sends the registration information to the reply queue;

The task service module updates its cloud service list according to the registration information of the cloud service, and sets the task execution status of the cloud service to connected mode;

Correspondingly, the pulling the interaction result between the task service module and the cloud service includes:

Pull the cloud service list of the task service module;

The sending the interaction result to the central management module includes:

The cloud service list is sent to the central management module so that the central management module updates the cloud service list corresponding to the private cloud received.
A private cloud task management method according to claim 3, wherein the message queue comprises a request queue, and the task service module interacts with the cloud service through the message queue, comprising:

When the task service module detects the unsubscribe event of the request queue, it sets the execution state of the cloud service task in the cloud service list to the disconnected state.
The private cloud task management method according to claim 7, wherein the unsubscribe event includes an abnormal event of the private cloud network and/or an event of stopping the operation of the cloud service.
A private cloud task management method according to claim 3, characterized in that, in the said pull task is transformed to obtain the cloud service task, and the cloud service task is sent to the task service module to make After the task service module transmits the cloud service task to the cloud service through the request queue and executes the corresponding cloud service task, it further includes:

Pull the first task to be synchronized in the task service module;

Performing compression processing and/or encryption processing on the first task to be synchronized;

The task to be synchronized after compression and/or encryption is sent to the central management module for decompression and/or decryption to obtain a second task to be synchronized, and the central management module is based on the second task to be synchronized Update the task list;

Send a mark modification request to the task service module to modify the task to be synchronized in the cloud service list to a synchronized task.
A storage medium containing computer-executable instructions, wherein the computer-executable instructions are used to execute the private cloud task management method according to any one of claims 3-9 when the computer-executable instructions are executed by a computer processor.