CN108733398B - Software upgrading processing method and device - Google Patents
Software upgrading processing method and device Download PDFInfo
- Publication number
- CN108733398B CN108733398B CN201810461312.0A CN201810461312A CN108733398B CN 108733398 B CN108733398 B CN 108733398B CN 201810461312 A CN201810461312 A CN 201810461312A CN 108733398 B CN108733398 B CN 108733398B
- Authority
- CN
- China
- Prior art keywords
- server
- software
- yum
- network card
- preset software
- 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
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/654—Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a processing method and a device for software upgrading, wherein the method comprises the following steps: when a network card is detected to be inserted into a first server, acquiring version information of preset software from the network card; when the preset software of the target version is determined to be installed in the first server, determining a pointing relationship; the pointing relation represents the position of the installation package of the preset software of the target version in the network card pointed by the Yum tool; and running a Yum tool to install the preset software of the target version into the operating system of the first server based on a channel between a main Board Management Controller (BMC) and the operating system.
Description
Technical Field
The invention relates to the technical field of software, in particular to a method and a device for processing software upgrading.
Background
At present, when a network card in a Server (Server) needs to upgrade software such as a driver (driver) or a firmware (firmware), a corresponding installation file is usually copied to an operating system for installation, and the installation file can also be installed through a specially developed tool responsible for software upgrading.
Disclosure of Invention
In view of the above, the present invention is to provide a method and an apparatus for processing software upgrade, which simplify the operation of upgrading the installed software, and thus are beneficial to improving the maintainability of the software.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the embodiment of the application provides a processing method for software upgrading, which comprises the following steps:
when a network card is detected to be inserted into a first server, acquiring version information of preset software from the network card;
when the preset software of the target version is determined to be installed in the first server, determining a pointing relationship; the pointing relation represents the position of the installation package of the preset software of the target version in the network card pointed by the Yum tool;
and running a Yum tool to install the preset software of the target version into the operating system of the first server based on a channel between a Baseboard Management Controller (BMC) and the operating system.
In the foregoing scheme, optionally, the acquiring version information of the preset software from the network card includes:
acquiring version information of preset software from the network card through BMC; the network card stores version information of at least one preset software.
In the foregoing solution, optionally, when it is determined that the preset software of the target version is installed in the first server, determining the pointing relationship includes:
when it is determined to update the preset software installed in the first server, or
And when the first server is determined not to be installed with preset software and the preset software is preinstalled, determining the orientation relation.
In the foregoing solution, optionally, the determining the orientation relationship includes:
and configuring a local Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired from the network card by the Yum tool exists in the local Yum source configuration file.
In the foregoing solution, optionally, the determining the orientation relationship includes:
and configuring a network Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired by the Yum tool from the network card or the network card inserted into other servers exists in the network Yum source configuration file.
In the foregoing scheme, optionally, before configuring the network Yum source configuration file in the BMC, the method further includes:
obtaining a local Yum source configuration file of at least one other server networked with the first server;
and synthesizing the local Yum source configuration file of the first server and the local Yum source configuration file of the at least one other server into a network Yum source configuration file.
An embodiment of the present application provides a processing apparatus for software upgrade, where the processing apparatus includes:
a memory for storing a local Yum source configuration file;
the processor is used for acquiring version information of preset software from the network card when the network card is detected to be inserted into the first server; when the preset software of the target version is determined to be installed in the first server, determining a pointing relationship; the pointing relation represents the position of the installation package of the preset software of the target version in the network card pointed by the Yum tool; and running a Yum tool to install the preset software of the target version into the operating system of the first server based on the channel between the BMC and the operating system.
In the foregoing scheme, optionally, the processor is further configured to:
acquiring version information of preset software from the network card through BMC; the network card stores version information of at least one preset software.
In the foregoing scheme, optionally, the processor is further configured to:
when it is determined to update the preset software installed in the first server, or
And when the first server is determined not to be installed with preset software and the preset software is preinstalled, determining the orientation relation.
In the foregoing scheme, optionally, the processor is further configured to:
and configuring a local Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired from the network card by the Yum tool exists in the local Yum source configuration file.
In the foregoing scheme, optionally, the processor is further configured to:
and configuring a network Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired by the Yum tool from the network card or the network card inserted into other servers exists in the network Yum source configuration file.
In the foregoing scheme, optionally, the processor is further configured to: before configuring a network Yum source configuration file in a BMC, acquiring a local Yum source configuration file of at least one other server networked with the first server; and synthesizing the local Yum source configuration file of the first server and the local Yum source configuration file of the at least one other server into a network Yum source configuration file.
The embodiment of the present application further provides a computer storage medium, where a computer-executable instruction is stored in the computer storage medium, and the computer-executable instruction is used to execute the processing method for software upgrade described in the embodiment of the present application.
By adopting the technical scheme of the embodiment of the application, when the network card is detected to be inserted into the first server, the version information of the preset software is obtained from the network card; when the preset software of the target version is determined to be installed in the first server, determining a pointing relationship; the pointing relation represents the position of the installation package of the preset software of the target version in the network card pointed by the Yum tool; and running the YUM tool to install the preset software of the target version into the operating system of the first server based on the channel between the BMC and the operating system, and thus, running the YUM tool to install the preset software of the target version based on the determined orientation relation simplifies the operation of upgrading the installed software, thereby being beneficial to improving the maintainability of the software.
Drawings
Fig. 1 is a schematic implementation flow diagram of a processing method for software upgrade provided in an embodiment of the present application;
FIG. 2 is a schematic diagram illustrating an association between an operating system, a BMC, and an adapter according to an embodiment of the present disclosure;
fig. 3 is a schematic diagram of an implementation flow of a processing method for software upgrade based on a local Yum source according to an embodiment of the present application;
fig. 4 is a schematic view of an implementation flow of a processing method for software upgrade based on a network Yum source according to an embodiment of the present application;
fig. 5 is a first schematic structural diagram of a processing device for software upgrade according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a processing device for software upgrade according to an embodiment of the present application.
Detailed Description
So that the manner in which the features and aspects of the present application can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings.
In the following embodiments of the software upgrade processing method and apparatus provided in the present application, the network card may be a board card or other device that can be plugged into or pulled out from a server.
The technical solution of the present application is further elaborated below with reference to the drawings and the specific embodiments.
Example one
The present embodiment provides a processing method for software upgrade, as shown in fig. 1, the processing method for software upgrade mainly includes the following steps:
step 101: and when the network card is detected to be inserted into the first server, acquiring the version information of the preset software from the network card.
In this embodiment, the network card may be understood as a pluggable network card.
That is, the network card can be inserted into a server network card slot or a network card slot, and can also be pulled out from the server.
Here, the network card stores software-related information of preset software, where the software-related information includes a version information file, an installation file, a dependency relationship file, and the like. Generally, the network card stores the rpm package and version information file of preset software such as driver/firmware.
Specifically, at least 2 independent files are stored in the network card, one is an installation file, and the other is version information, for example, the version information file can represent description information of rpm name and version number.
It should be noted that the dependency relationship file may exist in an independent file form, and may also be embedded in an installation file or a version information file.
Wherein, the dependency relationship can be understood as: to upgrade a, B must be upgraded first, and this dependency exists in the flash memory (flash) of the network card.
Illustratively, the software relevant information of the software is stored in the network card when the software is shipped out. Therefore, for the server, if the software installed on the server is required to be updated, the updating operation can be completed according to the information stored in the network card; if the software is not installed on the server, the initial installation operation can be completed according to the information stored in the network card.
In some optional embodiments, the obtaining of the version information of the preset software from the network card includes:
acquiring version information of preset software from the network card through a BMC in a first server; the network card stores version information of at least one preset software.
Here, a server typically has only one BMC.
Illustratively, the network card may store m versions of the software a, and the BMC may know the latest version of the software a in the m versions by analyzing the version information, and may determine whether the software a is currently installed in the first server and whether the installed version of the software a is the latest version.
Step 102: when the preset software of the target version is determined to be installed in the first server, determining a pointing relationship; and the pointing relation representation Yum tool points to the position of the installation package of the preset software of the target version in the network card.
Thus, due to the determined pointing relationship, subsequent running of the Yum tool to install the target version of the pre-set software is facilitated.
Here, the determining whether the target version of the preset software is installed in the first server includes:
acquiring version information of installed software in the first server;
and determining whether the target version of the preset software is installed in the first server or not according to the version information of the preset software acquired from the network card and the acquired version information of the installed software.
That is to say, the BMC in the server may automatically detect the network card inserted into the first server, and analyze the network card to determine whether the target version of the preset software is installed in the first server.
Of course, when the BMC analysis indicates that the target version of the preset software needs to be installed in the first server, it may also be determined whether the target version of the preset software needs to be installed in the first server and/or which version of the preset software needs to be specifically installed according to a user instruction. In this way, the user can have more control initiative and option, rather than being solely decided by the server.
In some optional embodiments, when it is determined that the target version of the pre-set software is installed in the first server, determining the orientation relationship includes:
and when the preset software installed in the first server is determined to be updated, determining the orientation relation.
In some optional embodiments, when it is determined that the target version of the pre-set software is installed in the first server, determining the orientation relationship includes:
and when the first server is determined not to be installed with preset software and the preset software is preinstalled, determining the orientation relation.
In some optional embodiments, the determining the directional relationship includes:
and configuring a local Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired from the network card by the Yum tool exists in the local Yum source configuration file.
Therefore, the installation or the update of the preset software is realized based on the installation mode of the local Yum source.
In some optional embodiments, the determining the directional relationship includes:
and configuring a network Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired by the Yum tool from the network card or the network card inserted into other servers exists in the network Yum source configuration file.
Optionally, before configuring the network Yum source configuration file in the BMC, the method further includes:
obtaining a local Yum source configuration file of at least one other server networked with the first server;
and synthesizing the local Yum source configuration file of the first server and the local Yum source configuration file of the at least one other server into a network Yum source configuration file.
Therefore, the installation or the update of the preset software is realized based on the installation mode of the network Yum source.
Step 103: and running a Yum tool to install the preset software of the target version into the operating system of the first server based on the channel between the BMC and the operating system.
Here, Yum (collectively called Yellow dog update) is a Shell front-end software package manager in Fedora and RedHat and CentOS. Based on the rpm package management, the rpm package can be automatically downloaded from a designated server and installed, dependency relationships can be automatically processed, and all dependent software packages can be installed at one time without the need for tedious downloading and installing at one time.
Fig. 2 shows a schematic diagram of association between an operating system, a BMC and an adapter, and as shown in fig. 2, the BMC in a server builds local and network Yum source configurations based on HTTP, and stores installation files (such as rpm installation packages) of preset software (such as driver and firmware) in a network card. Yum source can point to driver rpm package/firmware rpm package on the network card. Thus, Yum mode installation of preset software (such as driver and firmware) can be performed in the operating system based on channels of the BMC. Specifically, an Operating System (OS) obtains Yum source configuration from the BMC through a channel between the BMC and the OS, and because there is a pointing relationship in the configuration, the OS obtains an rpm packet from the network card according to the pointing relationship. Therefore, the corresponding installation files do not need to be copied to the operating system for installation, and the operation of upgrading the installed software is simplified. And the RPM found adapter in the BMC is used for finding an RPM packet, and if the RPM packet is found in the newly inserted network card, the YUm source configuration in the BMC is updated. In the operating system, a local Yum source can be used, and a network Yum source can also be used for realizing the installation of software through a BMC channel.
In this embodiment, when a network card is detected to be inserted into a first server, acquiring version information of preset software from the network card; when the preset software of the target version is determined to be installed in the first server, determining a pointing relationship; the pointing relation represents the position of the installation package of the preset software of the target version in the network card pointed by the Yum tool; and running the YUM tool to install the preset software of the target version in the operating system of the first server based on the channel between the BMC and the operating system, and thus, running the YUM tool to install the preset software of the target version based on the determined orientation relation, so that a corresponding installation file does not need to be copied to the operating system for installation, and the operation of upgrading the installed software is simplified. In addition, as long as one network card is provided with the preset software with the latest version, yum-mode updating of the latest software versions of all network cards in the same subnet of the data center can be realized, so that the maintainability of the software is improved.
Example two
This embodiment provides a processing method for software upgrade based on a local Yum source, as shown in fig. 3, the processing method for software upgrade based on a local Yum source mainly includes the following steps:
step 301: when the preset software leaves a factory, a network card is used as a carrier, and the software related information of the preset software is stored in the network card.
That is, the default software is put into the network card or the flash memory when leaving the factory.
For example, the rpm package and dependency relationship of driver/firmware are stored in the flash (flash) of the network card.
Step 302: the network card is inserted into the server, and the BMC in the server automatically identifies the version information of the preset software in the network card.
That is to say, the BMC in the server can detect whether a network card is inserted, and can recognize the version information of the preset software in the network card.
Step 303: and configuring a local Yum source configuration file in the BMC so that the local Yum source configuration file in the BMC points to the rpm packet in the network card.
That is to say, configuration information used for representing the pointing relationship of the position of the installation package of the preset software acquired from the network card by the Yum tool exists in the configured local Yum source configuration file.
Specifically, the http service is started by default in the BMC, and the Yum source is configured in the BMC. The default YUM source is a local source and points to a storage position of a default version of the network card detected in a network card slot (pci slot);
in some optional embodiments, before step 303, the method further comprises:
determining whether a target version of pre-set software is installed in the server.
Step 304: in the operating system, a Yum tool is run through a BMC channel to install preset software into the operating system of the server.
Here, the BMC channel refers to a channel between the BMC and the operating system.
For example, when detecting that a network card is inserted into the server 1, the BMC acquires version information of the driver/firmware from the network card, and determines whether the driver/firmware of the target version in the network card is installed in the server based on the known version information of the driver/firmware installed on the current server, and when determining that the driver/firmware is installed, configures a local Yum source configuration file in the BMC so that the local Yum source configuration file in the BMC points to an rpm package of the driver/firmware in the network card, and runs a Yum tool through a BMC channel to install the driver/firmware of the target version into an operating system of the server.
Therefore, the installation or the update of the preset software is realized based on the installation mode of the local Yum source. Therefore, the corresponding installation files do not need to be copied to the operating system for installation, and the operation of upgrading the installed software is simplified.
EXAMPLE III
This embodiment provides a processing method for software upgrade based on a network Yum source, as shown in fig. 4, the processing method for software upgrade based on a network Yum source mainly includes the following steps:
step 401: when the preset software leaves a factory, a network card is used as a carrier, and the software related information of the preset software is stored in the network card.
That is, the default software is put into the network card or the flash memory when leaving the factory.
For example, rpm package and dependency of driver/firmware are stored in a flash memory (flash) of the network card.
Step 402: the network card is inserted into the first server, and the BMC in the first server automatically identifies the version information of the preset software in the network card.
That is to say, the BMC in the first server may detect whether a network card is inserted, and may recognize version information of the preset software in the network card.
Step 403: the BMC in the first server judges whether the installation mode of the network Yum source is used, if so, the step 404 is executed; if not (not shown in the figure), the flow ends.
Here, the network Yum source is not used, and two situations are distinguished, namely, whether the resource can be used or not is judged; the second is that the other server has new resources, but the first server does not want to use.
Step 404: configuring the network ground Yum source configuration file in the BMC so that the network ground Yum source configuration file in the BMC points to the rpm packet in the network card, and then executing step 405.
Wherein, the configuring network ground Yum source configuration file in BMC includes:
obtaining a local Yum source configuration file of at least one other server networked with a first server;
and synthesizing the local Yum source configuration file of the first server and the local Yum source configuration file of the at least one other server into a network Yum source configuration file.
That is, one server may add or automatically identify a BMC configured Yum source on other servers of the same subnet, while the Yum source on the other servers is a network source with respect to the server.
In this way, by analyzing each version of the preset software in the network Yum source configuration file, the latest version can be determined, thereby facilitating upgrading of the preset software based on the latest version.
Here, the configured network Yum source configuration file has configuration information for representing a pointing relationship of a position where the Yum tool acquires the installation package of the preset software from the network card.
Step 405: in the operating system, a Yum tool is run through a BMC channel to install preset software into the operating system of the first server.
Here, the BMC channel refers to a channel between the BMC and the operating system.
For example, a network card storing a formally released version (GA) is inserted into the server 2, the BMC of server 1 obtains driver/firmware version information in the configuration file from servers 2, 3, 4, namely representing information such as rpm name and version number of driver/firmware, synthesizing a network YUM source configuration file, the network Yum source profile comprises at least the version numbers of these 4 servers, so that it can be analyzed who is the latest version, i.e., knowing that the network card inserted into the server 2 has the latest version, when the BMC of the server 1 determines the installation mode using the network Yum source, configuring configuration information of rpm package pointing to driver/firmware in network card of server 2 by network Yum source configuration file synthesized by BMC of server 1, and running a Yum tool through a BMC channel of the server 1 to install the driver/firmware of the target version into an operating system of the server 1.
That is, assuming that there are 4 servers to be upgraded, and the servers 1, 2, 3, and 4 are networked, when the network card G (the configuration file G containing the latest rpm packet) is inserted into the server 1, the servers 2, 3, and 4 acquire the configuration file G locally, and can know that there is a new network card inserted into the server 1.
Therefore, the latest firmware version is put into the pluggable network card, and when the pluggable network card is plugged into the server, a Yum tool can be used, wherein the Yum tool belongs to the self-contained operating system. Thus, at least the following advantages are achieved: firstly, the RPM file is not copied; second, tools to upgrade firmware, such as associative onecli, need not be developed.
Therefore, the installation or the update of the preset software is realized based on the installation mode of the network Yum source. Therefore, the corresponding installation files do not need to be copied to the operating system for installation, and the operation of upgrading the installed software is simplified.
The processing method for software upgrading can realize the separation of software version storage and YUM/HTTP service. The network card only needs to store installable files (such as rpm packets) of driver and firmware, and the configuration of the Yum source and the HTTP service are realized inside the BMC. Since HTTP services will typically turn on by default at the BMC. All that needs to be done for this application is to configure the Yum source. Thus, each time a network card is sold, no matter who, the network card can be used after being plugged into the server. The server only needs two operations, the Yum configuration file is updated in the network card, and the function of searching for upgrading is added in the BMC; the key point is that the rpm version is put on the network card, and the file can be installed in a YUm mode.
In addition, Yum sources support local and network sources. The local source is in default configuration, and the local source exists in the network card with version. The local source is configured to add the RPM source to the local source for subsequent use whenever a network card supporting the function is found by scanning at power-on. For the network source, the configuration of the network source can be realized by discovering the local source configuration in other BMCs in the subnet and copying the local source configuration to the Yum configuration file of the BMC of the server.
Because the Yum mode is used, the advantage of Yum can be utilized to update a specific version (generally, the latest version); and the addressing of dependency relationships can be implemented automatically.
Example four
An embodiment of the present application provides a processing apparatus for software upgrade, as shown in fig. 5, the processing apparatus includes:
a memory 10 for storing a local Yum source configuration file;
the processor 20 is configured to, when it is detected that a network card is inserted into the first server, obtain version information of the preset software from the network card; when the preset software of the target version is determined to be installed in the first server, determining a pointing relationship; the pointing relation represents the position of the installation package of the preset software of the target version in the network card pointed by the Yum tool; and running a Yum tool to install the preset software of the target version into the operating system of the first server based on a channel between the mainboard management controller BMC and the operating system.
As an embodiment, the processor 20 is further configured to:
acquiring version information of preset software from the network card through BMC; the network card stores version information of at least one preset software.
As an embodiment, the processor 20 is further configured to:
when it is determined to update the preset software installed in the first server, or
And when the first server is determined not to be installed with preset software and the preset software is preinstalled, determining the orientation relation.
As an embodiment, the processor 20 is further configured to:
and configuring a local Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired from the network card by the Yum tool exists in the local Yum source configuration file.
As an embodiment, the processor 20 is further configured to:
and configuring a network Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired by the Yum tool from the network card or the network card inserted into other servers exists in the network Yum source configuration file.
As an embodiment, the processor 20 is further configured to: before configuring a network Yum source configuration file in a BMC, acquiring a local Yum source configuration file of at least one other server networked with the first server; and synthesizing the local Yum source configuration file of the first server and the local Yum source configuration file of the at least one other server into a network Yum source configuration file.
It should be noted that: it should be understood by those skilled in the art that the functions of each device in the processing apparatus for software upgrade of the present embodiment may be understood by referring to the description of the processing method applied to the software upgrade at the server side in the embodiment, and are not described herein again.
In the processing device for software upgrading, the Yum tool is operated to install the preset software of the target version based on the determined orientation relation, so that the corresponding installation files do not need to be copied to the operating system for installation, and the operation of upgrading the installed software is simplified. In addition, as long as one network card is provided with the preset software with the latest version, the Yum mode updating of the latest software version of all network cards in the same subnet of the data center can be realized, so that the maintainability of the software is improved.
EXAMPLE five
The present embodiment provides a processing apparatus for software upgrade, as shown in fig. 6, the apparatus includes:
the acquiring unit 61 is configured to acquire version information of the preset software from the network card when it is detected that the network card is inserted into the first server;
a determining unit 62, configured to determine a pointing relationship when it is determined that the target version of the preset software is installed in the first server; the pointing relation represents the position of the installation package of the preset software of the target version in the network card pointed by the Yum tool;
and the processing unit 63 is configured to run a Yum tool to install the preset software of the target version in the operating system of the first server based on a channel between the motherboard management controller BMC and the operating system.
As an embodiment, the obtaining unit 61 is further configured to:
acquiring version information of preset software from the network card through BMC; the network card stores version information of at least one preset software.
As an embodiment, the determining unit 62 is further configured to:
when it is determined to update the preset software installed in the first server, or
And when the first server is determined not to be installed with preset software and the preset software is preinstalled, determining the orientation relation.
As an embodiment, the determining unit 62 is further configured to:
and configuring a local Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired from the network card by the Yum tool exists in the local Yum source configuration file.
As an embodiment, the determining unit 62 is further configured to:
and configuring a network Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired by the Yum tool from the network card or the network card inserted into other servers exists in the network Yum source configuration file.
As an embodiment, the determining unit 62 is further configured to: before configuring a network Yum source configuration file in a BMC, acquiring a local Yum source configuration file of at least one other server networked with the first server; and synthesizing the local Yum source configuration file of the first server and the local Yum source configuration file of the at least one other server into a network Yum source configuration file.
It should be noted that: in the processing apparatus for software upgrade provided in the above embodiment, only the division of each program module is exemplified when performing the processing of software upgrade, and in practical applications, the processing may be distributed to different program modules according to needs, that is, the internal structure of the server is divided into different program modules to complete all or part of the processing described above. In addition, the processing apparatus for software upgrade and the processing method for software upgrade provided in the foregoing embodiments belong to the same concept, and specific implementation processes thereof are described in detail in the method embodiments and are not described herein again.
In this embodiment, the obtaining Unit 61, the determining Unit 62, and the Processing Unit 63 in the Processing apparatus for software upgrade may be implemented by a Central Processing Unit (CPU) of the Processing apparatus for software upgrade or a Central Processing Unit (DSP), a Micro Control Unit (MCU) or a Programmable Gate Array (FPGA) in a server where the Processing apparatus for software upgrade is located in actual application.
In the processing device for software upgrading, the Yum tool is operated to install the preset software of the target version based on the determined orientation relation, so that the corresponding installation files do not need to be copied to the operating system for installation, and the operation of upgrading the installed software is simplified. In addition, as long as one network card is provided with the preset software with the latest version, yum-mode updating of the latest software versions of all network cards in the same subnet of the data center can be realized, so that the maintainability of the software is improved.
Example eight
The present embodiment provides a computer storage medium, on which computer instructions are stored, wherein the computer instructions are executable by a processor of a server to perform the steps of the method applied to the server side.
The present embodiments provide a computer storage medium having stored thereon computer instructions that, when executed by a processor, implement: when a network card is detected to be inserted into a first server, acquiring version information of preset software from the network card; when the preset software of the target version is determined to be installed in the first server, determining a pointing relationship; the pointing relation represents the position of the installation package of the preset software of the target version in the network card pointed by the Yum tool; and running a Yum tool to install the preset software of the target version into the operating system of the first server based on the channel between the BMC and the operating system.
Those skilled in the art should understand that the functions of each program in the computer storage medium of this embodiment can be understood by referring to the related description of the processing method for software upgrade described in the foregoing embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed server and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Alternatively, the integrated units described above in the present application may be stored in a computer-readable storage medium if they are implemented in the form of software functional modules and sold or used as independent products. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or portions thereof contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a removable storage device, a ROM, a RAM, a magnetic or optical disk, or various other media that can store program code.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (7)
1. A method for processing a software upgrade, the method comprising:
when a network card is detected to be inserted into a first server, acquiring version information of preset software from the network card through a mainboard management controller BMC in the first server; the network card stores version information of at least one preset software;
determining whether the preset software of the target version is installed in the first server or not according to the version information of the preset software and the version information of the installed software in the first server;
when the preset software installed in the first server is determined to be updated, or when the preset software is determined not to be installed in the first server and is preinstalled, determining a direction relationship; the pointing relation represents the position of the installation package of the preset software of the target version in the network card pointed by the Yum tool;
and running a Yum tool to install the preset software of the target version into the operating system of the first server based on the channel between the BMC and the operating system.
2. The method for processing software upgrade according to claim 1, wherein the determining a pointing relationship comprises:
and configuring a local Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired from the network card by the Yum tool exists in the local Yum source configuration file.
3. The method for processing software upgrade according to claim 1, wherein the determining a pointing relationship comprises:
and configuring a network Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired by the Yum tool from the network card or the network card inserted into other servers exists in the network Yum source configuration file.
4. The method of claim 3, wherein before configuring the network Yum source configuration file in the BMC, the method further comprises:
obtaining a local Yum source configuration file of at least one other server networked with the first server;
and synthesizing the local Yum source configuration file of the first server and the local Yum source configuration file of the at least one other server into a network Yum source configuration file.
5. A processing device for software upgrades, the processing device comprising:
a memory for storing a local Yum source configuration file;
the system comprises a processor, a first server and a second server, wherein the processor is used for acquiring version information of preset software from a network card through a mainboard management controller BMC in the first server when the network card is detected to be inserted into the first server; the network card stores version information of at least one preset software; determining whether the preset software of the target version is installed in the first server or not according to the version information of the preset software and the version information of the installed software in the first server; when the preset software installed in the first server is determined to be updated, or when the preset software is determined not to be installed in the first server and is preinstalled, determining a direction relationship; the pointing relation represents the position of the installation package of the preset software of the target version in the network card pointed by the Yum tool; and running a Yum tool to install the preset software of the target version into the operating system of the first server based on the channel between the BMC and the operating system.
6. The software upgrade processing device according to claim 5, wherein said processor is further configured to:
and configuring a local Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired from the network card by the Yum tool exists in the local Yum source configuration file.
7. The software upgrade processing device according to claim 5, wherein said processor is further configured to:
and configuring a network Yum source configuration file in the BMC so that configuration information for representing the pointing relationship of the position of the installation package of the preset software acquired by the Yum tool from the network card or the network card inserted into other servers exists in the network Yum source configuration file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810461312.0A CN108733398B (en) | 2018-05-15 | 2018-05-15 | Software upgrading processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810461312.0A CN108733398B (en) | 2018-05-15 | 2018-05-15 | Software upgrading processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108733398A CN108733398A (en) | 2018-11-02 |
| CN108733398B true CN108733398B (en) | 2021-06-15 |
Family
ID=63937553
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810461312.0A Active CN108733398B (en) | 2018-05-15 | 2018-05-15 | Software upgrading processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108733398B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109542467A (en) * | 2018-11-20 | 2019-03-29 | 郑州云海信息技术有限公司 | The configuration method in the source yum under a kind of linux system |
| CN110286860B (en) * | 2019-06-28 | 2021-06-15 | 联想(北京)有限公司 | Information processing method, information processing system and electronic device |
| TWI799035B (en) * | 2021-12-29 | 2023-04-11 | 威聯通科技股份有限公司 | System updating method and electronic apparatus |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102789388A (en) * | 2012-06-14 | 2012-11-21 | 曙光信息产业(北京)有限公司 | Method and system for adding network card function to MIPS frame server based on BMC |
| CN103713924A (en) * | 2013-12-24 | 2014-04-09 | 汉柏科技有限公司 | Upgrading method and system of cloud computing platform services |
| CN105183528A (en) * | 2015-10-29 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | Server bios upgrading method and system |
| CN106130750A (en) * | 2016-09-29 | 2016-11-16 | 安徽四创电子股份有限公司 | A kind of big data platform upgrade method based on privately owned Yum storehouse |
-
2018
- 2018-05-15 CN CN201810461312.0A patent/CN108733398B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102789388A (en) * | 2012-06-14 | 2012-11-21 | 曙光信息产业(北京)有限公司 | Method and system for adding network card function to MIPS frame server based on BMC |
| CN103713924A (en) * | 2013-12-24 | 2014-04-09 | 汉柏科技有限公司 | Upgrading method and system of cloud computing platform services |
| CN105183528A (en) * | 2015-10-29 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | Server bios upgrading method and system |
| CN106130750A (en) * | 2016-09-29 | 2016-11-16 | 安徽四创电子股份有限公司 | A kind of big data platform upgrade method based on privately owned Yum storehouse |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108733398A (en) | 2018-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9081747B1 (en) | Computer program deployment to one or more target devices | |
| US11599348B2 (en) | Container image building using shared resources | |
| EP3317762B1 (en) | Methods and apparatus for software lifecycle management of a virtual computing environment | |
| US9146729B2 (en) | Deployment and updating of applications and drivers on a client device using an extensible markup language (XML) configuration file | |
| EP2786279B1 (en) | Deployment of a driver or an application on a client device having a write-filter | |
| US7743242B2 (en) | Method and system for automatic generation of operating system boot images | |
| EP2786249B1 (en) | Creation or installation of a disk image for a target device having one of a plurality of hardware platforms | |
| US8291402B2 (en) | Using system fingerprints to accelerate package dependency resolution | |
| CN106911729B (en) | Remote installation method of operating system suitable for domestic processor | |
| US8402123B2 (en) | Systems and methods for inventorying un-provisioned systems in a software provisioning environment | |
| US9092286B2 (en) | System to automatically process components on a device | |
| US20130254759A1 (en) | Installing an operating system in a host system | |
| CN108733398B (en) | Software upgrading processing method and device | |
| WO2013081679A1 (en) | Automatic updating of an application or a driver on a client device using a deployment configuration file | |
| CN111475172B (en) | Bare metal deployment method and device | |
| CN105335195A (en) | Device driver upgrading method and device and electronic device | |
| Cisco | Installing the EISA PC Adapter NetWare Driver | |
| CN111324384B (en) | Device and method for selecting starting image file according to device message in pre-execution environment | |
| CN116541104B (en) | Program management method, control device, platform, device, and storage medium | |
| CN111240752B (en) | Operating system self-adaption method and system | |
| US20200073678A1 (en) | Systems and methods for operating system deployment | |
| KR20220043293A (en) | Method and apparatus for automatically installing operating system in an environment of network | |
| CN117453234A (en) | Deployment method and device of big data cluster and service system |
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 |