CN114035952A

CN114035952A - Server task implementation method and device, readable storage medium and electronic equipment

Info

Publication number: CN114035952A
Application number: CN202111318295.3A
Authority: CN
Inventors: 苏保林; 余海涛; 江芳正
Original assignee: Netease Hangzhou Network Co Ltd
Current assignee: Netease Hangzhou Network Co Ltd
Priority date: 2021-11-09
Filing date: 2021-11-09
Publication date: 2022-02-11

Abstract

The disclosure relates to a method and a device for realizing server tasks, a readable storage medium and electronic equipment, and relates to the technical field of computers, wherein the method comprises the following steps: acquiring a target task of a target server and task parameters corresponding to the target task, and storing the task parameters to a distribution queue; acquiring current task parameters included in the distribution queue, determining an executable operation list corresponding to the current task parameters, and storing executable operations in the executable operation list into an operation queue; and acquiring executable operations in the operation queue for execution, and completing the target task of the target server after all executable operations in the executable operation list are executed successfully. The method and the device improve the efficiency of the task realization of the server.

Description

Server task implementation method and device, readable storage medium and electronic equipment

Technical Field

The embodiment of the disclosure relates to the technical field of computers, and in particular relates to a server task implementation method, a server task implementation device, a readable storage medium and an electronic device.

Background

The server has high-speed CPU computing capacity, long-time reliable operation, strong input and output external data throughput capacity and better expansibility, and can provide computing or application services for other clients in a network.

However, the implementation of the server task at present depends on manual operation, and the manual operation has the problems of time delay and low execution efficiency, so that the unavailable time of the server is prolonged; in addition, manual operation is uncontrollable, the quality and safety of operation are difficult to ensure, and normal application service is affected.

Therefore, a new server task implementation method needs to be provided.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

An object of the present disclosure is to provide a server task implementation method, a server task implementation apparatus, a readable storage medium, and an electronic device, so as to overcome, at least to some extent, the problem of low server task implementation efficiency due to limitations and disadvantages of the related art.

According to one aspect of the present disclosure, a server task implementation method is provided, including:

acquiring a target task of a target server and task parameters corresponding to the target task, and storing the task parameters to a distribution queue;

acquiring current task parameters included in the distribution queue, determining an executable operation list corresponding to the current task parameters, and storing executable operations in the executable operation list into an operation queue;

and acquiring executable operations in the operation queue for execution, and completing the target task of the target server after all executable operations in the executable operation list are executed successfully.

In an exemplary embodiment of the present disclosure, acquiring a task parameter corresponding to the target task, and storing the task parameter to a distribution queue includes:

acquiring a unique identifier and a type of a target task, initialization operation of the target task and an initialization state of the initialization operation, wherein the unique identifier and the type of the target task are included in the task parameters;

generating a task key value pair according to the task parameter, and storing the task key value pair to the distribution queue; the unique identification and the type of the target task and an initialization operation key of the target task are set; the initialization state of the initialization operation is a value.

In an exemplary embodiment of the present disclosure, acquiring a current task parameter included in the distribution queue, and determining an executable operation list corresponding to the current task parameter includes:

monitoring the distribution queue to obtain a current task key value pair included in the distribution queue;

and determining an executable operation list corresponding to the type of the target task according to the type of the target task included in the key of the current task key value pair.

In an exemplary embodiment of the present disclosure, saving the executable operations in the executable operation list to an operation queue includes:

generating an operation key value pair according to the unique identification and the type of the target task, a first executable operation in the executable operation list and the operation state of the first executable operation; the unique identification and the type of the target task, the first executable operation are keys, and the operation state of the first executable operation is a value;

determining an operation type of the first executable operation;

and storing the operation key value pair into an operation queue corresponding to the operation type according to the operation type of the first executable operation.

In an exemplary embodiment of the present disclosure, acquiring an executable operation in the operation queue for execution includes:

monitoring the operation queue to acquire the current executable operation in the operation queue;

determining an execution thread corresponding to the current executable operation, and starting the execution thread to execute the current executable operation;

and after the execution of the current executable operation is finished, updating the operation state of the current executable operation.

In an exemplary embodiment of the present disclosure, after updating the operation state of the current executable operation, the server task implementation method further includes:

updating the operating state of the current executable operation stored in a distribution queue;

when the change of the operation state of the current executable operation is monitored in the distribution queue, acquiring the next executable operation of the current executable operation;

and generating an operation key value pair corresponding to the next executable operation, and storing the operation key value pair corresponding to the next executable operation into the operation queue.

In an exemplary embodiment of the present disclosure, the server task implementation method further includes:

acquiring the preset execution time of the target task, and storing the preset execution time of the target task to an overtime queue;

monitoring the overtime queue, and updating the overtime time of the target task and triggering alarm information when the execution time of the target task is greater than the preset execution time.

According to an aspect of the present disclosure, there is provided a server task implementation apparatus, including:

the target task distribution module is used for acquiring a target task of a target server and task parameters corresponding to the target task and storing the task parameters to a distribution queue;

an executable operation determining module, configured to obtain a current task parameter included in the distribution queue, determine an executable operation list corresponding to the current task parameter, and store an executable operation in the executable operation list in an operation queue;

and the executable operation execution module is used for acquiring executable operations in the operation queue for execution, and completing the target task of the target server after all executable operations in the executable operation list are executed successfully.

According to an aspect of the present disclosure, there is provided a readable storage medium, on which a computer program is stored, the computer program, when executed by a processor, implementing the server task implementation method according to any of the above exemplary embodiments.

According to an aspect of the present disclosure, there is provided an electronic device including:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is configured to execute the server task implementation method of any of the above exemplary embodiments via execution of the executable instructions.

The server task implementation method provided by the embodiment of the disclosure acquires a target task of a target server and task parameters corresponding to the target task, and stores the task parameters to a distribution queue; acquiring current task parameters included in the distribution queue, determining an executable operation list corresponding to the current task parameters, and storing executable operations in the executable operation list into an operation queue; obtaining executable operations in the operation queue for execution, and completing a target task of the target server after all executable operations in the executable operation list are successfully executed; on one hand, the task parameters of the acquired target tasks are stored in a distribution queue, the distribution queue is monitored to acquire the current task parameters in the distribution queue, an executable operation list corresponding to the current task parameters is determined, executable operations in the executable operation list are stored in an operation queue, and the executable operations in the operation queue are executed to complete the server tasks, so that the automatic realization of the server tasks is realized, the problems that the realization of the server tasks in the prior art depends on manual operation, the manual operation has time delay and low execution efficiency are solved, and the realization efficiency of the server tasks is improved; on the other hand, the automatic realization of the server task is realized, so that the quality and the safety of the realization of the server task are ensured.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.

Fig. 1 schematically shows a flow chart of a server task implementation method according to an example embodiment of the present disclosure.

Fig. 2 schematically illustrates a block diagram of a server task implementation system according to an example embodiment of the present disclosure.

Fig. 3 schematically illustrates a connection manner diagram of components included in a server task implementation system according to an example embodiment of the present disclosure.

Fig. 4 schematically illustrates a flowchart of a method for acquiring task parameters corresponding to a target task and storing the task parameters in a distribution queue according to an exemplary embodiment of the present disclosure.

Fig. 5 schematically illustrates a block diagram of a server operating system according to an example embodiment of the present disclosure.

Fig. 6 is a flowchart schematically illustrating a method for obtaining a current task parameter included in a distribution queue and determining an executable operation list corresponding to the current task parameter, according to an example embodiment of the present disclosure.

FIG. 7 is a flow chart that schematically illustrates a method for saving an executable operation in a list of executable operations to an operation queue, in accordance with an illustrative embodiment of the present disclosure.

FIG. 8 is a flow chart that schematically illustrates a method for obtaining executable operations in an operation queue for execution, in accordance with an exemplary embodiment of the present disclosure.

FIG. 9 schematically shows a flowchart of a server task implementation method after updating an operational state for a current executable operation, according to an example embodiment of the present disclosure.

Fig. 10 schematically illustrates a diagram of a target task implementation process according to an example embodiment of the present disclosure.

Fig. 11 schematically shows a flow chart of a server task implementation method according to an example embodiment of the present disclosure.

Fig. 12 is a schematic diagram schematically illustrating a method for implementing a server task when a target task is a reload task according to an example embodiment of the present disclosure.

Fig. 13 schematically illustrates a block diagram of a server task implementation device according to an example embodiment of the present disclosure.

Fig. 14 schematically illustrates an electronic device for implementing the above-described server task implementation method according to an example embodiment of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

The server tasks can include self-inspection of the server when the server arrives at a goods, online installation, delivery inspection, restarting, startup and shutdown, reinstallation, password resetting, system customized fault repair and the like. In the self-help reloading of the servers, parameter files are required to be configured manually or semi-automatically according to different reloading requirements of different servers, and meanwhile, each server needs to be independently and manually guided to enter a network for guiding, so that full automation cannot be realized, and the efficiency is low; moreover, the operation capability of the current self-service re-installing user-defined task is limited, only simple system re-installing can be solved, and a customized operation system cannot be realized; in addition, the self-help reinstallation of the server cannot automatically modify or manufacture a disk array (RAID), and requires the server to have a complete RAID, which depends on more hardware factors, resulting in lower automation implementation efficiency. In the rescue mode of the server, the system needs to rely on optical disc for guidance, has limited means for repairing system faults, is slow to operate and difficult to operate, relies on manual operation, cannot perform batch operation, and accordingly is low in efficiency.

Based on one or more of the above problems, the present exemplary embodiment first provides a method for implementing a server task, where the method may be executed in a server, a server cluster, a cloud server, or the like; of course, those skilled in the art may also operate the method of the present disclosure on other platforms as needed, which is not particularly limited in the exemplary embodiment. Fig. 1 shows a flowchart of a server task implementation method, and referring to fig. 1, the server task implementation method may include the following steps:

s110, acquiring a target task of a target server and task parameters corresponding to the target task, and storing the task parameters to a distribution queue;

s120, acquiring current task parameters included in the distribution queue, determining an executable operation list corresponding to the current task parameters, and storing executable operations in the executable operation list into an operation queue;

s130, obtaining executable operations in the operation queue for execution, and completing the target task of the target server after all the executable operations in the executable operation list are executed successfully.

The server task implementation method comprises the steps of obtaining a target task of a target server and task parameters corresponding to the target task, and storing the task parameters to a distribution queue; acquiring current task parameters included in the distribution queue, determining an executable operation list corresponding to the current task parameters, and storing executable operations in the executable operation list into an operation queue; obtaining executable operations in the operation queue for execution, and completing a target task of the target server after all executable operations in the executable operation list are successfully executed; on one hand, the task parameters of the acquired target tasks are stored in a distribution queue, the distribution queue is monitored to acquire the current task parameters in the distribution queue, an executable operation list corresponding to the current task parameters is determined, executable operations in the executable operation list are stored in an operation queue, and the executable operations in the operation queue are executed to complete the server tasks, so that the automatic realization of the server tasks is realized, the problems that the realization of the server tasks in the prior art depends on manual operation, the manual operation has time delay and low execution efficiency are solved, and the realization efficiency of the server tasks is improved; on the other hand, the automatic realization of the server task is realized, so that the quality and the safety of the realization of the server task are ensured.

Hereinafter, each step involved in the server task implementation method of the exemplary embodiment of the present disclosure is explained and explained in detail.

First, an application scenario and a disclosure purpose of the exemplary embodiments of the present disclosure are explained and explained. Specifically, the example embodiments of the present disclosure may be used to implement automatic implementation of a server task, and mainly research how to improve efficiency of implementing the server task.

According to the method and the device, on the basis of the received target task of the server and the task parameter corresponding to the target task, the task parameter of the obtained target task is stored in a distribution queue, the distribution queue is monitored, the current task parameter in the distribution queue is obtained, an executable operation list corresponding to the current parameter is determined, executable operations in the executable operation list are stored in an operation queue, the executable operations in the corresponding operation queue are completed by an execution thread, and after the executable operations are completed, the operation state of the executable operations is changed until all the executable operations in the executable operation queue are successfully executed, so that automatic implementation of the server task is achieved, and the implementation efficiency of the server task is improved.

Next, the server task implementation system related to the exemplary embodiment of the present disclosure is explained and explained. Referring to fig. 2, the server task implementation system may include a server resource management system 210, a server operation center 220, an out-of-band management interface 230, a target server 240, and a network boot environment 250; the server resource management system 210 is a data source and a front-end entrance, and may include a task work order flow inside, and a user may initiate target tasks to a target server in batch in the server resource management system 210 and forward target task parameters to the server operation center 220; a server operation center 220, which is connected to the server resource management system 210 via a network, and is a server task control forwarding center, and is configured to forward the target task parameters to the out-of-band management interface 230; an out-of-band management interface 230, which is network-connected to the server operation center 220, is obtained by performing tree node search optimization algorithm integration and extension encapsulation based on redfish (an open industry standard specification issued by a Distributed Management Task Force (DMTF)) protocol, and is used for accessing a target server through an out-of-band network; a target server 240, which is network-connected to the out-of-band management interface 230 and the network boot environment 240, and is configured to complete a target task according to the out-of-band network provided by the out-of-band management interface 230 and the dependent environment 240; a network boot environment 250, network-connected to the target server, for providing the target server with an IP when the target server is network booted, so that the target server completes a target task according to the IP; the network boot environment 250 includes dhcpset (Dynamic Host Configuration Protocol set, which is a server providing a temporary IP address for a target server), tftpset (simple File Transfer Protocol server), and httpset (HyperText Transfer Protocol, which is a server providing File download for a server).

Further, referring to fig. 3, the connection mode of each component included in the server task implementation system is as follows: the server resource management system 210 and the server operation center 220 are centralized software services for managing a plurality of servers; the out-of-band Management Interface 230 is disposed at a place where the out-of-band Management Interface can be connected to an out-of-band network, in fig. 3, a solid line represents that the components can communicate with each other through the network, the out-of-band Management Interface 230 can control the server through an IPMI (Intelligent Platform Management Interface) or a Redfish protocol, and the server operation center 220 can call the out-of-band Management Interface 230 through a plurality of communication protocols; the target server 240 may obtain an IP from the dhcpset in the dependent environment 240 through the internet access of the service network, and communicate on the service network by using the IP after obtaining the IP, and the target server 240 may also call an interface of the server operation center 220 to obtain the target task parameter and report the information.

Hereinafter, steps S110 to S130 will be explained and explained in detail with reference to fig. 2 and 3.

In step S110, a target task of a target server and a task parameter corresponding to the target task are obtained, and the task parameter is stored in a distribution queue.

In this exemplary embodiment, referring to fig. 4, acquiring a task parameter corresponding to the target task, and storing the task parameter in a distribution queue may include step S410 and step S420:

s410, acquiring a unique identifier and a type of a target task, initialization operation of the target task and an initialization state of the initialization operation, wherein the unique identifier and the type of the target task are included in the task parameters;

step S420, generating a task key value pair according to the task parameter, and storing the task key value pair to the distribution queue; the unique identification and the type of the target task and an initialization operation key of the target task are set; the initialization state of the initialization operation is a value.

Hereinafter, step S410 and step S420 will be explained and explained. Firstly, the server operation center 220 receives a target task of a target server, converts a task parameter of the server task, and stores the converted parameter into a distribution queue, wherein the task parameter includes a unique identifier of the target task, a type of the target task, an initialization operation of the target task, and an initialization state of the initialization operation; the server operation center 220 may convert the task parameter into a task key-value pair, where the unique identifier of the target task, the type of the target task, and the initialization operation of the target task may be a key of the task key-value pair, and the initialization state of the initialization operation is a value of the task key-value pair; after converting the task parameters into task key-value pairs, the task key-value pairs may be stored in a distribution queue.

For example, when the target server is an already-on-shelf server, the target task may be any one of restart, power-on/off, reinstallation, password resetting, and system-customized failover, and when the target task is reinstallation, the task parameters may include: the unique identification and type of the reloading task are initialization operations of the reloading and reloading tasks: starting the target server PXE, and starting the initialization operation of the reinstallation task in an initialization state: and generating a task key value pair according to the task parameter of the reloading task and storing the task key value pair into a distribution queue. When the target server is a server on shelf, the target task may be the target server on shelf, and the task parameters may include: the unique identification and type of the racking task are initialization operation of the racking task: the target server is powered on, and the initialization state of the initialization operation of the on-shelf task is as follows: and when the task is not finished, generating a task key value pair according to the task parameter of the on-shelf task, and storing the task key value pair into a distribution queue.

In this example embodiment, when the target task of the target server is a reinstallation task, the server operation center 220 may further receive installation parameters of the target server, where the installation parameters of the target server include: the Serial Number (SN) of the target server, the Hostname for uniquely identifying a server and the target server, is a configuration parameter of the operating system to be installed and an out-of-band IP of the target server.

Further, as shown in fig. 5, the server operation center 220 may include an information receiving module 510, a state control module 520, an execution module 530, a timeout control module 540, an alarm notification module 550, and an information returning module 560. The information receiving module 510 is configured to receive a task parameter of a target task of a target server sent by the server resource management system 210, convert the received task parameter into a task key value pair, and store the converted task key value pair in a distribution queue; the state control module 520 is configured to maintain an executable operation list corresponding to a task type of a target task, monitor a distribution queue, and determine, after a task key value pair is newly added to the distribution queue, an executable operation list corresponding to the target task according to the task type of the target task in the newly added task key value pair and the executable operation list corresponding to the task type of the target task; placing the executable operation once into an operation queue corresponding to the operation type of the executable operation according to the operation type of each executable operation in the executable operation list; an execution module 530, which monitors the operation queue, acquires an executable operation in the operation queue, and executes the executable operation, after the executable operation is executed, the state control module 520 updates the operation state of the executable operation, acquires a next executable operation in the executable operation list, stores the next executable operation in the corresponding operation queue, when it is determined that all executable operations in the executable operation list are executed successfully, the state control module 520 stores the unique identifier of the target task in the information return queue, and the information return module 560 monitors the information return queue, and returns a message of the completion of the execution of the target task to the server resource management system 210 after monitoring the unique identifier of the target task newly added in the information return queue; when the target task arrives at the information conversion module 510, the timeout control module 540 stores the timeout time of the target task into the timeout queue, and the state control module 520 monitors the timeout queue and updates the timeout time of the target task in time; the alarm notification module 550 monitors the operation condition of each of the other modules, and triggers an alarm when the operation condition of each of the modules is abnormal.

In step S120, a current task parameter included in the distribution queue is obtained, an executable operation list corresponding to the current task parameter is determined, and executable operations in the executable operation list are stored in an operation queue.

In this exemplary embodiment, referring to fig. 6, acquiring a current task parameter included in the distribution queue, and determining an executable operation list corresponding to the current task parameter may include step S610 and step S620:

s610, monitoring the distribution queue to obtain a current task key value pair included in the distribution queue;

s620, determining an executable operation list corresponding to the type of the target task according to the type of the target task included in the key of the current task key value pair.

Hereinafter, step S610 and step S620 will be explained and explained. Specifically, after storing the task key value pair of the target task in the distribution queue, the state control module 520 monitors the task distribution queue, obtains a newly added task key value pair in the distribution queue, obtains a task type of the target task included in the newly added task key value pair, and determines an executable operation list corresponding to the target task according to the task type of the target task. For example, when the task type of the target task included in the obtained key value pair is reinstallation, an executable operation list corresponding to the reinstallation may be obtained, where the executable operations included in the executable operation list corresponding to the reinstallation include: a server PXE (Preboot eXecution Environment) is restarted, a temporary IP (Internet Protocol Address) is obtained, a customized Ramfs (Random Access Memory Filing System) is loaded, a task parameter is downloaded and installed, a Raid, a partition and a grid configuration mount are carried out, a mirror image is downloaded and installed, a fixed IP host name is configured, a GRUB (shared unified Bootloader, a multiple operating System boot program) is installed, an initialization program is restarted and loaded, and a callback server operation center System is installed; when the task type of the target task included in the acquired key value pair is on shelf, an executable operation list corresponding to the on shelf can be acquired, and the executable operations included in the executable operation list include: the method comprises the steps of powering on a server, automatically PXE booting, acquiring a temporary IP, loading customized ramfs, and acquiring an out-of-band Mac address of a target server, a target server serial number SN, a switch TOR (Top of Rack) of a target server access network and a port of a target server port.

After acquiring the executable operation list of the target task, as shown in fig. 7, saving the executable operations in the executable operation list to the operation queue may include steps S710 to S730:

step S710, generating an operation key value pair according to the unique identification and the type of the target task, the first executable operation in the executable operation list and the operation state of the first executable operation; the unique identification and the type of the target task, the first executable operation are keys, and the operation state of the first executable operation is a value;

s720, determining the operation type of the first executable operation;

and S730, storing the operation key value pair into an operation queue corresponding to the operation type according to the operation type of the first executable operation.

Hereinafter, steps S710 to S730 will be explained and explained. Specifically, first, the state control module 520 generates an operation key value pair according to the unique identifier of the target task, the type of the target task, the first executable operation in the executable operation list corresponding to the target task, and the operation state of the first executable operation, where the unique identifier of the target task, the type of the target task, and the first executable operation in the executable operation list corresponding to the target task are keys of the operation key value pair, and the operation state of the first executable operation is a value of the operation key value pair; then, the operation type of the first executable operation is determined, an operation queue corresponding to the operation type is determined according to the operation type of the first executable operation, and finally, the state control module 520 stores the operation key value pair into the corresponding operation queue. The server operation center can comprise a plurality of operation queues, and the operation type of the executable operation stored in each operation queue is different. The plurality of operation queues are executed in parallel, and the executable operations in each operation queue are executed in series.

For example, when the target task is a reinstallation task, first, an operation key value pair may be generated according to a first executable operation in an executable operation list corresponding to the reinstallation task, where a key of the operation key value pair is a unique identifier of the reinstallation task, the reinstallation and a restart of the server PXE, and the value is incomplete; then, determining the operation type of the first executable operation as: and the PXE restarts, determines an operation queue for executing the PXE restarting operation, and stores the operation key value pair into the operation queue. When the target task is an on-shelf task, firstly, generating an operation key value pair according to a first executable operation in an executable operation list corresponding to the on-shelf task, wherein keys of the operation key value pair are unique identifiers of the on-shelf task, power-up of an on-shelf task and power-up of a server, and the value is incomplete; then, determining the operation type of the first executable operation as: and powering on, determining an operation queue for executing the power-on operation, and storing the operation key value pair into the operation queue.

In step S130, executable operations in the operation queue are obtained for execution, and after all executable operations in the executable operation list are successfully executed, the target task of the target server is completed.

In this exemplary embodiment, referring to fig. 8, acquiring the executable operations in the operation queue for execution may include steps S810 to S830:

step S810, monitoring the operation queue to obtain the current executable operation in the operation queue;

s820, determining an execution thread corresponding to the current executable operation, and starting the execution thread to execute the current executable operation;

and S830, after the execution of the current executable operation is finished, updating the operation state of the current executable operation.

Hereinafter, steps S810 to S830 will be explained and explained. Specifically, the execution module 530 monitors the operation queue, obtains the current executable operation in the operation queue, determines an execution thread for executing the current executable operation through the out-of-band management interface 230, starts the execution thread, and executes the current executable operation; when the execution thread finishes executing the current executable operation and the execution is successful, the state control module updates the operation state of the current executable operation.

Further, as shown in fig. 9, after the operation state of the currently executable operation is updated, the server task implementation method further includes steps S910 to S930:

step S910, updating the operation state of the current executable operation stored in the distribution queue;

step S920, when the operation state of the current executable operation is monitored to be changed in the distribution queue, obtaining the next executable operation of the current executable operation;

and S930, generating an operation key value pair corresponding to the next executable operation, and storing the operation key value pair corresponding to the next executable operation into the operation queue.

Hereinafter, steps S910 to S930 will be explained and explained. Specifically, firstly, after the execution module successfully executes the current executable operation, the state control module updates the operation state of the current executable operation stored in the distribution queue, when the operation state of the current executable operation is updated to be completed, the next executable operation of the current executable operation in the executable operation list corresponding to the target task is obtained, the operation key value pair of the next executable operation is generated and stored in the operation queue, the execution module executes the operation, and after the execution is successful, the state update module updates the operation state of the next executable operation, and the execution steps are repeated until all the executable operations in the executable operation list corresponding to the target task are successfully executed.

For example, when the target task is a reinstallation task, first, according to a first executable operation in an executable operation list corresponding to the reinstallation task: the server PXE restarts to generate an operation key value pair, the operation key value pair is stored in an operation queue, the execution module 530 obtains the operation key value pair and determines an execution thread for executing the server PXE restart through the out-of-band management interface 230, the execution thread is started, the execution thread executes the server PXE restart operation, and after the execution is successful, the state control module 520 updates the operation state of the server PXE restart operation from incomplete state to complete state; then, the state control module 520 obtains the next executable operation of the server PXE restart operation: and acquiring the temporary IP, executing the temporary IP by the execution module, updating the operation state of the operation of acquiring the temporary IP by the state control module after the execution is successful, and repeating the execution process until all the executable operation lists in the executable operation list corresponding to the reinstallation task are successfully executed. When the target task is an shelving task, firstly, according to a first executable operation in an executable operation list corresponding to the shelving task: the server is powered on to generate an operation key value pair, the operation key value pair is stored in an operation queue, the execution module 530 acquires the operation key value pair, determines an execution thread for powering on the execution server through the out-of-band management interface 230, starts the execution thread, executes the power-on operation of the server by the execution thread, and updates the operation state of the power-on operation of the server from incomplete state to complete state after the execution is successful; the state control module 520 then obtains the next executable operation for the server power-up operation: and the automatic PXE boot is executed by the execution module, and after the execution is successful, the state control module updates the operation state of the automatic PXE boot operation and repeats the execution process until all the executable operation lists in the executable operation list corresponding to the on-shelf task are successfully executed.

Further, the implementation of the objective task described in the example embodiment of the present application will be further explained and explained with reference to fig. 10. When the target task of the target Server is reinstalled, firstly, a Server Resource Management System (SRMS) pushes a task parameter of the target task to a Server Operation Center (SOC), the Server operation Center generates an installation parameter according to the target Server, and determines an executable operation list corresponding to the target task according to the received task parameter: the method comprises the steps that a PXE server is restarted, a temporary IP is obtained, customized Ramfs is loaded, task parameters of installation are downloaded, Raid, partition and grid configuration mounting, an installation mirror image is downloaded, a fixed IP host name is configured, GRUB installation is carried out, an initialization program and a server operation center are restarted and loaded, when executable operation in an executable operation list is executed, remote PXE Reset (restart + network boot) based on a Redfish protocol is carried out on a target server through an out-of-band management interface (ILOAPI), the target server then enters a network boot, a temporary service IP is obtained from a network boot dependence environment, a customized memory file system and a kernel are remotely loaded, then the task parameters of reloading are requested to an SOC, then a RAID, a disk partition, a grid and configuration mounting are manufactured according to the parameters, the needed operation system mirror image is downloaded from the network boot environment, and relevant basic configuration of an operation system is configured (such as the fixed network configuration, Installing GRUB and starting an executed initialization program next time), and then restarting a target operating system entering a target server after key installation of the operating system is basically completed, wherein the initialization program is loaded by default and is used for installing some service general dependent software and configuration, and finally, the SOC update state is called back to be installed and completed, and finally, the SOC reports a task completion state to the SRMS.

When the task of the target server is a task on shelf, the target server can automatically conduct PXE network boot when being powered on, the target server can acquire an out-of-band IP from a DHCPServer in the process of conducting network boot, download and load a customized memory file system and an inner core, after the customized memory file system is successfully loaded, the target server can automatically request parameters of the task on shelf from an SOC (System on chip) and execute a specified task program corresponding to the task on shelf, and the target server needs to acquire information in the process of executing the task, and the method comprises the following steps: tor, port, SN and out-of-band MAC, and upload the collected information to SRMS, thus ensuring the data integrity of the closed-loop SRMS. In the network dependent boot environment, the DHCPServer regularly acquires the latest out-of-band MAC and out-of-band IP from the SRMS, statically binds the out-of-band MAC and the out-of-band IP, and restarts the DHCPServer. The target server can acquire the out-of-band IP through the DHCPServer at each preset time, and at the moment, the server can acquire the specified out-of-band IP planned by the SRMS on the basis of a DHCP static binding priority principle, so that ILOAPI can perform remote operation through the out-of-band IP to complete the target task of the target server, and the task automation operation closed loop is realized.

In this exemplary embodiment, referring to fig. 11, the server task implementation method further includes steps S1110 to S1120:

step S1110, acquiring the preset execution time of the target task, and storing the preset execution time of the target task to an overtime queue;

step s1120, monitoring the timeout queue, and updating the timeout time of the target task and triggering an alarm message when the execution time of the target task is greater than the preset execution time.

Hereinafter, steps S1110 to S1120 will be explained and explained. Specifically, before executing a target task of a target server, first, a preset execution time of the target task is obtained, where the preset execution time of the target task may be dynamically specified by the target task, and may also be customized, and in this example embodiment, a generation manner of the preset execution time of the target task is not specifically limited; after the preset execution time of the target task is obtained, the timeout control module 540 may store the target task and the preset execution time of the target task into the timeout queue, and the state control module 520 monitors the timeout queue, and when the execution time of the target task is greater than the preset execution time of the target task, the state control module 520 updates the timeout time of the target task and triggers the alarm notification module 550 to send the alarm information of the target task. The completion time of the target task is determined by the execution time of the executable operation included in the executable operation list of the target task.

The server task implementation method provided by the disclosed example embodiment has at least the following advantages: on one hand, the task parameters of the acquired target tasks are stored in a distribution queue, the distribution queue is monitored to acquire the current task parameters in the distribution queue, an executable operation list corresponding to the current task parameters is determined, executable operations in the executable operation list are stored in an operation queue, and the executable operations in the operation queue are executed to complete the server tasks, so that the automatic realization of the server tasks is realized, the problems that the realization of the server tasks in the prior art depends on manual operation, the manual operation has time delay and low execution efficiency are solved, and the realization efficiency of the server tasks is improved; on the other hand, the automatic realization of the server task is realized, so that the quality and the safety of the realization of the server task are ensured.

Hereinafter, a task implementation method of the target server when the target task of the exemplary embodiment of the present disclosure is a reinstallation task is further explained and explained with reference to fig. 12. The method can comprise the following steps:

s1201.SRMS is used as a data source and a front end inlet and issues a target task to SOC;

s1202, the SOC serves as a task control forwarding center and forwards task high-concurrency asynchronous processing to ILOAPI;

s1203, using the ILOAPI as a remote basic operation channel, and directly accessing a data center server through an out-of-band network to perform power supply operation such as restarting and network guiding;

s1204, the target server obtains an out-of-band IP from the DHCPServer in the network boot process;

s1205, the target server downloads the customized memory file system and the kernel from the TFTPServer;

s1206, after the customized memory file system is loaded successfully, automatically requesting actual task parameters from the SOC, and executing a specified task program, wherein the customized memory file system and the kernel file are limited by the size, and part of the task program is stored in the HTTPServer, so that the task program can be downloaded through the HTTPServer;

and S1207, the target server uploads the acquired information of the target server to the SOC in the process of executing the target task.

An exemplary embodiment of the present disclosure further provides a server task implementing device, as shown in fig. 13, which may include: a target task distribution module 1310, an executable operation determination module 1320, and an executable operation execution module 1330. Wherein:

a target task distribution module 1310, configured to obtain a target task of a target server and a task parameter corresponding to the target task, and store the task parameter to a distribution queue;

an executable operation determining module 1320, configured to obtain a current task parameter included in the distribution queue, determine an executable operation list corresponding to the current task parameter, and store an executable operation in the executable operation list in an operation queue;

an executable operation executing module 1330, configured to obtain executable operations in the operation queue for execution, and complete the target task of the target server after all executable operations in the executable operation list are successfully executed.

The specific details of each module in the server task implementing device have been described in detail in the corresponding server task implementing method, and therefore are not described herein again.

determining an operation type of the first executable operation;

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.

In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, method or program product. Accordingly, various aspects of the present disclosure may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

An electronic device 1400 according to such an embodiment of the present disclosure is described below with reference to fig. 14. The electronic device 1400 shown in fig. 14 is only an example and should not bring any limitations to the functionality and scope of use of the embodiments of the present disclosure.

As shown in fig. 14, the electronic device 1400 is embodied in the form of a general purpose computing device. The components of the electronic device 1400 may include, but are not limited to: the at least one processing unit 1410, the at least one memory unit 1420, the bus 1430 that connects the various system components (including the memory unit 1420 and the processing unit 1410), and the display unit 1440.

Wherein the storage unit stores program code that is executable by the processing unit 1410, such that the processing unit 1410 performs steps according to various exemplary embodiments of the present disclosure described in the "exemplary methods" section above in this specification. For example, the processing unit 1410 may execute step S110 as shown in fig. 1: acquiring a target task of a target server and task parameters corresponding to the target task, and storing the task parameters to a distribution queue; s120: acquiring current task parameters included in the distribution queue, determining an executable operation list corresponding to the current task parameters, and storing executable operations in the executable operation list into an operation queue; s130: and acquiring executable operations in the operation queue for execution, and completing the target task of the target server after all executable operations in the executable operation list are executed successfully.

The storage unit 1420 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)14201 and/or a cache memory unit 14202, and may further include a read only memory unit (ROM) 14203.

Storage unit 1420 may also include a program/utility 14204 having a set (at least one) of program modules 14205, such program modules 14205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Bus 1430 may be any type of bus structure including a memory cell bus or memory cell controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 1400 may also communicate with one or more external devices 1500 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 1400, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 1400 to communicate with one or more other computing devices. Such communication can occur via an input/output (I/O) interface 1450. Also, the electronic device 1400 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 1460. As shown, the network adapter 1460 communicates with the other modules of the electronic device 1400 via the bus 1430. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 1400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, various aspects of the disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to perform the steps according to various exemplary embodiments of the disclosure described in the "exemplary methods" section above of this specification, when the program product is run on the terminal device.

According to the program product for implementing the above method of the embodiments of the present disclosure, it may employ a portable compact disc read only memory (CD-ROM) and include program codes, and may be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, 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.

A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

Furthermore, the above-described figures are merely schematic illustrations of processes included in methods according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A method for realizing server tasks is characterized by comprising the following steps:

2. The method for implementing the task of the server according to claim 1, wherein the step of obtaining the task parameter corresponding to the target task and storing the task parameter in a distribution queue comprises the steps of:

3. The method for implementing the task of the server according to claim 2, wherein obtaining a current task parameter included in the distribution queue, and determining an executable operation list corresponding to the current task parameter includes:

4. The server task implementation method of claim 3, wherein saving the executable operations in the executable operation list to an operation queue comprises:

determining an operation type of the first executable operation;

5. The method for implementing the task of the server according to claim 4, wherein obtaining the executable operation in the operation queue for execution comprises:

6. The server task implementation method of claim 5, wherein after updating the operational state of the currently executable operation, the server task implementation method further comprises:

7. The server task implementation method of claim 6, further comprising:

8. A server task implementation apparatus, comprising:

9. A readable storage medium on which a computer program is stored, the computer program, when being executed by a processor, implementing the server task implementing method according to any one of claims 1 to 7.

10. An electronic device, comprising:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform the server task implementation method of any one of claims 1-7 via execution of the executable instructions.