CN111654534B - Private cloud task management system, method and storage medium - Google Patents

Private cloud task management system, method and storage medium Download PDF

Info

Publication number
CN111654534B
CN111654534B CN202010449885.9A CN202010449885A CN111654534B CN 111654534 B CN111654534 B CN 111654534B CN 202010449885 A CN202010449885 A CN 202010449885A CN 111654534 B CN111654534 B CN 111654534B
Authority
CN
China
Prior art keywords
task
cloud
module
service
private
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010449885.9A
Other languages
Chinese (zh)
Other versions
CN111654534A (en
Inventor
陈海钊
罗平
季统凯
贺忠堂
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
G Cloud Technology Co Ltd
Original Assignee
G Cloud Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by G Cloud Technology Co Ltd filed Critical G Cloud Technology Co Ltd
Publication of CN111654534A publication Critical patent/CN111654534A/en
Priority to PCT/CN2021/074030 priority Critical patent/WO2021212950A1/en
Application granted granted Critical
Publication of CN111654534B publication Critical patent/CN111654534B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer And Data Communications (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The embodiment of the application discloses a private cloud task management system, a private cloud task management method and a storage medium. The embodiment of the application provides a private cloud task management system, which comprises a center management module, a client module and a task service module, wherein the client module and the task service module are deployed in a private cloud. The three-layer architecture of the central management module, the client module and the task service module is arranged to realize information interaction, tasks of a plurality of private clouds can be uniformly managed through the three-layer architecture, task distribution is carried out on the whole, a uniform basic task framework is provided for upgrading, operation and maintenance and service configuration of the plurality of private clouds, and function development and operation and maintenance under a plurality of private cloud management scenes are simplified. And the task service module has independent functions and can normally operate even without a central management module and a client module.

Description

Private cloud task management system, method and storage medium
Technical Field
The embodiment of the application relates to the technical field of cloud computing, in particular to a private cloud task management system, a private cloud task management method and a storage medium.
Background
At present, the private cloud is characterized in that cloud resources are only used by staff in an enterprise and public institution, and other people and institutions do not have rights to rent and use cloud computing resources. There is no strict regulation as to where the cloud deploys, to whom ownership is attributed, and by whom it is responsible for daily management. There are two possibilities, one is deployed inside a unit, such as in a machine room, which is called a local private cloud; second, hosted elsewhere, such as the ali cloud, is called a hosted private cloud. For the local private cloud, the maintenance is relatively simple, and the local private cloud can be directly managed by an information manager in an enterprise. However, when managing a specific private cloud, that is, when managing private clouds isolated from each other, a manager needs to build a corresponding management platform for each private cloud to perform corresponding management, or an operator needs to remotely log in to the private cloud to perform operation, which will provide a more comprehensive management service for the served enterprises. However, as the deployment of environments increases, managing the private cloud greatly increases the cost of the private cloud provider, where the private cloud management includes upgrading the private cloud, configuring services, uniformly managing images, and so on. Therefore, designing a task system capable of uniformly performing private cloud management services is a technical problem to be solved by those skilled in the art.
Disclosure of Invention
The embodiment of the application provides a private cloud task management system, a private cloud task management method and a private cloud task management storage medium, which adopt a three-layer architecture of a central management module, a client module and a task service module to realize information interaction, and the three-layer architecture can uniformly manage tasks of a plurality of private clouds and globally distribute the tasks, so that function development and operation and maintenance under a plurality of private cloud management scenes are simplified.
In a first aspect, an embodiment of the present application provides a private cloud task management system, including: the system comprises a central management module, a client module and a task service module:
the central management module is used for providing centralized task management for a preset number of private clouds; the central management module is communicated with the client module through a network;
the client module and the task service module are deployed in the private cloud, and the client module is used for pulling the task from the central management module, converting the pulled task and releasing the converted task to the task service module; the client module is also used for pulling tasks and/or marking tasks from the task service module and reporting tasks to the central management module according to the pulling tasks and/or marking tasks;
the task service module is used for issuing tasks to the cloud service in the corresponding private cloud, monitoring the task progress of the cloud service and maintaining a cloud service list of the private cloud; the cloud services include upgrade services, container services, mirror services, physical machine services, and monitoring services.
Further, the number of the private clouds is a plurality.
In a second aspect, an embodiment of the present application provides a private cloud task management method, including:
when the interaction between the task service module and the cloud service through the message queue is detected, pulling an interaction result between the task service module and the cloud service;
the interaction result is sent to a central management module so that the central management module updates a corresponding cloud service list;
performing task pulling operation on the central management module to pull tasks created in the queue to be processed;
converting the pulled task to obtain a cloud service task, and sending the cloud service task to a task service module so that the task service module can transmit the cloud service task to cloud service through a request queue and execute the corresponding cloud service task.
Further, the data structure of the queue to be processed includes a data structure in a key-value form, wherein the key is a private cloud id, and the value is a task queue.
Further, the performing a task pulling operation to the central management module to pull the task created in the pending queue includes:
and carrying out task pulling operation on the central management module according to a preset time interval so as to pull the task created in the queue to be processed.
Further, the message queue includes a response queue, and the task service module interacts with the cloud service through the message queue, including:
the task service module subscribes the response queue to monitor registration information of the cloud service, and the cloud service sends the registration information to the response queue;
the task service module updates a cloud service list in the task service module according to registration information of the cloud service, and sets a task execution state of the cloud service as a connected mode;
correspondingly, the pulling the interaction result of the task service module and the cloud service includes:
pulling a cloud service list of the task service module;
the sending the interaction result to a central management module comprises the following steps:
and sending the cloud service list to a central management module so that the central management module updates the cloud service list received by the corresponding private cloud.
Further, the message queue includes a request queue, and the task service module interacts with the cloud service through the message queue, including:
when the task service module detects an unsubscribe event of the request queue, the cloud service task execution state in the cloud service list is set to be an unconnected state.
Further, the unsubscribe event comprises a private cloud network abnormal event and/or a cloud service event stopping running.
Further, after the converting the pulled task to obtain a cloud service task and sending the cloud service task to a task service module, the task service module transmits the cloud service task to a cloud service through a request queue and executes a corresponding cloud service task, the method further includes:
pulling a first task to be synchronized in the task service module;
compressing and/or encrypting the first task to be synchronized;
the task to be synchronized after compression processing and/or encryption processing is sent to the central management module for decompression processing and/or decryption processing to obtain a second task to be synchronized, and the central management module updates a task list according to the second task to be synchronized;
and sending a mark modification request to the task service module to modify the task to be synchronized in the cloud service list into a synchronized task.
In a third aspect, embodiments of the present application provide a storage medium containing computer executable instructions which, when executed by a computer processor, are for performing the private cloud task management method of the second aspect.
According to the embodiment of the application, the information interaction is realized by setting the three-layer architecture of the central management module, the client module and the task service module, tasks of a plurality of private clouds can be uniformly managed through the three-layer architecture, task distribution is carried out on the whole, a task framework with uniform foundation is provided for upgrading, operation and maintenance and service configuration of the plurality of private clouds, and function development and operation and maintenance under a plurality of private cloud management scenes are simplified. And the task service module has independent functions and can normally operate even without a central management module and a client module.
Drawings
Fig. 1 is a flowchart of a private cloud task management method provided in an embodiment of the present application;
fig. 2 is a schematic flow chart of cloud service registration provided in an embodiment of the present application;
FIG. 3 is a schematic flow chart of task information synchronization provided in an embodiment of the present application;
fig. 4 is a block diagram of a private cloud task management system according to an embodiment of the present application;
fig. 5 is a specific interaction schematic diagram of a private cloud task management system provided in an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the following detailed description of specific embodiments thereof is given with reference to the accompanying drawings. It is to be understood that the specific embodiments described herein are merely illustrative of the application and not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the matters related to the present application are shown in the accompanying drawings. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart depicts operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently, or at the same time. Furthermore, the order of the operations may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figures. The processes may correspond to methods, functions, procedures, subroutines, and the like.
When the private cloud management is carried out in the existing scheme, operation and maintenance personnel are required to remotely log in the private cloud to operate or construct a single management platform corresponding to the private cloud. The mode can greatly increase the operation and maintenance cost of enterprises. Therefore, for function development and operation and maintenance in multiple private cloud management scenarios, task distribution and unified management need to be considered, otherwise operation and maintenance personnel need to remotely log in the private cloud to operate, or related functions need to process tasks by themselves, so that a unified and basic independent task framework is needed. Based on the information interaction method, the three-layer architecture of the central management module, the client module and the task service module is provided, the central management module is responsible for centralized management of unified private cloud, and the central management module can issue tasks for a plurality of private cloud; the client module and the task service module operate in the corresponding private cloud to acquire state information of cloud services in the private cloud. According to the scheme, a unified basic task framework is provided for upgrading, operation and maintenance and service configuration of a plurality of private clouds, function development and operation and maintenance under a plurality of private cloud management scenes are simplified, and further operation and maintenance cost of enterprises is reduced, so that the enterprises can concentrate on specific private cloud services more, and service quality is improved.
Fig. 1 is a flowchart of a private cloud task management method provided in the embodiment of the present application, where the private cloud task management method provided in the embodiment may be executed by a private cloud task management device, and the private cloud task management device may be implemented by software and/or hardware, and the private cloud task management device may be configured by two or more physical entities or may be configured by one physical entity. In general, the private cloud task management device may be a computer, a mobile phone, a tablet, a server, or the like.
The following describes an example of a server as an apparatus for executing the private cloud task management method. Referring to fig. 1, the private cloud task management method specifically includes:
s101: and when the interaction between the task service module and the cloud service through the message queue is detected, pulling an interaction result between the task service module and the cloud service.
In the description of the embodiment, the Task-Server refers to a Task service module, the Task-Client refers to a Client module, and the Task-Center refers to a central management module. When the task service module is detected to interact with the cloud service through the message queue, namely, when information exchange occurs between the task service module and the cloud service, the client module is required to pull the interaction result, and the client module can timely know the state of the cloud service in the private cloud through information pulling.
Specifically, as shown in fig. 2, fig. 2 is a schematic flow chart of cloud service registration provided in the embodiment of the present application; in this embodiment, the message queue includes a response queue and a request queue, and the task service module interacts with the cloud service through the message queue, including:
s1011: the task service module subscribes the response queue to monitor registration information of the cloud service, and the cloud service sends the registration information to the response queue.
Specifically, when the cloud service is started, subscribing to a message queue request, and sending a registration message to the message queue reply, wherein in the embodiment, the request queue refers to a request queue, and the reply queue refers to a response queue; after the cloud service sends the registration message to the reply queue, the task service module can subscribe the message to the reply queue to monitor the registration message of the cloud service. The timely acquisition of the registration message is realized through the operation.
S1012: and the task service module updates a cloud service list in the task service module according to the registration information of the cloud service, and sets the task execution state of the cloud service as a connected mode.
Specifically, the task service module adds or updates the monitored registration information of the cloud service to a cloud service list maintained by the task service module, and sets the task execution state of the cloud service as Idle, so that the cloud service registration information is updated in the task service module.
Correspondingly, the pulling the interaction result of the task service module and the cloud service includes:
and pulling the cloud service list of the task service module.
The Task-Client periodically pulls the cloud service list to the Task-Server and reports to the Task-Center. Namely, the Task-Client is used as a bridge for connecting the Task-Center and the Task-Server and is responsible for the functions of Task pulling, publishing, synchronizing and the like.
The sending the interaction result to a central management module comprises the following steps:
and sending the cloud service list to a central management module so that the central management module updates the cloud service list received by the corresponding private cloud.
In this embodiment, the Task-Center provides centralized management of private cloud tasks on the global, and the Task-Center receives a cloud service list of the private cloud and updates the cloud service list to a corresponding database and cache.
In addition to the above registered information interaction, the interaction operation of the present embodiment further includes an interaction operation of cloud service offline. The message queue comprises a request queue, and the task service module interacts with the cloud service through the message queue and comprises:
when the task service module detects an unsubscribe event of the request queue, the cloud service task execution state in the cloud service list is set to be an unconnected state.
In this embodiment, the unsubscribe event includes a private cloud network exception event and/or a cloud service event that stops running. The private cloud network abnormal event refers to the problem of the network at the private cloud, no method is available for connecting to the Internet, and the operation stopping of the cloud service event refers to the cancellation of the corresponding cloud service content by the user corresponding to the private cloud. Specifically, the subscription state of the cloud service can be automatically canceled under the conditions of network abnormality, operation stop and the like, so that the cloud service is automatically triggered to be offline, and the cloud service corresponding to the private cloud can be offline without manual operation and maintenance. Specifically, the Task-Server monitors an unsubscribed event of the request, and when the cloud service unsubscribes, triggers a cloud service offline flow of the Task-Server, and the Task-Server sets a Task execution state of the cloud service in the cloud service list as unconnected.
In this embodiment, the Task service module is a Task management program running in a single private cloud, and is responsible for Task management of the whole private cloud, and functions are independent, so that the Task service module can normally run even without Task-Center and Task-Client, and thus the independence of the private cloud running is ensured, and the running of the cloud service is not interfered by states of the Task-Center and the Task-Client.
S102: and sending the interaction result to a central management module so that the central management module updates the corresponding cloud service list.
The Task-Client periodically pulls the cloud service list to the Task-Server and reports to the Task-Center. Namely, the Task-Client is used as a bridge for connecting the Task-Center and the Task-Server and is responsible for the functions of Task pulling, publishing, synchronizing and the like. And the information issued by the cloud service and the central management module is transferred and synchronized through the client module.
S103: and carrying out task pulling operation on the central management module to pull the tasks created in the queue to be processed.
Specifically, the Task-Center receives a Task created by an operation and maintenance person, stores the Task in a database, sets the state as Waiting, then adds the Task into a to-be-processed queue for Task pulling by the Task-Client, and the Task-Client can only pull the to-be-processed Task of the corresponding private cloud, for example, the Task-Client is a Client module of the private cloud a, and cannot pull the corresponding to-be-processed Task of the private cloud b. And taking out the Task list from the to-be-processed queue corresponding to the private cloud where the Task-Client is located by the Task-Center, and returning the Task list to the Task-Client.
Further, the performing a task pulling operation to the central management module to pull the task created in the pending queue includes:
and carrying out task pulling operation on the central management module according to a preset time interval so as to pull the task created in the queue to be processed. Namely, task pulling is performed every preset time, and information pulling operation can be 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 a key-value form, where a key is a private cloud id and a value is a task queue. The data structure is used for representing a task queue to be processed corresponding to a private cloud. The corresponding private cloud is identified by key, and the specific task is identified by value.
S104: converting the pulled task to obtain a cloud service task, and sending the cloud service task to a task service module so that the task service module can transmit the cloud service task to cloud service through a request queue and execute the corresponding cloud service task.
Specifically, after receiving the Task, the Task-Client converts the Task and sends the Task to the Task-Server, the Task-Server receives the Task, stores the Task in a database, and sets the state as an operation state; the Task-Server issues the Task to the request queue, the cloud service acquires the Task from the request queue, the cloud service executes the Task, the Task result is issued to the reply queue, and the Task-Server acquires the Task result and updates the Task result to the database. The task is distributed through the steps, and when the cloud service interacts with the task service module, interaction is mainly carried out through a request queue request and a response queue reply queue.
As shown in fig. 3, fig. 3 is a schematic flow chart of task information synchronization provided in the embodiment of the present application, after step S104, further includes:
s104a: and pulling 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 state to be synchronized. Judging whether the Task is synchronized or not by the synchronous marking mode, and regularly pulling the synchronous mark to the Task-Server by the Task-Client to be synchronized. Through this step, all tasks to be synchronized can be pulled.
S104b: and carrying out compression processing and/or encryption processing on the first task to be synchronized.
Specifically, the Task-Client periodically pulls the synchronization mark to the Task-Server as a Task to be synchronized, compresses and encrypts the Task in a list form, and reports the Task-Server to the Task-Center. The Task-Center receives the Task list and returns success to the Task-Client, and as the Client module and the Center management module interact with each other through the Internet, the security of information transmission can be improved by compressing and encrypting the transmitted content.
S104c: and sending the compressed and/or encrypted task to be synchronized to the central management module for decompression and/or decryption to obtain a second task to be synchronized, wherein the central management module updates a task list according to the second task to be synchronized.
Specifically, the Task-Center decrypts and decompresses the Task list stored therein and corresponding to the private cloud, and updates the Task list to the database; the Task-Client sends a request to the Task-Server, and the synchronization mark of the Task in the Task list is set to be synchronized.
S104d: and sending a mark modification request to the task service module to modify the task to be synchronized in the cloud service list into a synchronized task.
Specifically, when the Task is added to the database by the Task-Server, the synchronous mark is set to be synchronous; the Task-Server obtains a Task result, and when the Task result is updated to the database, the synchronous mark is set to be synchronous; after the Task information is synchronized to the Task-Center by the Task-Client, a request is sent to the Task-Server, and the synchronous mark of the Task in the Task list is changed into synchronized. In this embodiment, the information marks at the central management module and the task service module are the same through synchronous mark interaction, that is, the information in the service list maintained by the central management module and the task service module is kept consistent, so that the update, operation and maintenance and service configuration of the private cloud are unified.
The private cloud task management method provided by the embodiment of the application can uniformly manage the tasks of a plurality of private clouds, perform task distribution on the whole, provide a uniform and basic independent task framework for the functions of upgrading, operation and maintenance, service configuration and the like of the plurality of private clouds, and simplify the function development and operation and maintenance in a plurality of private cloud management scenes.
According to the embodiment of the application, the information interaction is realized by setting the three-layer architecture of the central management module, the client module and the task service module, tasks of a plurality of private clouds can be uniformly managed through the three-layer architecture, task distribution is carried out on the whole, a task framework with uniform foundation is provided for upgrading, operation and maintenance and service configuration of the plurality of private clouds, and function development and operation and maintenance under a plurality of private cloud management scenes are simplified. And the task service module has independent functions and can normally operate even without a central management module and a client module.
Fig. 4 is a structural block diagram of a private cloud task management system provided by an embodiment of the present application, and fig. 5 is a specific interaction schematic diagram of the private cloud task management system provided by the embodiment of the present application, as shown in fig. 4 and fig. 5. The private cloud task management method of the embodiment operates in a private cloud task management system, wherein the private cloud task management system comprises a center management module, a client module and a task service module; the central management module is deployed at the management server; the central management module is not deployed within the private cloud.
The management server comprises a central management module 21, wherein the central management module 21 is used for providing centralized task management for a preset number of private clouds; the central management module 21 communicates with the client modules 22 via a network.
The client module 22 and the task service module 23 are deployed in the private cloud, and the client module 22 is configured to pull a task from the central management module 21, convert the pulled task, and issue the converted task to the task service module 23; the client module 22 is further configured to pull tasks and/or marking tasks from the task service module 23, and report tasks to the central management module 21 according to the pull tasks and/or marking tasks.
The task service module 23 is configured to issue a task to a corresponding cloud service in the private cloud, monitor a task progress of the cloud service, and maintain a cloud service list of the private cloud; the cloud services include upgrade services, container services, mirror services, physical machine services, and monitoring services. The task service module 23 and the client module 22 of the present embodiment both operate inside the private cloud. In this embodiment, the private cloud may be configured in a single server, or a plurality of servers together may construct a private cloud, or even a server includes a plurality of private clouds.
The task service module of the embodiment is a task management program running in a single private cloud and is responsible for task management of the whole private cloud, and functions are independent, so that the task service module can normally operate even if a central management module and a client module are not provided. The client module is a bridge connecting the central management module and the task service module and is mainly responsible for the functions of task pulling, publishing and synchronizing.
Further, the number of the private clouds is a plurality. That is, the management of a plurality of private clouds can be realized through a single central management module.
According to the embodiment of the application, the information interaction is realized by setting the three-layer architecture of the central management module, the client module and the task service module, tasks of a plurality of private clouds can be uniformly managed through the three-layer architecture, task distribution is carried out on the whole, a task framework with uniform foundation is provided for upgrading, operation and maintenance and service configuration of the plurality of private clouds, and function development and operation and maintenance under a plurality of private cloud management scenes are simplified. And the task service module has independent functions and can normally operate even without a central management module and a client module.
The embodiments also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are for performing a private cloud task management method comprising:
when the interaction between the task service module and the cloud service through the message queue is detected, pulling an interaction result between the task service module and the cloud service;
the interaction result is sent to a central management module so that the central management module updates a corresponding cloud service list;
performing task pulling operation on the central management module to pull tasks created in the queue to be processed;
converting the pulled task to obtain a cloud service task, and sending the cloud service task to a task service module so that the task service module can transmit the cloud service task to cloud service through a request queue and execute the corresponding cloud service task.
Storage media-any of various types of memory devices or storage devices. The term "storage medium" is intended to include: mounting media such as CD-ROM, floppy disk or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, lanbas (Rambus) RAM, etc.; nonvolatile memory such as flash memory, magnetic media (e.g., hard disk or optical storage); registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. In addition, the storage medium may be located in a first computer system in which the program is executed, or may be located in a second, different computer system connected to the first computer system through a network such as the internet. The second computer system may provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media residing in different locations (e.g., in different computer systems connected by a network). The storage medium may store program instructions (e.g., embodied as a computer program) executable by one or more processors.
Of course, the storage medium containing the computer executable instructions provided in the embodiments of the present application is not limited to the private cloud task management method described above, and may also perform related operations in the private cloud task management method provided in any embodiment of the present application.
The storage medium provided in the above embodiment may perform the private cloud task management method provided in any embodiment of the present application, and technical details not described in detail in the above embodiment may be referred to the private cloud task management method provided in any embodiment of the present application.
According to the embodiment of the application, the information interaction is realized by setting the three-layer architecture of the central management module, the client module and the task service module, tasks of a plurality of private clouds can be uniformly managed through the three-layer architecture, task distribution is carried out on the whole, a task framework with uniform foundation is provided for upgrading, operation and maintenance and service configuration of the plurality of private clouds, and function development and operation and maintenance under a plurality of private cloud management scenes are simplified. And the task service module has independent functions and can normally operate even without a central management module and a client module.
The foregoing description is only of the preferred embodiments of the present application and the technical principles employed. The present application is not limited to the specific embodiments described herein, but is capable of numerous obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the present application. Therefore, while the present application has been described in connection with the above embodiments, the present application is not limited to the above embodiments, but may include many other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the claims.

Claims (10)

1. The private cloud task management system is characterized by comprising a center management module, a client module and a task service module;
the central management module is used for providing centralized task management for a preset number of private clouds; the central management module is communicated with the client module through a network;
the client module and the task service module are deployed in the private cloud, and the client module is used for pulling the task from the central management module, converting the pulled task and releasing the converted task to the task service module; the client module is also used for pulling tasks and/or marking tasks from the task service module and reporting tasks to the central management module according to the pulling tasks and/or marking tasks;
the task service module is used for issuing tasks to corresponding cloud services in private clouds and monitoring task progress of the cloud services, is also used for maintaining a cloud service list of the private clouds, and is particularly used for subscribing a response queue to monitor registration information of the cloud services, the cloud services send the registration information to the response queue, and the task service module updates the cloud service list in the response queue according to the registration information of the cloud services and sets task execution states of the cloud services as connected modes; the cloud services include upgrade services, container services, mirror services, physical machine services, and monitoring services.
2. A private cloud task management system according to claim 1, wherein the number of private clouds is a plurality.
3. The private cloud task management method is characterized by comprising the following steps of:
after detecting that the task service module interacts with the cloud service through the message queue, the method comprises the following steps: the task service module subscribes the response queue to monitor the registration information of the cloud service, the cloud service sends the registration information to the response queue, the task service module updates a cloud service list in the response queue according to the registration information of the cloud service, the task execution state of the cloud service is set to be a connected mode, and an interaction result of the task service module and the cloud service is pulled;
the interaction result is sent to a central management module so that the central management module updates a corresponding cloud service list;
performing task pulling operation on the central management module to pull tasks created in the queue to be processed;
converting the pulled task to obtain a cloud service task, and sending the cloud service task to a task service module so that the task service module can transmit the cloud service task to cloud service through a request queue and execute the corresponding cloud service task.
4. A private cloud task management method according to claim 3, wherein 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.
5. A private cloud task management method according to claim 3, wherein said performing a task pulling operation on said central management module to pull tasks created in a pending queue comprises:
and carrying out task pulling operation on the central management module according to a preset time interval so as to pull the task created in the queue to be processed.
6. A private cloud task management method according to claim 3,
the pulling the interaction result of the task service module and the cloud service comprises the following steps:
pulling a cloud service list of the task service module;
the sending the interaction result to a central management module comprises the following steps:
and sending the cloud service list to a central management module so that the central management module updates the cloud service list received by the corresponding private cloud.
7. A private cloud task management method according to claim 3, wherein said message queue comprises a request queue, and said task service module interacts with a cloud service via said message queue, comprising:
when the task service module detects an unsubscribe event of the request queue, the cloud service task execution state in the cloud service list is set to be an unconnected state.
8. The private cloud task management method according to claim 7, wherein the unsubscribe event comprises a private cloud network exception event and/or a cloud service event that stops running.
9. The private cloud task management method according to claim 3, wherein after said converting the pulled task to obtain a cloud service task and sending the cloud service task to a task service module to enable the task service module to transmit the cloud service task to a cloud service through a request queue and execute the corresponding cloud service task, further comprising:
pulling a first task to be synchronized in the task service module;
compressing and/or encrypting the first task to be synchronized;
the task to be synchronized after compression processing and/or encryption processing is sent to the central management module for decompression processing and/or decryption processing to obtain a second task to be synchronized, and the central management module updates a task list according to the second task to be synchronized;
and sending a mark modification request to the task service module to modify the task to be synchronized in the cloud service list into a synchronized task.
10. A storage medium containing computer executable instructions which, when executed by a computer processor, are for performing the private cloud task management method of any of claims 3-9.
CN202010449885.9A 2020-04-22 2020-05-25 Private cloud task management system, method and storage medium Active CN111654534B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/074030 WO2021212950A1 (en) 2020-04-22 2021-01-28 Private cloud task management system and method, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010323804 2020-04-22
CN2020103238040 2020-04-22

Publications (2)

Publication Number Publication Date
CN111654534A CN111654534A (en) 2020-09-11
CN111654534B true CN111654534B (en) 2023-05-02

Family

ID=72343388

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010449885.9A Active CN111654534B (en) 2020-04-22 2020-05-25 Private cloud task management system, method and storage medium

Country Status (2)

Country Link
CN (1) CN111654534B (en)
WO (1) WO2021212950A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111654534B (en) * 2020-04-22 2023-05-02 国云科技股份有限公司 Private cloud task management system, method and storage medium
CN115460054B (en) * 2022-08-26 2024-04-19 深圳技威时代科技有限公司 Cloud service management and release method and system based on shared memory
CN116028544B (en) * 2023-03-30 2023-06-23 山东爱特云翔计算机有限公司 Timing task dynamic adding method based on OPENSTACK
CN117278635B (en) * 2023-11-03 2024-03-19 烽台科技（北京）有限公司 Industrial target range dispatching method and industrial target range system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106357609A (en) * 2016-08-22 2017-01-25 深圳市先河系统技术有限公司 User creation method and system, public network server and private cloud equipment
CN109067600A (en) * 2018-09-25 2018-12-21 郑州云海信息技术有限公司 A kind of private clound management platform system and its task processing method

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103380423B (en) * 2010-07-09 2016-01-27 道富公司 For the system and method for private cloud computing
US10235439B2 (en) * 2010-07-09 2019-03-19 State Street Corporation Systems and methods for data warehousing in private cloud environment
US20140280964A1 (en) * 2013-03-15 2014-09-18 Gravitant, Inc. Systems, methods and computer readable mediums for implementing cloud service brokerage platform functionalities
CN106027617A (en) * 2016-05-11 2016-10-12 广东浪潮大数据研究有限公司 Method for implementing dynamic scheduling of tasks and resources in private cloud environment
CN107528887B (en) * 2017-07-26 2020-10-16 广州云晫信息科技有限公司 Distributed cloud system based on fusion unified computing
CN108200022B (en) * 2017-12-22 2020-03-17 新华三云计算技术有限公司 Cloud platform access method and device and multi-cloud platform management system
CN110138876B (en) * 2019-05-30 2022-07-08 北京达佳互联信息技术有限公司 Task deployment method, device, equipment and platform
CN110365711B (en) * 2019-08-20 2022-03-25 中国工商银行股份有限公司 Multi-platform user identity association method and device, computer equipment and computer readable storage medium
CN110912975A (en) * 2019-11-12 2020-03-24 国云科技股份有限公司 Private cloud version management system and implementation method thereof
CN111654534B (en) * 2020-04-22 2023-05-02 国云科技股份有限公司 Private cloud task management system, method and storage medium

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106357609A (en) * 2016-08-22 2017-01-25 深圳市先河系统技术有限公司 User creation method and system, public network server and private cloud equipment
CN109067600A (en) * 2018-09-25 2018-12-21 郑州云海信息技术有限公司 A kind of private clound management platform system and its task processing method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
王传连 ; 张宗朔 ; .基于私有云的大规模交通视频处理框架设计.计算机工程与应用.2017,(21), *

Also Published As

Publication number Publication date
WO2021212950A1 (en) 2021-10-28
CN111654534A (en) 2020-09-11

Similar Documents

Publication Publication Date Title
CN111654534B (en) Private cloud task management system, method and storage medium
CN110832808B (en) Method, storage medium, and computing system for messaging service
US10261872B2 (en) Multilevel disaster recovery
US10726045B2 (en) Resource-efficient record processing in unified automation platforms for robotic process automation
US20190266276A1 (en) Instance data replication
CN1882911B (en) A method in a network of the delivery of files
EP3617961A1 (en) Intelligent adaptor service in unified automation platforms for robotic process automation
CN101160563A (en) Method and system for hosting and executing a component application
WO2019061720A1 (en) Data synchronization method and system
JP2006221376A (en) Plant emergency information display system and method, and web server
CN102664747B (en) Cloud calculating platform system
CN102763102A (en) Self-service configuration for data environment
US10567244B1 (en) Near real-time feed manager for data center infrastructure monitoring (DCIM) using custom tags for infrastructure assets
CN109783151B (en) Method and device for rule change
US8924530B2 (en) Multi-phase monitoring of hybrid system landscapes
CN109743399B (en) Internal and external network data transmission method and system for multi-task scheduling of physical examination center
CN102523115A (en) Server monitoring system based on power environment system
CN112099878A (en) Application software configuration management method, device and system
US20100325244A1 (en) Real time data network
WO2024032298A1 (en) Hosting system for scenarios and configurations in power system, and hosting method
CA2735389C (en) System for integrating service management systems
CN109062599B (en) Management method and device for code update under micro-service architecture
WO2017211091A1 (en) Method and device for configuring network access apparatus
JP4188615B2 (en) Video distribution server and video distribution system
US20180063242A1 (en) Method and apparatus for operating infrastructure layer in cloud computing architecture

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant