CN110098952B - Server management method and device - Google Patents
Server management method and device Download PDFInfo
- Publication number
- CN110098952B CN110098952B CN201910229607.XA CN201910229607A CN110098952B CN 110098952 B CN110098952 B CN 110098952B CN 201910229607 A CN201910229607 A CN 201910229607A CN 110098952 B CN110098952 B CN 110098952B
- Authority
- CN
- China
- Prior art keywords
- server
- protocol
- information
- management
- hardware
- 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
Images
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/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4406—Loading of operating system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a management method and a device of a server, wherein the management method based on the server is applied to a server management system and comprises the following steps: identifying hardware information of a server to be installed through an intelligent platform management interface IPMI protocol; hardware setting is carried out on the server to be installed through an IPMI protocol; determining an operating system of a server to be installed through hardware setting and a preset operating protocol; after the operating system is installed on the server to be installed, software configuration is carried out on the server to be installed by utilizing a Saltstack tool and a front-end software package management tool, wherein the software configuration comprises network IP address setting and/or system user permission setting and/or software installation; and writing the to-be-installed server and the hardware information which are configured by the software into a configuration management database so as to operate the to-be-installed server. Therefore, automatic processing from racking, installing, deploying to delivering to a user of the server can be achieved, and labor input is saved.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for managing a server.
Background
With the development of internet technology, the operation, maintenance and management operations of servers become important components in the operation and maintenance work of the internet, in the prior art, the installation of a server operating system, the configuration of a system operating environment, the monitoring of a system and the setting of service states, the inquiry of a system and service logs and the processing of emergencies are usually realized through manual operation or script writing, so that the manual deployment dimension and the script deployment dimension are very complicated, the problem is more obvious due to the increasing number of servers, and the existing operation and maintenance platform only provides one type of basic service and is dispersed in different systems, so that the automatic processing from the loading, installation, deployment to the delivery to a user cannot be realized.
Disclosure of Invention
In view of the foregoing problems, embodiments of the present application provide a method for managing a server, which can solve the problem that the prior art cannot implement automated processing.
Correspondingly, the embodiment of the application also provides a management device of the server, which is used for ensuring the realization and the application of the method.
In order to solve the above problem, an embodiment of the present application discloses a management method for a server, which is applied to a server management system, and the method includes:
identifying hardware information of a server to be installed through an intelligent platform management interface IPMI protocol, wherein the hardware information comprises hardware configuration information, network information and power state information of the server to be installed;
carrying out hardware setting on the server to be installed through the IPMI protocol, wherein the hardware setting comprises a starting protocol, power supply setting and disk setting;
determining an operating system of the server to be installed according to the hardware setting and a preset operating protocol, wherein the operating protocol comprises at least one of a Dynamic Host Configuration Protocol (DHCP) protocol, a simple file transfer protocol (TFTP) protocol and a multi-path MTFTP protocol;
after the operating system is installed on the server to be installed, performing software configuration on the server to be installed by using a Saltstack tool and a front-end software package management tool, wherein the software configuration comprises network IP address setting and/or system user permission setting and/or software installation;
and writing the to-be-installed server and the hardware information after the software configuration is completed into a configuration management database so as to operate the to-be-installed server.
Correspondingly, the embodiment of the application also discloses a management method and a management device of the server, which are applied to a server management system, wherein the device comprises the following steps:
the system comprises an information identification module, a power supply state identification module and a power supply state identification module, wherein the information identification module is used for identifying hardware information of a server to be installed through an intelligent platform management interface IPMI protocol, and the hardware information comprises hardware configuration information, network information and power supply state information of the server to be installed;
the hardware setting module is used for carrying out hardware setting on the server to be installed through the IPMI protocol, and the hardware setting comprises a starting protocol, power supply setting and disk setting;
the system determination module is used for determining an operating system of the server to be installed according to the hardware setting and a preset operating protocol, wherein the operating protocol comprises at least one of a Dynamic Host Configuration Protocol (DHCP) protocol, a simple file transfer protocol (TFTP) protocol and a multi-path MTFTP protocol;
the software configuration module is used for performing software configuration on the server to be installed by utilizing a Saltstack tool and a front-end software package management tool after the operating system is installed on the server to be installed, wherein the software configuration comprises network IP address setting and/or system user permission setting and/or software installation;
and the database writing module is used for writing the to-be-installed server and the hardware information which are subjected to software configuration into a configuration management database so as to operate the to-be-installed server.
An apparatus is also provided in an embodiment of the present application, comprising a processor and a memory, wherein,
the processor executes the computer program code stored in the memory to realize the management method of the server.
An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the management method for the server described in the present application.
The embodiment of the application has the following advantages:
identifying hardware information of a server to be installed through an intelligent platform management interface IPMI protocol, wherein the hardware information comprises hardware configuration information, network information and power state information of the server to be installed; carrying out hardware setting on the server to be installed through the IPMI protocol, wherein the hardware setting comprises a starting protocol, power supply setting and disk setting; determining an operating system of the server to be installed according to the hardware setting and a preset operating protocol, wherein the operating protocol comprises at least one of a Dynamic Host Configuration Protocol (DHCP) protocol, a simple file transfer protocol (TFTP) protocol and a multi-path MTFTP protocol; after the operating system is installed on the server to be installed, performing software configuration on the server to be installed by using a Saltstack tool and a front-end software package management tool, wherein the software configuration comprises network IP address setting and/or system user permission setting and/or software installation; and writing the to-be-installed server and the hardware information after the software configuration is completed into a configuration management database so as to operate the to-be-installed server. Therefore, automatic processing from racking, installing, deploying to delivering to a user of the server can be achieved, automatic operation and maintenance are carried out on the server after the server is racking, and labor input is saved.
Drawings
FIG. 1 is a flow chart of steps of an embodiment of a method for managing a server of the present application;
FIG. 2 is a flow chart of steps in an alternative embodiment of a method for managing a server of the present application;
FIG. 3 is a block diagram of a server management system according to the present application;
FIG. 4 is a flow chart of steps in an alternative embodiment of a method for managing a server of the present application;
FIG. 5 is a flow chart of steps of an embodiment of a method for managing a server of the present application;
FIG. 6 is a flow chart illustrating operations performed by a server to be installed in a server management system according to the present application;
FIG. 7 is a flow chart of steps of an embodiment of a method for managing a server of the present application;
fig. 8 is a block diagram of a management apparatus of a server according to an embodiment of the present application;
fig. 9 is a block diagram of an embodiment of a server management apparatus according to the present application.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.
Referring to fig. 1, a flowchart illustrating steps of an embodiment of a server management method according to the present application is shown, and is applied to a server management system, where the method specifically includes the following steps:
The hardware information comprises hardware configuration information, network information and power state information of the server to be installed.
IPMI (Chinese: Intelligent Platform Management Interface, English: Intelligent Platform Management Interface) is an open standard hardware Management Interface specification, defines a specific method for communication of an embedded Management subsystem, IPMI information is communicated through a baseboard Management controller (located on a hardware component of the IPMI specification), low-level hardware Intelligent Management is used for Management without using an operating system, so that out-of-band server Management can be performed, and the operating system does not need to bear tasks of transmitting system state data. And obtaining the hardware information of the current newly-accessed server, namely the server to be installed, by utilizing the IPMI so as to correspondingly realize the installation and racking operation of the server to be installed. After the step, the server to be installed is in a state of waiting for installation.
And 102, carrying out hardware setting on the server to be installed through an IPMI protocol.
The hardware setting comprises a starting protocol, a power supply setting and a disk setting.
Illustratively, the boot protocol includes hard disk boot, network card boot, optical disk boot, usb disk boot, etc., preferably, the network card boot is adopted, that is, PXE protocol, PXE (chinese: pre-boot execution environment, english: preboot execution environment), which is a network mode developed by Intel corporation and working in Client/Server, and supports the workstation to download images from a remote Server through a network, and thus supports the booting of an operating system through the network, during the boot process, the to-be-installed Server requires a Server management system to allocate IP addresses, and then performs the following operation of step 103, that is, downloads a boot software package into the memory of the to-be-installed Server for execution by using TFTP (chinese: simple file transfer protocol) or MTFTP (chinese: multiple simple file transfer protocol, english: multicast file transfer protocol), and the basic software setting of the to-be-installed Server is completed by the boot software package, thereby booting the operating system previously installed in the server. The automatic operation of the installation and deployment of the server can be further realized by adopting a network card starting mode.
And 103, determining an operating system of the server to be installed through hardware setting and a preset operating protocol.
Wherein the operation protocol comprises at least one of DHCP protocol, TFTP protocol and MTFTP protocol. The DHCP (Dynamic Host Configuration Protocol, english) Protocol is a network Protocol of a local area network, works using the UDP Protocol, and has two main uses: an IP address is automatically assigned to an internal network or network service provider as a means of central management of all computers to a user or internal network administrator.
And step 104, after the operating system is installed on the server to be installed, performing software configuration on the server to be installed by using a Saltstack tool and a front-end software package management tool.
Wherein the software configuration comprises network IP address setting and/or system user authority setting and/or software installation.
Illustratively, through the operations of step 101-103 described above, the hardware level setting of the server to be installed is realized, when the operating system is not installed on the server to be installed, the IPMI is used to realize the information acquisition and hardware setting of the server to be installed, the server to be installed after the operating system is installed may first register a saltswitch tool to realize the instruction transmission between the server to be installed and the server management system by using the saltswitch tool, wherein the saltswitch tool is an open source software tool, allows an administrator to establish a unified management system for various operating systems, acts as slave and master topologies, can be executed in one or more subordinates in combination with specific commands, the saltswitch allows the administrator to use "gradient" in addition to running remote commands, can run remote queries from the saltswitch, thus collects slave status information and allows the administrator to store information in a central location, while the SaltStack may also help the administrator define the desired states on the target system that are used when applied the sls file, which contains very specific requirements on how to obtain the desired states on the system.
A front-end software package management tool, such as YUM tool (Yellow dog update Modified), is a Shell front-end software package manager in Fedora and RedHat and CentOS, which can automatically download and install data packages from a specified server to automatically process dependency relationships and install all dependent software packages at once, without cumbersome downloading and installing many times.
And 105, writing the to-be-installed server with the software configuration and the hardware information into a configuration management database to operate the to-be-installed server.
The configuration management database, namely the CMDB database stores and manages various configuration information of equipment in an enterprise IT framework, is closely connected with all service support and service delivery processes, supports the operation of various processes, exerts the value of the configuration information and simultaneously depends on related processes to ensure the accuracy of data. In practical projects, CMDB is often considered a basis for building other ITIL procedures with priority. Since 70-80% of IT-related problems have a direct relationship with environmental changes, the change management needs to be implemented through an automatic and repeatable process to manage the changes, so that when the changes occur, a standardized process is executed, the influence of the changes on the whole system management can be predicted, and the influence can be evaluated and controlled, namely, the change management process automation is preferably realized based on the CMDB database.
For example, after the server to be installed after completing the software configuration is written into the CMBD, the server to be installed is on shelf, that is, the user can view the server to be installed and the corresponding data information on the platform of the server management system.
To sum up, the management method for a server provided in the embodiment of the present application is applied to a server management system, and identifies hardware information of a server to be installed through an IPMI protocol, where the hardware information includes hardware configuration information, network information, and power state information of the server to be installed; carrying out hardware setting on the server to be installed through an IPMI protocol, wherein the hardware setting comprises a starting protocol, power supply setting and disk setting; determining an operating system of a server to be installed through hardware setting and a preset operating protocol, wherein the operating protocol comprises at least one of a DHCP protocol, a TFTP protocol and a MTFTP protocol; after the operating system is installed on the server to be installed, software configuration is carried out on the server to be installed by utilizing a Saltstack tool and a front-end software package management tool, wherein the software configuration comprises network IP address setting and/or system user permission setting and/or software installation; and writing the to-be-installed server and the hardware information which are configured by the software into a configuration management database so as to operate the to-be-installed server. Therefore, automatic processing from racking, installing, deploying to delivering to a user of the server can be achieved, automatic operation and maintenance are carried out on the server after the server is racking, and labor input is saved.
Referring to fig. 2, a flow chart of steps of an alternative embodiment of a server management method of the present application is shown, the method further comprising the steps of:
and step 106, after the server to be installed runs, performing management operation on the server to be installed by using a Saltstack tool.
The management operation comprises cluster changing operation and/or off-shelf operation and/or running data updating operation.
Illustratively, for a life cycle of a server, including a process from ready-to-mount machine-ready to interact-idle-use-idle-off-shelf-scrapping, the steps in fig. 1 complete the states of ready-to-mount machine, in-mount machine, ready to interact, and idle of the server to be installed, that is, after the server to be installed is put on shelf through the above steps, the server to be installed is set to be in an idle state, and the server to be installed is waited to be assigned with a job task by the server management system. Therefore, after the server to be installed runs, that is, in an idle state, the management operation is continued on the server to be installed through the SaltStack tool, which is mainly used for issuing commands, execution and scripts, and currently prohibits the operation of issuing commands and scripts across the machine room, so as to avoid the existing risks.
For example, fig. 3 is a schematic diagram of an overall system structure of the technical solution proposed in the present application, where the mis-ui (theme interface) initiates a warehousing operation of a server to be installed, that is, invokes IMPI to identify, provide IP, application software, a machine room, environment information, configure a host name, add a cluster relationship, host operations on a bastion machine, and the like, applies for warehousing the server to be installed, so as to set the server to be installed in an idle state, and then enter the mis-worker, so as to implement installation of the server to be installed, operation management by using a saltswitch tool, and management of a life cycle. Wherein gifts is a module for storing scripts, which is used by a user when executing the scripts using the Saltstack tool; the timing tasks comprise synchronization of ucloud host information, synchronization of bastion machine authority, installation detection and the like.
Referring to fig. 4, which is a flowchart illustrating steps of an alternative embodiment of a server management method according to the present application, after an operating system is installed in a server to be installed, the step 104 configures software of the server to be installed by using a saltswitch tool and a front-end software package management tool, including the following steps:
and step 1041, controlling the server to be installed to download the corresponding application software package by using a Saltstack tool.
And step 1042, configuring the network IP address setting and/or the system user permission setting of the server to be installed by using a Saltstack tool and a front-end software package management tool.
Illustratively, after the installation of the operating system is completed by the server to be installed, a saltswitch tool is registered, which is equivalent to setting an Agent (Agent) in the server to be installed, for setting the authority of the server to be installed, and then the saltswitch tool can be used to implement control operations beyond a hardware level, that is, operations at a software level, such as executing a corresponding program, drawing, editing, and performing operation maintenance and management operations on the server to enter a field, issuing an instruction to the server to be installed through the saltswitch tool, for example, instructing the server to download an application package defined by an intranet, install the application package, start a certain service, and the like.
Referring to fig. 5, a flowchart illustrating steps of an alternative embodiment of a server management method according to the present application is shown, where the management operation is a shelf-off operation, and the step 106 is to perform the management operation on the server to be installed by using a saltswitch tool after the server to be installed runs, and includes the following steps:
The network access information comprises bastion machine information, monitoring information, virtual machine information, cluster information, setting information of the Saltstack tool and associated information of other servers.
For example, when a server to be installed runs for a certain period of time, a fault may occur or due to different actual requirements, the server to be installed needs to be off-shelf, bastard information set when the server to be installed initially enters a network loader needs to be deleted by using a saltswitch tool, monitoring of the system to be installed is deleted, a virtual machine (zstack, kvm, vsphere) corresponding to the system to be installed is deleted, registration information of salt-key, namely the saltswitch tool, is removed, and a cluster-host relationship corresponding to the server and other related information of the host are deleted; and if the running application needs to be closed, releasing the IP set for the server to be installed when the installation is carried out, and the like.
The bastion machine is used in a specific network environment, and is used to collect and monitor the system state, safety event and network activity of each component in the network environment in real time by various technical means in order to ensure that the network and data are not invaded and damaged by external and internal users, so as to alarm, process in time and audit and determine responsibility. Functionally, the method integrates two main functions of core system operation and safety audit management and control. In technical implementation, the direct access of the terminal computer to the network and server resources is cut off, and the access of the terminal computer to the network and the server is taken over in a protocol proxy mode. In a pictographic way, the terminal computer accesses the target and needs to be translated by the bastion machine. Therefore, before the installation of the server to be installed is started, the server to be installed needs to be hosted on the bastion machine, a clustering relation is added to the server to be installed, a host name and the like are configured, and when the server to be installed is off-shelf, the clustering relation, the bastion machine information and the like of the server to be installed are correspondingly clear, namely the information of the server is clear in the server system.
Referring to fig. 6, a flowchart of a plurality of operations performed by a server to be installed in a server management system according to an embodiment of the present application is shown.
Referring to fig. 7, a flowchart illustrating steps of an embodiment of a server management method according to the present application, which is applied to a server, includes the following steps:
The hardware setting comprises a starting protocol, a power supply setting and a disk setting, and the operation protocol comprises at least one of a DHCP protocol, a TFTP protocol and a MTFTP protocol.
At step 702, after the installation of the operating system is completed, a Saltstack tool is registered for software configuration and management operations via the Saltstack tool.
The software configuration comprises network IP address setting and/or system user authority setting and/or software installation, and the management operation comprises cluster change operation and/or off-shelf operation and/or operation data updating operation.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the embodiments are not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the embodiments. Further, those skilled in the art will also appreciate that the embodiments described in the specification are presently preferred and that no particular act is required of the embodiments of the application.
Referring to fig. 8, a block diagram of an embodiment of a management apparatus of a server according to the present application is shown, and is applied to a server management system, where the management apparatus specifically includes the following modules:
the information identifying module 810 is configured to identify hardware information of the server to be installed through an IPMI protocol, where the hardware information includes hardware configuration information, network information, and power status information of the server to be installed.
The hardware setting module 820 is configured to perform hardware setting on the to-be-installed server through an IPMI protocol, where the hardware setting includes a start protocol, a power supply setting, and a disk setting;
the system determining module 830 is configured to determine, through hardware setting and a preset operation protocol, an operating system of the server to be installed, where the operation protocol includes at least one of a dynamic host configuration protocol DHCP protocol, a simple file transfer protocol TFTP protocol, and a multiple simple file transfer protocol MTFTP protocol.
And the software configuration module 840 is configured to perform software configuration on the server to be installed by using a saltswitch tool and a front-end software package management tool after the operating system is installed on the server to be installed, where the software configuration includes network IP address setting and/or system user permission setting and/or software installation.
And a database writing module 850, configured to write the to-be-installed server with the software configuration completed and the hardware information into the configuration management database, so as to run the to-be-installed server.
Optionally, the apparatus 800 further includes: the operation management module is used for performing management operation on the server to be installed by utilizing a Saltstack tool after the server to be installed runs; the management operations include cluster change operations and/or off-shelf operations and/or run data update operations.
In an alternative embodiment of the present application, the software configuration module 840 includes the following sub-modules:
the downloading submodule is used for controlling the server to be installed to download the corresponding application software package by utilizing a Saltstack tool;
and the configuration submodule is used for configuring the network IP address setting and/or the system user permission setting of the server to be installed by utilizing the Saltstack tool and the front-end software package management tool.
Optionally, the management operation is a shelf-off operation, and the operation management module includes:
the deleting submodule is used for deleting network access information of the server to be installed, wherein the network access information comprises bastion machine information, monitoring information, virtual machine information, cluster information, setting information of Saltstack tools and relevant information of other servers;
and the changing submodule is used for changing the network information of the server to be installed.
Referring to fig. 9, a block diagram of an embodiment of a management apparatus of a server according to the present application is shown, and the management apparatus is applied to the server and specifically includes the following modules:
the system installation module 910 is configured to install an operating system determined by the server management system according to hardware settings of the server and a preset operation protocol, where the hardware settings include a boot protocol, a power setting, and a disk setting, and the operation protocol includes at least one of a DHCP protocol, a TFTP protocol, and a MTFTP protocol.
And a tool registration module 920, configured to register a saltswitch tool after the installation of the operating system is completed, so as to perform software configuration and management operations through the saltswitch tool, where the software configuration includes network IP address setting and/or system user authority setting and/or software installation, and the management operations include cluster change operations and/or off-shelf operations and/or running data update operations.
The present application further provides a non-volatile readable storage medium, where one or more modules (programs) are stored in the storage medium, and when the one or more modules are applied to a terminal device, the one or more modules may cause the terminal device to execute instructions (instructions) of method steps in the present application.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one of skill in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present application 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 present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present application 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 application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, 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 terminal 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 terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal 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 application have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the true scope of the embodiments of the application.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be 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. Also, 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 an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The principle and the implementation of the present application are explained herein by applying specific examples, and the above description of the embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A management method of a server is applied to a server management system, and the method comprises the following steps:
identifying hardware information of a server to be installed through an intelligent platform management interface IPMI protocol, wherein the hardware information comprises hardware configuration information, network information and power state information of the server to be installed;
carrying out hardware setting on the server to be installed through the IPMI protocol, wherein the hardware setting comprises a starting protocol, power supply setting and disk setting;
determining an operating system of the server to be installed according to the hardware setting and a preset operating protocol, wherein the operating protocol comprises at least one of a Dynamic Host Configuration Protocol (DHCP) protocol, a simple file transfer protocol (TFTP) protocol and a multi-path MTFTP protocol;
after the operating system is installed on the server to be installed, performing software configuration on the server to be installed by using a Saltstack tool and a front-end software package management tool, wherein the software configuration comprises network IP address setting and/or system user permission setting and/or software installation;
and writing the to-be-installed server and the hardware information after the software configuration into a configuration management database so as to operate the to-be-installed server.
2. The method of claim 1, further comprising:
after the server to be installed runs, the Saltstack tool is used for carrying out management operation on the server to be installed;
the management operation comprises cluster changing operation and/or off-shelf operation and/or operation data updating operation.
3. The method according to claim 1, wherein after the installation of the to-be-installed server completes the operating system, performing software configuration on the to-be-installed server by using a Saltstack tool and a YUM front-end software package management tool, and including:
controlling the server to be installed to download the corresponding application software package by using the Saltstack tool;
and configuring the network IP address setting and/or the system user permission setting of the server to be installed by utilizing the Saltstack tool and the front-end software package management tool.
4. The method of claim 2, wherein the management operation is the off-shelf operation, and wherein performing the management operation on the server to be installed using the Saltstack tool after the server to be installed is running comprises:
deleting network access information of the server to be installed, wherein the network access information comprises bastion machine information, monitoring information, virtual machine information, cluster information, setting information of the Saltstack tool and associated information of other servers;
and changing the network information of the server to be installed.
5. A management method of a server is applied to the server, and the method comprises the following steps:
installing an operating system determined by a server management system according to hardware settings of the server and a preset operating protocol, wherein the hardware settings comprise a starting protocol, power supply settings and disk settings, and the operating protocol comprises at least one of a Dynamic Host Configuration Protocol (DHCP) protocol, a simple file transfer protocol (TFTP) protocol and a multi-path MTFTP protocol; the hardware setting is carried out on the server to be installed through an IPMI protocol by a server management system; the server management system is also used for identifying hardware information of the server to be installed through an intelligent platform management interface IPMI protocol, wherein the hardware information comprises hardware configuration information, network information and power state information of the server to be installed;
after the installation of the operating system is completed, a Saltstack tool is registered, so that software configuration and management operation are carried out through the Saltstack tool, the software configuration comprises network IP address setting and/or system user authority setting and/or software installation, and the management operation comprises cluster changing operation and/or off-shelf operation and/or running data updating operation.
6. A management device of a server, applied to a server management system, the device comprising:
the system comprises an information identification module, a power supply state identification module and a power supply state identification module, wherein the information identification module is used for identifying hardware information of a server to be installed through an intelligent platform management interface IPMI protocol, and the hardware information comprises hardware configuration information, network information and power supply state information of the server to be installed;
the hardware setting module is used for carrying out hardware setting on the server to be installed through the IPMI protocol, and the hardware setting comprises a starting protocol, power supply setting and disk setting;
the system determination module is used for determining an operating system of the server to be installed according to the hardware setting and a preset operating protocol, wherein the operating protocol comprises at least one of a Dynamic Host Configuration Protocol (DHCP) protocol, a simple file transfer protocol (TFTP) protocol and a multi-path MTFTP protocol;
the software configuration module is used for performing software configuration on the server to be installed by utilizing a Saltstack tool and a front-end software package management tool after the operating system is installed on the server to be installed, wherein the software configuration comprises network IP address setting and/or system user permission setting and/or software installation;
and the database writing module is used for writing the to-be-installed server and the hardware information which are subjected to software configuration into a configuration management database so as to operate the to-be-installed server.
7. The apparatus of claim 6, further comprising:
the operation management module is used for performing management operation on the server to be installed by utilizing the Saltstack tool after the server to be installed runs;
the management operation comprises cluster changing operation and/or off-shelf operation and/or operation data updating operation.
8. The apparatus of claim 6, wherein the software configuration module comprises:
the downloading submodule is used for controlling the server to be installed to download the corresponding application software package by utilizing the Saltstack tool;
and the configuration submodule is used for configuring the network IP address setting and/or the system user permission setting of the server to be installed by utilizing the Saltstack tool and the front-end software package management tool.
9. The apparatus of claim 7, wherein the management operation is the racking operation, the operation management module comprising:
the deleting submodule is used for deleting network access information of the server to be installed, wherein the network access information comprises bastion machine information, monitoring information, virtual machine information, cluster information, setting information of the Saltstack tool and associated information of other servers;
and the changing submodule is used for changing the network information of the server to be installed.
10. An apparatus for managing a server, the apparatus being applied to the server, the apparatus comprising:
the system installation module is used for installing an operating system determined by a server management system according to hardware settings of the server and a preset operating protocol, wherein the hardware settings comprise a starting protocol, power supply settings and disk settings, and the operating protocol comprises at least one of a Dynamic Host Configuration Protocol (DHCP) protocol, a simple file transfer protocol (TFTP) protocol and a multi-path simple file transfer protocol (MTFTP) protocol;
the tool registration module is used for registering a Saltstack tool after the operating system is installed, so as to perform software configuration and management operation through the Saltstack tool, wherein the software configuration comprises network IP address setting and/or system user authority setting and/or software installation, and the management operation comprises cluster change operation and/or off-shelf operation and/or running data update operation; the hardware setting is carried out on the server to be installed through an IPMI protocol by a server management system; the server management system is further used for identifying hardware information of the server to be installed through an intelligent platform management interface IPMI protocol, and the hardware information comprises hardware configuration information, network information and power state information of the server to be installed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910229607.XA CN110098952B (en) | 2019-03-25 | 2019-03-25 | Server management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910229607.XA CN110098952B (en) | 2019-03-25 | 2019-03-25 | Server management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110098952A CN110098952A (en) | 2019-08-06 |
| CN110098952B true CN110098952B (en) | 2021-08-20 |
Family
ID=67443013
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910229607.XA Active CN110098952B (en) | 2019-03-25 | 2019-03-25 | Server management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110098952B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111224932B (en) * | 2019-10-15 | 2022-01-04 | 平安科技（深圳）有限公司 | User management method and device of server out-of-band management system |
| CN110890979B (en) * | 2019-11-14 | 2023-10-31 | 光通天下网络科技股份有限公司 | Automatic deployment method, device, equipment and medium for fort machine |
| CN111796875A (en) * | 2020-06-29 | 2020-10-20 | 苏州好玩友网络科技有限公司 | Host initialization method, device, system, equipment and storage medium |
| CN112272221B (en) * | 2020-10-19 | 2023-12-22 | 随锐科技集团股份有限公司 | Batch deployment method and system for server cluster and computer readable storage medium |
| CN113014432A (en) * | 2021-02-26 | 2021-06-22 | 山东英信计算机技术有限公司 | Server network configuration device and server network configuration method |
| CN113918230A (en) * | 2021-10-22 | 2022-01-11 | 中国建设银行股份有限公司 | Server configuration method and device |
| CN115134225A (en) * | 2022-06-29 | 2022-09-30 | 济南浪潮数据技术有限公司 | Automatic configuration method and device of server and computer readable storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106855819A (en) * | 2017-01-01 | 2017-06-16 | 国云科技股份有限公司 | A kind of method of automatic deployment operating system |
| CN107229492A (en) * | 2017-05-17 | 2017-10-03 | 东软集团股份有限公司 | Installation method, device, system, storage medium and the equipment of server system |
| CN107294785A (en) * | 2017-07-11 | 2017-10-24 | 上海帝联信息科技股份有限公司 | The automatic deployment method and device, computer-readable recording medium of CDN node service |
| CN107623598A (en) * | 2017-09-25 | 2018-01-23 | 郑州云海信息技术有限公司 | A kind of method of server examining system automatically dispose |
| CN108234172A (en) * | 2016-12-16 | 2018-06-29 | 上海仪电（集团）有限公司中央研究院 | A kind of physical resource automatic deployment system for cloud computing |
| CN109144607A (en) * | 2018-08-06 | 2019-01-04 | 成都知道创宇信息技术有限公司 | A kind of large-scale server automatic deployment and configuration method |
| CN109165024A (en) * | 2018-07-26 | 2019-01-08 | 天讯瑞达通信技术有限公司 | A kind of method of operation platform automatic deployment and monitoring server system |
-
2019
- 2019-03-25 CN CN201910229607.XA patent/CN110098952B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108234172A (en) * | 2016-12-16 | 2018-06-29 | 上海仪电（集团）有限公司中央研究院 | A kind of physical resource automatic deployment system for cloud computing |
| CN106855819A (en) * | 2017-01-01 | 2017-06-16 | 国云科技股份有限公司 | A kind of method of automatic deployment operating system |
| CN107229492A (en) * | 2017-05-17 | 2017-10-03 | 东软集团股份有限公司 | Installation method, device, system, storage medium and the equipment of server system |
| CN107294785A (en) * | 2017-07-11 | 2017-10-24 | 上海帝联信息科技股份有限公司 | The automatic deployment method and device, computer-readable recording medium of CDN node service |
| CN107623598A (en) * | 2017-09-25 | 2018-01-23 | 郑州云海信息技术有限公司 | A kind of method of server examining system automatically dispose |
| CN109165024A (en) * | 2018-07-26 | 2019-01-08 | 天讯瑞达通信技术有限公司 | A kind of method of operation platform automatic deployment and monitoring server system |
| CN109144607A (en) * | 2018-08-06 | 2019-01-04 | 成都知道创宇信息技术有限公司 | A kind of large-scale server automatic deployment and configuration method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110098952A (en) | 2019-08-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110098952B (en) | Server management method and device | |
| WO2021217871A1 (en) | Method and apparatus for deploying micro service cluster, computer device and storage medium | |
| CN109814879B (en) | Automatic CI/CD project deployment method and storage medium | |
| US20210314223A1 (en) | Managing Virtual Network Functions | |
| US20210406079A1 (en) | Persistent Non-Homogeneous Worker Pools | |
| US9465625B2 (en) | Provisioning of operating environments on a server in a networked environment | |
| KR101574366B1 (en) | Synchronizing virtual machine and application life cycles | |
| TWI411958B (en) | Creating templates of offline resources | |
| US8819202B1 (en) | Service configuration and deployment engine for provisioning automation | |
| US20040015957A1 (en) | Method to map an inventory management system to a configuration management system | |
| US20070118654A1 (en) | Method and apparatus for provisioning heterogeneous operating systems onto heterogeneous hardware systems | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| CN104360878A (en) | Method and device for deploying application software | |
| US10797952B1 (en) | Intelligent rollback analysis of configuration changes | |
| US20120005325A1 (en) | Systems and methods for automated processing of devices | |
| US9037843B2 (en) | Managing a target computing device | |
| US20220269494A1 (en) | Provisioning bare metal machines with a complex software product | |
| JP2016207184A (en) | Methods of updating firmware components, computer systems, and memory device | |
| US10291466B2 (en) | Computing infrastructure provisioning | |
| CN115292026A (en) | Management method, device and equipment of container cluster and computer readable storage medium | |
| US20220237090A1 (en) | Autonomous organization and role selection of homogenous workers | |
| US11750451B2 (en) | Batch manager for complex workflows | |
| CN115357198B (en) | Mounting method and device of storage volume, storage medium and electronic equipment | |
| CN107659621B (en) | RAID control card configuration method and device | |
| US11425203B2 (en) | Commissioning a virtualized network function |
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 |