CN112199197B - Server management method and system - Google Patents
Server management method and system Download PDFInfo
- Publication number
- CN112199197B CN112199197B CN202011149155.3A CN202011149155A CN112199197B CN 112199197 B CN112199197 B CN 112199197B CN 202011149155 A CN202011149155 A CN 202011149155A CN 112199197 B CN112199197 B CN 112199197B
- Authority
- CN
- China
- Prior art keywords
- server
- redfish
- target
- resources
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
- G06F16/2246—Trees, e.g. B+trees
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2474—Sequence data queries, e.g. querying versioned data
-
- 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)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Fuzzy Systems (AREA)
- Computational Linguistics (AREA)
- Probability & Statistics with Applications (AREA)
- Mathematical Physics (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention provides a server management method and a system, which are applied to a Redfish server, wherein the Redfish server is in communication connection with a management client and at least one server, and the method comprises the following steps: receiving a hardware operation request aiming at a target server, which is sent by a management client; acquiring a Redfish resource tree of a target server, and searching resources of a target node corresponding to an operation type; adjusting the resources of the target node according to the operation type to obtain a processing result returned by the target server; and returning the processing result to the management client. The server end is packaged into various hardware basic operation query interfaces of the server based on the redfish protocol, so that a series of hardware operation and query of the server are realized, and further automation of server cluster management is realized. In addition, a visual interface can be displayed on the client side in a mode of deploying the client side and the Redfish server side, so that a user can manage the server conveniently.
Description
Technical Field
The present invention relates to the field of device management technologies, and in particular, to a server management method and a server management system.
Background
With the rapid development of information technology and computer industry, the server is widely applied in the production and living of people today. In some applications such as large data centers or cloud computing bases, tens of thousands or even hundreds of thousands of servers may be deployed, so that management performance of the servers is crucial.
The current server automation management scheme mainly comprises the following steps: the IPMI (Intelligent Platform Management Interface ) based protocol uses Ipmitool for simple management of servers or uses a dedicated management tool provided by a server vendor for separate management.
However, as organizations get more and more favoured with large-scale solutions, traditional standards are not sufficient to successfully manage a large number of simple multi-node servers or hybrid infrastructures. Ipmitool is an IPMI platform management tool in a command line mode that can be used in a linux system, while IPMI is an early out-of-band management standard, and is limited to a "minimum common set" command set, such as power on/off/reboot, temperature value, text console, etc., because vendor expansion is not common on all platforms, the common function set of clients is reduced, and as a command line tool, the visualization and user experience are not perfect. The special management tool provided by each server manufacturer is perfect in the aspects of visualization and functionality, but only the server of the manufacturer is supported, and the server has no universality. For enterprise-level users, the devices are thousands or more, and the existing server automation management scheme cannot meet the large-scale scalable environment.
Disclosure of Invention
In view of the foregoing, embodiments of the present invention have been made to provide a server management method and a corresponding server management apparatus that overcome or at least partially solve the foregoing problems.
In a first aspect, an embodiment of the present invention discloses a server management method, which is applied to a Redfish server, where the Redfish server is communicatively connected with a management client and at least one server, and the method includes:
receiving a hardware operation request aiming at a target server in the at least one server, wherein the hardware operation request carries an operation type, and the hardware operation request is sent by the management client;
acquiring a Redfish resource tree of the target server, and searching resources of a target node corresponding to the operation type;
adjusting the resources of the target node according to the operation type to obtain a processing result returned by the target server;
and returning the processing result to the management client.
Optionally, the obtaining the Redfish resource tree of the target server and searching the resource of the target node corresponding to the operation type includes:
and calling a Redfish interface of the target server, acquiring a Redfish resource tree of the target server, and searching resources of the target node corresponding to the operation type.
Optionally, the calling the Redfish interface of the target server obtains a Redfish resource tree of the target server, and searches resources of the target node corresponding to the operation type, including:
invoking a Redfish interface of the target server to obtain a resource of a root node in the Redfish resource tree, wherein the resource of the root node contains Redfish version information;
if the target server supports expansion query according to the Redfish version information, calling a Redfish interface of the target server, and acquiring resources of a plurality of nodes in the Redfish resource tree to obtain the resources of the target node;
and if the target server does not support the Expand query according to the Redfish version information, sequentially calling Redfish interfaces of the target server from the root node, and acquiring resources of each node in the Redfish resource tree to obtain the resources of the target node.
Optionally, the calling the Redfish interface of the target server obtains resources of a plurality of nodes in the Redfish resource tree to obtain the resources of the target node, including:
determining the maximum query depth of the target server according to the Redfish version information;
Calculating the depth difference between the root node and a preset node;
determining query parameters according to the depth difference and the maximum query depth;
calling a Redfish interface of the target server, and acquiring resources of a plurality of nodes in the resource tree according to the query parameters to obtain a resource sub-tree;
and obtaining the resources of the target node from the resource subtree.
Optionally, the determining the query parameter according to the depth difference and the maximum query depth includes:
if the depth difference is smaller than the maximum query depth, determining the depth difference as a query parameter;
and if the depth difference is greater than or equal to the maximum query depth, determining the maximum query depth as a query parameter.
Optionally, after the step of obtaining the Redfish resource tree of the target server and searching the resources of the target node corresponding to the operation type, the method further includes:
determining one or more allowed operation types according to the resources of the target node;
if the one or more allowed operation types comprise the operation type, executing the subsequent steps;
if the one or more allowed operation types do not include the operation type, no subsequent steps are executed.
Optionally, the hardware operation request further carries a server serial number and an out-of-band IP address, and after the step of receiving the hardware operation request sent by the management client for the target server in the at least one server, the method further includes:
searching a target serial number corresponding to the out-of-band IP address from a preset database;
if the server serial number is the same as the target serial number, executing the subsequent steps;
if the server serial number is not the same as the target serial number, no subsequent steps are performed.
Optionally, after the step of receiving the hardware operation request for the target server in the at least one server sent by the management client, the method further includes:
searching an allowed operation node corresponding to the out-of-band IP address from a preset database;
if the allowed operation node contains a target node corresponding to the operation type, executing the subsequent steps;
and if the allowed operation node does not contain the target node corresponding to the operation type, the subsequent steps are not executed.
In a second aspect, the embodiment of the invention also discloses a server management system, which comprises a management client, a Redfish server and at least one server, wherein the Redfish server is in communication connection with the management client and the at least one server,
The management client is used for responding to user operation to determine the operation type; generating a hardware operation request aiming at a target server in the at least one server according to the operation type; the hardware operation request aiming at the target server is sent to a Redfish server; receiving a processing result returned by the Redfish server for processing the hardware operation request;
the Redfish server is used for receiving a hardware operation request aiming at a target server in the at least one server, which is sent by the management client, wherein the hardware operation request carries an operation type; acquiring a Redfish resource tree of the target server, and searching resources of a target node corresponding to the operation type; adjusting the resources of the target node according to the operation type to obtain a processing result returned by the target server; returning the processing result to the management client;
the at least one server is used for supporting a Redfish protocol and organizing resources of the at least one server to obtain a Redfish resource tree.
In a third aspect, the embodiment of the present invention further discloses a server management device, which is applied to a Redfish server, where the Redfish server is communicatively connected with a management client and at least one server, and includes:
The request receiving module is used for receiving a hardware operation request which is sent by the management client and aims at a target server in the at least one server, wherein the hardware operation request carries an operation type;
the resource searching module is used for acquiring the Redfish resource tree of the target server and searching the resources of the target node corresponding to the operation type;
the processing module is used for adjusting the resources of the target node according to the operation type to obtain a processing result returned by the target server;
and the result returning module is used for returning the processing result to the management client.
In a fourth aspect, an embodiment of the present invention further discloses an electronic device, including:
a processor, a storage medium, and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the electronic device is running, the processor executing the machine-readable instructions to perform a method according to any one of the embodiments of the present invention.
In a fifth aspect, embodiments of the present invention also disclose a storage medium having stored thereon a computer program which, when executed by a processor, performs a method according to any of the embodiments of the present invention.
The embodiment of the invention has the following advantages:
in the embodiment of the invention, a hardware operation request for a target server in at least one server, which is sent by a management client, is received, a Redfish resource tree of the target server is obtained, the resources of a target node corresponding to an operation type are searched, the resources of the target node are adjusted according to the operation type to obtain a processing result, and the processing result is returned to the management client. The server is packaged into various hardware basic operation query interfaces of the server based on a redfish protocol, so that a series of hardware operation and query of the server are realized, and further automation of server cluster management is realized. In addition, a visual interface can be displayed on the management client by deploying the management client and the Redfish server, so that a user can manage the server conveniently.
Drawings
FIG. 1 is a flow chart of steps of an embodiment of a server management method of the present invention;
FIG. 2 is a flow chart of a method for locating resources of a target node according to the present invention;
FIG. 3 is a flowchart illustrating steps of another embodiment of a server management method of the present invention;
FIG. 4 is a structural flow diagram of one embodiment of a server management system of the present invention;
FIG. 5 is a block diagram of a server management system of the present invention;
FIG. 6 is a block diagram of an embodiment of a server management apparatus of the present invention;
FIG. 7 is a block diagram of another embodiment of a server management apparatus of the present invention;
FIG. 8 is a block diagram of an electronic device of the present invention;
fig. 9 is a block diagram of a storage medium of the present invention.
Detailed Description
In order that the above-recited objects, features and advantages of the present invention will become more readily apparent, a more particular description of the invention will be rendered by reference to the appended drawings and appended detailed description.
Referring to fig. 1, a step flow chart of an embodiment of a server management method of the present invention is shown and applied to a Redfish server, where the Redfish server is communicatively connected with a management client and at least one server, and specifically may include the following steps:
step 101, receiving a hardware operation request for a target server in the at least one server, which is sent by the management client, wherein the hardware operation request carries an operation type;
the management client provides a program of local service for a user, and the user can manage at least one server through operation on a user interface of the management client, for example, a series of hardware information updating and inquiring operations such as restarting, reloading, startup and shutdown, bios changing, firmware upgrading, health status log checking and the like are performed for a single server or a batch of servers.
Specifically, by running the management client on the terminal device, a user interface may be provided on the terminal device, where the user interface may include a list of at least one server and various functional components, and the user may select a server to be managed through the list of at least one server, and set an operation type to be performed on the target server through the functional component, for example, may implement operations such as hard shutdown, hard restart, soft restart, forced startup through the power management component. When the management client receives the user operation, a hardware operation request for a target server in at least one server can be generated, and the hardware operation request is sent to the Redfish server.
It should be noted that, the Redfish server may be a terminal side for providing a Redfish service for the management client, so as to implement management on at least one server based on a Redfish protocol, where the Redfish is a management standard based on HTTPs (Hyper Text Transfer Protocol over SecureSocket Layer, hypertext transfer security protocol) service, and implement device management by using RESTful (Representational State Transfer) interfaces.
In the embodiment of the present invention, the Redfish server may receive a hardware operation request for a target server in at least one server, where the hardware operation request may be a request for operating the server, where the request is sent by the management client. In a specific implementation, the hardware operation request may carry an operation type, where the operation type may refer to type information describing an operation that needs to be performed, and for example, the operation type may be shutdown, restart, view a log, view a resource list, and so on.
In addition, the hardware operation request may further carry information such as a server serial number, an out-of-band IP address, a user name, and a user password, which is not limited in this embodiment of the present invention. The server Serial Number may be used to uniquely identify an SN (Serial Number) of the server, and the out-of-band IP (Internet Protocol ) address may be an address managed by the server out-of-band, where the user name and the user password may be a user name registered at the Redfish server and a login password corresponding to the user name and the user password, which are used to authenticate the hardware operation request.
102, acquiring a Redfish resource tree of the target server, and searching resources of a target node corresponding to the operation type;
the server supporting the Redfish protocol can store the hardware resources of the server in a tree mode to obtain the Redfish resource tree corresponding to each server. Specifically, the resources of each hardware in the server are respectively stored in different nodes, and the nodes in the Redfish resource tree can include a power source node, a firmware node, a log node and the like.
In a specific implementation, a Redfish resource tree corresponding to a target server may be obtained from a storage service of the Redfish server, and a target node corresponding to an operation type is determined from the Redfish resource tree, for example, when the operation type is a shutdown operation, the target node corresponding to the operation type is a power node. Further, the resources of the target node corresponding to the operation type are searched from the Redfish resource tree of the target server, specifically, the Redfish interface of the target server can be called, and the resources of the target node corresponding to the operation type are searched from the Redfish resource tree of the target server. Where a resource may refer to a URL (Uniform Resource Locator ) corresponding to each node, in a Redfish, each URL represents a resource, a service, or a set of resources, and a management client may interact with the resource through the URL.
Step 103, adjusting the resources of the target node according to the operation type to obtain a processing result returned by the target server;
in the embodiment of the invention, the resource of the target node can be adjusted according to the operation type, and the Redfish server can acquire the processing result returned by the target server after the operation on the target server.
As an example, assuming that the operation type is a soft restart operation, the action operation parameter in the resource of the target node may be adjusted to be a GracefulRestart operation, after the target server executes the GracefulRestart operation, the state of the actual restart success or failure of the target server is determined, and the processing result is returned to the Redfish server.
And 104, returning the processing result to the management client.
In the embodiment of the invention, the Redfish server can return the processing result returned by the obtained target server to the management client so as to display the processing result on the user interface of the management client.
In a preferred embodiment of the present invention, the step 102 may include the steps of:
and calling a Redfish interface of the target server, acquiring a Redfish resource tree of the target server, and searching resources of the target node corresponding to the operation type.
At least one server is provided with a Redfish interface for managing the server based on a Redfish protocol. In the embodiment of the invention, a Redfish interface of the target server can be called, a Redfish resource tree of the target server is obtained, and the resource of the target node corresponding to the operation type is searched from the Redfish resource tree.
In a preferred embodiment of the present invention, the calling the Redfish interface of the target server, obtaining a Redfish resource tree of the target server, and searching the resources of the target node corresponding to the operation type, includes:
s11, calling a Redfish interface of the target server to acquire resources of a root node in a Redfish resource tree of the target server, wherein the resources of the root node contain Redfish version information;
the server supporting the Redfish protocol organizes the resources of all servers in the form of a tree, and under the condition that the resource address of the target node is not known in advance, the Redfish interface needs to be sequentially called from the root node to access any resource, so that the resources of all nodes on the path from the root node to the target node are acquired. Because the interface call is a very time-consuming task, in order to reduce the number of times of calling the Redfish interface and achieve the purpose of reducing the response time of the system, the Redfish of the high-version server can search resources in a manner of supporting expansion query and query the resources of a plurality of nodes at one time. The Expand query may be to obtain the resources of multiple nodes at one time according to the query depth by setting the query depth, for example, if the query depth is set to 1, the resources of the node and the resources of all its child nodes may be obtained, and if the query depth is set to 2, the resources of the child nodes corresponding to all the child nodes may be obtained on the basis of the set query depth.
The resources of the root node in the Redfish resource tree of the target server are obtained by calling the Redfish interface of the target server, and the resources of the root node contain Redfish version information, so that whether the resources of the target node can be searched in an expansion query mode can be judged according to the Redfish version information.
Step S12, if the target server supports expansion query according to the Redfish version information, calling a Redfish interface of the target server, and acquiring resources of a plurality of nodes in the Redfish resource tree to acquire the resources of the target node;
in the embodiment of the invention, if the target server supports the expansion query according to the Redfish version information, the Redfish interface of the target server is called to acquire the resources of a plurality of nodes in the Redfish resource tree, and the resources of the target node can be further searched from the resources of the plurality of nodes.
Specifically, by determining a query depth, the resources of the multiple nodes queried according to the query depth can include the resources of the target node, so that after the resources in the Redfish resource tree are acquired by calling the Redfish interface for the second time, the resources of the target node can be obtained, the times of calling the Redfish interface are reduced, and the response speed of the system is improved.
And S13, if the target server does not support the Expand query according to the Redfish version information, sequentially calling the Redfish interfaces of the target server from the root node, and acquiring the resources of each node in the Redfish resource tree to obtain the resources of the target node.
In the embodiment of the invention, if the target server does not support the Expand query according to the Redfish version information, the Redfish interfaces of the target server are sequentially called from the root node to acquire the resources of each node in the Redfish resource tree until the resources of the target node are acquired.
By means of acquiring the resources of each node in the Redfish resource tree one by one, the Redfish interface needs to be called once every time the resources of the nodes are acquired, namely, N times of Redfish interfaces need to be called when N nodes are contained from a root node to a target node, and the resources of the target node need to be acquired in a query-by-query mode because the Redfish of the low-version server does not support expansion query.
In a preferred embodiment of the invention, said substep S12 may comprise the substeps of:
determining the maximum query depth of the target server according to the Redfish version information; calculating the depth difference between the root node and a preset node; determining query parameters according to the depth difference and the maximum query depth; calling a Redfish interface of the target server, and acquiring resources of a plurality of nodes in the resource tree according to the query parameters to obtain a resource sub-tree; and obtaining the resources of the target node from the resource subtree.
Specifically, after the Redfish version information of the target server is determined, the hardware information of the server organized by the Redfish server is also determined, and the structure of the Redfish resource tree generated by adopting the hardware information is also determined, so that the maximum query depth of the target server can be determined according to the Redfish version information. The maximum query depth may be the number of layers from the root node to the lowest node in the Redfish resource tree, for example, the number of layers from the root node to the lowest node is 5, and the maximum query depth is 5. Further, the depth difference between the root node and the preset node may be calculated, where the preset node may be a preset node, the preset node may be set empirically, and the preset node that is generally set may satisfy that some nodes commonly used, for example, including the target node, are included between the root node and the preset node.
After determining the depth difference and the maximum query depth, determining a query parameter according to the depth difference and the maximum query depth; and then calling a Redfish interface of the target server, acquiring resources of a plurality of nodes in the resource tree according to the query parameters to obtain a resource sub-tree, and determining the resources of the target node from the resource sub-tree. For example, if the query parameter is 2, the resources of the child nodes of the root node and the resources of the child nodes may be obtained to obtain a resource sub-tree, and the resources of the target node may be obtained from the resource sub-tree.
In a preferred embodiment of the present invention, the determining the query parameters according to the depth difference and the maximum query depth includes:
if the depth difference is smaller than the maximum query depth, determining the depth difference as a query parameter; and if the depth difference is greater than or equal to the maximum query depth, determining the maximum query depth as a query parameter.
In the embodiment of the invention, if the depth difference is smaller than the maximum query depth, determining the depth difference as the query parameter can acquire the resources of all nodes from the root node to the preset node. If the depth difference is greater than or equal to the maximum query depth, determining the maximum query depth as a query parameter, and acquiring the resources of all nodes in the resource tree.
As shown in fig. 2, a flow chart of searching resources of a target node according to the present invention specifically includes the following steps:
step S1: calling a Redfish interface of the target server to acquire resources of a root node in a Redfish resource tree;
step S2: acquiring version information of the Redfish according to the resource of the root node;
step S3: judging whether Expand query is supported;
step S4: if the Expand query is not supported, sequentially calling a Redfish interface to acquire resources of all nodes from the root node to the target node;
Step S5: finding out the resource of the target node;
step S6: if the Expand query is supported, determining the maximum query depth of the target server according to the Redfish version information;
step S7: calculating the depth difference between the root node and a preset node;
step S8: judging whether the depth difference is smaller than the maximum query depth;
step S9: if the depth difference is smaller than the maximum query depth, determining the maximum query depth as a query parameter, calling a Redfish interface of the target server, and acquiring resources of a plurality of nodes in the resource tree according to the query parameter to obtain a resource sub-tree; step S5 is then performed.
Step S10: if the depth difference is greater than or equal to the maximum query depth, determining the depth difference as a query parameter, calling a Redfish interface of the target server, acquiring resources of a plurality of nodes in the resource tree according to the query parameter to obtain a resource sub-tree, and executing step S5.
In a preferred embodiment of the present invention, after the step of obtaining the Redfish resource tree of the target server and searching the resources of the target node corresponding to the operation type, the method further includes:
determining one or more allowed operation types according to the resources of the target node; if the one or more allowed operation types comprise the operation type, executing the subsequent steps; if the one or more allowed operation types do not include the operation type, no subsequent steps are executed.
Specifically, one or more allowed operation types may be determined according to the resource of the target node, for example, the target node is a power source, if the power state of the server is a power-on state, a restart operation, a shutdown operation, and the like are allowed, and if the power state is a power-off state, only the power-on operation can be performed. If the one or more allowed operation types include an operation type, performing the following steps 103-104; if the one or more allowed operation types do not include an operation type, then the following steps 103-104 are not performed.
In a preferred embodiment of the present invention, the hardware operation request further carries a server serial number and an out-of-band IP address, and the following steps may be further included after the step 101:
searching a target serial number corresponding to the out-of-band IP address from a preset database; if the server serial number is the same as the target serial number, executing the subsequent steps; if the server serial number is not the same as the target serial number, no subsequent steps are performed.
In the embodiment of the invention, the authority of the out-of-band management user can be verified, and when the verification fails, any subsequent operation is not performed so as to avoid misoperation.
Specifically, the target serial number corresponding to the out-of-band IP address may be searched from a preset database, where the preset database may be a database preset in the Redfish server, and is configured to store a server registered in the Redfish server and various information thereof, including the server serial number and the out-of-band IP address, and further may store information such as a registered account number and a password, which is not limited in the embodiment of the present invention.
Comparing the target sequence number with the server sequence number, if the server sequence number is the same as the target sequence number, passing the verification, and executing the following steps 102-104; if the server serial number is not the same as the target serial number, the verification is not passed, and the subsequent steps 102-104 are not performed to avoid misoperations.
In a preferred embodiment of the present invention, the following steps may be further included after the step 101:
searching an allowed operation node corresponding to the out-of-band IP address from a preset database; if the allowed operation node contains a target node corresponding to the operation type, executing the subsequent steps; and if the allowed operation node does not contain the target node corresponding to the operation type, the subsequent steps are not executed.
In some scenarios, to avoid damaging the hardware of the server for hardware operations of the server, operations on some of the hardware of the server are not open, and thus, nodes that need to operate may be verified.
Specifically, the corresponding relation between the out-of-band IP address and the allowed operation node can be stored in a preset database, and the allowed operation node corresponding to the out-of-band IP address is searched from the preset database; if the allowed operation node includes a target node corresponding to the operation type, executing the following steps 102-104; if the allowed operation node does not include the target node corresponding to the operation type, the following steps 102-104 are not performed.
In a specific implementation, for each request and return action at the Redfish server, corresponding log data can be generated and recorded, so that archiving and obstacle removal are facilitated.
In the embodiment of the invention, the hardware operation request for the target server sent by the management client is received, the resources of the target node corresponding to the operation type are searched from the Redfish resource tree of the target server, the resources of the target node are adjusted according to the operation type to obtain the processing result, and the processing result is returned to the management client. The server end is packaged into various hardware basic operation query interfaces of the server based on the redfish protocol, so that a series of hardware operation and query of the server are realized, and further automation of server cluster management is realized. In addition, a visual interface can be displayed on the management client by deploying the management client and the Redfish server, so that a user can manage the server conveniently.
The example of the invention requires an out-of-band management restart server, and after the Redfish server receives a hardware operation request, the steps are divided into 3, and the specific steps are as follows:
step one: the request for obtaining the server serial number by the Redfish server is expressed as follows: https:// repadsfish.nie.netease.com/getservercerialenumber user = xxx & password = xxx & host = xxx.xxx.xxx & system = xxx. Wherein, user parameter indicates User name, password indicates User password, host out-of-band management address, system indicates server System ID, "all" designates all systems, if not, default first System.
In the Redfish, data is transmitted in JSON format, for example, a request for acquiring a server serial number for the Redfish server side is returned as follows:
where Id is a server system identification, model represents a server Model number, manufacturer represents a server Manufacturer, and SerialNumber represents a server serial number.
Step two: the request to query the power state is expressed as follows: https:// repadsfish.nie.netease.com/getpowerstateuser=xxx & password=xxx & host=xxx, xxx.xxx & system=xxx. Wherein, the User parameter represents a User name, the password represents a User password, the Host out-of-band management address, and the System represents a server System ID.
For the above request for querying the power state, the return data is as follows:
wherein Id is a server system identifier, model represents a server Model, manufacturer represents a server Manufacturer, powerState represents a power state, A1 lowbleActions represents allowed operation types, and the allowed operation types include: on power up Nmi can not mask interrupt, graceful Shutdown soft power down, graceful restart soft start, forceOn forced power up, forceOff forced power down, forceRestart forced restart.
Step three: and performing actual soft restart operation on the server, so as to integrally realize out-of-band automatic restart operation on the server, wherein the soft restart request is expressed as follows:
wherein host represents a server management address, user represents an out-of-band management user name, password represents an out-of-band management user password, action represents an operation to be performed, and serial number represents a server serial number.
After performing the actual soft restart operation on the server, a processing result may be generated to return the processing result to the management client, for example, the generated processing result is as follows:
"data":[],
"message":"",
"returnCode":0,
"success":true,
"total":0
wherein data represents data, message represents message, return code represents return data, success represents success, total represents total number. It should be noted that, since the restart operation is successful, the returned data is empty.
Referring to fig. 3, a flowchart illustrating steps of another embodiment of a server management method of the present invention is applied to a management client, where the management client is communicatively connected to a Redfish server, and the Redfish server is communicatively connected to at least one server, and may specifically include the following steps:
step 301, determining an operation type in response to a user operation;
the management client provides a program of local services to the user, who can manage the server by performing operations on a user interface of the management client. Specifically, by running the management client on the terminal device, a user interface may be provided on the terminal device, where the user interface may include a list of at least one server and various functional components, and the user may select a server to be managed through the list of at least one server, and set an operation type to be performed on the target server through the functional component, for example, may implement operations such as hard shutdown, hard restart, soft restart, forced startup through the power management component. When the management client receives a user operation, the operation type may be determined in response to the user operation.
Step 302, generating a hardware operation request aiming at a target server in the at least one server according to the operation type;
In the embodiment of the present invention, a hardware operation request for a target server in at least one server may be generated according to an operation type, where the hardware operation request may carry the operation type, may also carry information such as a server serial number and an out-of-band IP address, and an account number and a password of the operation, and the embodiment of the present invention is not limited to this.
Step 303, sending the hardware operation request for the target server in the at least one server to a Redfish server;
after generating the hardware operation request for the target server in the at least one server, the hardware operation request for the target server in the at least one server may be sent to the Redfish server, so as to implement an automation management server through the Redfish server.
Step 304, receiving a processing result returned by the Redfish server to process the hardware operation request.
After receiving the hardware operation request, the Redfish server can process the hardware operation request, determine a processing result, return the processing result to the management client, for example, if the operation type carried in the hardware operation request is a restarting operation, restart the server, determine that the restarting is successful or the restarting is failed, and then generate a corresponding processing result.
In a preferred embodiment of the present invention, the step 302 may comprise the following sub-steps:
acquiring a server serial number and an out-of-band IP address corresponding to the target server; a management request is generated that includes the server serial number, the out-of-band IP address, and the operation type.
The management client may organize some information of the server for identity verification by the Redfish server after determining the operation type. Specifically, a server serial number and an out-of-band IP address corresponding to the target server may be obtained, and then a management request including the server serial number, the out-of-band IP address, and the operation type may be generated.
In the embodiment of the invention, the operation type is determined in response to the user operation, and the hardware operation request aiming at the target server in at least one server is generated according to the operation type. The hardware operation request is sent to the Redfish server, and a processing result returned by the Redfish server for processing the hardware operation request is received, so that a user can operate on the visual interface to manage at least one server by displaying the visual interface on the management client.
It should be noted that, for simplicity of description, the method embodiments are shown as a series of acts, but it should be understood by those skilled in the art that the embodiments are not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred embodiments, and that the acts are not necessarily required by the embodiments of the invention.
Referring to fig. 4, there is shown a block diagram of an embodiment of a server management system of the present invention, the server management system comprising a management client 401, a Redfish server 402, and at least one server 403, the Redfish server being communicatively connected to the management client and the at least one server, wherein,
the management client 401 is configured to determine an operation type in response to a user operation; generating a hardware operation request aiming at a target server in the at least one server according to the operation type; the hardware operation request aiming at the target server is sent to a Redfish server; receiving a processing result returned by the Redfish server for processing the hardware operation request;
specifically, the management client is mainly responsible for organizing and providing basic parameters of the server, such as server serial number SN, out-of-band IP, manufacturer model information, out-of-band management account number and the like, generating a hardware operation request according to the parameters, and transmitting the hardware operation request, so that out-of-band automatic management of the specified server is realized.
The Redfish server 402 is configured to receive a hardware operation request for a target server in the at least one server, where the hardware operation request is sent by the management client and carries an operation type; acquiring a Redfish resource tree of the target server, and searching resources of a target node corresponding to the operation type; adjusting the resources of the target node according to the operation type to obtain a processing result returned by the target server; returning the processing result to the management client;
The at least one server 403 is configured to support a Redfish protocol, and organize resources of the at least one server to obtain a Redfish resource tree.
Specifically, the hardware of the BMC (Baseboard Manager Controller, baseboard management controller) corresponding to the servers with different manufacturer models supports the Redfish protocol, and specifically, all server resources are organized in a tree form, and for the Redfish protocol, each large manufacturer server supports the Redfish interface call of the server, so that a basic premise is provided for controlling the functions of the management server, such as hardware operation inquiry.
Fig. 5 shows a block diagram of a server management system according to the present invention, where the server management system mainly includes a management client, a Redfish server, and at least one server. The Redfish server side can be divided into 4 modules, and specifically comprises a permission module, a log module, a DB module and an S3 storage module which can be summarized as a storage module, a basic information module, a resource list module, a power supply module, a guide item module, a firmware module, a task module, a log module, a network card module, a BIOS module and an out-of-band user management module which can be summarized as a service module. Specifically, the main function of the permission module is to control and solve the relative security problem, such as which source IP management client can access which function interfaces through which specified key; the log module is mainly responsible for recording all management client request information and abnormal error reporting information, and is convenient for archiving and obstacle removal; the service module is mainly responsible for realizing access and control based on a redfish protocol to each server hardware, so that out-of-band automatic management to the server is realized, and finally, the server is encapsulated and provided for a management client to call in an interface mode; the storage module is mainly responsible for the out-of-band login account passwords of different servers and storing files needed for uploading and downloading partial interface files of the service module.
Referring to fig. 6, a block diagram of an embodiment of a server management device of the present invention is shown, and the block diagram is applied to a Redfish server, where the Redfish server is communicatively connected with a management client and at least one server, and may specifically include the following modules:
a request receiving module 601, configured to receive a hardware operation request sent by the client for a target server in the at least one server, where the hardware operation request carries an operation type;
the resource searching module 602 is configured to obtain a Redfish resource tree of the target server, and search a resource of a target node corresponding to the operation type;
a processing module 603, configured to adjust the resource of the target node according to the operation type, to obtain a processing result returned by the target server;
and a result returning module 604, configured to return the processing result to the management client.
In a preferred embodiment of the present invention, the resource searching module 602 may include the following sub-modules:
and the resource searching sub-module is used for calling the Redfish interface of the target server, acquiring a Redfish resource tree of the target server and searching the resource of the target node corresponding to the operation type.
In a preferred embodiment of the present invention, the resource searching sub-module that invokes the Redfish interface of the target server may include the following units:
a root node resource obtaining unit, configured to invoke a Redfish interface of the target server to obtain a resource of a root node in the Redfish resource tree, where the resource of the root node includes Redfish version information;
a first target resource obtaining unit, configured to invoke a Redfish interface of the target server if it is determined that the target server supports expansion query according to the Redfish version information, obtain resources of a plurality of nodes in the Redfish resource tree, and obtain resources of the target node;
and the second target resource obtaining unit is used for sequentially calling the Redfish interfaces of the target server from the root node to obtain the resources of each node in the Redfish resource tree if the target server does not support the Expand query according to the Redfish version information, so as to obtain the resources of the target node.
In a preferred embodiment of the present invention, the first target resource obtaining unit may include the following sub-units:
a maximum query depth determining subunit, configured to determine a maximum query depth of the target server according to the Redfish version information;
A depth difference calculating subunit, configured to calculate a depth difference between the root node and a preset node;
a query parameter determining subunit, configured to determine a query parameter according to the depth difference and a maximum query depth;
a resource sub-tree obtaining subunit, configured to invoke a Redfish interface of the target server, and obtain resources of a plurality of nodes in the resource tree according to the query parameter to obtain a resource sub-tree;
and the target resource obtaining subunit is used for obtaining the resource of the target node from the resource subtree.
In a preferred embodiment of the present invention, the query parameter determining subunit may include the following subunits:
a first query parameter determining subunit, configured to determine the depth difference as a query parameter if the depth difference is smaller than the maximum query depth;
and the second query parameter determining subunit is configured to determine the maximum query depth as a query parameter if the depth difference is greater than or equal to the maximum query depth.
In a preferred embodiment of the invention, the device further comprises the following modules:
an allowable operation type determining module, configured to determine one or more allowable operation types according to the resources of the target node;
The first execution module is used for executing the subsequent steps if the one or more allowed operation types contain the operation type;
and the second execution module is used for not executing the subsequent steps if the operation type is not included in the allowed one or more operation types.
In a preferred embodiment of the present invention, the hardware operation request further carries a server serial number and an out-of-band IP address, and the apparatus further comprises the following modules:
the target serial number searching module is used for searching a target serial number corresponding to the out-of-band IP address from a preset database;
the third execution module is used for executing the subsequent steps if the server serial number is the same as the target serial number;
and the fourth execution module is used for not executing the subsequent steps if the server serial number is different from the target serial number.
In a preferred embodiment of the invention, the device further comprises the following modules:
the allowed operation node searching module is used for searching allowed operation nodes corresponding to the out-of-band IP addresses from a preset database;
a fifth execution module, configured to execute a subsequent step if the allowed operation node includes a target node corresponding to the operation type;
And the sixth execution module is used for not executing the subsequent steps if the allowed operation node does not contain the target node corresponding to the operation type.
Referring to fig. 7, there is shown a block diagram of another embodiment of a server management device of the present invention, which is applied to a management client, where the management client is communicatively connected to a Redfish server, and the Redfish server is communicatively connected to at least one server, and may specifically include the following modules:
an operation determining module 701 for determining an operation type in response to a user operation;
a request generating module 702, configured to generate a hardware operation request for a target server in the at least one server according to the operation type;
a request sending module 703, configured to send the hardware operation request for the target server in the at least one server to a Redfish server;
and a result receiving module 704, configured to receive a processing result returned by the Redfish server side in processing the hardware operation request.
In a preferred embodiment of the present invention, the request generation module 702 may include the following sub-modules:
the serial number acquisition sub-module is used for acquiring a server serial number and an out-of-band IP address corresponding to the target server;
And the request generation sub-module is used for generating a management request containing the server serial number, the out-of-band IP address and the operation type.
For the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points.
As shown in fig. 8, an embodiment of the present invention further provides an electronic device, including:
a processor 801, a storage medium 802, and a bus 803, the storage medium 802 storing machine-readable instructions executable by the processor 801, the processor 801 and the storage medium 802 communicating over the bus 803 when the electronic device is running, the processor 801 executing the machine-readable instructions to perform a method according to any of the embodiments of the invention. The specific implementation manner and the technical effect are similar, and are not repeated here.
As shown in fig. 9, an embodiment of the present invention further provides a storage medium having stored thereon a computer program 901, which when executed by a processor performs a method according to any of the embodiments of the present invention. The specific implementation manner and the technical effect are similar, and are not repeated here.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.
It will be apparent to those skilled in the art that embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the invention may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the scope of the embodiments of the invention.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or terminal device comprising the element.
The foregoing has described in detail a server management method and a server management system according to the present invention, and specific examples have been used herein to illustrate the principles and embodiments of the present invention, where the above examples are provided only to assist in understanding the method and core idea of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.
Claims (9)
1. The server management method is characterized by being applied to a Redfish server, wherein the Redfish server is in communication connection with a management client and at least one server, and the method comprises the following steps:
receiving a hardware operation request aiming at a target server in the at least one server, wherein the hardware operation request carries an operation type, and the hardware operation request is sent by the management client;
acquiring a Redfish resource tree of the target server, and searching resources of a target node corresponding to the operation type;
adjusting the resources of the target node according to the operation type to obtain a processing result returned by the target server;
returning the processing result to the management client;
the obtaining the Redfish resource tree of the target server and searching the resources of the target node corresponding to the operation type comprises the following steps:
invoking a Redfish interface of the target server to acquire resources of a root node in a Redfish resource tree of the target server, wherein the resources of the root node contain Redfish version information;
if the target server supports expansion query according to the Redfish version information, calling a Redfish interface of the target server, and acquiring resources of a plurality of nodes in the Redfish resource tree to obtain the resources of the target node;
And if the target server does not support the Expand query according to the Redfish version information, sequentially calling Redfish interfaces of the target server from the root node, and acquiring resources of each node in the Redfish resource tree to obtain the resources of the target node.
2. The method of claim 1, wherein the calling the Redfish interface of the target server to obtain the resources of the plurality of nodes in the Redfish resource tree to obtain the resources of the target node comprises:
determining the maximum query depth of the target server according to the Redfish version information;
calculating the depth difference between the root node and a preset node;
determining query parameters according to the depth difference and the maximum query depth;
calling a Redfish interface of the target server, and acquiring resources of a plurality of nodes in the resource tree according to the query parameters to obtain a resource sub-tree;
and obtaining the resources of the target node from the resource subtree.
3. The method of claim 2, wherein said determining query parameters from said depth difference and a maximum query depth comprises:
if the depth difference is smaller than the maximum query depth, determining the depth difference as a query parameter;
And if the depth difference is greater than or equal to the maximum query depth, determining the maximum query depth as a query parameter.
4. The method of claim 1, further comprising, after the step of obtaining the Redfish resource tree of the target server and searching for the resources of the target node corresponding to the operation type:
determining one or more allowed operation types according to the resources of the target node;
if the one or more allowed operation types comprise the operation type, executing the subsequent steps;
if the one or more allowed operation types do not include the operation type, no subsequent steps are executed.
5. The method of claim 1, wherein the hardware operation request further carries a server serial number and an out-of-band IP address, and further comprising, after the step of receiving the hardware operation request sent by the management client for a target server of the at least one server:
searching a target serial number corresponding to the out-of-band IP address from a preset database;
if the server serial number is the same as the target serial number, executing the subsequent steps;
If the server serial number is not the same as the target serial number, no subsequent steps are performed.
6. The method according to claim 1 or 5, further comprising, after the step of receiving a hardware operation request for a target server of the at least one server sent by the management client:
searching an allowed operation node corresponding to the out-of-band IP address carried by the hardware operation request from a preset database;
if the allowed operation node contains a target node corresponding to the operation type, executing the subsequent steps;
and if the allowed operation node does not contain the target node corresponding to the operation type, the subsequent steps are not executed.
7. A server management system is characterized by comprising a management client, a Redfish server and at least one server, wherein the Redfish server is in communication connection with the management client and the at least one server,
the management client is used for responding to user operation to determine the operation type; generating a hardware operation request aiming at a target server in the at least one server according to the operation type; the hardware operation request aiming at the target server is sent to a Redfish server; receiving a processing result returned by the Redfish server for processing the hardware operation request;
The Redfish server is used for receiving a hardware operation request aiming at a target server in the at least one server, which is sent by the management client, wherein the hardware operation request carries an operation type; acquiring a Redfish resource tree of the target server, and searching resources of a target node corresponding to the operation type; adjusting the resources of the target node according to the operation type to obtain a processing result returned by the target server; returning the processing result to the management client;
the at least one server is used for supporting a Redfish protocol and organizing resources of the at least one server to obtain a Redfish resource tree;
the obtaining the Redfish resource tree of the target server and searching the resources of the target node corresponding to the operation type comprises the following steps:
invoking a Redfish interface of the target server to acquire resources of a root node in a Redfish resource tree of the target server, wherein the resources of the root node contain Redfish version information;
if the target server supports expansion query according to the Redfish version information, calling a Redfish interface of the target server, and acquiring resources of a plurality of nodes in the Redfish resource tree to obtain the resources of the target node;
And if the target server does not support the Expand query according to the Redfish version information, sequentially calling Redfish interfaces of the target server from the root node, and acquiring resources of each node in the Redfish resource tree to obtain the resources of the target node.
8. An electronic device, comprising:
a processor, a storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium in communication over a bus when the electronic device is running, the processor executing the machine-readable instructions to perform the method of any one of claims 1-6.
9. A storage medium having stored thereon a computer program which, when executed by a processor, performs the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011149155.3A CN112199197B (en) | 2020-10-23 | 2020-10-23 | Server management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011149155.3A CN112199197B (en) | 2020-10-23 | 2020-10-23 | Server management method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112199197A CN112199197A (en) | 2021-01-08 |
| CN112199197B true CN112199197B (en) | 2023-07-18 |
Family
ID=74011245
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011149155.3A Active CN112199197B (en) | 2020-10-23 | 2020-10-23 | Server management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112199197B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI770941B (en) * | 2021-04-15 | 2022-07-11 | 新加坡商捷普電子(新加坡)公司 | Method of accessing redfish data on unified extensible firmware interface |
| CN113342356B (en) * | 2021-05-18 | 2023-03-28 | 浪潮软件股份有限公司 | Client framework operation and management configuration method |
| CN113204427A (en) * | 2021-05-20 | 2021-08-03 | 远景智能国际私人投资有限公司 | Resource management method, resource management device, computer equipment and storage medium |
| CN113849373A (en) * | 2021-09-27 | 2021-12-28 | 中国电信股份有限公司 | Server supervision method and device and storage medium |
| CN113849377A (en) * | 2021-09-30 | 2021-12-28 | 联想(北京)有限公司 | Server management method, device, equipment and computer storage medium |
| CN114143187B (en) * | 2021-10-26 | 2023-08-18 | 苏州浪潮智能科技有限公司 | Intelligent platform interface network address management method, system, terminal and storage medium |
| CN114050971B (en) * | 2021-11-09 | 2024-02-02 | 网易（杭州）网络有限公司 | Server configuration method, device, system, electronic equipment and storage medium |
| CN115473779B (en) * | 2022-07-21 | 2024-01-09 | 浪潮通信技术有限公司 | Server management method and system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107590392A (en) * | 2017-08-14 | 2018-01-16 | 大唐高鸿信安（浙江）信息科技有限公司 | Utilize the system and method for script verification hardware integrity |
| CN108259270A (en) * | 2018-01-11 | 2018-07-06 | 郑州云海信息技术有限公司 | A kind of data center's system for unified management design method |
| CN108334411A (en) * | 2018-01-30 | 2018-07-27 | 郑州云海信息技术有限公司 | Resource transfer method and device based on Redfish in a kind of BMC |
| CN108920103A (en) * | 2018-06-29 | 2018-11-30 | 平安科技（深圳）有限公司 | Management method, device, computer equipment and the storage medium of server |
| CN110858144A (en) * | 2018-08-24 | 2020-03-03 | 中国电信股份有限公司 | Automatic server deployment method, device and system and computer readable storage medium |
| CN111130861A (en) * | 2019-12-11 | 2020-05-08 | 苏州浪潮智能科技有限公司 | Method and device for stateless automatic management of whole cabinet equipment |
| CN111130891A (en) * | 2019-12-26 | 2020-05-08 | 北京浪潮数据技术有限公司 | Server management device and method, electronic equipment and storage medium |
| CN111400167A (en) * | 2020-02-21 | 2020-07-10 | 苏州浪潮智能科技有限公司 | Redfish service compliance verification method, device, equipment and medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10067547B2 (en) * | 2012-06-28 | 2018-09-04 | Intel Corporation | Power management control of remote servers |
| US10122739B2 (en) * | 2016-08-31 | 2018-11-06 | Dell Products L.P. | Rootkit detection system and method |
| US11016833B2 (en) * | 2017-07-01 | 2021-05-25 | Intel Corporation | Remote debug for scaled computing environments |
| US10997092B2 (en) * | 2017-08-10 | 2021-05-04 | Seagate Technology Llc | Enabling out-of-band hardware management via an in-band communications channel |
| US11132315B2 (en) * | 2019-02-04 | 2021-09-28 | American Megatrends International, Llc | Secured and out-of-band (OOB) server san solution on a commodity storage box |
-
2020
- 2020-10-23 CN CN202011149155.3A patent/CN112199197B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107590392A (en) * | 2017-08-14 | 2018-01-16 | 大唐高鸿信安（浙江）信息科技有限公司 | Utilize the system and method for script verification hardware integrity |
| CN108259270A (en) * | 2018-01-11 | 2018-07-06 | 郑州云海信息技术有限公司 | A kind of data center's system for unified management design method |
| CN108334411A (en) * | 2018-01-30 | 2018-07-27 | 郑州云海信息技术有限公司 | Resource transfer method and device based on Redfish in a kind of BMC |
| CN108920103A (en) * | 2018-06-29 | 2018-11-30 | 平安科技（深圳）有限公司 | Management method, device, computer equipment and the storage medium of server |
| CN110858144A (en) * | 2018-08-24 | 2020-03-03 | 中国电信股份有限公司 | Automatic server deployment method, device and system and computer readable storage medium |
| CN111130861A (en) * | 2019-12-11 | 2020-05-08 | 苏州浪潮智能科技有限公司 | Method and device for stateless automatic management of whole cabinet equipment |
| CN111130891A (en) * | 2019-12-26 | 2020-05-08 | 北京浪潮数据技术有限公司 | Server management device and method, electronic equipment and storage medium |
| CN111400167A (en) * | 2020-02-21 | 2020-07-10 | 苏州浪潮智能科技有限公司 | Redfish service compliance verification method, device, equipment and medium |
Non-Patent Citations (4)
| Title |
|---|
| A Standard to Rule Them All：Redfish;Glauco Goncalves et al.;《IEEE Communications Standards Magazine》;第3卷(第2期);第36-43页 * |
| 基于Redfish的服务器管理;田祥波;《中小企业管理与科技（上旬刊）》(第6期);第234页 * |
| 基于微服务的VPX机箱管理系统研究;刘峰;;环境技术(第04期);第18-21页 * |
| 自动化批量部署管理的实践;魏海涛;;中国传媒科技(第10期);第119-121页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112199197A (en) | 2021-01-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112199197B (en) | Server management method and system | |
| US8402123B2 (en) | Systems and methods for inventorying un-provisioned systems in a software provisioning environment | |
| US9250672B2 (en) | Cloning target machines in a software provisioning environment | |
| US8832256B2 (en) | Providing a rescue Environment in a software provisioning environment | |
| US8601466B2 (en) | Software deployment method and system, software deployment server and user server | |
| CN108737467B (en) | Server log viewing method, device and system | |
| US20100217843A1 (en) | Systems and methods for collecting and altering firmware configurations of target machines in a software provisioning environment | |
| CN110943860B (en) | BMC (baseboard management controller) firmware updating method and system, electronic equipment and storage medium | |
| US9690593B2 (en) | Server information handling system configuration from an end state definition file | |
| CN111130962B (en) | Automatic configuration method, equipment, system and storage medium for switch | |
| CN111786810A (en) | Automatic deployment method and system for large-scale test bed nodes | |
| US20210328874A1 (en) | Compute node discovery mechanism | |
| WO2018082079A1 (en) | Method and apparatus for dynamically managing data exchange | |
| CN113535262A (en) | Method, device, equipment and storage medium for controlling starting of proxy node | |
| CN113596087A (en) | Application upgrading method and device and computer readable storage medium | |
| CN112463549A (en) | Auditing method, device and equipment of cloud platform and computer readable storage medium | |
| CN116627595A (en) | Virtual machine creation method and related components | |
| US8190715B1 (en) | System and methods for remote agent installation | |
| CN106375132B (en) | Cloud server system and management method thereof | |
| CN111600751B (en) | Data center management method and system | |
| US11528185B1 (en) | Automated network device provisioning | |
| CN113656378A (en) | Server management method, device and medium | |
| WO2012054023A1 (en) | Computer system with computers that perform network boots | |
| CN109101253B (en) | Management method and device for host in cloud computing system | |
| CN111596933A (en) | File processing method and device, electronic equipment and computer readable 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 |