CN114879981A - Installation method and device of cloud operating system, electronic equipment and storage medium - Google Patents
Installation method and device of cloud operating system, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114879981A CN114879981A CN202210594783.5A CN202210594783A CN114879981A CN 114879981 A CN114879981 A CN 114879981A CN 202210594783 A CN202210594783 A CN 202210594783A CN 114879981 A CN114879981 A CN 114879981A
- Authority
- CN
- China
- Prior art keywords
- installation
- sub
- task
- operating system
- cloud operating
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- 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)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The disclosure provides an installation method and device of a cloud operating system, electronic equipment and a storage medium, and relates to the technical field of cloud platforms. The specific implementation scheme is as follows: receiving an installation request, wherein the installation request carries a target sub-installation task identifier; the target sub-installation task identifier is an identifier of a sub-installation task in installation tasks of the cloud operating system; and executing installation operation aiming at the cloud operating system based on the target sub-installation task identification and the installation configuration file aiming at the cloud operating system. The technology disclosed by the invention can effectively improve the installation efficiency of the cloud operating system.
Description
Technical Field
The present disclosure relates to the technical field of artificial intelligence, and in particular, to the technical field of cloud platforms, and in particular, to a method and an apparatus for installing a cloud operating system, an electronic device, and a storage medium.
Background
When a private cloud product is delivered, a service provider generally installs a delivery base on a client side before formally installing the service. And then installing software corresponding to the service on the delivery base.
For example, a related art delivery base may include: the Kubernetes (k 8s for short) environment, which may also be referred to as a chassis, and the service provider's own middleware services such as database, cache, file services, etc. Where middleware services are required by other upper layer software. That is, the most basic K8S environment and middleware services may be collectively referred to as a delivery chassis. Since the delivery chassis is for use with private cloud products, it may also be referred to as a cloud operating system.
Disclosure of Invention
The disclosure provides an installation method and device of a cloud operating system, electronic equipment and a storage medium.
According to an aspect of the present disclosure, there is provided an installation method of a cloud operating system, including:
receiving an installation request, wherein the installation request carries a target sub-installation task identifier; the target sub-installation task identifier is an identifier of a sub-installation task in installation tasks of the cloud operating system;
and executing installation operation aiming at the cloud operating system based on the target sub-installation task identification and the installation configuration file aiming at the cloud operating system.
According to another aspect of the present disclosure, there is provided an installation apparatus of a cloud operating system, including:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving an installation request which carries a target sub-installation task identifier; the target sub-installation task identifier is an identifier of a sub-installation task in installation tasks of the cloud operating system;
and the processing module is used for executing the installation operation aiming at the cloud operating system based on the target sub-installation task identifier and the installation configuration file aiming at the cloud operating system.
According to still another aspect of the present disclosure, there is provided an electronic device including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method of the aspects and any possible implementation as described above.
According to yet another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of the above-described aspect and any possible implementation.
According to yet another aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the method of the aspects and any possible implementation as described above.
According to the technology disclosed by the invention, the installation efficiency of the cloud operating system can be effectively improved.
It should be understood that the statements in this section are not intended to identify key or critical features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is a schematic diagram according to a first embodiment of the present disclosure;
FIG. 2 is a schematic diagram according to a second embodiment of the present disclosure;
FIG. 3 is a schematic diagram according to a third embodiment of the present disclosure;
FIG. 4 is a schematic diagram according to a fourth embodiment of the present disclosure;
FIG. 5 is a schematic diagram according to a fifth embodiment of the present disclosure;
FIG. 6 is a block diagram of an electronic device used to implement methods of embodiments of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It is to be understood that the described embodiments are only a few, and not all, of the disclosed embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
It should be noted that the terminal device involved in the embodiments of the present disclosure may include, but is not limited to, a mobile phone, a Personal Digital Assistant (PDA), a wireless handheld device, a Tablet Computer (Tablet Computer), and other intelligent devices; the display device may include, but is not limited to, a personal computer, a television, and the like having a display function.
In addition, the term "and/or" herein is only one kind of association relationship describing an associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.
In the related art, when the cloud operating system is installed offline, after installation is started, the installation process cannot be controlled until installation is finished or an installation error occurs, so that installation failure is caused. Moreover, when an installation error occurs, the installation needs to be restarted from the beginning, which wastes time and labor and reduces installation efficiency.
FIG. 1 is a schematic diagram according to a first embodiment of the present disclosure; as shown in fig. 1, the present embodiment provides an installation method of a cloud operating system, which may be applied to an installation apparatus of a cloud operating system, and specifically includes the following steps:
s101, receiving an installation request, wherein the installation request carries a target sub-installation task identifier; the target sub-installation task identifier is an identifier of a sub-installation task in installation tasks of the cloud operating system;
s102, executing installation operation aiming at the cloud operating system based on the target sub-installation task identification and the installation configuration file aiming at the cloud operating system.
In the installation method of the cloud operating system in this embodiment, an installation request may be initiated to an installation apparatus of the cloud operating system by an installer of the cloud operating system through the human-machine interface module. The installation request may carry an identifier of a sub-installation task in the installation tasks of the cloud operating system, that is, a target sub-installation task identifier. That is, the installation task of the cloud operating system of the present embodiment may include a plurality of sub-installation tasks. The installation request may carry a target sub-installation task identifier. For the installation device of the cloud operating system, after receiving the installation request, the installation device may execute the installation operation for the cloud operating system based on the target sub-installation task identifier in the installation request and the installation configuration file for the cloud operating system. Wherein all files required in the installation of the cloud operating system can be included in the installation configuration file.
That is, the installation of the cloud operating system in the present embodiment does not have only one installation task as in the related art, and the installation needs to be restarted from the beginning after the installation is interrupted. In this embodiment, the installation operation for the cloud operating system may be executed based on the target sub-installation task identifier of the installation request, so that the installation of the cloud operating system of this embodiment may be performed with each sub-installation task as an object, and then the breakpoint installation of the cloud operating system is supported, which may effectively improve the installation efficiency of the cloud operating system.
According to the installation method of the cloud operating system, an installation request is received, and the installation request carries a target sub-installation task identifier; and executing installation operation aiming at the cloud operating system based on the target sub-installation task identifier and the installation configuration file, so that the installation operation of the cloud operating system can be carried out based on the sub-installation task of the cloud operating system, and the installation of the cloud operating system is more controllable. For example, when the installation fails, the sub-installation tasks which fail can be only reinstalled, so that the whole installation from the beginning is avoided, the installation time and labor can be effectively saved, and the installation efficiency is effectively improved.
FIG. 2 is a schematic diagram according to a second embodiment of the present disclosure; the embodiment provides an installation method of a cloud operating system, and based on the technical solution of the embodiment shown in fig. 1, the technical solution of the present disclosure is further described in more detail. As shown in fig. 2, the present embodiment provides an installation method of a cloud operating system, which specifically includes the following steps:
s201, receiving an installation request, wherein the installation request carries a target sub-installation task identifier and an installation strategy;
s202, based on the target sub-installation task identifier and the installation configuration file aiming at the cloud operating system, executing installation operation aiming at the cloud operating system according to an installation strategy.
Different from the embodiment shown in fig. 1, the installation request of this embodiment may also carry an installation policy. The installation strategy is used for limiting how to perform installation operation of the cloud operating system based on the target sub-installation task identification.
In an embodiment of the present disclosure, when implementing the installation, the step S202 may specifically include the following steps:
(1) acquiring corresponding installation information from an installation configuration file according to an installation strategy based on the target sub-installation task identifier;
(2) and executing installation operation aiming at the cloud operating system based on the installation information.
For example, the installation strategy of the present embodiment may include the following three cases:
in case one, the installation policy may require that only the installation operation of the target sub-installation task corresponding to the target sub-installation task identifier is performed. Correspondingly, in this case, the step (1) may be to acquire the installation information of the target sub-installation task from the installation configuration file based on the target sub-installation task identifier; the step (2) may be to perform an installation operation for the target sub-installation task in the cloud operating system based on the installation information of the target sub-installation task.
Optionally, in an embodiment of the present disclosure, the installation task of the cloud operating system may include a plurality of sub-installation tasks, and the identifiers corresponding to the plurality of sub-installation tasks may be stored in a task sequence table corresponding to the cloud operating system. The task sequence table of the cloud operating system is generated in advance, the task sequence table can comprise identifications of a plurality of sub-installation tasks, and each sub-installation task can be independently executed with installation operation. In addition, the task sequence table of the cloud operating system can also identify the execution sequence of the plurality of sub-installation tasks, and specifically, the plurality of sub-installation tasks can be sequentially executed in a serial manner; or part of the sub-installation tasks may be performed concurrently in parallel. Each sub-installation task may be independently performed for installation.
For example, if the number of the sub-installation tasks is n, the corresponding task sequence table may be represented as [ sub-installation task 1 identifier, sub-installation task 2 identifier, … …, sub-installation task n identifier ] according to the execution sequence of each sub-installation task. In addition, if part of the sub-installation tasks can be executed in parallel, the sub-installation tasks can be marked in the task sequence list. For example, preset symbol segmentation, such as colon, can be adopted between the identifiers of the sub-installation tasks executed in parallel. In this case, the corresponding task sequence table may be represented as [ sub-installation task 1 identifier, sub-installation task 2 identifier, sub-installation task 3 identifier, … …, and sub-installation task n identifier ], where sub-installation task 2 and sub-installation task 3 may be executed in parallel. In practical application, other manners may also be adopted to identify that different sub-installation tasks in the task sequence table may be executed in parallel, which is not described in detail herein.
The following two cases and three cases are implemented based on the task sequence table corresponding to the cloud operating system.
In case two, the installation policy may require that installation operations of all sub-installation tasks before the target sub-installation task identifier in the task sequence table are executed. Correspondingly, in this case, in the step (1), based on the target sub-installation task identifier, the installation information of all sub-installation tasks in the task sequence list before the sub-installation task identifier is obtained from the installation configuration file; for example, the identifiers of all the sub-installation tasks before the target sub-installation task identifier may be obtained from the task sequence table; and then acquiring installation information corresponding to the identifiers of all the sub installation tasks before the identifier of the target sub installation task in the task sequence list from the installation configuration file. In the step (2), based on the obtained installation information of all sub-installation tasks before the target sub-installation task identifier in the task sequence table, installation operations may be performed on all sub-installation tasks corresponding to all sub-installation task identifiers before the target sub-installation task identifier in the task sequence table. Specifically, in the installation operation execution process, the sub-installation tasks may be executed in sequence or in parallel based on the installation order of all the sub-installation tasks identified in the task sequence table.
And in case three, the installation strategy can require the installation of all the sub-installation tasks after the sub-installation task identifiers in the task sequence table are executed. Correspondingly, in this case, the step (1) may be to obtain, based on the sub-installation task identifier, installation information of all sub-installation tasks in the task sequence table after the sub-installation task identifier from the installation configuration file; for example, the identifiers of all the sub-installation tasks after the target sub-installation task identifier may be obtained from the task sequence table; and then acquiring installation information corresponding to the identifiers of all the sub installation tasks after the identifier of the target sub installation task in the task sequence list from the installation configuration file. The step (2) may be to perform installation operation on all sub-installation tasks corresponding to the target sub-installation task identifier in the task sequence table based on the installation information of all sub-installation tasks after the sub-installation task identifier in the task sequence table. Similarly, in the specific installation operation execution process, based on the installation order of all the sub-installation tasks identified in the task sequence table, the sub-installation tasks may be executed sequentially, or part of the sub-installation tasks may also be executed in parallel.
It should be noted that, in an embodiment of the present disclosure, if the installation request only carries the target subtask identifier and there is no installation policy, at this time, any one of the three situations may be defined, and in a specific implementation, the default situation may be configured in advance.
According to the installation method of the cloud operating system, the installation of the cloud operating system can be executed based on the target task identifier and the installation strategy in the installation request and in combination with the installation configuration file generated in advance, the installation of the cloud operating system in various situations can be realized, and the installation flexibility and the convenience are improved.
FIG. 3 is a schematic diagram according to a second embodiment of the present disclosure; the embodiment provides an installation method of a cloud operating system, and the technical solution of the present disclosure is further described in more detail on the basis of the technical solution of the embodiment shown in fig. 1 or 2. As shown in fig. 3, the present embodiment provides an installation method of a cloud operating system, which specifically includes the following steps:
s301, acquiring a task sequence table of the cloud operating system, wherein the task sequence table comprises identifiers of a plurality of sub-installation tasks;
for example, the task sequence table of the cloud operating system may be automatically generated by an installation apparatus of the cloud operating system. Or the operation information can be manually generated by an installer of the cloud operating system and prestored in the local or input into an installation device of the cloud operating system for use when the cloud operating system is installed.
For example, when the installation apparatus of the cloud operating system generates the task sequence table, the method may specifically include the following steps:
(a1) the method comprises the steps that on the principle that each sub-installation task can be independently executed, an installation task of the cloud operating system is divided into a plurality of sub-installation tasks;
specifically, the installation device of the cloud operating system may split the installation task of the cloud operating system by referring to the number of preset sub installation tasks to be split, based on the principle that each sub installation task can be independently executed. The amount here can be set according to practical experience or practical requirements. The split sub-installation tasks have a front-back dependency relationship, that is, the installation needs to be performed substantially according to a sequence, and of course, part of the sub-installation tasks can be performed in parallel. The installation operation of each sub-installation task may correspond to a phase. Namely, the installation process of the cloud operating system is split into n stages. The sub-installation tasks at each stage can independently perform installation operations.
(b1) And acquiring a task sequence table based on the plurality of sub-installation tasks.
For example, the dependency relationship between each sub-installation task and other sub-installation tasks may be obtained first; and then generating a task sequence list based on the dependency relationship between each sub-installation task and other sub-installation tasks.
Specifically, all installation information is included in the installation task of the cloud operating system. Referring to each sub-task split in the step (a1), the offline dependency information of each sub-task may be obtained from an installation task of the cloud operating system. For example, the offline dependency information of each subtask may include an installation package of the subtask, configuration information, and a dependency relationship of the subtask with other subtasks. Only the dependency relationship between each subtask and other subtasks can be obtained, the execution sequence of each subtask can be sequenced, and then a task sequence table of the cloud operating system is obtained. The task sequence table of the cloud operating system generated by the method is very accurate, the installation of the cloud operating system can be effectively guided, and the installation accuracy of the cloud operating system is ensured.
When the task sequence table of the cloud operating system is generated by the staff of the cloud operating system, the task sequence table can be implemented according to the above logic, and the task sequence table can be input to the installation device of the cloud operating system.
S302, generating an installation configuration file;
specifically, the step S302 may specifically be implemented by the following steps:
(a2) acquiring offline dependence information of each sub-installation task; the offline dependency information may include an installation package, configuration information, and dependency relationships with other subtasks; the configuration information includes parameter configuration or environment configuration in the installation process, and the like.
(b2) Acquiring a built-in shell command corresponding to each sub-installation task;
(c2) and generating an installation configuration file based on the offline dependency information of each sub-installation task and the corresponding built-in shell command.
The installation task of the existing cloud operating system can be regarded as an installation command of only one overall task, such as an overall target built-in shell command, namely an overall installation command. In this embodiment, the installation task of the cloud operating system is split into a plurality of sub-installation tasks, such as n sub-installation tasks. Correspondingly, the built-in shell command corresponding to each sub-installation task, i.e. the sub-installation command, needs to be configured. Namely, the method is equivalent to splitting a total target built-in shell command into sub-target built-in shell commands corresponding to n sub-installation tasks according to each sub-installation task in a task sequence table. The built-in shell command of each sub-target corresponds to one sub-installation task.
And then, arranging the offline dependency information of all the sub-installation tasks and the built-in shell commands of all the sub-installation tasks into an installation configuration file. In this way, in the installation process, the installation package, the configuration information and the like of each sub installation task do not need to be acquired through a network, the installation information corresponding to the sub installation task can be acquired directly based on the generated installation configuration file, for example, the installation information may include the installation command corresponding to the sub installation task, such as the corresponding built-in shell command, the installation package and the configuration information corresponding to the sub installation task, and further, the installation of each sub installation task may be realized based on the acquired installation information. By the method, the configuration file can be accurately configured, and a foundation is provided for accurate and effective installation of the cloud operating system.
S303, receiving an installation request triggered by an installer of the cloud operating system, wherein the installation request comprises a target sub-installation task identifier and an installation strategy;
s304, acquiring corresponding installation information from the generated installation configuration file according to an installation strategy based on the target sub-installation task identifier;
s305, executing installation operation aiming at the cloud operating system based on the acquired installation information;
specifically, the implementation of steps S304-S305 can refer to the three situations of the embodiment shown in fig. 2, which are not described herein again.
Optionally, in an embodiment of the present disclosure, the installation policy may not be carried in the installation request, and at this time, it may be preset that all installations are performed according to one situation of the embodiment shown in fig. 2.
S306, if the installation failure is detected, acquiring a failure sub-installation task identifier and/or a failure reason of the installation failure;
s307, displaying the failed sub-installation task identifier and/or the failure reason;
it should be noted that after the installation is performed, a specific installation process may cause an installation failure. At this point, the progress of the installation may be monitored at all times to determine whether the installation was successful or failed. Moreover, when the installation fails, the failed sub-installation task identifier and/or the failure reason of the installation failure may be recorded in a local error log, or other information corresponding to the sub-installation task with the installation failure may be recorded, but the failed sub-installation task identifier may be determined based on the other information. At this time, the identifier of the failed sub-installation task and/or the reason of the failure can be displayed so as to be checked by an installer in time and the reason of the failure can be checked. And after the investigation and the repair, the corresponding installation request of the cloud operating system can be initiated only aiming at the failed sub-installation task identifier. This mode can show failure information in real time when the installation fails to make things convenient for installer in time to investigate the problem, and repair the problem, and the implementation mode is very intelligent.
For example, if the installation policy is the second or third case of the embodiment shown in fig. 2, when the installation of a plurality of consecutive sub-installation tasks is performed, the installation may fail after the plurality of sub-installation tasks are successfully installed. At this time, the sub-installation tasks corresponding to the sub-installation task identifiers before the failed sub-installation task identifier in the task sequence list are all installed successfully, and continuous re-installation is not needed. And the subsequent installation only needs to install the failed sub-installation task identifier and the sub-installation task positioned behind the failed sub-installation task identifier and the task sequence table. In the specific installation process, the way of the case one in the embodiment shown in fig. 2 can be adopted, and one sub-installation task is used for installation. Installation may also be performed as described above in the case three of the embodiment shown in fig. 2.
The installation method of the embodiment can also display the installation progress of each sub-installation task of the cloud operating system in real time based on the task sequence table. Specifically, the state corresponding to each sub-installation task identifier in the task sequence table is displayed in real time as being successfully installed or not installed.
S308, receiving a new installation request carrying the failed sub-installation task identifier and the new installation strategy;
s309, based on the failed sub-installation task identifier and the installation configuration file, executing installation operation of the sub-installation tasks of the cloud operating system according to the new installation strategy until all the sub-installation tasks of the cloud operating system are installed, and achieving installation of the cloud operating system.
Optionally, step S308 may not carry the installation policy, and at this time, the corresponding step S309 may be executed according to the preset installation policy. In the installation process of the step S309, if an installation failure occurs, continuing to return to the step S306, and repeating the process until all the sub-installation tasks in the task sequence list are installed, so as to implement installation of the cloud operating system. Based on this, it can be seen that the installation method of the cloud operating system of this embodiment can continue to install the cloud operating system based on the failed sub-installation task identifier after the installation fails and after troubleshooting, and the installation of this manner can support breakpoint installation, and does not need to start installation from the beginning again after each failure, and can effectively improve the installation efficiency of the cloud operating system.
According to the technology of the embodiment, when a private cloud product is delivered, the cloud operating system, namely a delivery base, including a k8s environment and a middleware service can be installed offline on a client side quickly, accurately and efficiently in the manner of the embodiment. The service to be delivered can then be installed based on the k8s environment and the middleware service, which is very convenient to use.
The installation method of the cloud operating system can reasonably and accurately configure the task sequence list and the installation configuration file, and provides a basis for installation of the cloud operating system. In addition, through the installation in the mode, when the installation is wrong, the installation does not need to be restarted, the installation can be restarted from the installation error point, the breakpoint installation is realized, the installation efficiency can be greatly improved, and the installation time is effectively saved.
FIG. 4 is a schematic diagram according to a fourth embodiment of the present disclosure; as shown in fig. 4, the present embodiment provides an installation apparatus 400 of a cloud operating system, including:
a receiving module 401, configured to receive an installation request, where the installation request carries a target sub-installation task identifier; the target sub-installation task identifier is an identifier of a sub-installation task in installation tasks of the cloud operating system;
a processing module 402, configured to execute an installation operation for the cloud operating system based on the target sub-installation task identifier and the installation configuration file for the cloud operating system.
The implementation principle and technical effect of the installation of the cloud operating system by using the modules in the installation apparatus 400 of the cloud operating system in this embodiment are the same as those of the related method embodiments, and reference may be made to the description of the related method embodiments in detail, which is not described herein again.
FIG. 5 is a schematic diagram according to a fifth embodiment of the present disclosure; this embodiment further introduces the technical solution of the present disclosure in more detail based on the embodiment shown in fig. 4. As shown in fig. 5, the installation apparatus 500 of the cloud operating system of the present embodiment includes a receiving module 501 and a processing module 502, which are the same-name functional modules as those of the embodiment shown in fig. 4.
In this embodiment, the installation request received by the receiving module 501 may further include an installation policy;
specifically, the processing module 502 is configured to:
and executing installation operation aiming at the cloud operating system according to the installation strategy based on the target sub-installation task identifier and the installation configuration file.
Further optionally, as shown in fig. 5, in the installation apparatus 500 of the cloud operating system in this embodiment, the processing module 502 may include:
an obtaining unit 5021, configured to obtain corresponding installation information from an installation configuration file according to an installation policy based on a target sub-installation task identifier;
an execution unit 5022, configured to execute an installation operation for the cloud operating system based on the installation information.
Further optionally, in an embodiment of the present disclosure, the obtaining unit 5021 is configured to:
if the installation strategy requires that only the installation operation of the target sub-installation task corresponding to the target sub-installation task identifier is executed, acquiring the installation information of the target sub-installation task from the installation configuration file based on the target sub-installation task identifier;
an execution unit 5022, configured to:
and executing installation operation aiming at the target sub-installation task in the cloud operating system based on the installation information of the target sub-installation task.
Further optionally, in an embodiment of the present disclosure, the installation task of the cloud operating system includes a plurality of sub-installation tasks, and identifiers corresponding to the plurality of sub-installation tasks are stored in a task sequence table corresponding to the cloud operating system.
Further optionally, in an embodiment of the present disclosure, the obtaining unit 5021 is configured to:
if the installation strategy requires to execute the installation operation of all sub-installation tasks before the target sub-installation task identifier in the task sequence table, acquiring the installation information of all sub-installation tasks before the target sub-installation task identifier in the task sequence table from the installation configuration file based on the target sub-installation task identifier;
an execution unit 5022, configured to:
and executing installation operation on all sub-installation tasks corresponding to the target sub-installation task identifier in the task sequence list based on the installation information of all sub-installation tasks before the target sub-installation task identifier in the task sequence list.
Further optionally, in an embodiment of the present disclosure, the obtaining unit 5021 is configured to:
if the installation strategy requires to execute the installation of all sub-installation tasks after the target sub-installation task identifier in the task sequence table, acquiring the installation information of all sub-installation tasks after the target sub-installation task identifier in the task sequence table from the installation configuration file based on the target sub-task identifier;
an execution unit 5022, configured to:
and executing installation operation on all the corresponding sub-installation tasks after the target sub-installation task identifier in the task sequence table based on the installation information of all the sub-installation tasks after the target sub-installation task identifier in the task sequence table.
Further optionally, as shown in fig. 5, the installation apparatus 500 of the cloud operating system of this embodiment further includes:
a failure information obtaining module 503, configured to, if it is detected that the installation fails, obtain a failed sub-installation task identifier and/or a failure reason of the installation failure;
and the display module 504 is configured to display the failed sub-installation task identifier and/or the failure reason.
Further optionally, in the installation apparatus 500 of the cloud operating system of this embodiment, the receiving module 501 is further configured to receive a new installation request carrying the failed sub-installation task identifier and the new installation policy;
the processing module 502 is further configured to execute an installation operation of the corresponding sub-installation task of the cloud operating system according to the new installation policy based on the failed sub-installation task identifier and the installation configuration file.
Further optionally, as shown in fig. 5, the installation apparatus 500 of the cloud operating system of this embodiment further includes:
a task sequence table obtaining module 505, configured to:
the method comprises the steps that on the principle that each sub-installation task can be independently executed, an installation task of the cloud operating system is divided into a plurality of sub-installation tasks;
a task sequence table is obtained based on a plurality of sub-installation tasks.
Further optionally, the task sequence table obtaining module 505 is configured to:
acquiring the dependency relationship between each sub-installation task and other sub-installation tasks;
and generating a task sequence list based on the dependency relationship between each sub-installation task and other sub-installation tasks.
A generating module 506 for:
acquiring offline dependence information of each sub-installation task; the offline dependency information comprises an installation file package, configuration information and dependency relationship with other sub-installation tasks;
acquiring a built-in shell command corresponding to each sub-installation task;
and generating an installation configuration file based on the offline dependency information of each sub-installation task and the corresponding built-in shell command.
The implementation principle and technical effect of the installation of the cloud operating system by using the modules in the installation apparatus 500 of the cloud operating system in this embodiment are the same as those of the related method embodiments, and reference may be made to the description of the related method embodiments in detail, which is not described herein again.
In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, and do not violate the good customs of the public order.
The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.
FIG. 6 illustrates a schematic block diagram of an example electronic device 600 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 6, the apparatus 600 includes a computing unit 601, which can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)602 or a computer program loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 can also be stored. The calculation unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
A number of components in the device 600 are connected to the I/O interface 605, including: an input unit 606 such as a keyboard, a mouse, or the like; an output unit 607 such as various types of displays, speakers, and the like; a storage unit 608, such as a magnetic disk, optical disk, or the like; and a communication unit 609 such as a network card, modem, wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 601 performs the respective methods and processes described above, such as the above-described methods of the present disclosure. For example, in some embodiments, the above-described methods of the present disclosure may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 600 via the ROM 602 and/or the communication unit 609. When the computer program is loaded into the RAM 603 and executed by the computing unit 601, one or more steps of the above-described method of the present disclosure described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured by any other suitable means (e.g., by means of firmware) to perform the above-described methods of the present disclosure.
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server combining a blockchain.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.
The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.
Claims (27)
1. A cloud operating system installation method comprises the following steps:
receiving an installation request, wherein the installation request carries a target sub-installation task identifier; the target sub-installation task identifier is an identifier of a sub-installation task in installation tasks of the cloud operating system;
and executing installation operation aiming at the cloud operating system based on the target sub-installation task identification and the installation configuration file aiming at the cloud operating system.
2. The method of claim 1, wherein the installation request further includes an installation policy; executing installation operation aiming at the cloud operating system based on the target sub-installation task identification and the installation configuration file aiming at the cloud operating system, wherein the installation operation aiming at the cloud operating system comprises the following steps:
and executing installation operation aiming at the cloud operating system according to the installation strategy based on the target sub-installation task identifier and the installation configuration file.
3. The method of claim 2, performing installation operations for the cloud operating system in accordance with the installation policy based on the target sub-installation task identification and the installation configuration file, comprising:
acquiring corresponding installation information from the installation configuration file according to the installation strategy based on the target sub-installation task identifier;
and executing installation operation aiming at the cloud operating system based on the installation information.
4. The method of claim 3, wherein obtaining corresponding installation information from the installation configuration file according to the installation policy based on the target sub-installation task identifier comprises:
if the installation strategy requires to execute only the installation operation of the target sub-installation task corresponding to the target sub-installation task identifier, acquiring the installation information of the target sub-installation task from the installation configuration file based on the target sub-installation task identifier;
based on the installation information, executing installation operation aiming at the cloud operating system, wherein the installation operation comprises the following steps:
and executing installation operation aiming at the target sub-installation task in the cloud operating system based on the installation information of the target sub-installation task.
5. The method of claim 3, wherein the installation task of the cloud operating system comprises a plurality of sub-installation tasks, and identifications corresponding to the plurality of sub-installation tasks are stored in a task sequence table corresponding to the cloud operating system.
6. The method of claim 5, wherein obtaining corresponding installation information from the installation configuration file according to the installation policy based on the target sub-installation task identifier comprises:
if the installation strategy requires to execute installation operation of all sub-installation tasks before the target sub-installation task identifier in the task sequence table, acquiring installation information of all sub-installation tasks before the target sub-installation task identifier in the task sequence table from the installation configuration file based on the target sub-installation task identifier;
based on the installation information, executing installation operation aiming at the cloud operating system, wherein the installation operation comprises the following steps:
and executing installation operation on all sub-installation tasks corresponding to the target sub-installation task identifier in the task sequence list based on the installation information of all sub-installation tasks before the target sub-installation task identifier in the task sequence list.
7. The method of claim 5, wherein obtaining corresponding installation information from the installation configuration file according to the installation policy based on the target sub-installation task identifier comprises:
if the installation strategy requires to execute installation of all sub-installation tasks after the target sub-installation task identifier in the task sequence table, acquiring installation information of all sub-installation tasks after the target sub-installation task identifier in the task sequence table from the installation configuration file based on the target sub-task identifier;
based on the installation information, executing installation operation aiming at the cloud operating system, wherein the installation operation comprises the following steps:
and executing installation operation on all sub-installation tasks corresponding to the target sub-installation task identifier in the task sequence table based on the installation information of all sub-installation tasks after the target sub-installation task identifier in the task sequence table.
8. The method of any of claims 1-7, wherein after performing the installation operation for the cloud operating system based on the target sub-installation task identification and the installation configuration file for the cloud operating system, the method further comprises:
if the installation failure is detected, acquiring a failure sub-installation task identifier and/or a failure reason of the installation failure;
and displaying the failed sub-installation task identifier and/or the failure reason.
9. The method of claim 8, wherein after presenting the loser install task identification, further comprising:
receiving a new installation request carrying the failed sub-installation task identifier and a new installation strategy;
and executing the installation operation of the corresponding sub installation task of the cloud operating system according to the new installation strategy based on the failed sub installation task identifier and the installation configuration file.
10. The method of any of claims 1-7, wherein prior to receiving the installation request, the method further comprises:
splitting the installation task of the cloud operating system into a plurality of sub-installation tasks on the basis that each sub-installation task can be independently executed;
and acquiring the task sequence list based on the plurality of sub-installation tasks.
11. The method of claim 10, wherein obtaining the task sequence list based on the plurality of sub-installation tasks comprises:
acquiring the dependency relationship between each sub-installation task and other sub-installation tasks;
and generating the task sequence list based on the dependency relationship between each sub-installation task and other sub-installation tasks.
12. The method of any of claims 1-7, wherein prior to performing the installation operation for the cloud operating system based on the target sub-installation task identification and the installation configuration file for the cloud operating system, the method further comprises:
acquiring offline dependence information of each sub-installation task; the offline dependency information comprises an installation package, configuration information and dependency relationship with other sub-installation tasks;
acquiring a built-in shell command corresponding to each sub-installation task;
and generating the installation configuration file based on the offline dependency information of each sub-installation task and the corresponding built-in shell command.
13. An installation apparatus of a cloud operating system, comprising:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving an installation request which carries a target sub-installation task identifier; the target sub-installation task identifier is an identifier of a sub-installation task in installation tasks of the cloud operating system;
and the processing module is used for executing the installation operation aiming at the cloud operating system based on the target sub-installation task identifier and the installation configuration file aiming at the cloud operating system.
14. The apparatus of claim 13, wherein the installation request further includes an installation policy; the processing module is configured to:
and executing installation operation aiming at the cloud operating system according to the installation strategy based on the target sub-installation task identifier and the installation configuration file.
15. The apparatus of claim 14, the processing module, comprising:
an obtaining unit, configured to obtain, based on the target sub-installation task identifier, corresponding installation information from the installation configuration file according to the installation policy;
an execution unit configured to execute an installation operation for the cloud operating system based on the installation information.
16. The apparatus of claim 15, wherein the obtaining unit is configured to:
if the installation strategy requires to execute only the installation operation of the target sub-installation task corresponding to the target sub-installation task identifier, acquiring the installation information of the target sub-installation task from the installation configuration file based on the target sub-installation task identifier;
the execution unit is configured to:
and executing installation operation aiming at the target installation subtask in the cloud operating system based on the installation information of the target installation subtask.
17. The apparatus of claim 15, wherein the installation task of the cloud operating system comprises a plurality of sub-installation tasks, and identifiers corresponding to the plurality of sub-installation tasks are stored in a task sequence table corresponding to the cloud operating system.
18. The apparatus of claim 17, wherein the obtaining unit is configured to:
if the installation strategy requires to execute installation operation of all sub-installation tasks before the target sub-installation task identifier in the task sequence table, acquiring installation information of all sub-installation tasks before the target sub-installation task identifier in the task sequence table from the installation configuration file based on the target sub-installation task identifier;
the execution unit is configured to:
and executing installation operation on all sub-installation tasks corresponding to the target sub-installation task identifier in the task sequence list based on the installation information of all sub-installation tasks before the target sub-installation task identifier in the task sequence list.
19. The apparatus of claim 17, wherein the obtaining unit is configured to:
if the installation strategy requires to execute installation of all sub-installation tasks after the target sub-installation task identifier in the task sequence table, acquiring installation information of all sub-installation tasks after the target sub-installation task identifier in the task sequence table from the installation configuration file based on the target sub-task identifier;
the execution unit is configured to:
and executing installation operation on all sub-installation tasks corresponding to the target sub-installation task identifier in the task sequence table based on the installation information of all sub-installation tasks after the target sub-installation task identifier in the task sequence table.
20. The apparatus of any of claims 13-19, wherein the apparatus further comprises:
the failure information acquisition module is used for acquiring a failure sub-installation task identifier and/or a failure reason of the installation failure if the installation failure is detected;
and the display module is used for displaying the failed sub-installation task identifier and/or the failure reason.
21. The apparatus of claim 20, wherein:
the receiving module is further configured to receive a new installation request carrying the failed sub-installation task identifier and a new installation policy;
and the processing module is further configured to execute an installation operation of the corresponding sub-installation task of the cloud operating system according to the new installation policy based on the failed sub-installation task identifier and the installation configuration file.
22. The apparatus of any of claims 13-19, wherein the apparatus further comprises:
a task sequence table acquisition module configured to:
splitting the installation task of the cloud operating system into a plurality of sub-installation tasks on the basis that each sub-installation task can be independently executed;
and acquiring the task sequence list based on the plurality of sub-installation tasks.
23. The apparatus of claim 22, wherein the task sequence table obtaining module is configured to:
acquiring the dependency relationship between each sub-installation task and other sub-installation tasks;
and generating the task sequence list based on the dependency relationship between each sub-installation task and other sub-installation tasks.
24. The apparatus of any of claims 13-19, further comprising:
a generation module to:
acquiring offline dependence information of each sub-installation task; the offline dependency information comprises an installation package, configuration information and dependency relationship with other sub-installation tasks;
acquiring a built-in shell command corresponding to each sub-installation task;
and generating the installation configuration file based on the offline dependency information of each sub-installation task and the corresponding built-in shell command.
25. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-12.
26. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-12.
27. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210594783.5A CN114879981B (en) | 2022-05-27 | 2022-05-27 | Cloud operating system installation method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210594783.5A CN114879981B (en) | 2022-05-27 | 2022-05-27 | Cloud operating system installation method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114879981A true CN114879981A (en) | 2022-08-09 |
| CN114879981B CN114879981B (en) | 2023-06-06 |
Family
ID=82679724
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210594783.5A Active CN114879981B (en) | 2022-05-27 | 2022-05-27 | Cloud operating system installation method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114879981B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100031248A1 (en) * | 2008-07-31 | 2010-02-04 | Microsoft Corporation | Installation Sequence Manager |
| CN104166571A (en) * | 2014-08-15 | 2014-11-26 | 百度在线网络技术（北京）有限公司 | Software installation control method and device |
| CN107741904A (en) * | 2017-09-14 | 2018-02-27 | 平安科技（深圳）有限公司 | Test machine method of automatic configuration, device, equipment and storage medium |
| US20180365067A1 (en) * | 2016-05-31 | 2018-12-20 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method for Assigning Installation Task and Terminal Device |
| CN109165027A (en) * | 2018-08-10 | 2019-01-08 | 郑州市景安网络科技股份有限公司 | VME operating system installation method, device, equipment and readable storage medium storing program for executing |
| CN109254783A (en) * | 2018-09-18 | 2019-01-22 | 郑州云海信息技术有限公司 | A kind of server system installation method, device, equipment and readable storage medium storing program for executing |
| CN110045969A (en) * | 2019-04-23 | 2019-07-23 | 广东小天才科技有限公司 | Application program installation method, server, system, equipment and storage medium |
| CN110597613A (en) * | 2018-06-12 | 2019-12-20 | 成都鼎桥通信技术有限公司 | Task processing method, device, equipment and computer readable storage medium |
| CN111258591A (en) * | 2020-01-14 | 2020-06-09 | 广州极晟网络技术有限公司 | Program deployment task execution method and device, computer equipment and storage medium |
| CN111309357A (en) * | 2020-02-24 | 2020-06-19 | 腾讯科技(成都)有限公司 | Cloud game software updating method and device, storage medium and cloud game system |
| CN113946816A (en) * | 2021-10-15 | 2022-01-18 | 北京百度网讯科技有限公司 | Cloud service-based authentication method and device, electronic equipment and storage medium |
| CN114237853A (en) * | 2021-12-21 | 2022-03-25 | 建信金融科技有限责任公司 | Task execution method, device, equipment, medium and program product applied to heterogeneous system |
-
2022
- 2022-05-27 CN CN202210594783.5A patent/CN114879981B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100031248A1 (en) * | 2008-07-31 | 2010-02-04 | Microsoft Corporation | Installation Sequence Manager |
| CN104166571A (en) * | 2014-08-15 | 2014-11-26 | 百度在线网络技术（北京）有限公司 | Software installation control method and device |
| US20180365067A1 (en) * | 2016-05-31 | 2018-12-20 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method for Assigning Installation Task and Terminal Device |
| CN107741904A (en) * | 2017-09-14 | 2018-02-27 | 平安科技（深圳）有限公司 | Test machine method of automatic configuration, device, equipment and storage medium |
| CN110597613A (en) * | 2018-06-12 | 2019-12-20 | 成都鼎桥通信技术有限公司 | Task processing method, device, equipment and computer readable storage medium |
| CN109165027A (en) * | 2018-08-10 | 2019-01-08 | 郑州市景安网络科技股份有限公司 | VME operating system installation method, device, equipment and readable storage medium storing program for executing |
| CN109254783A (en) * | 2018-09-18 | 2019-01-22 | 郑州云海信息技术有限公司 | A kind of server system installation method, device, equipment and readable storage medium storing program for executing |
| CN110045969A (en) * | 2019-04-23 | 2019-07-23 | 广东小天才科技有限公司 | Application program installation method, server, system, equipment and storage medium |
| CN111258591A (en) * | 2020-01-14 | 2020-06-09 | 广州极晟网络技术有限公司 | Program deployment task execution method and device, computer equipment and storage medium |
| CN111309357A (en) * | 2020-02-24 | 2020-06-19 | 腾讯科技(成都)有限公司 | Cloud game software updating method and device, storage medium and cloud game system |
| CN113946816A (en) * | 2021-10-15 | 2022-01-18 | 北京百度网讯科技有限公司 | Cloud service-based authentication method and device, electronic equipment and storage medium |
| CN114237853A (en) * | 2021-12-21 | 2022-03-25 | 建信金融科技有限责任公司 | Task execution method, device, equipment, medium and program product applied to heterogeneous system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114879981B (en) | 2023-06-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112653758B (en) | Method, device, equipment and medium for updating edge node | |
| CN115794257B (en) | System starting method, device, electronic equipment and storage medium | |
| CN115373861B (en) | GPU resource scheduling method and device, electronic equipment and storage medium | |
| CN114025037B (en) | Cloud mobile phone overhaul method and device, electronic equipment and storage medium | |
| CN113885911A (en) | Robot version updating method and device based on RPA and AI | |
| CN113609027A (en) | ARM cloud server testing method and device, electronic equipment and storage medium | |
| CN113220367A (en) | Applet running method and device, electronic equipment and storage medium | |
| CN111767149A (en) | Scheduling method, device, equipment and storage equipment | |
| CN114879981A (en) | Installation method and device of cloud operating system, electronic equipment and storage medium | |
| CN115599438A (en) | Method, device, equipment and medium for constructing application program publishing package | |
| CN115454872A (en) | Database test method, device, equipment and storage medium | |
| CN112667255B (en) | Updating method, updating device, electronic equipment and storage medium | |
| CN112148447B (en) | Task processing method and system based on risk control and electronic equipment | |
| CN114389969A (en) | Client test method and device, electronic equipment and storage medium | |
| CN114218166A (en) | Data processing method and device, electronic equipment and readable storage medium | |
| CN114374703A (en) | Method, device and equipment for acquiring cloud mobile phone information and storage medium | |
| CN114116487A (en) | Pressure testing method and device, electronic equipment and storage medium | |
| CN112965836A (en) | Service control method and device, electronic equipment and readable storage medium | |
| US10296425B2 (en) | Optimizing data processing across server clusters and data centers using checkpoint-based data replication | |
| CN111694686A (en) | Abnormal service processing method and device, electronic equipment and storage medium | |
| CN116521199B (en) | Component upgrading method, device, equipment and storage medium | |
| CN115993983A (en) | Software updating method, device, electronic equipment and medium | |
| CN114398616A (en) | Login method and device of embedded system, electronic equipment and readable storage medium | |
| CN115061817A (en) | Operation and maintenance method, device, system and computer program product | |
| CN114090024A (en) | Interlocking equipment burning method, device, equipment and storage medium |
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 |