CN119597310A - System environment deployment method and electronic equipment - Google Patents
System environment deployment method and electronic equipment Download PDFInfo
- Publication number
- CN119597310A CN119597310A CN202411657497.4A CN202411657497A CN119597310A CN 119597310 A CN119597310 A CN 119597310A CN 202411657497 A CN202411657497 A CN 202411657497A CN 119597310 A CN119597310 A CN 119597310A
- Authority
- CN
- China
- Prior art keywords
- information
- fru
- test tool
- target
- target component
- 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.)
- Pending
Links
Landscapes
- Stored Programmes (AREA)
Abstract
本发明公开了一种系统环境部署方法及电子设备。用于实现定制化操作系统环境的自动化部署，提高部署效率，节省人力成本。该方法包括：利用BMC获取FRU信息，根据FRU信息确定OS信息，并安装所述OS信息对应的OS；根据所述FRU信息获取所述OS对应的目标部件；将所述OS下的待更新部件更新为所述目标部件。
The present invention discloses a system environment deployment method and electronic device. The method is used to realize the automated deployment of a customized operating system environment, improve the deployment efficiency, and save labor costs. The method comprises: obtaining FRU information using BMC, determining OS information according to the FRU information, and installing the OS corresponding to the OS information; obtaining the target component corresponding to the OS according to the FRU information; and updating the component to be updated under the OS to the target component.
Description
Technical Field
The present invention relates to the field of computer software technologies, and in particular, to a system environment deployment method and an electronic device.
Background
Most of the current system environment deployment methods are deployed aiming at the system environment of a general operating system, but the general operating system cannot meet the customized system requirements, cannot adapt to the customized system and cannot deploy test environments aiming at the customized system. The general purpose operating system is also not associated with Firmware (FW) versions, driver versions, test tool versions, etc.
In the current system environment deployment process, a corresponding execution operating system (executive operating system, OS) is usually installed, after the OS is installed, components such as FW and drivers need to be manually updated, manual intervention is needed, and complete automatic deployment is not realized.
When the requirement of the customized OS system environment deployment is met, the specific FW, the driver, the testing tool and other components cannot be automatically adapted according to the customized OS, and the automatic deployment of the customized operating system environment cannot be realized.
Disclosure of Invention
The invention provides a system environment deployment method and electronic equipment, which are used for realizing automatic deployment of a customized operating system environment, improving deployment efficiency and saving labor cost.
In a first aspect, a system environment deployment method provided by an embodiment of the present invention includes:
acquiring FRU information by using a BMC, determining OS information according to the FRU information, and installing an OS corresponding to the OS information;
Acquiring a target component corresponding to the OS according to the FRU information;
and updating the part to be updated under the OS to the target part.
In the embodiment, by establishing the association between the OS and the target component, the corresponding target component is acquired and automatically updated after the OS is automatically installed. The full-automatic deployment of the system environment is realized, the deployment efficiency is improved, and the labor cost is saved.
As an alternative embodiment, the method further comprises:
and acquiring a testing tool corresponding to the OS according to the FRU information, and installing the testing tool.
According to the embodiment, through the association relation between the OS and the test tools, after the OS is installed, the corresponding test tools are determined from FRU information, and the test tools are automatically installed, so that automatic deployment and installation of the test tools based on a customized system are realized, the method is suitable for automatic installation of the test tools of any operating system, and the deployment efficiency and universality of the test tools are improved.
As an alternative embodiment, after the test tool is installed, the method further comprises:
Debugging the test tool, and judging whether the test tool is abnormal according to a debugging result;
and if the testing tool is abnormal, outputting abnormal information.
After the test tool is automatically installed, the test tool can be debugged and verified, whether the test tool is abnormal or not is checked, a more comprehensive installation and debugging function is provided, and the usability of the test tool is automatically detected.
As an optional implementation manner, the determining OS information according to FRU information and installing an OS corresponding to the OS information includes:
Determining OS information according to the first field of FRU information;
and acquiring the OS corresponding to the OS information from the PXE resource pool, and installing the OS.
According to the method and the device, the general or customized OS can be obtained from the PXE resource pool and installed, and the method and the device enable the OS of a required type to be obtained from one resource pool when different operating systems are installed in a mode that different operating systems are stored in the PXE resource pool, so that the OS is automatically installed, and universality of operating system deployment are improved.
As an optional implementation manner, the acquiring, according to the FRU information, the target component corresponding to the OS includes:
determining target component information according to the second field of the FRU information;
and acquiring the target component corresponding to the target component information from a remote warehouse.
According to the embodiment, the target components such as the firmware or the driver can be obtained from the remote warehouse, automatic installation can be carried out on different target components, and universality of automatic deployment of the firmware or the driver are improved.
As an optional implementation manner, the acquiring, according to the FRU information, a test tool corresponding to the OS includes:
determining test tool information according to the third field of the FRU information;
and acquiring the testing tool corresponding to the testing tool information from a remote warehouse.
According to the method, the device and the system, the test tools can be automatically installed and deployed aiming at different test tools in a mode of acquiring the test tools from the remote warehouse, so that universality and universality of automatic deployment of the test tools of any system are improved.
As an optional implementation manner, before acquiring the target component or the test tool corresponding to the OS, the method further includes:
Determining current configuration information corresponding to the OS;
Determining target configuration information corresponding to the OS according to the FRU information;
And if the current configuration information is the same as the target configuration information, acquiring a target component or a testing tool corresponding to the OS.
After the OS is installed, the embodiment judges whether the current actual configuration meets the configuration requirement or not by comparing the current configuration information with the target configuration information, thereby ensuring that the configuration of the current equipment is available and meets the configuration requirement when the target component or the test tool is installed, and improving the accuracy of automatic deployment.
As an alternative embodiment, the current configuration information and the target configuration information are determined by:
determining current configuration information corresponding to the OS according to the current configuration under the OS;
and determining target configuration information corresponding to the OS according to the fourth field of the FRU information.
According to the embodiment, the current configuration information of the current configuration and the fourth field of the FRU information are automatically grabbed, so that whether the current actual configuration is the same as the target configuration or not is compared, the configuration of the current equipment is convenient to ensure to be available and meet the configuration requirement when the target component or the test tool is installed, and the accuracy of automatic deployment is improved.
In a second aspect, an embodiment of the present invention further provides an electronic device, including a processor and a memory, where the memory is configured to store a program executable by the processor, and the processor is configured to read the program in the memory and execute the following steps:
acquiring FRU information by using a BMC, determining OS information according to the FRU information, and installing an OS corresponding to the OS information;
Acquiring a target component corresponding to the OS according to the FRU information;
and updating the part to be updated under the OS to the target part.
As an alternative embodiment, the processor is specifically further configured to perform:
and acquiring a testing tool corresponding to the OS according to the FRU information, and installing the testing tool.
As an alternative embodiment, after the test tool is installed, the processor is specifically further configured to perform:
Debugging the test tool, and judging whether the test tool is abnormal according to a debugging result;
and if the testing tool is abnormal, outputting abnormal information.
As an alternative embodiment, the processor is specifically configured to perform:
Determining OS information according to the first field of FRU information;
and acquiring the OS corresponding to the OS information from the PXE resource pool, and installing the OS.
As an alternative embodiment, the processor is specifically configured to perform:
determining target component information according to the second field of the FRU information;
and acquiring the target component corresponding to the target component information from a remote warehouse.
As an alternative embodiment, the processor is specifically configured to perform:
determining test tool information according to the third field of the FRU information;
and acquiring the testing tool corresponding to the testing tool information from a remote warehouse.
As an alternative embodiment, before acquiring the target component or the test tool corresponding to the OS, the processor is specifically further configured to perform:
Determining current configuration information corresponding to the OS;
Determining target configuration information corresponding to the OS according to the FRU information;
And if the current configuration information is the same as the target configuration information, acquiring a target component or a testing tool corresponding to the OS.
As an alternative embodiment, the processor is specifically configured to determine the current configuration information and the target configuration information by:
determining current configuration information corresponding to the OS according to the current configuration under the OS;
and determining target configuration information corresponding to the OS according to the fourth field of the FRU information.
In a third aspect, an embodiment of the present invention further provides a system environment deployment apparatus, where the apparatus includes:
The system installation module is used for acquiring FRU information by utilizing the BMC, determining OS information according to the FRU information, and installing an OS corresponding to the OS information;
the component acquisition module is used for acquiring a target component corresponding to the OS according to the FRU information;
and the component updating module is used for updating the component to be updated under the OS into the target component.
As an alternative embodiment, the apparatus further comprises a test mounting module for:
and acquiring a testing tool corresponding to the OS according to the FRU information, and installing the testing tool.
As an alternative embodiment, after the test tool is installed, the apparatus further comprises a debug module for:
Debugging the test tool, and judging whether the test tool is abnormal according to a debugging result;
and if the testing tool is abnormal, outputting abnormal information.
As an alternative embodiment, the system installation module is specifically configured to:
Determining OS information according to the first field of FRU information;
and acquiring the OS corresponding to the OS information from the PXE resource pool, and installing the OS.
As an alternative embodiment, the component acquisition module is specifically configured to:
determining target component information according to the second field of the FRU information;
and acquiring the target component corresponding to the target component information from a remote warehouse.
As an alternative embodiment, the test installation module is specifically configured to:
determining test tool information according to the third field of the FRU information;
and acquiring the testing tool corresponding to the testing tool information from a remote warehouse.
As an optional implementation manner, before acquiring the target component or the test tool corresponding to the OS, the apparatus further includes a judging module specifically configured to:
Determining current configuration information corresponding to the OS;
Determining target configuration information corresponding to the OS according to the FRU information;
And if the current configuration information is the same as the target configuration information, acquiring a target component or a testing tool corresponding to the OS.
As an optional implementation manner, the judging module is specifically configured to determine the current configuration information and the target configuration information by:
determining current configuration information corresponding to the OS according to the current configuration under the OS;
and determining target configuration information corresponding to the OS according to the fourth field of the FRU information.
In a fourth aspect, embodiments of the present invention also provide a computer storage medium having stored thereon a computer program for carrying out the steps of the method according to any one of the first aspects described above when executed by a processor.
In a fifth aspect, the present application provides a computer program product comprising computer program code which, when run on a computer, causes the computer to perform the method of any of the first aspects.
These and other aspects of the application will be more readily apparent from the following description of the embodiments.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments will be briefly described below, it will be apparent that the drawings in the following description are only some embodiments of the present invention, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a system environment deployment method according to an embodiment of the present invention;
FIG. 2 is a flowchart of a method for implementing automatic deployment of a system environment according to an embodiment of the present invention;
FIG. 3 is a flowchart of a system environment deployment method according to an embodiment of the present invention;
fig. 4 is a schematic diagram of an electronic device according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a system environment deployment device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail below with reference to the accompanying drawings, and it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In the embodiment of the invention, the term "and/or" describes the association relation of the association objects, which means that three relations can exist, for example, A and/or B, and can mean that A exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
The application scenario described in the embodiment of the present invention is for more clearly describing the technical solution of the embodiment of the present invention, and does not constitute a limitation on the technical solution provided by the embodiment of the present invention, and as a person of ordinary skill in the art can know that the technical solution provided by the embodiment of the present invention is applicable to similar technical problems as the new application scenario appears. In the description of the present invention, unless otherwise indicated, the meaning of "a plurality" is two or more.
Before describing the system environment deployment method provided by the embodiment of the present application, for convenience of understanding, the following detailed description is first provided for the technical background of the embodiment of the present application.
Most of the current system environment deployment methods are deployed aiming at the system environment of a general operating system, but the general operating system cannot meet the customized system requirements, cannot adapt to the customized system and cannot deploy test environments aiming at the customized system. The general purpose operating system is also not associated with Firmware (FW) versions, driver versions, test tool versions, etc. In the current system environment deployment process, a corresponding execution operating system (executive operating system, OS) is usually installed, after the OS is installed, components such as FW and drivers need to be manually updated, manual intervention is needed, and complete automatic deployment is not realized. When the requirement of the customized OS system environment deployment is met, the specific FW, the driver, the testing tool and other components cannot be automatically adapted according to the customized OS, and the automatic deployment of the customized operating system environment cannot be realized.
It should be noted that, the OS refers to an operating system that a machine (device) runs, is a computer program that manages and controls computer hardware and software resources, is the most basic system software that runs directly on a "bare metal", and any other software or system must run with the support of the operating system. FW is a program written in EPROM (Erasable Programmable Read-Only Memory), EEPROM (ELECTRICALLY ERASABLE PROGRAMMABLE READ ONLY MEMORY), or the like. The firmware refers to a device "driver" stored in the device, through which an operating system can implement operation of a specific machine according to a standard device driver, for example, an optical drive, a recorder, and the like all have internal firmware. Firmware is software that serves the most basic, bottom-level work in a system. In the hardware device, the firmware is a soul of the hardware device, and because some hardware devices have no other software components except the firmware, the firmware also determines the functions and performances of the hardware device.
The current server test environment deployment method does not realize complete automatic deployment. And the general automatic deployment is only aimed at a general tester type, and a test tool deployment method aiming at a customized test environment is not provided. The testing environment is not automatically deployed according to the specific parts FW, drivers and testing tools of different versions which are matched with the specific OS at present.
At present, the industry has no excessive demands on customized OS, most of the customized OS is a universal server, but the universal server is not specific at all and only needs to meet the mode of measurement at any time, so the meaning of automatic deployment is not great, and the automatic deployment needs to be changed after one test is completed. However, there is an increasing need for custom-made systems, which creates a need for automatic deployment of custom-made systems, as long as a certain model or models need to be adapted to the customer system. The previous generic OS cannot be associated with FW, driver version, test tool version of the component. However, the custom OS of the customer needs to be completely adapted to the production environment of the customer, that is, FW, driver-component and complete machine test tool of the custom OS-component need to be strongly bound, so how to satisfy the deployment of the custom test tool and system environment has become a technical problem to be solved at present.
In order to solve the above technical problems, an embodiment of the present application provides a system environment deployment method, which has the core concept that an OS is automatically installed through operation information OS information contained in FRU (Field Replaceable Unit ) information, a target component corresponding to the OS is obtained according to the FRU information, and automatic update of a component to be updated under the OS is performed. And acquiring the corresponding target component and automatically updating after automatically installing the OS by establishing the association between the OS and the target component. That is, after the OS is installed, the driver or firmware corresponding to the OS is automatically updated by association between the OS and the target component (e.g., driver or firmware). The full-automatic deployment of the system environment is realized, the deployment efficiency is improved, and the labor cost is saved.
As shown in fig. 1, the implementation flow of the system environment deployment method provided in this embodiment is as follows:
step 100, acquiring FRU information by utilizing a BMC, determining OS information according to the FRU information, and installing an OS corresponding to the OS information;
in the implementation, after the device is powered on, the BMC is utilized to automatically capture FRU information, wherein the FRU information is information written into a BMC chip in the production and manufacturing process of the device, so that the BMC is utilized to obtain FRU information, OS information including information such as an OS name and an OS version is determined from the FRU information, an OS corresponding to the OS information is automatically obtained, and the OS is automatically installed.
The BMC (Baseboard Management Controller ) in this embodiment is a dedicated microcontroller embedded on the device motherboard, responsible for managing the system and interfaces between the management software and the server platform hardware. The BMC provides management functions for FRUs (Field Replaceable Unit, field replaceable units) including reading and updating FRU data via IPMI (INTELLIGENT PLATFORM MANAGEMENT INTERFACE ) specifications. In this embodiment, the BMC is used to manage and read the FRU information in the device.
FRU refers to equipment components/parts or modules that may be replaced or serviced in the field. The BMC will typically maintain FRU information to accurately identify and locate the parts that need replacement when the equipment needs replacement or repair. The FRU typically contains the physical component information of the device, and a portion of this information may include the VPD (Virtual Product Data, vital product data) of the device, such as manufacturer, model number, serial number, etc. Such a design may help the management system accurately identify and locate components that need replacement when replacement or repair of equipment is required, and provide critical equipment attribute information. For example, the FRU information is replaceable equipment components/parts, such as a motherboard, a power supply, a fan, etc., and detailed information (such as manufacturer, product number, etc.) of the components/parts is usually stored in a nonvolatile memory, such as an EEPROM, and the detailed information of the components can be obtained by reading the FRU information through the BMC, so as to help an administrator to perform fault diagnosis and maintenance.
Optionally, FRU information in this embodiment includes, but is not limited to, any one or more of model Number, serial Number (SN), configuration information, OS information, FW information, drive information, test tool information, and the like.
The SN is a check-in number, a sequence number, a number (of an equipment file, etc.), etc., and is unique and used for recording an identification code of a product. An SN is typically a set of characters consisting of numbers, letters, or a combination of both, that are used to identify and track individual items or devices. The SN is typically assigned by the manufacturer, and is unique for each product and can be used to verify the authenticity of the product and to provide after-market services.
Configuration information includes, but is not limited to, hard disk information, memory information, network card information, and the like. The hard disk information comprises, but is not limited to, hard disk size, hard disk use condition, available hard disk size and the like, and the memory information comprises, but is not limited to, memory size, memory use condition, available memory size and the like.
The OS information comprises, but is not limited to, at least one or more of an OS name, an OS version, an OS manufacturer, configuration information corresponding to the OS, an application scene corresponding to the OS, FW information corresponding to the OS, driving information corresponding to the OS, and testing tool information corresponding to the OS, wherein the FW information comprises, but is not limited to, at least one or more of an FW name, an FW version, an FW manufacturer and an FW number, the driving information comprises, but is not limited to, at least one or more of a driving name, a driving version, a driving manufacturer and a driving number, and the testing tool information comprises, but is not limited to, at least one or more of a testing tool name, a testing tool version, a testing tool manufacturer and a testing tool number.
In some embodiments, the FRU information in this embodiment includes, but is not limited to, a first field, a second field, a third field, a fourth field, etc., with different fields being used to represent different information. The first field is used for representing OS information, the second field is used for representing target component information, the target component information comprises but is not limited to firmware, drive and the like, the third field is used for representing test tool information, and the fourth field is used for representing configuration information, wherein the configuration information comprises but is not limited to existing memory information, hard disk information, network card information and the like.
The FRU information can be expressed as a string of numbers, a string of numbers plus text description, or English, i.e. any one field in the FRU information can be one form or combination of a plurality of forms of numbers, text description, english, etc., and the information contained in each field represents one type of information of the device. The FRU information may indicate that all information of the device is stored. For example, FRU information is represented in a series of numbers, such as 10101010, that represent the version of the OS that the device needs to install, such as a first number representing a linux or windows system, a second number representing a release version such as centos (one release version of linux) or red hat system, a third number representing a version of the system under the same manufacturer, such as a seventh or eighth generation system, a fourth number representing a small version number, a fifth number representing kernel version information, and so on, the more numbers in FRU information representing the more definitive version of the OS that is used, the theoretically this degree of detail is not limited. Similarly, on the customized project, the client can provide the OS used by the manufacturer, and usually, the OS can record information such as what system version and what kernel version are recorded more accurately, so that the information of the OS can be read more accurately by reading the FRU information, and the suitability and accuracy of the subsequent components/assemblies can be ensured. The embodiment completely meets the reading requirement of FRU information in terms of data length reading.
In some embodiments, the present embodiment determines OS information according to FRU information and installs an OS corresponding to the OS information by:
And acquiring the OS corresponding to the OS information from the PXE resource pool, and installing the OS.
In the implementation, according to a preset reading rule, a BMC is utilized to read a first field of FRU information, the first field is converted into a language which can be identified by a script, OS information such as an OS version and an OS manufacturer is determined according to the first field, after the OS information is determined, an OS corresponding to the OS information is obtained from a PXE resource pool, for example, the OS which is the same as the OS manufacturer and the OS version is downloaded from the PXE resource pool, and the OS is automatically installed.
It should be noted that the pre-boot execution environment (Preboot eXecution Environment, PXE) is a network boot technology that allows a computer to obtain an operating system image or boot loader from a server through a network during a boot process, instead of booting from a local hard disk or optical drive. PXE technology was developed by Intel to provide a standardized way to achieve operating system startup without local storage devices. The network mode of working in Client/Server, support workstation download the image from the remote Server through the network, and support and start the operating system through the network from this, in the start-up process, the terminal asks the Server to distribute the IP address, download a start-up software package to the local memory to carry out with TFTP (TRIVIAL FILE TRANSFER Protocol) or MTFTP (multi-cast TRIVIAL FILE TRANSFER Protocol), finish the terminal (Client) basic software setting by this start-up software package, thus guide the terminal operating system installed in the Server in advance. PXE can boot a variety of operating systems.
The PXE resource pool is a network resource pool constructed by using the PXE (pre-boot execution environment) technology and is mainly used for realizing remote network starting and operating system installation of a computer. The PXE resource pool typically includes the components of a PXE server responsible for providing boot images and installation files, and typically requires configuration of DHCP (Dynamic Host Configuration Protocol ) and TFTP services in order to assign IP (Internet Protocol ) addresses to the PXE clients and transfer the boot files. And the PXE client is a network card supporting the PXE technology and can download the boot image from the server through a PXE protocol during starting. Network environment-ensure that the PXE client can access the PXE server over the network. The working principle of the PXE resource pool is that when the computer is started, the BIOS (Basic Input Output System ) calls the PXE client into the internal memory to execute, the PXE client obtains the IP address through the DHCP server, and then downloads the starting mirror image through the TFTP server. The downloaded boot image contains a small operating system environment which can further download a complete operating system installation package through a network to realize unattended installation.
Optionally, the PXE resource pool in this embodiment is used to store a general OS and OS customized by different manufacturers, after determining, according to the first field, OS information required by the device, whether an OS corresponding to the OS information exists is searched from the PXE resource pool, and if so, the OS corresponding to the OS information is directly downloaded from the PXE resource pool.
Step 101, acquiring a target component corresponding to the OS according to the FRU information;
In implementation, after the OS is acquired and automatically installed, a target component corresponding to the currently installed OS may also be acquired according to the FRU information, where the target component includes, but is not limited to, FW, driver, and the like.
In some embodiments, the present embodiment obtains the target component corresponding to the OS according to the FRU information by:
and acquiring the target component corresponding to the target component information from a remote warehouse.
In implementation, according to a preset reading rule, the BMC is utilized to read a second field of FRU information, the second field is converted into a language which can be recognized by the script itself, and target component information is determined according to the second field, including but not limited to determining firmware information, driving information and the like according to the second field. And downloading firmware corresponding to the firmware information and a driver corresponding to the driving information from a remote warehouse. Wherein the firmware information includes, but is not limited to, a firmware name, a firmware vendor, a firmware version, etc., and the driver information includes, but is not limited to, a driver name, a driver vendor, a driver version, etc.
Alternatively, the remote repository in this embodiment may be an FTP (FILE TRANSFER Protocol) resource pool, where FW, driver, test tool, etc. required by a general-purpose OS, and FW, driver, test tool, etc. required by an OS customized by different vendors are stored. The components in the remote repository may be invoked for automated deployment if desired. FTP is a widely used standard protocol for file transfer in a network, and is used as a basic tool in network communication, and allows a user to interact with a server through client software to realize uploading, downloading and other file operations of a file. FTP works at the application layer of the OSI (Open System Interconnect, open systems interconnection) model, typically using TCP (TransmissionControl Protocol ) as its transmission protocol, ensuring the reliability and the sequency of data transmission.
It should be noted that the remote repository refers to an internet-based code hosting platform, which allows developers to host files in a local version library to a remote server for storage, so that multiple developers can cooperatively develop, share codes, backup codes, and the like. Common remote warehouse platforms include GitHub, gitLab, bitbucket, etc. FTP resource pool is a resource pool for managing FTP (file transfer protocol) connections, the main objective of which is to improve the performance and efficiency of applications. Through the FTP resource pool, the application program can efficiently manage and reuse the FTP connection, and the time for connection establishment and disconnection is reduced, so that the overall performance is improved. The FTP resource pool enables multiplexing of FTP connections by maintaining a pool of connections. When an application needs to connect to the FTP server, it will acquire a free connection from the resource pool, and return the connection to the resource pool after use, rather than immediately close. In this way, the overhead of connection setup and disconnection is amortized over multiple requests, significantly improving efficiency.
The system environment deployment method provided in this embodiment may be implemented by a script, where the script may be written according to python, and in combination with an ipmitool (INTELLIGENT PLATFORM MANAGEMENT INTERFACE tool ), an ipmitool FRU command (which is a command line tool for acquiring hardware information) is used, and according to the read FRU information, a corresponding OS, FW, driver, test tool, etc. are installed in a targeted manner.
Optionally, the target components in this embodiment include, but are not limited to, at least one or more of FW, drive.
In this embodiment, the correspondence between the OS and the FW, the driver, and the test tool required by the OS is established, and after the OS is installed, the FW, the driver, and the test tool required by the OS are automatically installed by acquiring the FW, the driver, and the test tool required by the OS. The automated deployment of the system environment may be performed for any custom OS, generic OS. The accuracy of automatic deployment can be improved, and the efficiency and universality of automatic deployment are improved.
And 102, updating the part to be updated under the OS to the target part.
Optionally, the to-be-updated component in the embodiment includes, but is not limited to, firmware, a driver, and the like, where the version of the to-be-updated component is different from the version of the target component, and the to-be-updated component is updated to be the same type of target component, that is, the firmware in the to-be-updated component is updated to be the firmware in the target component, and the driver in the to-be-updated component is updated to be the driver in the target component.
It should be noted that, during the process of installing the OS, the OS itself already has a component to be updated (such as firmware to be updated, a driver, etc.), but the version of the component to be updated may be different from the version of the target component required by the OS, and is generally configured with the lowest version, so after the target component required by the currently installed OS is obtained, the low-version component to be updated existing under the currently installed OS is updated to the high-version target component, for example, the low-version firmware under the currently installed OS is updated to the high-version firmware, and the low-version driver under the currently installed OS is updated to the high-version driver. So that the target component is more adapted to the current OS.
In some embodiments, the embodiment may further obtain a test tool corresponding to the OS according to the FRU information, and install the test tool.
In implementation, after the OS is automatically installed and the target component corresponding to the OS is automatically updated, the test tool adapted to the OS may also be automatically installed.
In some embodiments, the test tool corresponding to the OS is obtained according to the FRU information by:
And acquiring the testing tool corresponding to the testing tool information from a remote warehouse.
In the implementation, according to a preset reading rule, the third field of the FRU information is read by the BMC, the third field is converted into a language which can be identified by the script itself, the test tool information is determined according to the third field, the test tool information comprises information such as a test tool name, a test tool manufacturer, a test tool version and the like, and a test tool corresponding to the test tool information is downloaded from a remote warehouse.
In some embodiments, after installing the OS corresponding to the OS information, before acquiring the target component corresponding to the OS, the present embodiment may further confirm the current configuration of the device, as shown in the following specific details:
Determining current configuration information corresponding to the OS, determining target configuration information corresponding to the OS according to the FRU information, and acquiring a target component corresponding to the OS if the current configuration information is the same as the target configuration information.
Optionally, the target component includes, but is not limited to, target firmware, target drivers, and the like.
In some embodiments, the current configuration information and the target configuration information are determined by:
And determining the target configuration information corresponding to the OS according to a fourth field of the FRU information.
In implementation, after installing the OS, in order to verify whether the current actual configuration under the OS is the target configuration corresponding to the OS, the present embodiment first grabs the current configuration information under the OS, where the current configuration includes, but is not limited to, the current hard disk, the current memory, the current network card, and the like. The current configuration information comprises, but is not limited to, current hard disk information, current memory information, current network card information and the like, then target configuration information corresponding to the OS is determined according to the FRU information, specifically, a fourth field of the FRU information is read by the BMC, the fourth field is converted into a language which can be identified by a script, and the target configuration information, namely ideal configuration information corresponding to the current OS, is determined according to the fourth field. One of the current configuration corresponds to one of the target configuration, and one of the current configuration information corresponds to one of the target configuration information. The target configuration includes, but is not limited to, a target hard disk, a target memory, a target network card, etc. The target configuration information includes, but is not limited to, target hard disk information, target memory information, target network card information, and the like.
After the current configuration information and the target configuration information are obtained, comparing whether the current configuration information and the target configuration information are the same, if the current hard disk information and the target hard disk information are the same, the current memory information and the target memory information are the same, and if the current network card information and the target network card information are the same, obtaining a target component corresponding to the OS, namely obtaining target firmware, target drive and the like corresponding to the current OS, thereby automatically installing the target firmware and the target drive.
In some embodiments, after installing the OS corresponding to the OS information, before acquiring the test tool corresponding to the OS, the present embodiment may further confirm the current configuration of the device, as shown in the following specific details:
Determining current configuration information corresponding to the OS, determining target configuration information corresponding to the OS according to the FRU information, and acquiring a test tool corresponding to the OS if the current configuration information is the same as the target configuration information.
In implementation, after installing the OS, in order to verify whether the current actual configuration under the OS is the target configuration corresponding to the OS, the present embodiment first grabs the current configuration information under the OS, where the current configuration includes, but is not limited to, the current hard disk, the current memory, the current network card, and the like. The current configuration information comprises, but is not limited to, current hard disk information, current memory information, current network card information and the like, then target configuration information corresponding to the OS is determined according to the FRU information, specifically, a fourth field of the FRU information is read by the BMC, the fourth field is converted into a language which can be identified by a script, and the target configuration information, namely ideal configuration information corresponding to the current OS, is determined according to the fourth field. One of the current configuration corresponds to one of the target configuration, and one of the current configuration information corresponds to one of the target configuration information. The target configuration includes, but is not limited to, a target hard disk, a target memory, a target network card, etc. The target configuration information includes, but is not limited to, target hard disk information, target memory information, target network card information, and the like.
After the current configuration information and the target configuration information are obtained, comparing whether the current configuration information and the target configuration information are the same, and if the current hard disk information and the target hard disk information are the same, the current memory information and the target memory information are the same, and the current network card information and the target network card information are the same, obtaining a target component corresponding to the OS, namely obtaining a test tool corresponding to the current OS, thereby automatically installing the test tool.
In some embodiments, after the test tool is installed, the method further comprises:
and debugging the test tool, judging whether the test tool is abnormal according to a debugging result, and outputting abnormal information if the test tool is abnormal.
In implementation, after the test tool is installed, the test tool can be automatically debugged, whether the test tool can work normally or not is verified, and when the test tool is abnormal, abnormal information is output and used for prompting a user to install manually.
It should be noted that the test tool in this embodiment includes, but is not limited to, at least one of a hardware test tool and a software test tool. The test tool is used for debugging and testing the software and/or hardware of the equipment. Optionally, the test tools in this embodiment include, but are not limited to, various pressure test software, cycle scripts, FIO, etc. The FIO refers to a FIO (Flexible Input/Output) on a server, which is a tool based on a command line and is used for performing performance test and load test on a storage device. Through FIO, various read-write scenes and load modes can be simulated, and the performance and stability of the storage device can be evaluated. The FIO can create a plurality of threads on the server to concurrently execute the I/O operation, and parameters such as the concurrency number, the queue depth, the I/O size, the operation mode and the like can be flexibly set, so that the load conditions in various practical application scenes can be simulated. In the performance test, the FIO can be used for testing and evaluating performance indexes such as random read-write, sequential read-write, random mixed read-write and the like of the storage device. In addition, the FIO may also output detailed test reports and logs to help the user analyze performance bottlenecks and potential problems of the storage device. In summary, FIO is a powerful performance testing tool that can help users evaluate and optimize the storage performance of a server.
It should be noted that, the system environment deployment method in this embodiment is applied to a device, and the device may be a server or other types of electronic devices, which is not limited in this embodiment too.
The system environment deployment method in this embodiment may be implemented through a script, and automatically read FRU information through the script, automatically acquire OS information, and acquire a corresponding OS from a PXE resource pool to perform automatic installation, and then acquire a target component and a test tool corresponding to the OS, and automatically install the target component and the test tool.
Optionally, the system environment deployment method in this embodiment may perform batch installation on a plurality of devices, read an OS in a PXE resource pool and a target component and a test tool in a remote repository through one script, and after the plurality of devices are powered on simultaneously, obtain FRU information of each device in parallel through the script, obtain a corresponding OS, a target component and a test tool from the PXE resource pool, and perform automatic installation. Therefore, automatic deployment of a batch system environment of a large number of devices is realized.
According to the embodiment, when the current tester is unfamiliar with information such as FW, drive and test tool used by the customized OS, manual installation is not needed, FRU information can be directly obtained through the BMC, the customized OS, the corresponding FW, drive and test tool and the like are determined according to the FRU information, time spent on equipment configuration is saved, labor cost is reduced, and deployment efficiency is effectively improved. In addition, when a large amount of test tools are required to be replaced for some reason, and information of parts FW, drivers and the like is updated, only different test tools FW, drivers and the like are required to be acquired, and specific configuration of each item is not required to be confirmed, so that manpower and material resources are greatly saved, and only one system installation process is consumed.
The embodiment not only can install the designated operating system according to the requirement, but also can determine the configuration of the system after the corresponding system is installed, confirm the drive, and update the FW, the drive and the like corresponding to the system. After the system version, FW version and driving version required by the customization are confirmed, the testing tool version required by the customization client can be installed. Batch installation of the operating system, components FW, drivers, and test tools can also be performed. The labor cost is greatly saved. With this system, no option is required and no interaction is required during batch installation. The FW, the driver, the test tool corresponding to the operating system required by different clients are different, and the system environment deployment method provided by the embodiment supports full automation of environment deployment by only selecting the corresponding Operating System (OS), installing the corresponding system version, correspondingly installing the corresponding FW, driver, test tool and the like, no matter which machine type the device is.
As shown in fig. 2, the embodiment provides a method for automatically deploying a system environment, and the specific implementation flow of the method is as follows:
Step 200, powering up and starting up the equipment;
Optionally, the device comprises a server.
Step 201, reading OS information from a PXE resource pool, reading target component information and test tool information from a remote warehouse, and recording the OS information, the target component information and the test tool information;
Step 202, obtaining FRU information by utilizing BMC;
Step 203, determining OS information according to the first field of the FRU information, determining target component information according to the second field of the FRU information, and determining test tool information according to the third field of the FRU information;
204a, determining that the OS information exists in a PXE resource pool from the recorded OS information, acquiring an OS corresponding to the OS information from the PXE resource pool, and automatically installing the OS;
204b, if the OS information is not found from the recorded OS information, the OS is failed to be installed;
step 205, capturing current configuration information corresponding to an OS, and determining target configuration information corresponding to the OS according to a fourth field of the FRU information;
step 206, judging whether the current configuration information and the target configuration information are the same, if yes, executing step 207, otherwise, executing step 213;
Step 207, determining that the target component information and the test tool information exist in the remote warehouse from the recorded target component information and test tool information, and acquiring target components and test tools respectively corresponding to the target component information and the test tool information from the remote warehouse;
step 208, automatically installing target components and test tools;
step 209, judging whether the installation is completed, if yes, executing step 210, otherwise, executing step 212;
step 210, screen printing the version information of the current FW, driving and testing tools;
step 211, displaying that installation is abnormal, and printing information such as BMC, OS and the like on a screen.
Step 212, displaying installation failure, and printing error reporting information on a screen;
step 213, prompting the user for different configuration information.
For example, the user is prompted that the hard disks are different, and the screen outputs configuration information of the hard disks which are not consistent in detail for manual debugging. If any of FW, drive and test tools have not been successfully installed multiple times, the screen prints the error message and prompts the user for manual installation.
The embodiment provides a system for automatically deploying a customized test tool based on a PXE resource pool and an FTP resource pool. The method not only can install the client-designated operating system on the server according to the user requirements, but also can determine the FW of the configuration of the system after the corresponding system is installed, confirm the drive, and update the corresponding FW and drive. After the system version required by customization is confirmed, the FW and the driver of the tested component can be provided with the version of the testing tool required by the customization client, such as testing tools like FIO, etc., cycle script, etc. Not only can the required designated operating system be installed, the required components FW and the required test tools be driven, namely after a required server is provided, all requirements can be installed by the method provided by the embodiment, but also the batch installation of the operating system, the batch installation of the components FW and the drive and the test tools can be carried out by the method. The labor cost is greatly saved. When the method provided by the embodiment is used for batch installation, no selection is needed, parts FW, drivers and test tool versions corresponding to the operating systems needed by different clients are different, no matter which type of server to be tested is, the corresponding operating system version is installed as long as FRU information is read, and the FW, the drivers and the test tools corresponding to the operating systems are correspondingly installed. The labor can be greatly saved, and the testing efficiency of the whole testing period is improved.
As shown in fig. 3, this embodiment further provides an implementation flow of a system environment deployment method, as follows:
step 300, obtaining FRU information by utilizing BMC;
Step 301, determining OS information according to a first field of FRU information;
step 302, acquiring an OS corresponding to the OS information from a PXE resource pool, and installing the OS;
Step 303, determining current configuration information corresponding to the OS according to the current configuration under the OS, and determining target configuration information corresponding to the OS according to a fourth field of FRU information;
Step 304, judging whether the current configuration information and the target configuration information are the same, if yes, executing step 305, otherwise, executing step 311;
step 305, determining firmware information and driving information according to the second field of the FRU information;
Step 306, obtaining firmware corresponding to the firmware information and a driver corresponding to the driving information from a remote warehouse;
step 307, updating the current firmware under the OS to the firmware corresponding to the firmware information, and updating the current driver to the driver corresponding to the driver information;
step 308, determining test tool information according to the third field of the FRU information;
Step 309, obtaining a test tool corresponding to the test tool information from a remote warehouse, and installing the test tool;
step 310, debugging the test tool, and judging whether the test tool is abnormal according to a debugging result;
step 311, outputting different configuration information.
The embodiment can automatically install FW, drive, test tools and the like of the OS and required components according to the read FRU information. And the machine SN is not required to be arranged in order, and the automatic deployment is not required to be carried out. Since the FW, the driver, and the test tool of the component are determined by the FRU information in this embodiment, that is, "upstream", only the FW, the driver, and the test tool of the component need to be stored in the remote repository, and the OS is stored in the PXE resource pool, it is not necessary to expend effort to manually select which component needs to update the driver, which component needs to update the FW, or which server needs to use which test tool. The labor cost can be greatly saved, and the efficiency and the universality of automatic deployment are improved.
Based on the same inventive concept, the embodiment of the present invention further provides an electronic device, and because the electronic device is the electronic device in the method in the embodiment of the present invention, and the principle of the electronic device for solving the problem is similar to that of the method, implementation of the electronic device may refer to implementation of the method, and repeated descriptions are omitted.
As shown in fig. 4, the electronic device comprises a processor 400 and a memory 401, the memory 401 is used for storing a program executable by the processor 400, and the processor 400 is used for reading the program in the memory 401 and executing the following steps:
acquiring FRU information by using a BMC, determining OS information according to the FRU information, and installing an OS corresponding to the OS information;
Acquiring a target component corresponding to the OS according to the FRU information;
and updating the part to be updated under the OS to the target part.
As an alternative embodiment, the processor 400 is specifically further configured to perform:
and acquiring a testing tool corresponding to the OS according to the FRU information, and installing the testing tool.
As an alternative embodiment, after the test tool is installed, the processor 400 is specifically further configured to perform:
Debugging the test tool, and judging whether the test tool is abnormal according to a debugging result;
and if the testing tool is abnormal, outputting abnormal information.
As an alternative embodiment, the processor 400 is specifically configured to perform:
Determining OS information according to the first field of FRU information;
and acquiring the OS corresponding to the OS information from the PXE resource pool, and installing the OS.
As an alternative embodiment, the processor 400 is specifically configured to perform:
determining target component information according to the second field of the FRU information;
and acquiring the target component corresponding to the target component information from a remote warehouse.
As an alternative embodiment, the processor 400 is specifically configured to perform:
determining test tool information according to the third field of the FRU information;
and acquiring the testing tool corresponding to the testing tool information from a remote warehouse.
As an alternative embodiment, before acquiring the target component or the test tool corresponding to the OS, the processor 400 is specifically further configured to perform:
Determining current configuration information corresponding to the OS;
Determining target configuration information corresponding to the OS according to the FRU information;
And if the current configuration information is the same as the target configuration information, acquiring a target component or a testing tool corresponding to the OS.
As an alternative embodiment, the processor 400 is specifically configured to determine the current configuration information and the target configuration information by:
determining current configuration information corresponding to the OS according to the current configuration under the OS;
and determining target configuration information corresponding to the OS according to the fourth field of the FRU information.
Based on the same inventive concept, the embodiment of the present invention further provides a system environment deployment device, and since the device is the device in the method in the embodiment of the present invention, and the principle of the device for solving the problem is similar to that of the method, the implementation of the device may refer to the implementation of the method, and the repetition is omitted.
As shown in fig. 5, the apparatus includes:
the system installation module 500 is configured to obtain FRU information by using a BMC, determine OS information according to the FRU information, and install an OS corresponding to the OS information;
A component obtaining module 501, configured to obtain a target component corresponding to the OS according to the FRU information;
And the component updating module 502 is configured to update the component to be updated under the OS to the target component.
As an alternative embodiment, the apparatus further comprises a test mounting module for:
and acquiring a testing tool corresponding to the OS according to the FRU information, and installing the testing tool.
As an alternative embodiment, after the test tool is installed, the apparatus further comprises a debug module for:
Debugging the test tool, and judging whether the test tool is abnormal according to a debugging result;
and if the testing tool is abnormal, outputting abnormal information.
As an alternative embodiment, the system installation module 500 is specifically configured to:
Determining OS information according to the first field of FRU information;
and acquiring the OS corresponding to the OS information from the PXE resource pool, and installing the OS.
As an alternative embodiment, the component acquisition module 501 is specifically configured to:
determining target component information according to the second field of the FRU information;
and acquiring the target component corresponding to the target component information from a remote warehouse.
As an alternative embodiment, the test installation module is specifically configured to:
determining test tool information according to the third field of the FRU information;
and acquiring the testing tool corresponding to the testing tool information from a remote warehouse.
As an optional implementation manner, before acquiring the target component or the test tool corresponding to the OS, the apparatus further includes a judging module specifically configured to:
Determining current configuration information corresponding to the OS;
Determining target configuration information corresponding to the OS according to the FRU information;
And if the current configuration information is the same as the target configuration information, acquiring a target component or a testing tool corresponding to the OS.
As an optional implementation manner, the judging module is specifically configured to determine the current configuration information and the target configuration information by:
determining current configuration information corresponding to the OS according to the current configuration under the OS;
and determining target configuration information corresponding to the OS according to the fourth field of the FRU information.
Based on the same inventive concept, the disclosed embodiments provide a computer storage medium including computer program code which, when run on a computer, causes the computer to perform a system environment deployment method as any one of the previously discussed. Since the principle of the solution of the problem of the computer storage medium is similar to that of the deployment method of the system environment, the implementation of the computer storage medium can refer to the implementation of the method, and the repetition is omitted.
In a specific implementation, the computer storage medium may include a Universal Serial Bus (USB) flash drive (Universal Serial Bus FLASH DRIVE), a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic or optical disk, and other various storage media that may store program code.
Based on the same inventive concept, the disclosed embodiments also provide a computer program product comprising computer program code which, when run on a computer, causes the computer to perform a system environment deployment method as any of the preceding discussion. Since the principle of the solution of the problem of the computer program product is similar to that of the deployment method of the system environment, the implementation of the computer program product can refer to the implementation of the method, and the repetition is omitted.
The computer program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of a readable storage medium include an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (10)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411657497.4A CN119597310A (en) | 2024-11-19 | 2024-11-19 | System environment deployment method and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411657497.4A CN119597310A (en) | 2024-11-19 | 2024-11-19 | System environment deployment method and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN119597310A true CN119597310A (en) | 2025-03-11 |
Family
ID=94833604
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202411657497.4A Pending CN119597310A (en) | 2024-11-19 | 2024-11-19 | System environment deployment method and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN119597310A (en) |
-
2024
- 2024-11-19 CN CN202411657497.4A patent/CN119597310A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6550021B1 (en) | Internet-implemented method supporting component repair services | |
| US6959433B1 (en) | Data processing system, method, and program for automatically testing software applications | |
| EP1691276B1 (en) | System and method for verifying compatiblity of computer equipment with a software product | |
| US7392148B2 (en) | Heterogeneous multipath path network test system | |
| US8352916B2 (en) | Facilitating the automated testing of daily builds of software | |
| US9294296B2 (en) | Automated test execution in a shared virtualized resource pool | |
| US9747192B2 (en) | Automated operating system installation on multiple drives | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| CN113505073B (en) | Performance test method, device, equipment and medium of database | |
| CN101420326A (en) | Method, system and apparatus for implementing failure restoration and data backup | |
| US9542304B1 (en) | Automated operating system installation | |
| JP2016194891A (en) | Method of updating software component, computer system, and memory apparatus | |
| CN106897223A (en) | A kind of software kit delivery method and device based on continuous integrating | |
| US11733979B2 (en) | System for automatically generating customer specific data center application program interfaces | |
| CN111694604A (en) | Method, device and equipment for installing drivers in batches and machine-readable storage medium | |
| CN107544879A (en) | Diagnostic method, device and the machinable medium of server | |
| CN115913913B (en) | Method and device for locating fault of network card pre-start execution environment function | |
| US20060168564A1 (en) | Integrated chaining process for continuous software integration and validation | |
| CN119597310A (en) | System environment deployment method and electronic equipment | |
| CN116244186A (en) | Operating system test management method and device and computing equipment | |
| CN110532151A (en) | A kind of automatic operation method of monitoring instrument, device, equipment and storage medium | |
| CN116541270A (en) | Method and device for testing adaptation verification of operating system | |
| CN116302543A (en) | Continuous integration job processing method, device, equipment and storage medium | |
| CN109245920B (en) | Automatic switch configuration method and device, switch and storage medium | |
| US10216525B1 (en) | Virtual disk carousel |
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 |