CN110286937B - Distributed software operation method and system - Google Patents

Distributed software operation method and system Download PDF

Info

Publication number
CN110286937B
CN110286937B CN201910599531.XA CN201910599531A CN110286937B CN 110286937 B CN110286937 B CN 110286937B CN 201910599531 A CN201910599531 A CN 201910599531A CN 110286937 B CN110286937 B CN 110286937B
Authority
CN
China
Prior art keywords
distributed software
running
virtual machine
distributed
update
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
CN201910599531.XA
Other languages
Chinese (zh)
Other versions
CN110286937A (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.)
Shenzhen fingertip Interactive Entertainment Co.,Ltd.
Original Assignee
Shenzhen Fingertip Interactive Entertainment 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 Shenzhen Fingertip Interactive Entertainment Co ltd filed Critical Shenzhen Fingertip Interactive Entertainment Co ltd
Priority to CN201910599531.XA priority Critical patent/CN110286937B/en
Publication of CN110286937A publication Critical patent/CN110286937A/en
Application granted granted Critical
Publication of CN110286937B publication Critical patent/CN110286937B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • G06F8/656Updates while running
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45562Creating, deleting, cloning virtual machine instances
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/4557Distribution of virtual machine instances; Migration and load balancing

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The application discloses a method and a system for running distributed software, wherein the method for running the distributed software specifically comprises the following steps: acquiring distributed software operation information; establishing a plurality of virtual machines according to the running information of the distributed software, and issuing the distributed tasks to the established virtual machines; during the running of the virtual machine, responding to the received update instruction of the distributed software, and selecting the virtual machine for executing the update instruction; and updating the distributed software running on the selected virtual machine according to the selection result. The method and the device can establish the corresponding virtual machine for the operation of the distributed software, the virtual machine uniformly executes the distributed software tasks in the distributed software, and the completion speed of the distributed software tasks can be ensured while the operation integrity of the distributed software is ensured.

Description

Distributed software operation method and system
Technical Field
The present application relates to the field of software, and in particular, to a method and a system for operating distributed software.
Background
In the prior art, distributed computers have been developed along with the ubiquitous idea of interconnection, the scale of software is continuously increased, more distributed application programs are provided, and the mode of a single server in the past cannot meet the use requirement, so that multitask parallel processing by using a distributed software system is generated. However, although the efficiency of the distributed software processing task is improved, when a parallel program is executed in the distributed software, the task needs to be distributed to different physical machines for execution. However, the speed of the physical machine in executing different tasks is not considered in the execution process of the conventional distributed software, and the allocation situation in different physical machines is often uneven to the resource allocation required by the distributed software tasks, thereby causing the running of the distributed software to be incomplete. Meanwhile, if the distributed software needs to be updated, the conventional physical machine needs to execute the distributed software update on the basis of notifying the external service, and the external service is recovered after the distributed software update is completed, so that the distributed software system with larger and larger scale cannot be met, and the resource waste is caused. Therefore, a stronger distributed software running mode is needed, the distributed software task execution running integrity can be guaranteed through balanced distribution, the most reasonable mode is selected for updating the distributed software, and the speed of updating the distributed software is guaranteed.
Disclosure of Invention
The application aims to provide a distributed software running method and a distributed software running system, which can ensure the running integrity of distributed software in the running process of the distributed software, and select a most reasonable and most resource-saving mode to update the distributed software when an updating instruction occurs in the running of the distributed software.
In order to achieve the above object, the present application provides a method for operating distributed software, which specifically includes the following steps: acquiring distributed software operation information; establishing a plurality of virtual machines according to the running information of the distributed software, and issuing distributed tasks to the established virtual machines; during the running of the virtual machine, responding to the received update instruction of the distributed software, and selecting the virtual machine for executing the update instruction; and updating the distributed software running on the selected virtual machine according to the selection result.
As above, the acquiring the distributed software running information specifically includes: responding to the running of the distributed software in one or more physical machines, and acquiring running information of the distributed software; the running information comprises resource information required by running of the distributed software and environment information of running of the distributed software.
As above, if the number of the physical machines is one, the physical machines are used to establish the virtual machines according to one or more pieces of information in the running information of the distributed software.
As above, if the number of the physical machines is multiple, one or more physical machines of the multiple physical machines are selected as the main physical machine, and the main physical machine establishes the virtual machine according to one or more pieces of information in the running information of the distributed software.
As above, after the plurality of virtual machines are established, establishing corresponding distributed software tasks for the distributed software is further included.
As above, wherein the number of virtual machines is not less than the number of distributed software tasks.
As above, the selecting the virtual machine to execute the update instruction specifically includes the following sub-steps: acquiring the service capacity of the virtual machine when the virtual machine is used for executing distributed software; determining a standby virtual machine according to the service capacity of each virtual machine; and selecting a low-consumption virtual machine, and establishing a pre-updating environment for updating the distributed software in the low-consumption virtual machine.
As above, the service capability is determined according to the time required by the virtual machine to execute the distributed software task and the size of the consumed resource.
The method comprises the steps of selecting a specified number of standby virtual machines as the low-consumption virtual machines to establish a pre-update environment of the distributed software for executing the update instructions.
A distributed software running system comprises one or more physical machines which are connected with each other, wherein the distributed software runs on the physical machines, one or more virtual machines are built on the physical machines, and the physical machines execute the method.
The application has the following beneficial effects:
(1) the distributed software running method and the distributed software running system can establish the corresponding virtual machine for running of the distributed software, the virtual machine uniformly executes distributed software tasks in the distributed software, and the completion speed of the distributed software tasks can be guaranteed while the running integrity of the distributed software is guaranteed.
(2) The distributed software running method and the distributed software running system can select the most appropriate low-consumption virtual machine to update the distributed software when the distributed software needs to be updated, select the most reasonable and resource-saving mode for updating the distributed software, and improve the resource utilization rate of the virtual machine.
(3) The method and the system for running the distributed software can execute the distributed software updating and can also pre-update the distributed software, thereby further guaranteeing the updating success rate of the distributed software.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a flow chart of a method of distributed software execution provided according to an embodiment of the present application;
fig. 2 is a system internal structure diagram of distributed software operation provided according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application are clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The application relates to a distributed software task running method and a distributed software task running system. According to the method and the device, the running integrity of the distributed software can be guaranteed in the running process of the distributed software, the distributed software can be updated in a most reasonable and resource-saving mode when an updating instruction occurs in the running of the distributed software, and meanwhile the speed and the efficiency of updating the distributed software are guaranteed.
Fig. 1 is a flowchart illustrating a method for distributed software execution provided in the present application.
Step S110: and acquiring the running information of the distributed software.
Wherein the number of distributed software can be one or more. Specifically, the running information of the distributed software is obtained in response to the running of the distributed software in one or more physical machines. The running information comprises resources required by the running of the distributed software and environment information of the running of the distributed software.
Step S120: and establishing a plurality of virtual machines according to the running information of the distributed software, and issuing the distributed tasks to the established virtual machines.
Specifically, since the number of the physical machines is one or more, if there is one physical machine, the physical machine is used to establish the virtual machine according to one or more pieces of information in the running information of the distributed software.
If a plurality of physical machines exist, one or more physical machines in the plurality of physical machines are selected as main physical machines, and the main physical machines establish virtual machines according to one or more pieces of information in the running information of the distributed software.
For example, one or more virtual machines with resources sufficient for running the distributed software can be established according to the resources required by the running of the distributed software, or the virtual machines capable of meeting the running environment of the distributed software can be established according to the running environment of the distributed software.
Further, after the plurality of virtual machines are established, corresponding distributed software tasks are established for the distributed software, wherein the distributed software tasks can be established according to the types of the distributed software and the tasks contained in the distributed software, and specifically, the types of the distributed software can be divided into distributed operation software, distributed programming language and compiling software thereof, distributed file software, distributed database software and the like.
Preferably, one or more distributed software tasks are established according to the distributed software types, and if the distributed software of the same type contains different tasks, a plurality of different distributed software tasks are correspondingly established according to the number of the tasks.
In particular, multiple tasks may also be distributed within the same distributed software task. E.g., large traffic is required between multiple tasks, the multiple tasks may be distributed among the same distributed software task.
Illustratively, if three parallel tasks are included in the distributed software, a distributed software task 1, a distributed software task 2, and a distributed software task 3 may be established. If two of the three tasks have large communication traffic, the two tasks can be distributed in the same distributed software task to establish a distributed software task 1 and a distributed software task 2.
And further, issuing the established distributed software task to a corresponding virtual machine, and executing the distributed software by the virtual machine through completing the task of the distributed software.
Because the number of the distributed software tasks is one or more, the number of the virtual machines is consistent with or larger than the number of the distributed software tasks, and enough virtual machines can be ensured to execute the distributed software tasks.
Preferably, the number setting of the virtual machines can be specifically set according to the information in the distributed software task in the actual state, and the number is set by the task and can be modified.
Step S130: during the running of the virtual machine, in response to receiving an update instruction of the distributed software, selecting the virtual machine executing the update instruction.
Specifically, selecting a virtual machine to execute the update instruction specifically includes the following sub-steps:
step D1: and acquiring the service capability of the virtual machine when the virtual machine is used for executing the distributed software.
Specifically, the service capability can be determined according to the time required by the virtual machine to execute the distributed software task and the size of the consumed resource.
Step D2: and determining the standby virtual machines according to the service capacity of each virtual machine.
Specifically, because the distributed software tasks processed by each virtual machine are not completely consistent, and in order to ensure the smoothness of the distributed software during execution, a standby virtual machine is usually set, which is different from the normal virtual machine for processing and executing the distributed software tasks, and the standby virtual machine usually does not process and execute the distributed software tasks but is in an idle state, so that the standby virtual machine can quickly take over the virtual machine for processing and executing the distributed software tasks when the normal virtual machine is disconnected or abnormal, thereby ensuring the processing of the distributed software tasks and the integrity of the distributed software.
Step D3: and selecting a low-consumption virtual machine, and establishing a pre-updating environment for updating the distributed software in the low-consumption virtual machine.
The low-consumption virtual machine described in this step is different from the high-consumption virtual machine, specifically, the high-consumption virtual machine consumes more or too large resources when executing the distributed software task, and the low-consumption virtual machine does not need to execute the distributed software task and basically does not consume the resources.
Because the standby virtual machines have the performance and the capability of executing the distributed software, the load in the standby virtual machines is far smaller than that of the normal virtual machines although being larger than 0, and therefore, a specified number of standby virtual machines are selected from all the virtual machines to serve as low-consumption virtual machines to establish a pre-update environment of the distributed software, and therefore the low-consumption virtual machines, namely the virtual machines executing the update instructions, execute the update operation of the distributed software on the low-consumption virtual machines.
In response to the establishment of the pre-update environment, step S140 is performed.
Step S140: and updating the distributed software running on the corresponding virtual machine according to the selection result of the virtual machine.
Specifically, the virtual machine that performs the distributed software update is the low-consumption virtual machine mentioned in step S130.
Specifically, before executing the update operation of the distributed software, the method further comprises the following steps:
step P1: and further acquiring the update information of the distributed software.
Specifically, the update information includes version information after the update of the distributed software, resources required after the update of the distributed software, and the like.
Step P2: and acquiring the update data file according to the update information.
The updated data file is obtained according to the update information, namely, data information which is the same as the content of an old version in the distributed software is saved, partial data which needs to be added or replaced is compressed into the updated data file, or resource information which is needed by the distributed software is increased/decreased according to needs and is compressed into the updated data file, the distributed software is subjected to modularized or unitized function update, and the update speed is improved.
Step P3: and installing the update data file in a pre-update environment of the low-consumption virtual machine.
Specifically, the specific installation method may be performed according to an installation method of software or files in the prior art, which is not described herein again.
Step P4: and executing the pre-update of the distributed software in a pre-update environment, and judging whether the distributed software can be updated normally.
Specifically, whether the execution result meets the expected update of the distributed software or not can be judged through the execution result after the execution of the pre-update operation is finished, so that partial function adjustment of the distributed software is brought. For example, it may be determined whether the updated version of the distributed software reaches the expected updated version, or whether resources in the updated distributed software are increased or decreased as expected to determine whether the distributed software can be updated normally.
If the distributed software can be updated normally, step P5 is executed. Otherwise, step P6 is executed.
Step P5: and setting the pre-updating environment as an actual updating environment, and actually executing the updating operation of the distributed software in the actual updating environment.
In particular, corresponding support is provided for the whole updating operation of the distributed software in the actual updating environment, so that the updating operation of the distributed software can be completely executed.
Step P6: the cause of the anomaly that failed to update normally is checked.
Specifically, the cause of the abnormality can be checked in a system self-checking manner. For example, the reason analysis may be performed by checking whether the distributed software itself is operating normally, whether the obtained update information and the update data file are correct, and the like, and if the abnormality reason can be obtained, the step P1 is executed again, otherwise, the step P7 is executed.
Step P7: and sending out a prompt of abnormal updating, and exiting the updating process.
Because the system cannot accurately check the reason of the update abnormality, a prompt of the update abnormality needs to be sent out, so that a worker can further check the reason of the update abnormality through a manual checking mode, and the distributed software can be ensured to continuously complete the update operation after a short time.
The present application also includes providing a distributed software task execution system, as shown in fig. 2, where the distributed software task execution system includes one or more physical machines 203, distributed software 201, and virtual machines 202 connected to each other. Wherein the distributed software 201 runs in the physical machine 203, and the distributed software 201 comprises distributed software tasks (not shown in the figure);
the physical machine 203 executes a distributed software task execution method. Specifically, the number of the physical machines 203 is one or more, the physical machines 203 establish one or more virtual machines 202 according to the running information of the distributed software, or select a host physical machine 204 from the physical machines 203 to establish the virtual machine 202, the virtual machine 202 is used for executing one or more tasks in the distributed software tasks, and a processor on the system executes the method of the distributed software running, which is stored on a storage medium of the system in the form of computer instructions.
The application has the following beneficial effects:
(1) the distributed software running method and the distributed software running system can establish the corresponding virtual machine for running of the distributed software, the virtual machine uniformly executes distributed software tasks in the distributed software, and the completion speed of the distributed software tasks can be guaranteed while the running integrity of the distributed software is guaranteed.
(2) The distributed software running method and the distributed software running system can select the most appropriate low-consumption virtual machine to update the distributed software when the distributed software needs to be updated, select the most reasonable and resource-saving mode for updating the distributed software, and improve the resource utilization rate of the virtual machine.
(3) The method and the system for running the distributed software can execute the distributed software updating and can also pre-update the distributed software, thereby further guaranteeing the updating success rate of the distributed software.
Although the present application has been described with reference to examples, which are intended to be illustrative only and not to be limiting of the application, changes, additions and/or deletions may be made to the embodiments without departing from the scope of the application.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A method for running distributed software is characterized by comprising the following steps:
acquiring distributed software operation information;
establishing a plurality of virtual machines according to the running information of the distributed software, and issuing distributed tasks to the established virtual machines;
during the running of the virtual machine, responding to the received update instruction of the distributed software, and selecting the virtual machine for executing the update instruction;
updating the distributed software running on the selected virtual machine according to the selection result;
before the updating operation of the distributed software is executed, the method further comprises the following steps:
further acquiring update information of the distributed software;
acquiring an update data file according to the update information;
installing an update data file in a pre-update environment of a low-consumption virtual machine;
executing the pre-update of the distributed software in a pre-update environment, and judging whether the distributed software can be updated normally;
setting a pre-updating environment as an actual updating environment, and actually executing the updating operation of the distributed software in the actual updating environment;
checking abnormal reasons which cannot be updated normally;
sending out a prompt of abnormal updating, and exiting the updating process;
one or more distributed software tasks are established according to the distributed software type, and the number of the virtual machines is consistent with or greater than that of the distributed software tasks;
the number of the distributed software is one or more, and after the plurality of virtual machines are established, the distributed software tasks are established according to the type of the distributed software or the distributed software and the tasks contained in the distributed software.
2. The method for distributed software operation according to claim 1, wherein the acquiring the distributed software operation information specifically includes: responding to the running of the distributed software in one or more physical machines, and acquiring running information of the distributed software; the running information comprises resource information required by running of the distributed software and environment information of running of the distributed software.
3. The method for distributed software running according to claim 2, wherein if the number of the physical machines is one, the physical machines are used for establishing the virtual machines according to one or more pieces of running information of the distributed software.
4. The distributed software running method according to claim 2, wherein if the number of the physical machines is plural, one or more of the physical machines is/are selected as a main physical machine, and the main physical machine establishes the virtual machine according to one or more pieces of running information of the distributed software.
5. The method of distributed software execution according to claim 1, further comprising, in response to establishing the plurality of virtual machines, establishing corresponding distributed software tasks for the distributed software.
6. A method of distributed software execution as claimed in claim 5, wherein the number of virtual machines is not less than the number of distributed software tasks.
7. A method of distributed software execution as claimed in claim 1, characterized in that the selection of the virtual machine executing the update instruction comprises in particular the sub-steps of:
acquiring the service capacity of the virtual machine when the virtual machine is used for executing distributed software;
determining a standby virtual machine according to the service capacity of each virtual machine;
and selecting a low-consumption virtual machine, and establishing a pre-updating environment for updating the distributed software in the low-consumption virtual machine.
8. The method of distributed software execution according to claim 7, wherein the service capability is determined according to the time required by the virtual machine to execute the distributed software task and the size of the consumed resources.
9. The method for distributed software operation according to claim 8, wherein a specified number of standby virtual machines are selected as the low-consumption virtual machines to establish a pre-update environment of the distributed software for execution of the update instruction.
10. A distributed software execution system comprising one or more physical machines connected to each other, wherein the distributed software is executed on the physical machines, and wherein one or more virtual machines are established on the physical machines, and wherein the physical machines perform the method according to any one of claims 1 to 9.
CN201910599531.XA 2019-07-04 2019-07-04 Distributed software operation method and system Active CN110286937B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910599531.XA CN110286937B (en) 2019-07-04 2019-07-04 Distributed software operation method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910599531.XA CN110286937B (en) 2019-07-04 2019-07-04 Distributed software operation method and system

Publications (2)

Publication Number Publication Date
CN110286937A CN110286937A (en) 2019-09-27
CN110286937B true CN110286937B (en) 2021-06-15

Family

ID=68020615

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910599531.XA Active CN110286937B (en) 2019-07-04 2019-07-04 Distributed software operation method and system

Country Status (1)

Country Link
CN (1) CN110286937B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103164283A (en) * 2012-05-10 2013-06-19 上海兆民云计算科技有限公司 Method and system for dynamic scheduling management of virtualized resources in virtualized desktop system
CN106155763A (en) * 2015-04-21 2016-11-23 中兴通讯股份有限公司 Dispatching method of virtual machine and device
CN107977254A (en) * 2017-12-05 2018-05-01 郑州云海信息技术有限公司 The response method and computer-readable recording medium asked in cloud data system
CN108681461A (en) * 2018-05-07 2018-10-19 广东电网有限责任公司 A kind of clustered software system does not shut down newer method, system and relevant apparatus

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7607129B2 (en) * 2005-04-07 2009-10-20 International Business Machines Corporation Method and apparatus for using virtual machine technology for managing parallel communicating applications
KR101558047B1 (en) * 2013-09-09 2015-10-06 삼성에스디에스 주식회사 Cluster system and method for providing service availbility in cluster system
EP4071605A1 (en) * 2013-10-23 2022-10-12 Huawei Cloud Computing Technologies Co., Ltd. Method, system and apparatus for creating virtual machine
US9680965B2 (en) * 2015-04-01 2017-06-13 Alcatel-Lucent Usa Inc. Software upgrades for offline charging systems within a network
US20160344671A1 (en) * 2015-05-19 2016-11-24 Amazon Technologies, Inc. Executing commands on virtual machine instances in a distributed computing environment
CN105871928B (en) * 2016-06-21 2019-03-29 佛山科学技术学院 A kind of method of controlling security and system of distributed network
US10379835B2 (en) * 2016-12-19 2019-08-13 International Business Machines Corporation Optimized creation of distributed storage and distributed processing clusters on demand

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103164283A (en) * 2012-05-10 2013-06-19 上海兆民云计算科技有限公司 Method and system for dynamic scheduling management of virtualized resources in virtualized desktop system
CN106155763A (en) * 2015-04-21 2016-11-23 中兴通讯股份有限公司 Dispatching method of virtual machine and device
CN107977254A (en) * 2017-12-05 2018-05-01 郑州云海信息技术有限公司 The response method and computer-readable recording medium asked in cloud data system
CN108681461A (en) * 2018-05-07 2018-10-19 广东电网有限责任公司 A kind of clustered software system does not shut down newer method, system and relevant apparatus

Also Published As

Publication number Publication date
CN110286937A (en) 2019-09-27

Similar Documents

Publication Publication Date Title
US7395455B2 (en) System, method and program product for recovering from a failure
US20150100832A1 (en) Method and system for selecting and executing test scripts
CN111158715B (en) Gray release control method and system
CN113569987A (en) Model training method and device
US20110197193A1 (en) Device and method for controlling communication between bios and bmc
CN109766172B (en) Asynchronous task scheduling method and device
CN104809045A (en) Operation method and device of monitoring script
CN107479984B (en) Distributed spatial data processing system based on message
CN112579304A (en) Resource scheduling method, device, equipment and medium based on distributed platform
CN115373835A (en) Task resource adjusting method and device for Flink cluster and electronic equipment
CN113157411B (en) Celery-based reliable configurable task system and device
CN113805925A (en) Online upgrading method, device, equipment and medium for distributed cluster management software
CN115237566A (en) Batch task execution method, device, equipment, medium and product
CN112860251A (en) Method and system for constructing website front end
CN107025129B (en) Data processing method and device
CN101256484A (en) Method and equipment for determining to call at least one application program frequency
CN110286937B (en) Distributed software operation method and system
CN110928659B (en) Numerical value pool system remote multi-platform access method with self-adaptive function
JP5056464B2 (en) Process monitoring method, information processing apparatus, and program
US20110154349A1 (en) Resource fault management for partitions
CN110297692B (en) Distributed software task dynamic management method and system
CN113515293A (en) Method and system for managing DevOps tool chain
CN112231231A (en) Method, system and device for debugging cloud service
CN111679899A (en) Task scheduling method, device, platform equipment and storage medium
CN110928756A (en) Supercomputing platform resource use monitoring method

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
TA01 Transfer of patent application right

Effective date of registration: 20210527

Address after: 1311, Changhong science and technology building, No.18, Keji South 12th Road, high tech community, Yuehai street, Nanshan District, Shenzhen, Guangdong 518000

Applicant after: Shenzhen fingertip Interactive Entertainment Co.,Ltd.

Address before: 101300 room 3001, 3rd floor, 102 door, building 8, yard 12, Xinzhong street, Nanfaxin Town, Shunyi District, Beijing

Applicant before: Beijing Weijie Dongbo Information Technology Co.,Ltd.

TA01 Transfer of patent application right
GR01 Patent grant
GR01 Patent grant